Token Price Index
How accurate is this index?
Every day, we check each published price against its source. This page is the record of those checks, counted directly from the files they wrote, and updated with every daily run.
Confirmed against their sources at the last check123 / 123100%
Waiting for a person right now0prices the check could not confirm
Records re-read blind by a second reader198 / 20298.0%
Comparisons made so far1,8241756 confirmed · 16 changed · 44 page changed · 8 source faults
Day by day
| Check (UTC) | Compared | Confirmed | Changed | Page changed | Source broken | Other | New records | Two readerssame / new / held | Second readermatched / open |
|---|---|---|---|---|---|---|---|---|---|
| 2026-11-15 22:15 UTC | 123 | 122 | 1 | · | · | · | 1 | · | 1 / 0 |
| 2026-11-13 22:15 UTC | 123 | 113 | 3 | 7 | · | · | 10 | 6 / 0 / 1 | 10 / 0 |
| 2026-11-12 22:15 UTC | 134 | 131 | 3 | · | · | · | 3 | · | 3 / 0 |
| 2026-11-11 22:15 UTC | 134 | 119 | 2 | 13 | · | · | 15 | 13 / 0 / 0 | 15 / 0 |
| 2026-11-10 22:15 UTC | 134 | 111 | 3 | 20 | · | · | 23 | 16 / 0 / 4 | 23 / 0 |
| 2026-11-09 22:15 UTC | 128 | 122 | 2 | 4 | · | · | 16 | 7 / 0 / 0 | 16 / 0 |
| 2026-11-09 13:41 UTC | 128 | 128 | · | · | · | · | 1 | · | 1 / 0 |
| 2026-11-09 09:54 UTC | 115 | 115 | · | · | · | · | · | · | · |
| 2026-11-09 09:10 UTC | 115 | 115 | · | · | · | · | 1 | · | 1 / 0 |
| 2026-11-09 02:15 UTC | 115 | 112 | 1 | · | 2 | · | 1 | · | 1 / 0 |
| 2026-11-08 02:15 UTCchecked 2026-11-09 | 115 | 112 | 1 | · | 2 | · | 2 | · | 2 / 0 |
| 2026-11-07 02:15 UTCchecked 2026-11-09 | 115 | 113 | · | · | 2 | · | 2 | · | 2 / 0 |
| 2026-11-06 02:15 UTCchecked 2026-11-09 | 115 | 113 | · | · | 2 | · | 1 | · | 1 / 0 |
| 2026-11-05 02:15 UTCchecked 2026-11-09 | 115 | 115 | · | · | · | · | 3 | · | 3 / 0 |
| 2026-11-04 07:05 UTCchecked 2026-11-09 | 115 | 115 | · | · | · | · | 2 | · | 2 / 0 |
Against real charges
Every hour we send each model a small request. When the provider reports what it charged, we compare that with the recorded list price. In the last 7 days, 1547 of 2330 such requests were billed at the exact list price. The charge differed on 7 model(s), all on a marketplace that routes to providers with different prices: All measurements →
- GLM-5.3-Flash OpenRouter +276%
- DeepSeek V4.1 Flash OpenRouter −48%
- MiniMax M3.1 Flash OpenRouter +58%
- MiniMax M3 OpenRouter −21%
- DeepSeek V4 Pro OpenRouter −13%
- Gemini 3.8 Flash OpenRouter −9.1%
- Kimi K3.1 Pro OpenRouter −6.5%
How to read it
- Compared, confirmed
- Every published price was compared with a fresh copy of its source. Confirmed means the source still shows the recorded price.
- Changed, page changed
- Changed: a machine-readable price list shows a new price; we add a new record and keep the old one. Page changed: the text on a pricing web page has changed, so two independent readers read it again.
- Source broken, other
- The page no longer shows prices, the model is no longer listed, or the check failed. These are reported as faults, never as "no change".
- Two readers
- For changed pages: both readers agreed with the record (same), both agreed on a new price (new), or they disagreed and the price waits for a person (held).
- Second reader
- A different AI model re-reads new records blind from the snapshot file. Matched: it found the same numbers. Open: not yet matched; the record shows as unverified until it is.
- What this page does not say
- Confirmed means the page still shows the number we recorded, not that your invoice will match it. The section above compares list prices with actual charges for providers that report a cost per request; it does not yet cover the others.
The method behind these checks: Methodology. The rows themselves: audit.json.