> ## Documentation Index
> Fetch the complete documentation index at: https://docs.compute-desk.com/llms.txt
> Use this file to discover all available pages before exploring further.
# GPU Rental Prices: As Of
> Vendor prices for renting GPU compute, in USD per GPU-hour.
Returns the same view as `/latest`, as it stood at the moment you pass in `at`. Give it a date or a full timestamp; a plain date means the end of that day.
If nothing was published at that exact moment — a weekend, a holiday, a gap in a vendor's feed — you get the most recent value before it, rather than an empty response.
A date earlier than your licensed history is rejected rather than quietly moved forward, so you are never handed an answer to a different question.
**Every query must name an anchor**: one of `vendor`, `gpu_canonical_name`, `gpu_search`,
`base_product_key` or `product_key`. Without one the request is refused with `400 missing_anchor`.
`region` and `contract_type` narrow an anchored query; they cannot anchor it on their own.
[`/metadata`](/pricing/endpoint/gpu-rental-prices-metadata) lists every value you can use.
**Needs historical access to this data**, which is granted separately from access to current
values — so a token may be able to read today's figures but not last year's. How far back you
can read is reported by [`/metadata`](/pricing/endpoint/gpu-rental-prices-metadata) as
`history_starts_at`.
Results are paged. Follow `meta.next` until it is `null`, and send nothing alongside it — the
link already carries your filters, dates and ordering. See
[Paging](/pricing/concepts#paging).
## Example
```bash theme={null}
curl -H "Authorization: Bearer $TOKEN" \
"https://data-api.compute-index.com/v2/gpu/rental/prices/as-of?at=2026-06-01T12:00:00Z&gpu_search=H100&vendor=aws"
```
## OpenAPI
````yaml pricing/openapi.json GET /v2/gpu/rental/prices/as-of
openapi: 3.1.0
info:
title: GPU Pricing API (v2)
description: >
Pricing data for GPU compute — rental and purchase prices, settled
transactions, published indices, and LLM inference prices.
Every data type exposes the same four endpoints over one filter vocabulary,
one response envelope and one error format, so learning one is learning all
of
them. **Start at `/metadata`**, which lists the values a type accepts and
the
range it holds.
<details>
<summary><strong>Endpoints</strong> — what the four paths
return</summary>
| path | returns |
| --- | --- |
| `/latest` | the current state, one row per thing |
| `/as-of` | the state as it stood on a given date |
| `/history` | rows over a time window |
| `/metadata` | the type's own vocabulary — the valid filter values, and
what it covers |
Some types have fewer. Settled transactions are events, and "the current
state
of events" is not a question, so those types serve `/history` and
`/metadata`
and nothing else.
</details>
<details>
<summary><strong>Responses and paging</strong> — the envelope, and
how to get page two</summary>
Every response is `{"data": [...], "meta": {...}}`.
`data` is the rows; `meta`
describes the request they answer — the sort applied, the window resolved,
and
the paging position.
Nulls are always present. A null means the value is not published, which is
different from zero and different from absent.
`page_size` sets the rows per page (default 100, max 1000). Follow
`meta.next`
for the following page, and stop when it is null.
`meta.next` is an object describing the following page three ways: `url` is
an
absolute URL ready to call, and `path` plus `query_params` are the same
request
split up for clients that build their own. Use whichever suits your HTTP
layer.
Each carries a `page_token`, and the token IS the request — it replays your
filters, window and sort exactly — so a following page cannot silently
change
the question. There is nothing to merge in and nothing to add: do not
construct
or edit a token, and send no parameters beside it. There is no offset, and
no
total count.
</details>
<details>
<summary><strong>Filtering, sorting and time</strong> — anchors,
sort fields, UTC windows</summary>
Filters are per type and listed on each operation. Values are exact matches
unless the parameter says otherwise, and where a list is accepted it is
comma-separated.
**Some types require an anchor** — at least one filter that narrows the
query,
such as a vendor or a GPU. Asking for everything at once is rejected with a
clear error naming the fields that qualify, and `/metadata` lists them.
`sort_by` and `sort_order` control ordering, from that type's own set of
sortable fields; `meta.sort` reports what was applied.
All timestamps are UTC, ISO-8601. Windows are `start`/`end` and are
half-open
— `start` is included, `end` is not — so consecutive windows tile without
double-counting a boundary row.
</details>
<details>
<summary><strong>Access and errors</strong> — tokens, entitlements,
rate limits</summary>
Send a bearer token: `Authorization: Bearer <token>`. Entitlements are
per
data type, so a token reaches the types it is granted and 403s on the rest.
Rate limits are reported on every response in the `X-RateLimit-*` headers.
Errors are RFC 9457 problem details, served as `application/problem+json`
with
`type`, `title`, `status` and `detail`.
</details>
contact:
name: API Support
email: david@compute-index.com
version: 2.0.0
servers:
- url: https://data-api.compute-index.com
security: []
tags:
- name: GPU Rental Prices
description: >-
What it costs to rent GPU compute, as listed by the vendors themselves.
One row is one vendor's price for one product.
Prices are normalised so they compare across vendors: read
`price_usd_per_gpu_hour`. `raw_price` and `raw_price_unit` keep whatever
the vendor actually published, for when you need the original.
A price that changes produces a new row rather than editing the old one,
so `/history` reads as a list of changes and `/as-of` as a single state.
Collection queries need an anchor — a vendor, a GPU, or another narrowing
filter. `/metadata` lists which fields qualify here.
- name: GPU Rental Aggregated Transactions
description: >-
Settled GPU deals published as blends rather than individually. Every row
is a volume-weighted blend of at least two deals, so no single deal can be
identified from it.
`price` is the only price figure on a row: there is no median, range or
spread to ask for.
**Do not sum across rows.** Some rows share a deal with the row before
them, so adding up `total_gpu_count` or `total_gpu_hours` will
double-count. `is_rolling` marks those rows, and `blend_axis` names what
was combined to make up the row.
There is no `/latest` or `/as-of` — use `/history` with a window.
- name: GPU Price Indexes
description: >-
Published GPU price indices — blended transaction indices at daily and
30-minute resolution, by GPU family or by GPU, per region — and the GPU
reference price, the fleet-weighted mean of the per-GPU indices.
**One index per request.** Every data endpoint takes a required `id`;
`/metadata` lists the ids you hold, and an id you do not hold returns 404.
**Two row shapes, told apart by `type`.** A `daily` row's `timestamp` is a
calendar date (`2026-09-02`); an `intraday` row's is the UTC instant its
interval starts (`2026-09-02T10:00:00+00:00`). `/metadata` gives each
index's `row_type`, so you know the shape before you ask. Sort by
`timestamp` or `value`.
`/metadata` says who computes each index. `p5` and `p95` bracket `value`
where an envelope is published, and are null where it is not.
- name: GPU Hardware Prices
description: >-
What it costs to buy GPU hardware outright, from resale, marketplace and
reseller listings — the capex counterpart to rental prices. One row is one
listing on one day it was seen.
A listing that was not seen on a given day has no row for that day, so
`/latest` returns each listing's most recent observation rather than a
single snapshot. Check `last_observed` in `/metadata` before reading a
product's price as current.
**Seller identity is not published** — no platform, seller or listing URL,
and none of them filterable. What you get instead is the classification a
price needs to be read correctly: `market`, `channel`, `price_type`,
`source_type`, `confidence` and `counterparty_class`. Check the
`includes_*` fields too — a whole-chassis price and a bare-module price
are not the same number.
- name: LLM Token Prices
description: >-
Published prices for LLM inference, normalised to USD per 1M tokens so
they compare across sources that quote per-token, per-1k and per-1M.
**One model has many rows.** A row is identified by the whole combination
of source, model, serving provider, price type, region, metric and
qualifiers — input and output are priced separately, and the same model
appears once per source and once per provider. Filtering to a model and
expecting a single row will not work.
Implausible prices are flagged rather than removed: `is_price_outlier`
marks them and they are included by default, so a response is the data as
recorded. Pass `exclude_outliers=true` to drop them.
paths:
/v2/gpu/rental/prices/as-of:
get:
tags:
- GPU Rental Prices
summary: GPU Rental Prices on a given date
description: >-
Vendor prices for renting GPU compute, in USD per GPU-hour.
Returns the same view as `/latest`, as it stood at the moment you pass
in `at`. Give it a date or a full timestamp; a plain date means the end
of that day.
If nothing was published at that exact moment — a weekend, a holiday, a
gap in a vendor's feed — you get the most recent value before it, rather
than an empty response.
A date earlier than your licensed history is rejected rather than
quietly moved forward, so you are never handed an answer to a different
question.
operationId: as_of_gpu_rental_prices_as_of_get
parameters:
- name: at
in: query
required: true
schema:
type: string
description: >-
Point in time (ISO 8601 datetime, UTC assumed if no offset) or a
bare date. A bare date means the end of that day (23:59:59.999999
UTC) — 'as of June 1st' includes June 1st. Returns the records
that were valid at exactly the resolved instant.
examples:
- '2026-06-01T12:00:00Z'
- '2026-06-01'
title: At
description: >-
Point in time (ISO 8601 datetime, UTC assumed if no offset) or a
bare date. A bare date means the end of that day (23:59:59.999999
UTC) — 'as of June 1st' includes June 1st. Returns the records that
were valid at exactly the resolved instant.
- name: vendor
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Vendor slug, exact match. Comma-separated list accepted (max 20).
Example: `aws,coreweave`
examples:
- aws
title: Vendor
description: >-
Vendor slug, exact match. Comma-separated list accepted (max 20).
Example: `aws,coreweave`
- name: gpu_canonical_name
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Canonical GPU name, exact match — the catalog slug form.
Comma-separated list accepted (max 20). Values are listed by the
data type's `/metadata` endpoint.
examples:
- nvidia-h100-sxm5-80gb
title: Gpu Canonical Name
description: >-
Canonical GPU name, exact match — the catalog slug form.
Comma-separated list accepted (max 20). Values are listed by the
data type's `/metadata` endpoint.
- name: gpu_search
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
GPU model as free text, resolved server-side into
`gpu_canonical_name` values. Matched as a substring against the
GPU names and the vendor spellings listed by
`/v2/gpu/rental/prices/metadata`, ignoring case, spaces and
punctuation — `H100`, `h 100` and `h-100` are the same search.
Spellings cover the whole history of each GPU, not just its
current listings, so a discontinued name still resolves on
`/history` and `/as-of`. Counts as an anchor. Comma-separated list
accepted (max 20 terms); a row matching any term is returned. A
search resolving to more than 20 GPUs is refused rather than
expanded — name the ones you want with `gpu_canonical_name`
instead, which `/v2/gpu/rental/prices/metadata` lists in full.
examples:
- H100
title: Gpu Search
description: >-
GPU model as free text, resolved server-side into
`gpu_canonical_name` values. Matched as a substring against the GPU
names and the vendor spellings listed by
`/v2/gpu/rental/prices/metadata`, ignoring case, spaces and
punctuation — `H100`, `h 100` and `h-100` are the same search.
Spellings cover the whole history of each GPU, not just its current
listings, so a discontinued name still resolves on `/history` and
`/as-of`. Counts as an anchor. Comma-separated list accepted (max 20
terms); a row matching any term is returned. A search resolving to
more than 20 GPUs is refused rather than expanded — name the ones
you want with `gpu_canonical_name` instead, which
`/v2/gpu/rental/prices/metadata` lists in full.
- name: region
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Region, exact match. Comma-separated list accepted (max 20).
Example: `us-east-1`
title: Region
description: >-
Region, exact match. Comma-separated list accepted (max 20).
Example: `us-east-1`
- name: contract_type
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Contract type, exact match. Comma-separated list accepted (max
20). Example: `ondemand,spot`
title: Contract Type
description: >-
Contract type, exact match. Comma-separated list accepted (max 20).
Example: `ondemand,spot`
- name: base_product_key
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Identity hash: every observation of one priced thing over time,
across price changes. Obtain it from a previous response — it is
the natural anchor for history drill-down.
title: Base Product Key
description: >-
Identity hash: every observation of one priced thing over time,
across price changes. Obtain it from a previous response — it is the
natural anchor for history drill-down.
- name: product_key
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Snapshot identity hash: one exact observation (identity + time +
price).
title: Product Key
description: >-
Snapshot identity hash: one exact observation (identity + time +
price).
- name: availability
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Availability status, exact match (single value). Example:
`available`
title: Availability
description: >-
Availability status, exact match (single value). Example:
`available`
- name: min_price
in: query
required: false
schema:
anyOf:
- type: number
minimum: 0
- type: 'null'
description: Only rows with price_usd_per_gpu_hour >= this value (inclusive).
title: Min Price
description: Only rows with price_usd_per_gpu_hour >= this value (inclusive).
- name: max_price
in: query
required: false
schema:
anyOf:
- type: number
minimum: 0
- type: 'null'
description: Only rows with price_usd_per_gpu_hour <= this value (inclusive).
title: Max Price
description: Only rows with price_usd_per_gpu_hour <= this value (inclusive).
- name: min_gpu_count
in: query
required: false
schema:
anyOf:
- type: number
minimum: 0
- type: 'null'
description: Only rows whose GPU count >= this value (inclusive).
title: Min Gpu Count
description: Only rows whose GPU count >= this value (inclusive).
- name: max_gpu_count
in: query
required: false
schema:
anyOf:
- type: number
minimum: 0
- type: 'null'
description: Only rows whose GPU count <= this value (inclusive).
title: Max Gpu Count
description: Only rows whose GPU count <= this value (inclusive).
- name: min_gpu_memory_gb
in: query
required: false
schema:
anyOf:
- type: number
minimum: 0
- type: 'null'
description: Only rows with gpu_memory_gb >= this value (inclusive).
title: Min Gpu Memory Gb
description: Only rows with gpu_memory_gb >= this value (inclusive).
- name: max_gpu_memory_gb
in: query
required: false
schema:
anyOf:
- type: number
minimum: 0
- type: 'null'
description: Only rows with gpu_memory_gb <= this value (inclusive).
title: Max Gpu Memory Gb
description: Only rows with gpu_memory_gb <= this value (inclusive).
- name: sort_by
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Sort field. One of: gpu_canonical_name, gpu_count, gpu_memory_gb,
price_usd_per_gpu_hour, region, valid_from, vendor. Default:
`gpu_canonical_name`.
title: Sort By
description: >-
Sort field. One of: gpu_canonical_name, gpu_count, gpu_memory_gb,
price_usd_per_gpu_hour, region, valid_from, vendor. Default:
`gpu_canonical_name`.
- name: sort_order
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: 'Sort direction: `asc` or `desc`. Default: `asc`.'
title: Sort Order
description: 'Sort direction: `asc` or `desc`. Default: `asc`.'
- name: page_size
in: query
required: false
schema:
type: integer
maximum: 1000
minimum: 1
description: Rows per page (max 1000).
default: 100
title: Page Size
description: Rows per page (max 1000).
- name: page_token
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
description: >-
Opaque token token from a previous response's `meta.next`. It
carries the whole request — filters, ordering, window and position
— so supply it alone; the only parameter that may accompany it is
`page_size`. Do not construct or parse these; the format is not
part of the contract.
title: Page Token
description: >-
Opaque token token from a previous response's `meta.next`. It
carries the whole request — filters, ordering, window and position —
so supply it alone; the only parameter that may accompany it is
`page_size`. Do not construct or parse these; the format is not part
of the contract.
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/Page_PriceRow_AsOfMeta_'
'401':
description: Unauthorized — `code` is `unauthenticated`.
content:
application/problem+json:
example:
status: 401
title: Unauthorized
detail: Missing or invalid bearer token.
code: unauthenticated
request_id: 01JQ2X8N4T6V9WZ0ABCD
'403':
description: Forbidden — `code` is `insufficient_entitlement`.
content:
application/problem+json:
example:
status: 403
title: Forbidden
detail: The token does not carry the scopes this endpoint requires.
code: insufficient_entitlement
request_id: 01JQ2X8N4T6V9WZ0ABCD
'404':
description: Not Found — `code` is `not_found`.
content:
application/problem+json:
example:
status: 404
title: Not Found
detail: No such resource, or none you are entitled to see.
code: not_found
request_id: 01JQ2X8N4T6V9WZ0ABCD
'422':
description: Unprocessable Content — `code` is `validation_failed`.
content:
application/problem+json:
example:
status: 422
title: Unprocessable Content
detail: A parameter failed validation.
code: validation_failed
request_id: 01JQ2X8N4T6V9WZ0ABCD
'429':
description: Too Many Requests — `code` is `rate_limited`.
content:
application/problem+json:
example:
status: 429
title: Too Many Requests
detail: Rate limit exceeded; see the X-RateLimit-* headers.
code: rate_limited
request_id: 01JQ2X8N4T6V9WZ0ABCD
security:
- HTTPBearer: []
components:
schemas:
Page_PriceRow_AsOfMeta_:
properties:
data:
items:
$ref: '#/components/schemas/PriceRow'
type: array
title: Data
description: The rows in this page, ordered as `meta.sort` reports.
meta:
$ref: '#/components/schemas/AsOfMeta'
additionalProperties: false
type: object
required:
- data
- meta
title: Page[PriceRow, AsOfMeta]
PriceRow:
properties:
vendor:
type: string
title: Vendor
description: The cloud provider offering this price.
examples:
- coreweave
vendor_gpu_name:
anyOf:
- type: string
- type: 'null'
title: Vendor Gpu Name
description: The GPU name as the vendor writes it.
examples:
- H100
vendor_sku:
anyOf:
- type: string
- type: 'null'
title: Vendor Sku
description: The vendor's own SKU string.
vendor_region:
anyOf:
- type: string
- type: 'null'
title: Vendor Region
description: The region as the vendor names it.
examples:
- us-east-01
region:
anyOf:
- type: string
- type: 'null'
title: Region
description: Normalised cloud region.
examples:
- us-east
gpu_canonical_name:
type: string
title: Gpu Canonical Name
description: >-
Catalog GPU slug — the one identifier that means the same thing
across every data type.
examples:
- nvidia-h100-sxm5-80gb
gpu_manufacturer:
anyOf:
- type: string
- type: 'null'
title: Gpu Manufacturer
examples:
- NVIDIA
gpu_model:
anyOf:
- type: string
- type: 'null'
title: Gpu Model
description: Coarse display model, not the catalog slug.
examples:
- H100
gpu_count:
anyOf:
- type: number
- type: 'null'
title: Gpu Count
description: GPUs in the priced instance.
examples:
- 8
gpu_memory_gb:
anyOf:
- type: number
- type: 'null'
title: Gpu Memory Gb
description: Per-GPU memory in GB.
examples:
- 80
vcpu:
anyOf:
- type: number
- type: 'null'
title: Vcpu
description: vCPUs in the priced instance.
examples:
- 104
ram_gb:
anyOf:
- type: number
- type: 'null'
title: Ram Gb
description: System RAM in GB.
examples:
- 1024
os:
anyOf:
- type: string
- type: 'null'
title: Os
description: Operating system, where the vendor distinguishes one.
form_factor:
anyOf:
- type: string
- type: 'null'
title: Form Factor
examples:
- SXM
interconnect:
anyOf:
- type: string
- type: 'null'
title: Interconnect
examples:
- InfiniBand
instance_type:
anyOf:
- type: string
- type: 'null'
title: Instance Type
description: The vendor's instance family.
instance_variant:
anyOf:
- type: string
- type: 'null'
title: Instance Variant
description: A variant within that family, where one exists.
contract_type:
anyOf:
- type: string
- type: 'null'
title: Contract Type
description: Commercial term shape.
examples:
- ondemand
contract_term:
anyOf:
- type: string
- type: 'null'
title: Contract Term
description: Commitment length as the vendor states it.
examples:
- 1 year
contract_details:
anyOf:
- type: string
- type: 'null'
title: Contract Details
description: Any further terms the vendor attaches to this price.
availability:
anyOf:
- type: string
- type: 'null'
title: Availability
description: What the vendor says about stock at capture time.
price_usd_per_gpu_hour:
anyOf:
- type: number
- type: 'null'
title: Price Usd Per Gpu Hour
description: >-
The normalised price: USD per GPU per hour, comparable across
vendors whatever unit they quote in. This is the field to compare
on.
examples:
- 2.99
raw_price:
anyOf:
- type: number
- type: 'null'
title: Raw Price
description: The price exactly as the vendor published it, before normalisation.
examples:
- 23.92
raw_price_unit:
anyOf:
- type: string
- type: 'null'
title: Raw Price Unit
description: The unit `raw_price` is quoted in.
examples:
- USD/instance/hr
valid_from:
anyOf:
- type: string
- type: 'null'
title: Valid From
description: Inclusive start of this row's validity interval, as a UTC instant.
examples:
- '2026-08-01T00:00:00+00:00'
valid_to:
anyOf:
- type: string
- type: 'null'
title: Valid To
description: >-
Exclusive end of the interval. Null means still in force — but note
that `null` is not the same as 'in force now', because a row can
have a future `valid_from`.
examples:
- null
extracted_at:
anyOf:
- type: string
- type: 'null'
title: Extracted At
description: >-
When this snapshot was captured. Immutable for the life of the row,
and NOT a validity bound — use `valid_from`/`valid_to` for that. A
row's `extracted_at` never changes, so a response is stable to
re-request.
examples:
- '2026-08-01T03:00:00+00:00'
base_product_key:
anyOf:
- type: string
- type: 'null'
title: Base Product Key
description: >-
Hash identifying this product across its price changes — the chain's
identity.
product_key:
anyOf:
- type: string
- type: 'null'
title: Product Key
description: Hash identifying this one immutable priced row.
additionalProperties: false
type: object
required:
- vendor
- vendor_gpu_name
- vendor_sku
- vendor_region
- region
- gpu_canonical_name
- gpu_manufacturer
- gpu_model
- gpu_count
- gpu_memory_gb
- vcpu
- ram_gb
- os
- form_factor
- interconnect
- instance_type
- instance_variant
- contract_type
- contract_term
- contract_details
- availability
- price_usd_per_gpu_hour
- raw_price
- raw_price_unit
- valid_from
- valid_to
- extracted_at
- base_product_key
- product_key
title: PriceRow
description: >-
One vendor's price for one product, over the period it applied.
When a price changes, the previous row is closed off at `valid_to` and a
new
row starts — so a product's price history reads as a series of rows,
each
covering the period its price was in force.
AsOfMeta:
properties:
page_size:
type: integer
title: Page Size
description: Rows requested per page.
examples:
- 100
returned:
type: integer
title: Returned
description: Rows in this page, which is `page_size` or fewer.
examples:
- 100
has_more:
type: boolean
title: Has More
description: Whether a further page exists.
next:
anyOf:
- $ref: '#/components/schemas/NextPage'
- type: 'null'
description: >-
How to fetch the following page, or null at the end of the walk. Use
it exactly as given: it locks in every defaulted parameter — the
window and the resolved ordering in particular — so later pages
cannot drift against earlier ones. There is no `offset`, and nothing
may be added to the request it describes.
sort:
$ref: '#/components/schemas/SortMeta'
as_of:
type: string
title: As Of
description: The instant the state was read at, normalised to a UTC instant.
examples:
- '2026-06-15T00:00:00+00:00'
additionalProperties: false
type: object
required:
- page_size
- returned
- has_more
- next
- sort
- as_of
title: AsOfMeta
description: '`/as-of`, which additionally echoes the instant it resolved.'
NextPage:
properties:
path:
type: string
title: Path
description: Path to call, without an origin.
examples:
- /v2/gpu/rental/prices/history
query_params:
additionalProperties:
type: string
type: object
title: Query Params
description: >-
The query parameters to send, unencoded. Always exactly the token
and the page size — the token carries every filter, the window and
the ordering, so nothing else may accompany it.
examples:
- page_size: '100'
page_token: eyJkIjoicHJpY2VzIiwiZSI6Imhpc3RvcnkiLC4uLg.qgLm5w
url:
type: string
title: Url
description: The same request as an absolute URL, ready to call.
examples:
- >-
https://data-api.compute-index.com/v2/gpu/rental/prices/history?page_token=eyJkIjoicHJpY2VzIiwiZSI6Imhpc3RvcnksLi4u.qgLm5w&page_size=100
additionalProperties: false
type: object
required:
- path
- query_params
- url
title: NextPage
description: >-
Where to get the following page, given three ways.
All three describe the same request, so use whichever suits your HTTP
layer: `url` to call directly, `path` if you already hold a base URL,
and
`query_params` if you pass parameters as a mapping rather than building
a
query string.
There is nothing to merge in and nothing to add: the page token carries
the
whole request — every filter, the window and the ordering — so this is
the
complete next call.
SortMeta:
properties:
by:
type: string
title: By
description: The field the rows are ordered by.
examples:
- valid_from
order:
type: string
title: Order
description: '`asc` or `desc`.'
examples:
- desc
additionalProperties: false
type: object
required:
- by
- order
title: SortMeta
description: |-
The ordering actually applied, echoed so a caller who sent no sort
parameters can read what they got instead of inferring it from the docs.
securitySchemes:
HTTPBearer:
type: http
scheme: bearer
````