> ## Documentation Index
> Fetch the complete documentation index at: https://data.ornn.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# The Price Index

> What the GPU index value represents, its units, granularity, and how often it updates.

The core metric in the Ornn Data API is the **price index**: a number that tracks the on-demand rental price of a GPU model over time.

## What the index value means

`index_value` is the **going rate of compute** for a GPU model, measured in **US dollars per GPU-hour**. It is a **weighted average of all verified compute transactions across the market** for that model. For example, an H100 SXM index of `2.00` means the market rate for an H100 SXM is about **\$2.00 per GPU-hour**.

<Note>
  The index reflects actual transactions, not list prices. Treat `index_value` as a normalized market rate per GPU model rather than a quote from any single provider.
</Note>

## Hourly and daily

The API exposes the GPU index at two granularities:

| Granularity | What it is                                        | Where you see it                              |
| ----------- | ------------------------------------------------- | --------------------------------------------- |
| **Hourly**  | The index sampled on the hour                     | Point-in-time and ranged history endpoints    |
| **Daily**   | The aggregated daily average of the hourly values | Daily-index endpoints and long history ranges |

History endpoints automatically choose between hourly and daily: short ranges return hourly points, long ranges (more than \~30 days) return daily points. You can also force a granularity with the `granularity` parameter where supported.

## Update frequency

* **GPU index (hourly / daily)**: refreshed **hourly**, on the hour.
* **Memory prices**: refreshed **once per trading day (weekdays)**. See [Memory Price Index](/docs/memory-index).

The `last_updated` (or `updatedAt`) field on each response tells you exactly when the value was computed.

## Regions

The index currently tracks a single **global** region. The optional `region` parameter exists on several endpoints, but the only populated region is global, and it's the default. You can omit it.

<Tip>
  In some responses `region` echoes back as an empty string (`""`) and in others as `"global"`. Both refer to the same global index. This is a cosmetic difference between endpoints, not different data.
</Tip>

## Supported GPUs

The index covers these models:

`H100 SXM` · `H200` · `A100 SXM4` · `B200` · `RTX 5090` · `RTX PRO 6000 WS`

GPU names are **case- and spelling-sensitive** and must match exactly. Fetch the live list any time from [`/api/gpu-types`](/docs/api-reference/reference/list-supported-gpu-models), or see [Supported GPUs & memory types](/docs/supported-types).

## Working with the endpoints

The GPU index is exposed through a family of endpoints. A few common starting points:

| You want…                         | Endpoint                                                                                              | Key params                                          |
| --------------------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| The latest price for one GPU      | [`/api/daily-index`](/docs/api-reference/current-prices/get-latest-daily-index-for-one-gpu)                | `gpuType`                                           |
| A clean daily series for charting | [`/api/gpu/{gpuName}/history-range`](/docs/api-reference/historical-prices/get-history-rows-with-metadata) | `startDate`, `endDate`, `limit`                     |
| Annualized volatility             | [`/api/gpu/{gpuName}/volatility`](/docs/api-reference/analytics/get-annualized-price-volatility)           | `startDate`, `endDate`, `windowDays` (default `30`) |
| Utilization / volume metrics      | [`/api/gpu/{gpuName}/volume-metrics`](/docs/api-reference/analytics/get-market-utilization)                | `startDate`, `endDate`, `granularity`               |

A ranged daily history for the H100, oldest first:

```bash theme={null}
curl "https://api.ornnai.com/api/gpu/H100%20SXM/history-range?startDate=2026-05-01&endDate=2026-05-31" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

<Tip>
  GPU names go in the path and must be URL-encoded (`H100 SXM` becomes `H100%20SXM`). History ranges longer than \~30 days come back at daily resolution; shorter ranges come back hourly. Force a granularity with `granularity` where the endpoint supports it. See [Analytics](/docs/analytics) for what volatility and utilization mean.
</Tip>