Skip to main content
GET
/
v1
/
catalog
/
listings
curl "https://gpuoutlet.ai/v1/catalog/listings?model=H100&minVramGb=80&maxPricePerHourCents=300" \
  --cookie "sid=$SID"

{
  "listings": [
    {
      "id": "lst_01H...",
      "model": "H100_SXM_80GB",
      "family": "h100-80gb",
      "vramGb": 80,
      "gpuCount": 1,
      "pricePerHourCents": 280,
      "providerCode": "vast",
      "region": "US-East",
      "regionCode": "US",
      "interconnect": "NVLink"
    }
  ],
  "nextCursor": "eyJsYXN0SWQiOiJsc3RfMDFILi4ifQ=="
}
​
model
string
Filter to a specific canonical model code, e.g. RTX_4090, H100_SXM_80GB, B200. Combine with minVramGb to narrow further.
​
minVramGb
number
Minimum VRAM in GB. Excludes e.g. 40GB A100 variants when set to 80.
​
gpuCount
number
Filter to listings offering exactly this GPU count: 1, 2, 4, 8.
​
region
string
ISO country code (US, DE, JP, etc.) or one of us, eu, apac to filter by broader region.
​
maxPricePerHourCents
number
Cap on hourly rate. Listings above this aren’t returned.
​
cursor
string
Pagination cursor from a previous response’s nextCursor.
​
pageSize
number
default:"50"
How many listings per response. Max 200.
​
listings
array
Array of listing objects, sorted cheapest-first.
​
nextCursor
string | null
Pass to the next request as ?cursor=…. null when there are no more results.
curl "https://gpuoutlet.ai/v1/catalog/listings?model=H100&minVramGb=80&maxPricePerHourCents=300" \
  --cookie "sid=$SID"

{
  "listings": [
    {
      "id": "lst_01H...",
      "model": "H100_SXM_80GB",
      "family": "h100-80gb",
      "vramGb": 80,
      "gpuCount": 1,
      "pricePerHourCents": 280,
      "providerCode": "vast",
      "region": "US-East",
      "regionCode": "US",
      "interconnect": "NVLink"
    }
  ],
  "nextCursor": "eyJsYXN0SWQiOiJsc3RfMDFILi4ifQ=="
}

​
What’s a “listing”?

A single offering from one upstream provider: “this provider, in this region, has 1× H100 80GB SXM available at $2.80/hr”. Multiple listings can exist for the same model — that’s how the dashboard finds the cheapest H100 across all providers. When you call POST /v1/rentals, the server picks the cheapest live listing matching your spec automatically. You don’t usually need to call /listings directly — it’s there for clients that want to display the breakdown.

​
Display-price override

The dashboard’s Create page uses display-only prices (e.g. RTX 4090 is shown at 0.65/hrevenifthecheapestlivelistingis0.65/hr even if the cheapest live listing is 0.71/hr). This is a UI-layer override that does NOT affect the actual rental cost — when you launch, the backend bills at the real listing rate. The override exists during early launch while we hand-pick promotional pricing. API consumers get the real pricePerHourCents. Use that for budgeting / scripts.