> For the complete documentation index, see [llms.txt](https://inferra.gitbook.io/inferra-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inferra.gitbook.io/inferra-docs/the-ecosystem/the-gpu-hour-index.md).

# The GPU-hour index

The Inferra Index is a live price for one hour of GPU time, quoted in dollars, for each GPU model. It is the number a renter pays on the marketplace and the number a trader takes a view on. Because both sides read the same price, trading the index is how the market discovers what an hour of compute is really worth.

### What it measures

For each model, the index tracks the going rate to rent one card by the hour, on demand, right now. It looks at what compute actually clears at, not headline "from $X" teasers, and it normalizes multi-card machines down to a single card so every model is comparable.

There is one price per model, and it moves as the rental market moves.

### The models

Inferra prices six GPU tiers.

<table data-search="false"><thead><tr><th>Tier</th><th>Card</th></tr></thead><tbody><tr><td>A5000</td><td>RTX A5000, 24GB</td></tr><tr><td>A100</td><td>A100 80GB SXM</td></tr><tr><td>H100</td><td>H100 80GB SXM</td></tr><tr><td>H200</td><td>H200 141GB SXM</td></tr><tr><td>MI300X</td><td>MI300X 192GB</td></tr><tr><td>B200</td><td>B200 180GB</td></tr></tbody></table>

### How the price is built

The index blends live rental prices from the open market with Inferra's own settled trades, so it reflects both what the wider market charges and what compute actually changes hands for on Inferra.

* **Real market rates** are the main input, drawn from the liquid on-demand rental market.
* **Inferra's own volume** contributes what compute has recently settled at on the platform. Its weight is capped at 20%, so the index can never be driven by Inferra's own flow. The measurement leads the market rather than following its own book.
* **Outliers are filtered out** before anything is blended, so a single strange quote cannot move the price. The result is smoothed over time, so the price tracks the trend rather than every twitch.

If the market goes thin and there is not enough real data to trust, the price holds at its last good value rather than printing a number that is not there.

### Why it matters

The index is not a detached benchmark. It is the price a renter pays to provision a machine and the price a trader prices a position against. Real demand for compute anchors it, and trading it feeds back into what the next buyer pays. That is what makes it price discovery for compute, rather than a rate card someone sets by hand.

The price is a public good in its own right. A provider can price against it, a buyer can check it, and a builder can read it. Perpetuals and futures settle against it. See [Perpetuals and futures](/inferra-docs/inferra-terminal/perpetuals-and-futures.md) for how positions are marked, and [Renting compute](/inferra-docs/inferra-cloud/renting-compute.md) for how it sets the rental rate.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://inferra.gitbook.io/inferra-docs/the-ecosystem/the-gpu-hour-index.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
