Claude Opus 5 Released: What Changed on July 24
Latest status — July 24, 2026: Anthropic has officially released Claude Opus 5. It is available on Claude, Claude Code, the Claude API, Amazon Bedrock, Google Cloud Vertex AI, and Microsoft Foundry. Anthropic has also made it the default model for Claude Max subscribers and the strongest selectable model on Claude Pro.
claude-opus-5, with a 1M-token context window, up to 128K output tokens, and Anthropic list pricing of $5 per million input tokens and $25 per million output tokens—the same base rates listed for Opus 4.8.This URL previously tracked Honeycomb and other pre-release signals. We are retaining that history below so readers can distinguish what was known before launch from what Anthropic has now confirmed.
Claude Opus 5 release status
| Question | Official answer on July 24, 2026 | Production meaning |
|---|---|---|
| Has Claude Opus 5 launched? | Yes, Anthropic announced it on July 24 | Teams can move from release monitoring to controlled evaluation |
| Where is it available? | Claude, Claude Code, Anthropic API, Bedrock, Vertex AI, and Microsoft Foundry | Access is broad, but account and regional eligibility can still differ |
| What is the API model ID? | claude-opus-5 | Use the documented identifier only after the target route is verified |
| What are the base list prices? | $5/MTok input and $25/MTok output | Same base rates as Opus 4.8; successful-task cost still depends on output, retries, and review |
| What are the limits? | 1M context and 128K maximum output | Long-context and long-running agent traces still need workload testing |
| Is it the default everywhere? | Default on Claude Max; strongest selectable model on Claude Pro | Subscription defaults do not prove API economics or application compatibility |
What Anthropic says changed
low, medium, high, xhigh, and max effort levels.Two behavior changes matter during migration:
- Requests that disable thinking while using
xhighormaxeffort return a 400 error. - Fast mode targets roughly 2.5× the speed at 2× the base token price, so latency-sensitive traffic needs its own cost lane.
How to read the benchmark claims
The launch includes strong first-party results, but “Opus 5 beats Fable 5” is too broad. The accurate version is benchmark-specific.
| Anthropic launch claim | Reported result | Safe interpretation |
|---|---|---|
| ARC-AGI-3 | About 3× the next-best model | Anthropic reports a new state of the art on this benchmark |
| CursorBench 3.2 | Max effort comes within 0.5% of Fable's peak at about half the cost | Near-parity on this coding harness, not proof of universal coding superiority |
| AutomationBench | About 1.5× the next best at the same task cost | Strong first-party evidence for autonomous computer workflows |
| OSWorld 2.0 | Above Fable's best at just over one-third the cost | A favorable computer-use result under Anthropic's published setup |
| Frontier-Bench v0.1 | Highest published result | Evidence for difficult frontier tasks within that evaluation |
These are Anthropic's launch results, not independent EvoLink benchmarks. They should become hypotheses for a matched replay using the same prompts, tools, timeouts, effort, and acceptance criteria.
Anthropic also says Opus 5 remains behind Mythos 5 on cybersecurity. That exception is useful: model selection should follow the job, not a single global ranking.
Claude Opus 5 release timeline
| Date | Status event | What changed |
|---|---|---|
| July 24, 2026 | Anthropic officially launched Claude Opus 5 | Product name, API ID, pricing, limits, platforms, and launch benchmarks became official |
| July 14, 2026 | Secondary reports circulated a possible Vertex AI identifier | A meaningful signal, but still not a durable developer contract |
| July 8–9, 2026 | Honeycomb EAP reportedly appeared briefly in Cursor | Partner testing became visible; the final identity remained unconfirmed |
| May 28, 2026 | Claude Opus 4.8 launched | Established the previous Opus baseline and current migration control |
Before July 24, Honeycomb supported a plausible “next Opus” hypothesis, but screenshots could not confirm the name, price, model ID, or release date. The announcement resolves those fields. Old predictions about a 3M-token context window or unknown price should now be discarded in favor of official documentation.
What production teams should verify now
Official release is the start of evaluation, not the end of it.
| Verification area | Minimum evidence before scaling |
|---|---|
| Route contract | Successful request, returned model, usage fields, errors, streaming, and billing |
| Behavioral compatibility | Prompt adherence, output shape, tool selection, structured output, and recovery |
| Long-context reliability | Retrieval accuracy and constraint retention across representative 1M-context workloads |
| Effort policy | Quality, latency, and cost measured separately for each allowed effort level |
| Safety fallback | If the beta fallback is enabled, logs and acceptance tests account for possible Opus 4.8 retries |
| Economics | Cost per accepted task includes output, retries, cache, fallback, and reviewer time |
| Rollback | Opus 4.8 or another measured route remains available until promotion criteria are met |
A practical rollout sequence
- Keep model selection in configuration rather than business logic.
- Replay known-success tasks, known Opus 4.8 failures, and frontier tasks against Opus 5.
- Record accepted-task rate, tool failures, latency, tokens, fallbacks, and review time.
- Start with a narrow lane for high-value coding or agent tasks.
- Promote only the workloads where Opus 5 improves quality or successful-task cost.
- Preserve a tested fallback and measurable rollback thresholds.
This is where a unified gateway creates practical value: the application can compare models and change routing policy without rebuilding provider integrations for every release.
Final status
Treat benchmark leadership as a reason to test, not a reason to replace every default. Use a controlled challenger lane, compare against Opus 4.8 and other strong models, and route by measured task value.
Check Claude Opus 5 availability on EvoLinkSources
- Anthropic: Introducing Claude Opus 5
- Anthropic: Claude API release notes
- Anthropic: Models overview
- Anthropic: What's new in Claude Opus 5
- Anthropic: Claude API pricing
FAQ
Is Claude Opus 5 coming?
It has already arrived. Anthropic announced Claude Opus 5 on July 24, 2026 and made it available across its first-party products, API, and major cloud platforms.
When was Claude Opus 5 released?
Claude Opus 5 was released on July 24, 2026.
Is Claude Opus 5 available through the API?
claude-opus-5. Availability through EvoLink is a separate route-level status that should be checked on the model page.What is the Claude Opus 5 model ID?
claude-opus-5 as the API model ID. Verify that exact identifier against the gateway or cloud route you use before changing production configuration.How much does Claude Opus 5 cost?
Anthropic lists standard pricing at $5/MTok input and $25/MTok output. Fast mode is approximately 2.5 times faster at twice the base token price, so it should be measured as a separate latency lane.
Is Claude Opus 5 the default model on Claude Max?
Yes. Anthropic says Opus 5 is the default for Max subscribers. Pro subscribers can select it as the strongest available model.
Did Claude Opus 5 beat Fable 5?
Is Claude Opus 5 state of the art on ARC-AGI-3?
Anthropic reports that Opus 5 sets a new state of the art on ARC-AGI-3, scoring about three times the next-best model in its launch results.
What changed from the Honeycomb preview?
Honeycomb was a pre-release signal rather than a documented product. The July 24 launch confirmed the final Opus 5 name, API identifier, price, limits, availability, and behavior.
