About ChangeLedger
We watch the boring-but-expensive stuff so you don’t have to: which models are going away, what APIs cost now, and what your coding plan really includes.
What we cover
- Shutdowns. Model and API deprecations, with the date it stops working and the provider’s suggested replacement.
- Prices. API price changes: per-token prices, cache pricing, introductory prices that end.
- Plan limits. Changes to what coding plans include or cost (Cursor, Claude, Codex and similar): tiers, usage allowances, who gets what.
How it’s sourced
- Official pages first. Every entry links to the provider’s own deprecation page, pricing page, changelog, release notes or help-center article. We read the page before we write about it.
- No source, no entry. If we can’t confirm something on a provider’s own page, it doesn’t go in. Rumors, leaks and screenshots don’t count, even when they’re probably right.
- Plain wording, with the provider’s numbers. We repeat the provider’s own dates and prices rather than interpreting them. When a provider is vague (for example “a lower usage allowance”), we say it’s vague.
- Dates mean two things. The date on a card is when the change was announced or published. The “shutdown” or “effective” date is when it actually takes effect. Where a provider gives no date, we say so.
- Pages change. Provider docs get edited without notice. Always check the linked page before you act on a date, especially for anything within a few weeks.
Corrections
Found something wrong, stale, or missing? We want to know, and we’ll fix it and note the fix. Please include the entry title and a link to the provider page that shows the right answer.
Send corrections to orgosiavanghoul@gmail.com.
Independence
ChangeLedger is independent and isn’t affiliated with OpenAI, Anthropic, Google, Cursor or any other provider listed. We plan to support the site later through sponsors, affiliate links and paid listings. If we do, they’ll be clearly labeled and kept separate from the feed, and they won’t change what we report. See the sponsor page.
Machine-readable
Everything here comes from one file, data/changes.json, and the RSS feed is generated from it.