AI Pricing
3 of the 73 write-ups here are tagged AI Pricing. Every figure quoted below is in the figures table with the sentence it came from.
The figures
- $462.60 — One estimate has two models both scoring 99/100 on writing tasks with monthly API bills of $462.60 and $116.10 — roughly a 4x gap on similar list prices. →
- $0.181 — Sources are already presenting $0.181 per successful task next to a coding score of 96.0, side by side, which is the shape the conversation is heading toward. →
- 30% — Those who have already made the switch to Chinese tools have seen productivity increases of up to 30%. →
- 20% — Developers should build buffer time into their workflows when using Chinese AI coding tools, which is illustrated by the fact that one developer added 20% extra time to their coding sessions when using these tools because of the higher frequency of stability issues. →
- $19 billion — Anthropic signed a data center lease reported at $19 billion, which is the kind of commitment that only makes sense if compute, not model architecture, is the constraint that decides who is still standing in five years. →
- $1 — My reading, and I could be wrong about the timing, is that the $1 tier holds while that build-out is being financed and that the pressure surfaces later as capacity limits rather than as price rises. →
The write-ups
Your LLM Bill Is 2x the Sticker Price: Peak-Hour Pricing and the 272K Token Cliff
In September and October 2026, a run of Chinese-language model price sheets started circulating with a line at the top that English cost write-ups still don’t have: these are off-peak prices.
The Hidden Costs of AI Coding Tools: What English Developers Don’t Know
English write-ups rank these tools on model quality and price per token.
AI Model Costs: Beyond Per-Token Pricing
Microsoft’s evaluation of Kimi K3 landed on a number that should change how you read a pricing page: about 60 percent of the cost difference between models comes from the thinking depth a task requ…
Did this answer it? A star on the repository is the whole ask — it is what puts these in front of the next person looking; the data is CC BY and does not require starring.
Want a figure that is not here yet? Say which metric, which provider, which unit — one required field, and the page you came from is already filled in.
Got a better number? Open an issue — corrections and counter-data are the point.