Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Anthropic Google OpenAI

Providers

Anthropic 29 Google 24 OpenAI 103
Anthropic claude-opus-4-8

Claude Opus 4.8 (Anthropic)

Shutdown scheduled Shuts down in 302 days

No — Claude Opus 4.8 is not deprecated as of July 30, 2026. Anthropic has not deprecated it, but publishes May 28, 2027 (in 302 days) as the earliest date it could be retired.

The last Opus of the 4.x line, and the successor Anthropic names for Opus 4.1, Opus 4, Opus 3 and the Claude 2 family — four generations of migration paths converge here. Still active, with an earliest retirement date of May 2027.

The facts

Provider Anthropic
Model id claude-opus-4-8
Released —
Deprecated not deprecated
Shutdown (earliest) May 28, 2027 · in 302 days

The provider publishes this as the earliest date the model could be retired, not a commitment. It may move later, but not earlier.
Status Shutdown scheduled
Last verified July 30, 2026

Frequently asked questions

When will Anthropic Claude Opus 4.8 shut down?
Anthropic Claude Opus 4.8 is scheduled to shut down on May 28, 2027, in 302 days. Anthropic publishes this as the earliest possible retirement date rather than a firm commitment, so it may move later — but not earlier.
Is Anthropic Claude Opus 4.8 still available?
Yes. Anthropic Claude Opus 4.8 is active and fully supported as of July 30, 2026.

Models that migrate here

Anthropic names Claude Opus 4.8 as the replacement for 5 models.

Sources

Found something wrong? The data is one YAML file — edit it on GitHub.

This page, for machines

JSON Markdown Badge JSON

Drop the badge in a README so it turns red the day this model is retired:

[![claude-opus-4-8](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/anthropic/claude-opus-4-8.json)](https://modeldeprecations.dev/anthropic/claude-opus-4-8)

Other Anthropic models

All Anthropic deprecations →

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.