Serverless GPU

Manual for agents, automated clients, and developers using Cloud GPU Prices.

Agent and data access manual

What this catalog can answer

The accepted catalog is designed to answer which providers and GPU products are available, how their published prices are structured, which complete prices are comparable, how recently evidence was verified, and what official evidence exists for EU/EEA compute claims.

It does not currently establish which service is fastest. Price, hardware labels, and provider claims are not substitutes for workload-specific benchmark measurements.

Interpretation rules

  1. Only variants with comparison.total_price_eligible=true are complete prices that may be ranked as totals. Additive CPU, memory, and GPU meters remain separate components.
  2. Geography uses four truth states: yes, no, unknown, and conflicting. Unknown means that accepted evidence does not establish the answer; it never means no.
  3. Compare monetary totals only within one currency. The API requires exactly one currency when sorting by comparable hourly price.
  4. A provider-selected pool lists possible hardware but does not guarantee a specific GPU for a request. Do not present it as a fixed-GPU offer.
  5. Prefer effective_amount_picos for the applicable commercial variant and retain the published amount, unit, quantity, source URL, warnings, and verification timestamp when citing it.

Representations

Human and browser-agent HTML
/pricing accepts the same filters and renders ordinary links, forms, tables, and evidence.
Exact JSON
/api/v1/offerings is the authoritative machine representation. Integer quantities and pico-unit monetary values are decimal strings.
Context-efficient Markdown
/pricing.md gives a readable result table plus evidence notes. Use JSON when exact structure matters.
Contract
/api/v1/openapi.json describes the query parameters and response schema.

Querying

Filters use normal URL query parameters. Repeat provider, gpu, category, hardware_selection, pricing_structure, freshness, or currency to match any of several values. Unknown parameters, unsupported values, and unsafe comparison requests return HTTP 400; nothing is silently ignored.

Common filters:

  • provider, gpu, category
  • hardware_selection, pricing_structure, total_price
  • eu_compute, eu_constrained, eu_only
  • freshness, currency, q
  • sort, order, limit, cursor

Examples

Pagination and caching

Results are paginated by offering, with commercial variants nested beneath each offering. Follow links.next or reuse pagination.next_cursor without changing the other query parameters. Cursors are deliberately bound to the normalized query. JSON responses expose ETag and Last-Modified headers for conditional requests.

Evidence, citations, and change

Cite the catalog result together with the offering's source_url and provenance.verified_at. New providers and offerings can appear without changing the endpoint. Fields may be added compatibly within API v1; consumers should ignore fields they do not understand. Breaking changes will use a new versioned API path.

Additional product categories, model-as-a-service pricing, and benchmark measurements may be added later. Their commercial units and comparison rules will remain explicit rather than being forced into GPU-hour semantics.