The model table in your code goes stale. This one doesn't.
125 models across 10 providers, re-read from each vendor's published page every three hours. The data is free and stays free — you pay when you need to depend on it: higher limits, the full archive, and a licence that lets you ship it.
No card for the free tier and no account to read the API.
Anthropic raised Claude Sonnet 5 by 50%
Cheaper alternatives at your volume: GPT-5.1, GPT-5. Open the comparison →
Watchlists, not a firehose
Group the models you actually run. Alerts fire only for those, so a Voyage embedding change does not wake you at 3am.
Your bill, not just the list price
Store your monthly volume once and every alert arrives with the dollar impact on your own spend attached.
Scheduled changes ahead of time
Announced increases, deprecations and retirements land the day we see them, not the day they bite.
Email, Slack or webhook
Within minutes of the vendor page moving, with the old number, the new number and the source link.
Everything public, no account.
- The whole dataset: prices, context windows, identifiers
- Open JSON API and the npm package — no key
- Change log, calculator, comparisons, calendar, RSS
- 1,000 API requests a day, fair use
For one engineer who needs the archive.
- 50,000 API requests a day
- Full historical series — every observation, per model
- Filtered change streams and bulk CSV export
- Watchlist alerts by email and webhook, with your cost impact
- Scheduled-change calendar and CI helper
When your product depends on the feed.
- Unmetered API, no per-day cap
- Redistribution licence — ship the data inside your own product
- Versioned, stability-guaranteed response shape
- Told before any breaking change, never after
- A named human replying to email
Why the data is free. A pricing dataset that sits behind a paywall stops being checkable, and checkable is the only thing this project has. So the numbers stay open — what costs money is depending on them: volume, the archive nobody can rebuild after the fact, and permission to put them in something you sell.
Email alerts are live. Card details are handled entirely by Stripe and never touch statlyte. Cancel from your account at any time.
Why this exists
If you run anything on a model API, your unit economics are set by numbers on someone else's web page — numbers that can change without an announcement. An introductory rate quietly expires, a model you depend on gets retired, a competitor halves its price and you carry on paying the old one. 125 models across 10 providers are on file here, and every movement since we started watching is recorded with the page it came from.