DEV Community

Riley Calhoun
Riley Calhoun

Posted on

I got tired of checking GPU cloud pricing pages by hand, so I built a price index API

Every time I needed to rent a GPU, the workflow was the same: open six provider tabs, squint at pricing pages that all structure their numbers differently, and try to remember whether that H100 price was spot, on-demand, or a 3-year contract rate buried in a footnote.

So I built the thing I wanted: a price index that normalizes GPU cloud pricing into one dataset, where every row says what kind of price it is and links back to the provider page it came from.

Some of what the data shows right now (it refreshes hourly):

GPU Cheapest $/hr Provider Price type
H100 1.37 Vast.ai spot
H200 2.62 CoreWeave spot
A100 1.15 Paperspace 3-yr contract
L40S 0.79 RunPod community cloud
B200 4.26 CoreWeave spot

The price-type column is the part I care about most. A $1.15 A100 sounds cheaper than a $1.37 H100 until you notice one is a 3-year contract and the other is spot. Most comparison content flattens that away; the index doesn't.

The API is live on RapidAPI as GPU Index — there's a free tier (1,000 requests/month) if you want to poke at it: https://rapidapi.com/vangogh/api/gpu-index1

Endpoints are simple: /prices for the full normalized dataset (filter by GPU family, provider, or price type), /summary for the cheapest price per family, /gpus and /providers for what's covered and how fresh each source is.

While I was in there, I built the same pattern for a few other datasets I kept checking by hand:

All of them have the same free tier, and every price row in the indexes carries its source URL so you can check my work. If you're building a router, a cost dashboard, or anything that picks compute or models programmatically, I'd rather you call an API than maintain your own scrapers — that was certainly true for me.

Feedback welcome: what provider or GPU family am I missing?

Top comments (0)