Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Anthropic Google OpenAI

Providers

Anthropic 29 Google 24 OpenAI 103
Anthropic claude-opus-4-1-20250805

Claude Opus 4.1 (Anthropic)

Deprecated Shuts down in 6 days

Yes — Anthropic deprecated Claude Opus 4.1 on June 5, 2026 and shuts it down on August 5, 2026 (in 6 days). The recommended replacement is Claude Opus 4.8.

The August 2025 Opus, and the last Anthropic model priced at $15/$75 per million tokens — three times what Opus costs today. It is the only deprecated Anthropic model still answering requests, and it has days left.

The facts

Provider Anthropic
Model id claude-opus-4-1-20250805
Also published as claude-opus-4-1
Released August 5, 2025
Deprecated June 5, 2026
Shutdown August 5, 2026 · in 6 days
Status Deprecated
Last verified July 30, 2026

What to use instead

Anthropic Claude Opus 4.8 claude-opus-4-8 Provider-recommended Shutdown scheduled

Opus 4.7 and later reject temperature, top_p and top_k with a 400 error when set to a non-default value. Remove them from the request rather than tuning them down. Opus 4.8 also defaults effort to high on every surface, so set it explicitly if you were relying on a cheaper default.

What parameters claude-opus-4-8 accepts on modelparams.dev

Change the id

In most cases the migration is one string. Check the parameter differences before you ship — newer models drop older sampling knobs more often than they add them. 

- "model": "claude-opus-4-1-20250805"
+ "model": "claude-opus-4-8"

Frequently asked questions

When will Anthropic Claude Opus 4.1 shut down?
Anthropic Claude Opus 4.1 is scheduled to shut down on August 5, 2026, in 6 days.
What replaces Anthropic Claude Opus 4.1?
Anthropic recommends Claude Opus 4.8 (`claude-opus-4-8`) as the replacement for Anthropic Claude Opus 4.1. Opus 4.7 and later reject temperature, top_p and top_k with a 400 error when set to a non-default value. Remove them from the request rather than tuning them down. Opus 4.8 also defaults effort to high on every surface, so set it explicitly if you were relying on a cheaper default.
Is Anthropic Claude Opus 4.1 still available?
Yes, for now. Anthropic Claude Opus 4.1 is deprecated but still answers requests until August 5, 2026. Deprecated models get no further updates and are the first to lose capacity.
How do I migrate from Anthropic Claude Opus 4.1 to claude-opus-4-8?
Swap the model id in your API call: replace "claude-opus-4-1-20250805" with "claude-opus-4-8". Opus 4.7 and later reject temperature, top_p and top_k with a 400 error when set to a non-default value. Remove them from the request rather than tuning them down. Opus 4.8 also defaults effort to high on every surface, so set it explicitly if you were relying on a cheaper default.
Does this apply to claude-opus-4-1 too?
Yes. Anthropic Claude Opus 4.1 is also published as `claude-opus-4-1`; that id shares the same lifecycle dates as `claude-opus-4-1-20250805`.

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-1-20250805](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/anthropic/claude-opus-4-1-20250805.json)](https://modeldeprecations.dev/anthropic/claude-opus-4-1-20250805)

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.