claude-opus-4-1 — pricing, context window and limits
Retired on the Claude API on 2026-08-05; requests to it there now fail. Amazon Bedrock and Google Cloud set their own schedules and still list it. Migrate to Claude Opus 5.5.
Price per million tokens
| Input | $15 |
|---|---|
| Output | $75 |
| Cache write, 5-minute TTL | $18.75 |
| Cache write, 1-hour TTL | $30 |
| Cache read | $1.50 (0.1x input) |
| Batch input / output | $7.50 / $37.50 |
Limits and behaviour
| Status | Retired on the Claude API |
|---|---|
| Context window | 200K tokens |
| Max output | 32K tokens |
| Min cacheable prefix | 1,024 tokens |
| Effort levels | not supported |
| Effort default | — |
| Thinking | Fixed budget_tokens, off unless requested |
| Forced tool_choice | Accepted |
| Platforms | Amazon Bedrock, Google Cloud |
Lifecycle
| API model name | claude-opus-4-1-20250805 |
|---|---|
| Deprecated | 5 Jun 2026 |
| Retired | 5 Aug 2026 |
| Still listed on | Amazon Bedrock, Google Cloud |
| Successor | Claude Opus 5.5 |
Retired on the Claude API
Opus 4.1's retirement executed on schedule: Anthropic's lifecycle table now lists it as retired, and a request to it on the Claude API fails. When this page was first written we could only say the published date had passed; the date is now confirmed, and the lifecycle table above shows it. If an integration of yours still names this id against the first-party API, it is already broken, not about to break.
Where it still answers, and why that is not a reprieve
Anthropic's retirement dates govern its own platforms. Amazon Bedrock and Google Cloud set their own schedules, and Anthropic's pricing page still lists this model there. Code that routes through one of those platforms may keep working for a while — but on a timetable you do not control and this site does not track, at a per-token price well above every current Opus.
Its figures are reference only
None of this site's calculators price against this model. The figures above are the last ones Anthropic published for it, kept so a reader auditing an old invoice or a partner-platform bill has something to check against.
Where to migrate
The migration guide now points code on this model at Opus 5.5, applying the Opus 4.6, 4.7, 4.8 and 5 changes in order: adaptive thinking, removal of the sampling parameters, then the thinking-default changes of the last two generations.
Related
See the model ID you're calling has been retired for what the failure looks like, and claude-opus-5-5 for the current Opus.
Verified 2026-09-30 against claude-api skill — shared/models.md, model-migration.md + SKILL.md model table and Anthropic's pricing and model-deprecation pages (canonical: https://platform.claude.com/docs/en/about-claude/models/overview, https://platform.claude.com/docs/en/about-claude/pricing, https://platform.claude.com/docs/en/about-claude/model-deprecations).Could not confirm: Partner platforms keep their own retirement dates, which we do not track — check Amazon Bedrock's and Google Cloud's model pages before relying on it there. Its prices are shown for reference and are not used by any calculator on this site.
Verified 2026-10-28 against Anthropic's model-deprecations status table and pricing page (canonical: https://platform.claude.com/docs/en/about-claude/model-deprecations, https://platform.claude.com/docs/en/about-claude/pricing).Could not confirm: These dates apply to the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed) and Microsoft Foundry. Amazon Bedrock and Claude Models on Google Cloud (Google managed) keep their own retirement schedules, which we do not track.