Home
/
API
Model deprecation API
Static JSON, served from the edge, CORS-enabled, no key and no rate limit.
156 models with status, dates, replacement and the sources behind them.
MIT licensed — use it in a linter, a CI check, or a runtime guard.
Check one model
curl https://modeldeprecations.dev/api/v1/models/anthropic/claude-1.0.json
The response carries both the authored status and a
computed_status recalculated against the build date, so
a model whose shutdown has passed reads retired without
anyone editing data.
The whole catalog
curl https://modeldeprecations.dev/api/v1/models.json
Ids are provider/model. Dated snapshots such as
gpt-4-32k-0613 are listed in an entry's
aliases rather than duplicated as their own records.
Markdown, for agents
Every model page also exists as Markdown. Append .md.
curl https://modeldeprecations.dev/anthropic/claude-1.0.md
README badges
A shields.io endpoint per model. Green while it works, amber once deprecated, red once it is gone.
JSON Schema
Every entry validates against a published schema. Put this line at the top of a YAML file for
editor autocomplete:
# yaml-language-server: $schema=https://modeldeprecations.dev/api/v1/schema.json
The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.
Copy
# 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.