> ## 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. # Aggregated Transactions: History > Settled GPU deals combined in groups, so no single deal can be identified. Returns everything that happened inside the range. These are settled events, so this is the only way to read them — there is no current state to ask for. `start` is included and `end` is not, so consecutive ranges join up without returning anything twice. A plain date for `end` means the end of that day, so `start=2026-06-01&end=2026-06-01` is that whole day. Omitting `start` gives you the most recent 90 days. **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. Every row combines at least two deals, which is why `price_usd_per_gpu_hour` is the only price figure: publishing a range alongside it could reveal the individual deals behind it. **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-transactions-aggregated-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/transactions/aggregated/history?start=2026-06-01&end=2026-07-01&gpu_canonical_name=nvidia-h100-sxm5-80gb" ``` ## OpenAPI ````yaml pricing/openapi.json GET /v2/gpu/rental/transactions/aggregated/history 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/transactions/aggregated/history: get: tags: - GPU Rental Aggregated Transactions summary: GPU Rental Aggregated Transactions over a date range description: >- Settled GPU deals combined in groups, so no single deal can be identified. Returns everything that happened inside the range. These are settled events, so this is the only way to read them — there is no current state to ask for. `start` is included and `end` is not, so consecutive ranges join up without returning anything twice. A plain date for `end` means the end of that day, so `start=2026-06-01&end=2026-06-01` is that whole day. Omitting `start` gives you the most recent 90 days. operationId: history_gpu_rental_transactions_aggregated_history_get parameters: - name: start in: query required: false schema: anyOf: - type: string - type: 'null' description: >- Window start, inclusive (ISO 8601 datetime, or a bare date = start of that day UTC). Default: `end` minus 90 days. title: Start description: >- Window start, inclusive (ISO 8601 datetime, or a bare date = start of that day UTC). Default: `end` minus 90 days. - name: end in: query required: false schema: anyOf: - type: string - type: 'null' description: >- Window end, exclusive (ISO 8601 datetime, or a bare date = that whole day, i.e. the bound becomes the following midnight UTC). Default: now. Consecutive windows tile with no overlap: `start=2026-06-01&end=2026-06-07` then `start=2026-06-08&end=2026-06-14`. title: End description: >- Window end, exclusive (ISO 8601 datetime, or a bare date = that whole day, i.e. the bound becomes the following midnight UTC). Default: now. Consecutive windows tile with no overlap: `start=2026-06-01&end=2026-06-07` then `start=2026-06-08&end=2026-06-14`. - name: gpu_model in: query required: false schema: anyOf: - type: string - type: 'null' title: Gpu Model - 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: region_group in: query required: false schema: anyOf: - type: string - type: 'null' description: >- Region group, exact match — a coarse trading group, NOT a cloud region (see `region` for those). Values are listed by `/metadata`. examples: - us title: Region Group description: >- Region group, exact match — a coarse trading group, NOT a cloud region (see `region` for those). Values are listed by `/metadata`. - 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: 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: sort_by in: query required: false schema: anyOf: - type: string - type: 'null' description: >- Sort field. One of: contract_type, gpu_model, price_usd_per_gpu_hour, region_group, tenor_days, total_gpu_count, transaction_date. Default: `transaction_date`. title: Sort By description: >- Sort field. One of: contract_type, gpu_model, price_usd_per_gpu_hour, region_group, tenor_days, total_gpu_count, transaction_date. Default: `transaction_date`. - name: sort_order in: query required: false schema: anyOf: - type: string - type: 'null' description: 'Sort direction: `asc` or `desc`. Default: `desc`.' title: Sort Order description: 'Sort direction: `asc` or `desc`. Default: `desc`.' - 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_TxnAggregateRow_HistoryMeta_' '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_TxnAggregateRow_HistoryMeta_: properties: data: items: $ref: '#/components/schemas/TxnAggregateRow' type: array title: Data description: The rows in this page, ordered as `meta.sort` reports. meta: $ref: '#/components/schemas/HistoryMeta' additionalProperties: false type: object required: - data - meta title: Page[TxnAggregateRow, HistoryMeta] TxnAggregateRow: properties: gpu_model: type: string title: Gpu Model description: Coarse display model. examples: - H100 gpu_canonical_name: anyOf: - type: string - type: 'null' title: Gpu Canonical Name description: Catalog GPU slug. examples: - nvidia-h100-sxm5-80gb region_group: anyOf: - type: string - type: 'null' title: Region Group description: >- Coarse trading region — a trading group, not a cloud region. Values are listed by `/metadata`. examples: - US contract_type: anyOf: - type: string - type: 'null' title: Contract Type examples: - reserved tenor_days: anyOf: - type: integer - type: 'null' title: Tenor Days description: Commitment length of the blended prints, in days. examples: - 365 price_usd_per_gpu_hour: anyOf: - type: number - type: 'null' title: Price Usd Per Gpu Hour description: >- The volume-weighted price in USD per GPU per hour, and the only price statistic published. No median, min, max or percentile exists here by design. examples: - 2.05 total_gpu_count: anyOf: - type: number - type: 'null' title: Total Gpu Count description: >- GPUs across the deals in this row. Do not sum across rows — see `is_rolling`. examples: - 1024 total_gpu_hours: anyOf: - type: number - type: 'null' title: Total Gpu Hours description: GPU-hours across the blended prints. NOT additive across rows. examples: - 8970240 transaction_date: anyOf: - type: string - type: 'null' title: Transaction Date description: Settlement date of the blend, ISO-8601. examples: - '2026-08-14' discount_percentage: anyOf: - type: number - type: 'null' title: Discount Percentage description: Discount against the public reference price, in percent. examples: - 24.1 is_rolling: anyOf: - type: boolean - type: 'null' title: Is Rolling description: >- True when this row shares a deal with the previous row. Rows marked this way must not be summed together, and their values update as further deals settle. blend_axis: anyOf: - type: string - type: 'null' title: Blend Axis description: What was combined to make up this row. examples: - tenor blend_tenor_days: anyOf: - type: integer - type: 'null' title: Blend Tenor Days description: The second tenor, when `blend_axis` is tenor. blend_region_group: anyOf: - type: string - type: 'null' title: Blend Region Group description: The second region, when `blend_axis` is region. row_key: type: string title: Row Key description: >- Opaque, stable identifier for this blended row, used as the pagination tiebreak. v2's own — it is not a column on the underlying data. additionalProperties: false type: object required: - gpu_model - gpu_canonical_name - region_group - contract_type - tenor_days - price_usd_per_gpu_hour - total_gpu_count - total_gpu_hours - transaction_date - discount_percentage - is_rolling - blend_axis - blend_tenor_days - blend_region_group - row_key title: TxnAggregateRow description: >- A blend of at least two settled deals, never a single one. `price` is a volume-weighted blend, and it is the only price figure here: publishing a range alongside it could reveal the individual deals behind it. 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. HistoryMeta: 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' window: $ref: '#/components/schemas/WindowMeta' additionalProperties: false type: object required: - page_size - returned - has_more - next - sort - window title: HistoryMeta description: '`/history`, which additionally reports the window it queried.' 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. WindowMeta: properties: start: type: string title: Start description: Inclusive start of the effective window, as a UTC instant. examples: - '2026-06-01T00:00:00+00:00' end: type: string title: End description: >- Exclusive end of the effective window, as a UTC instant. Half-open, so consecutive windows tile without returning any row twice. examples: - '2026-07-01T00:00:00+00:00' clamped: type: boolean title: Clamped description: True when the caller's licensed history depth moved `start` forward. history_starts_at: anyOf: - type: string - type: 'null' title: History Starts At description: >- The caller's licensed history floor. Null means no floor applies, or that this data type is not floor-bound. Always present, so an absent key never has to be interpreted. additionalProperties: false type: object required: - start - end - clamped title: WindowMeta description: |- The window `/history` actually queried, after defaulting and clamping. Reported because both can move what the caller asked for: an omitted `start` defaults to the type's trailing window, and a start earlier than the caller's licensed history is clamped forward to it. securitySchemes: HTTPBearer: type: http scheme: bearer ````