Skip to content
modeldeprecations.dev

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.

How to use this site

The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.

# How to use modeldeprecations.dev

[modeldeprecations.dev](https://modeldeprecations.dev) answers one question per model: is it deprecated,
when does it shut down, and what replaces it. Every date on the site is cited to the
provider's own documentation, with the date we last checked it.

Three lifecycle states are used, matching the providers' own vocabulary:

- **active** — still supported, no deprecation announced.
- **deprecated** — the provider has announced it is going away. It still answers requests.
- **retired** — API access is gone. Requests fail.

A model can be active *and* carry a shutdown date: Anthropic publishes a
"not sooner than" date and Google publishes an earliest shutdown date for models
that are current and fully supported. Those are reported as scheduled shutdowns,
not deprecations, because that is what the provider actually committed to.

## Check one model

```bash
curl https://modeldeprecations.dev/api/v1/models/openai/gpt-4-32k.json
```

Or fetch the page as Markdown, which includes the answer, the dates and the sources:

```bash
curl https://modeldeprecations.dev/openai/gpt-4-32k.md
```

## Full catalog

```bash
curl https://modeldeprecations.dev/api/v1/models.json
```

Ids are `provider/model`. Dated snapshots (`gpt-4-32k-0613`) are listed as aliases of
their canonical entry rather than as separate records.

Each entry carries `computed_status`, the lifecycle state recomputed against the build
date — so a model whose shutdown has passed reads `retired` without anyone editing data.

## Badges

A shields.io endpoint per model, for READMEs that should go red when a model dies:

```
https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4-32k.json
```

## Calendar and changelog

- Subscribe to every shutdown date: https://modeldeprecations.dev/calendar.ics
- Changelog RSS: https://modeldeprecations.dev/changelog.xml

## JSON Schema

```bash
curl https://modeldeprecations.dev/api/v1/schema.json
```

## Contribute

Data lives in YAML under `models/{provider}/{model}.yaml` in the
[GitHub repo](https://github.com/mnfst/modeldeprecations.dev). Every lifecycle date needs a source URL; CI rejects a
date without one. Open a PR.

## For agents

- Machine-readable overview: https://modeldeprecations.dev/llms.txt
- This guide plus every model inline: https://modeldeprecations.dev/llms-full.txt
- Any page also exists as Markdown: append `.md` to a model URL.
- In a browser, this site registers a **WebMCP** tool on `navigator.modelContext`:
  `check_model_deprecation`, `list_shutdowns`, `find_replacement`, and `get_usage_guide`.
- Parameters each model accepts are catalogued on the sibling site, https://modelparams.dev.