Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Amazon Anthropic Cohere DeepSeek Google MiniMax Mistral Moonshot AI OpenAI Qwen xAI Xiaomi MiMo Z.ai

Providers

Amazon 8 Anthropic 31 Cohere 35 DeepSeek 5 Google 34 MiniMax 17 Mistral 53 Moonshot AI 18 OpenAI 106 Qwen 26 xAI 26 Xiaomi MiMo 4 Z.ai 22

AI models shutting down in 2027

13 models lose API access during 2027, across every provider we track. In date order, with the replacement each provider names. Every date is cited on the model's own page.

2027 shutdowns

Ordered by the day API access ends. A date marked earliest is the soonest a provider says it could retire the model, not a commitment.

Model Provider Status Shutdown Replacement
GPT Audio
gpt-audio
 OpenAI Deprecated January 20, 2027
in 170 days
 gpt-audio-1.5
GPT Audio mini
gpt-audio-mini
 OpenAI Deprecated January 20, 2027
in 170 days
 gpt-audio-1.5
GPT Realtime
gpt-realtime
 OpenAI Deprecated January 20, 2027
in 170 days
 gpt-realtime-2.1
GPT Realtime mini
gpt-realtime-mini
 OpenAI Deprecated January 20, 2027
in 170 days
 gpt-realtime-2.1-mini
GPT-4o mini Transcribe (2025-03-20)
gpt-4o-mini-transcribe-2025-03-20
 OpenAI Deprecated January 20, 2027
in 170 days
 gpt-4o-mini-transcribe-2025-12-15
Claude Opus 4.6
claude-opus-4-6
 Anthropic Shutdown scheduled February 5, 2027 (earliest)
in 186 days
 —
Claude Sonnet 4.6
claude-sonnet-4-6
 Anthropic Shutdown scheduled February 17, 2027 (earliest)
in 198 days
 —
Claude Opus 4.7
claude-opus-4-7
 Anthropic Shutdown scheduled April 16, 2027 (earliest)
in 256 days
 —
Gemini 3.1 Flash-Lite
gemini-3.1-flash-lite
 Google Shutdown scheduled May 7, 2027 (earliest)
in 277 days
 gemini-3.5-flash-lite
Claude Opus 4.8
claude-opus-4-8
 Anthropic Shutdown scheduled May 28, 2027 (earliest)
in 298 days
 —
Claude Fable 5
claude-fable-5
 Anthropic Shutdown scheduled June 9, 2027 (earliest)
in 310 days
 —
Claude Sonnet 5
claude-sonnet-5
 Anthropic Shutdown scheduled June 30, 2027 (earliest)
in 331 days
 —
Claude Opus 5
claude-opus-5
 Anthropic Shutdown scheduled July 24, 2027 (earliest)
in 355 days
 —

Keep looking

Shutdowns in 2028

Every model whose API access ends during 2028.

 Shutdowns in 2026

Every model whose API access ends during 2026.

 Shutdowns in 2025

Every model whose API access ends during 2025.

 Shutdowns in 2024

Every model whose API access ends during 2024.

 Shutdowns in 2023

Every model whose API access ends during 2023.

 Deprecated models

Announced for retirement, still answering for now.

 Retired models

Already gone. Requests to these fail.

 Shutdown calendar

Every date in order, subscribable as .ics.

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.