How this catalog is built
Every date on this site comes from the provider's own documentation, is linked from the page that uses it, and is stamped with the day a human last checked it. Nothing is inferred, and nothing is generated.
Model deprecations are announced in changelogs, footnotes and table rows that get quietly edited or deleted once a model is gone. 156 models across 3 providers are tracked here so that history stays readable after the provider has moved on.
The rules
- A date without a source is not published
- Every deprecation and shutdown date has to be verifiable at a URL listed under Sources on the model's page. If we cannot find the date, the field is left out and the page says so. A page that admits it has no shutdown date is useful; a page with a plausible wrong date is worse than nothing, because someone will plan a migration around it.
- The provider's own wording wins
- Anthropic and Google publish an earliest possible retirement date for models that are current and fully supported. Those render as a scheduled shutdown, not a deprecation, because that is what the provider actually committed to. Where a third-party registry and a provider page disagree, the provider page wins.
- Status is computed, not stored
- A model becomes retired here on the day its published shutdown date passes, recomputed at every build. Nobody has to remember to edit a file, so the site cannot drift into telling you a model still works after it has stopped.
- Changes are reviewed in public
- The data is one YAML file per model in a public repository. Continuous integration rejects a file that claims a date without a source, and a second check blocks the quieter regressions: deleting a page, dropping an alias that used to resolve, or moving a date without moving the verification stamp forward.
Found something wrong?
Wrong dates are the failure mode that matters, so corrections are the most useful thing you can send. Open an issue with the provider URL that proves it, or edit the YAML directly — there is a link to the exact file on every model page.
Who maintains it
Built and maintained by Manifest, an open-source LLM router, with contributions from anyone who opens a pull request. We keep it because we route traffic to these models and need to know when they stop answering. It is MIT licensed and free to use, including commercially.
Its sibling modelparams.dev catalogues the parameters each model accepts — the other half of the question when you are changing a model id.