The Platform Ledger
The ground your project is built on, measured
Every day we snapshot the whole routed model market — who added a model, who killed one, who changed the price, who scheduled a shutdown — and translate it into the only terms that matter on a delivery: contract clauses, scoping calls, business-case risk. Receipts, not takes.
Four honest caveats. First: the OpenRouter catalogue is a large sample of the market, not the whole of it — models behind private contracts won't appear. Second: lifespan figures only cover models that have actually died, so early numbers skew short. Third: day one is July 2026 — this record only gets more valuable with age, and we show "collecting since" until a metric has enough history to mean anything. Fourth: the calendar separates confirmed shutdowns (announced retirements) from guaranteed-until dates (a live model's earliest possible retirement per provider docs, not an announcement) — we don't dress an end-of-life date up as a shutdown.
The scoreboard
Five numbers, each with the delivery decision it should change. Medians over means while samples are small; sample sizes shown; nothing extrapolated.
Loading the ledger.
What moved
The last 90 days of catalogue changes, newest first. The most citable block on the page.
Loading events…
Confirmed shutdowns
Announced retirements, soonest first. If a client system pins any of these, that's a change request waiting to be scoped.
Loading calendar…
Guaranteed until (EOL)
These models are live and supported. The date is the provider's earliest possible retirement, not an announcement. Plan maintenance windows against it anyway.
Loading…
Model availability & pricing via the OpenRouter API. Deprecation dates via Quora's open model-deprecation tracker + provider docs.
What this means for your engagement
Each number is a delivery move
Repricing → business-case cadence
If prices move this often, a one-and-done ROI model is fiction. Re-run the business case on the repricing cadence, and say so in the proposal. The AI Pricing Framework has the recalc template.
Deprecation runway → SOW clause
Median notice is finite and shrinking. Write a model-deprecation clause with a maintenance window shorter than the runway, and price the migration as a change request up front. See the SOW Toolkit.
Churn → model-pinning strategy
The catalogue moves under you. Pin a specific model version in production, test the successor before the shutdown date, and keep an abstraction layer between your app and the provider. The Vendor Evaluation Matrix weights this.
Price direction → vendor weighting
Which way the ground tilts should change how you weight vendors in an evaluation — a lab cutting prices monthly is a different bet from one that only ever raises them.
The loop
The companies measured here also read this page
We know because we log them. The labs whose churn and pricing we track send their crawlers to read what we wrote about them — and every visit lands on the Bot Ledger.
Want the raw numbers?
This whole ledger is public JSON
/platform-ledger/data.json — metrics, 90 days of events, the deprecation calendar. Cite it, chart it, build on it. Attribution to projectwrecked.com is all we ask.
Or query it live from your agent: the Project Wrecked MCP server exposes check_model, deprecation_calendar and more to Claude Code, Cowork, Cursor and any MCP client.