← Anthropic — deprecations

Observed 24 October 2026

Anthropic's page now lists Google Cloud as partly Anthropic-managed, and says the temperature, top_p and top_k settings are removed in API version 2026-10-21, with the rest being minor wording edits.

what changed matterssummary written by a model — check it against the diff below

A restriction or obligation was removed or reworded — 13 lines containing binding language went away. Loosenings are rarely announced.

+17 −17  ·  1bb4691 → 2253424  ·  22534247d6fa  ·  live page

anthropic/model-deprecations.txt24 Oct 2026
6 unchanged lines
Overview
Anthropic uses the following terms to describe the model lifecycle:
- Active: The model is fully supported and recommended for use.
- Legacy: The model will no longer receive updates and may be deprecated in the future.
- Legacy: The model will no longer receive updates and might be deprecated in the future.
- Deprecated: The model is still functional but no longer recommended. Anthropic provides a recommended replacement and assigns a retirement date.
- Retired: The model is no longer available for use. Requests to retired models will fail.
- Retired: The model is no longer available for use. Requests to retired models fail.
Deprecated models are likely to be less reliable than active models. Move workloads to active models to maintain the highest level of support and reliability.
The dates on this page apply to Anthropic-operated platforms: the Claude API, Claude Platform on AWS , and Microsoft Foundry . Partner-operated platforms (Amazon Bedrock and Google Cloud) set their own retirement schedules, so a model's lifecycle status and dates can differ. See the Amazon Bedrock , Amazon Bedrock (Opus 4.6 and earlier) , and Google Cloud model tables.
The dates on this page apply to Anthropic-operated platforms: the Claude API, Claude Platform on AWS , Claude Models on Google Cloud (Anthropic managed) , and Microsoft Foundry . Partner-operated platforms, Amazon Bedrock and Claude Models on Google Cloud (Google managed), set their own retirement schedules, so a model's lifecycle status and dates can differ. See the Amazon Bedrock , Amazon Bedrock (Opus 4.6 and earlier) , and Claude Models on Google Cloud (Google managed) model tables.
Migrating to replacements
Once a model is deprecated, migrate all usage to a suitable replacement before the retirement date. Requests to models past the retirement date will fail.
To help measure the performance of replacement models on your tasks, consider thorough testing of your applications with the new models well before the retirement date.
For specific instructions on migrating to the latest Claude models, see the Migration guide .
For specific instructions on migrating to the latest Claude models, see Migration guides .
Notifications
Anthropic notifies customers with active deployments for models with upcoming retirements, providing at least 60 days' notice before model retirement for publicly released models.
Auditing model usage
To help identify usage of deprecated models, customers can access an audit of their API usage. Follow these steps:
To help identify usage of deprecated models, you can access an audit of your API usage. Follow these steps:
- Go to the Usage page in Claude Console.
- Click Export .
- Review the downloaded CSV to see usage broken down by API key and model.
This audit will help you locate any instances where your application is still using deprecated models, allowing you to prioritize updates to newer models before the retirement date.
This audit helps you locate any instances where your application is still using deprecated models, allowing you to prioritize updates to newer models before the retirement date.
Best practices
- Regularly check the documentation for updates on model deprecations.
- Test your applications with newer models well before the retirement date of your current model.
- Update your code to use the recommended replacement model as soon as possible.
- Contact the support team if you need assistance with migration or have any questions.
- Contact the support team if you need help with migration or have any questions.
Deprecation downsides and mitigations
Anthropic currently deprecates and retires models to ensure capacity for new model releases. This comes with downsides:
- Users who value specific models must migrate to new versions
- Researchers lose access to models for ongoing and comparative studies
- Model retirement introduces safety- and model welfare-related risks
- Users who value specific models must migrate to new versions.
- Researchers lose access to models for ongoing and comparative studies.
- Model retirement introduces safety- and model welfare-related risks.
At some point, Anthropic hopes to make past models publicly available again. In the meantime, Anthropic has committed to long-term preservation of model weights and other measures to help mitigate these impacts. For more details, see Commitments on Model Deprecation and Preservation .
Model status
Current and recently retired models are listed in the following table with their status:
40 unchanged lines
June 15, 2026 claude-opus-4-20250514 claude-opus-4-8
2026-02-19: Claude Haiku 3 model
This model was retired April 20, 2026.
On February 19, 2026, Anthropic notified developers using Claude Haiku 3 model of its upcoming retirement on the Claude API.
On February 19, 2026, Anthropic notified developers using Claude Haiku 3 of its upcoming retirement on the Claude API.
Retirement date Deprecated model Recommended replacement
April 20, 2026 claude-3-haiku-20240307 claude-haiku-4-5-20251001
2025-12-19: Claude Haiku 3.5 model
This model was retired February 19, 2026.
On December 19, 2025, Anthropic notified developers using Claude Haiku 3.5 model of its upcoming retirement on the Claude API.
On December 19, 2025, Anthropic notified developers using Claude Haiku 3.5 of its upcoming retirement on the Claude API.
Retirement date Deprecated model Recommended replacement
February 19, 2026 claude-3-5-haiku-20241022 claude-haiku-4-5-20251001
2025-10-28: Claude Sonnet 3.7 model
This model was retired February 19, 2026.
On October 28, 2025, Anthropic notified developers using Claude Sonnet 3.7 model of its upcoming retirement on the Claude API.
On October 28, 2025, Anthropic notified developers using Claude Sonnet 3.7 of its upcoming retirement on the Claude API.
Retirement date Deprecated model Recommended replacement
February 19, 2026 claude-3-7-sonnet-20250219 claude-sonnet-5-5
2025-08-13: Claude Sonnet 3.5 models
4 unchanged lines
October 28, 2025 claude-3-5-sonnet-20241022 claude-sonnet-5-5
2025-06-30: Claude Opus 3 model
This model was retired January 5, 2026.
On June 30, 2025, Anthropic notified developers using Claude Opus 3 model of its upcoming retirement.
On June 30, 2025, Anthropic notified developers using Claude Opus 3 of its upcoming retirement.
Retirement date Deprecated model Recommended replacement
January 5, 2026 claude-3-opus-20240229 claude-opus-4-8
2025-01-21: Claude 2, Claude 2.1, and Claude Sonnet 3 models
15 unchanged lines
November 6, 2024 claude-instant-1.1 claude-haiku-4-5-20251001
November 6, 2024 claude-instant-1.2 claude-haiku-4-5-20251001
API parameter deprecations
Anthropic occasionally deprecates request parameters that no longer apply to current models. How the API treats a deprecated parameter depends on the model, as the following table shows. Most SDKs keep deprecated parameters in their request types so existing code continues to type-check. The Python SDK (v1.0 and later) removes temperature , top_p , and top_k , so passing them raises a TypeError .
Anthropic occasionally deprecates request parameters that no longer apply to current models. A new model can reject a deprecated parameter, and a new API version can remove it for every model.
Parameter Status Behavior Recommended replacement
temperature , top_p , top_k Deprecated (Claude 4.7 and later models) Returns a 400 error when set to a non-default value on Claude 4.7 and later models and Claude Mythos Preview . Omit and use prompting to guide model behavior.
For migration steps, see the migration guide .
temperature , top_p , top_k Removed in API version 2026-10-21 Returns a 400 error. Earlier API versions return it when set to a non-default value on Claude 4.7 and later models and Claude Mythos Preview . Omit and use prompting to guide model behavior.
For migration steps, see Migration guides .
 

Underlined words mark what moved within a rewritten line. Nothing here is interpreted — this is the difference between two captures, and the conclusion is yours.