What is working, and what is not
What is working, what is not, and what we are late on. Published by us, before anyone else finds it.
Sources last read 2026-11-03 at 05:16 UTC. Page built 2026-11-03 at 10:06 UTC. 2 567 published values are overdue for a re-check, and 115 contradictions are open, and 4 845 values are frozen because their source stopped publishing them. Collection runs every six hours; the site is rebuilt every hour, so the two timestamps above are never the same and neither one stands in for the other.
Every source we read
| Source | Last run | Result | Values written | Last failure | Why it failed |
|---|---|---|---|---|---|
| anthropic_models | 2026-11-03 02:16 | ran clean | 5 | 2026-10-08 | the run did not complete |
| anthropic_pricing | 2026-11-03 02:21 | ran clean | 0 | 2026-10-08 | the page changed shape and our reader lost its footing |
| aws_bedrock | 2026-11-03 02:26 | ran clean | 0 | 2026-08-26 | the source gave two different values for the same cell |
| baseten_pricing | 2026-11-03 02:33 | ran clean | 0 | 2026-11-02 | the page changed shape and our reader lost its footing |
| cerebras_pricing | 2026-11-03 05:16 | ran clean | 0 | 2026-09-11 | values we knew went missing from the source |
| cloudflare_workers_ai | 2026-11-03 02:11 | ran clean | 0 | 2026-09-15 | the page changed shape and our reader lost its footing |
| deepinfra | 2026-11-03 05:10 | ran clean | 0 | never | |
| deepseek_pricing | 2026-11-03 02:43 | ran clean | 0 | 2026-10-17 | the page changed shape and our reader lost its footing |
| ecb_fx | 2026-11-03 02:15 | ran clean | 11 | 2026-09-01 | the page changed shape and our reader lost its footing |
| fireworks_pricing | 2026-11-03 02:30 | ran clean | 50 | 2026-11-02 | the page changed shape and our reader lost its footing |
| google_gemini | 2026-11-03 02:48 | failed | 0 | 2026-11-03 | the page changed shape and our reader lost its footing |
| groq_pricing | 2026-11-03 02:55 | ran clean | 0 | 2026-10-06 | the source did not answer in time |
| hf_router_perf | 2026-11-03 03:52 | ran clean | 279 | 2026-10-09 | the run did not complete |
| litellm_registry | 2026-11-03 03:02 | ran clean | 414 | 2026-10-10 | the run did not complete |
| mistral_pricing | 2026-11-03 03:12 | ran clean | 0 | 2026-11-03 | the run did not complete |
| moonshot_pricing | 2026-11-03 03:12 | ran clean | 0 | 2026-11-02 | the page changed shape and our reader lost its footing |
| nebius_token_factory | 2026-11-03 02:23 | ran clean | 0 | 2026-10-23 | the page changed shape and our reader lost its footing |
| novita_api | 2026-11-03 02:33 | ran clean | 14 | 2026-10-09 | the run did not complete |
| novita_pricing | 2026-11-03 02:50 | ran clean | 0 | 2026-11-03 | the run did not complete |
| openai_pricing | 2026-11-03 03:22 | ran clean | 0 | 2026-10-23 | the page changed shape and our reader lost its footing |
| openrouter_models | 2026-11-03 05:16 | ran clean | 207 | 2026-09-13 | the run did not complete |
| openrouter_uptime | 2026-11-03 03:25 | ran clean | 645 | 2026-09-29 | the run did not complete |
| ovh_ai_endpoints | 2026-11-03 03:31 | ran clean | 0 | never | |
| perplexity_pricing | 2026-11-03 03:35 | ran clean | 0 | 2026-10-23 | the run did not complete |
| replicate_pricing | 2026-11-03 02:41 | ran clean | 118 | 2026-09-05 | the page changed shape and our reader lost its footing |
| snowflake_cortex | 2026-11-03 02:30 | ran clean | 834 | 2026-11-03 | the page changed shape and our reader lost its footing |
| vendor_entities | 2026-11-02 04:09 | ran clean | 0 | never | |
| xai_pricing | 2026-11-03 03:40 | ran clean | 0 | 2026-08-27 | values we knew went missing from the source |
| zai_pricing | 2026-11-03 03:53 | ran clean | 0 | 2026-09-11 | values we knew went missing from the source |
« Values written » counts what a run actually recorded, not what it read. A run that finds every figure unchanged writes nothing, and that is the normal case: we record a value when it moves, never once per pass.
What we are holding back, and why
| Count | What it is |
|---|---|
| 20 622 | Parameters seen only by a third-party aggregator. Level 5 is never published on its own, so these stay out until a vendor page confirms them. |
| 261 | Parameters our own code stopped producing after we changed how we read a page, and which a current parameter already covers with the same value. Kept in the archive, removed from the pages. |
| 2 567 | Published values not re-checked within three times the cadence we announced for them. They stay visible and carry their real observation date, which is the point. |
| 115 | Open contradictions: two sources disagree, or a movement looked like a redesign rather than a repricing. Each one is recorded rather than silently resolved in our favour. |
| 4 845 | Values frozen because the source stopped publishing them. We keep them with the date they were last observed, which is what a registry is for. Nothing can bring this number down, and nothing should. |
What this page deliberately does not show
Three figures would look good here and would not be honest yet. The median delay between a vendor changing a price and us detecting it, because we do not yet record the vendor's own effective date and would be measuring our own collection interval. A breakdown of held-back parameters by reason, because there is only one reason so far. And an uptime percentage, because this site has been collecting since 25 August 2026 and a percentage over three days says nothing.