Model file · Opus 5

Claude Opus 5 — the frontier stopped being the expensive one.

For as long as these leaderboards have existed, the most capable model was also the priciest. On July 24, 2026 that stopped being true. Opus 5 took the top of the independent index at lower cost per task than the model below it — and shipped with a dial that lets you spend a sixth as much for most of the capability.

Sourced from Anthropic's announcement, the 194-page Opus 5 System Card, Anthropic's live pricing and model docs, Artificial Analysis and ARC Prize. The tier discipline is Ch 24. What to actually run on it lives on the use-cases page.

Jump to section tap to open

The 30-second answer

Claude Opus 5 shipped July 24, 2026. claude-opus-5, 1M context, 128K output, May 2026 cutoff. $5/$25 per Mtok — unchanged from Opus 4.8, half of Fable 5. Default on Claude Max, top model on Pro. It deprecates nothing. The headline feature is a five-position effort dial, and the single most important thing to know about it is that the API default is high while every launch benchmark number is reported at max. Two things go backwards: no Priority Tier, no server-side web_fetch.

What shipped — the specs that change decisions

Model idclaude-opus-5 — dateless, but still a pinned snapshot, not an evergreen alias
Price$5 in / $25 out per Mtok · batch $2.50 / $12.50 · cache hits $0.50 · Fast mode $10 / $50 (research preview, 2× base)
Context1,000,000 tokens — default and maximum, no smaller variant, no long-context surcharge
Max output128,000 tokens (300,000 on the Batch API beta)
Training cutoffMay 2026 — four months fresher than Fable 5 and Sonnet 5, both January 2026
ThinkingAdaptive only, on by default. thinking.type: "enabled" is gone; disabling it 400s at xhigh and max
PlansDefault on Claude Max, strongest model on Claude Pro. Anthropic's launch post names only Max and Pro and is silent on Team and Enterprise — so this page doesn't claim them either.
Not supportedPriority Tier · the server-side web_fetch tool
Earliest retirementnot sooner than 2027-07-24

The pricing line worth pausing on is the one that isn't in the announcement. There is no long-context surcharge. A 900,000-token request bills at exactly the per-token rate of a 9,000-token one. GPT-5.6, by contrast, charges 2× input and 1.5× output above 272K. If your workload is "put the whole repository in the window and let it think," that is a structural pricing advantage, not a benchmark one — and benchmarks will never show it to you.

The line that quietly works against you: the tokenizer tax. Claude 4.7 and later produce roughly 30% more tokens for the same text than Sonnet 4.6 and earlier. Per-token price is flat; token count is not. Any cost-per-task comparison you carry over from a pre-4.7 model is inflated by about 30% before you start measuring anything.

The effort dial — the only lever that moves capability and the invoice together

Five settings, no beta header, set via output_config: {"effort": "…"}. Anthropic's own descriptions and intended uses:

Effort What Anthropic says it's for
max"Absolute maximum capability with no constraints on token spending."
xhighLong-running agentic and coding tasks over 30 minutes, token budgets in the millions
high default"High capability. Equivalent to not setting the parameter."
mediumAgentic tasks balancing speed, cost and performance
low"Most efficient… simpler tasks, such as subagents"

Artificial Analysis measured the whole ladder on launch day. This is the most decision-useful table in the release, because it is the only one that prices the dial:

Effort Index Rank /190 Cost to run the Index Output tokens Time to first token
low 51.0 #23 $556.06 12M 3.66s
medium 56.3 #8 $1,114.96 29M 5.88s
highdefault 58.9 #5 $1,973.77 52M 21.67s
xhigh 60.1 #2 $2,909.91 76M 37.38s
max 60.7 #1 $3,835.51 100M 66.36s

Artificial Analysis, 2026-07-24 · captured 2026-07-27. "Cost to run the Index" is what AA paid to run the entire benchmark suite at that setting — not a per-task figure. Different denominator, kept separate on purpose.

The arithmetic that should change your defaults: 6.9× the cost from low to max, for 9.7 index points. From the default high to max it is 1.94× the spend for 1.8 points. Time-to-first-token scales 18× across the ladder while throughput stays flat at 52–56 tokens per second — you are not buying speed at any setting, only depth.

That is the genuinely counter-intuitive finding, and it is corroborated three ways. Cognition ran FrontierCode 1.1 and got Opus 5's best Main score at medium. Anthropic documents the decline itself: "a decline in FrontierCode score above high effort… Opus 5 at these effort levels [makes] more changes than the task requires (e.g., refactoring)." And on Anthropic's own FrontierBench, xhigh (44.4) beats max (43.3). On GDPval-AA v2, xhigh scores 1827 using 25% fewer output tokens than max and still beats every other model on the board.

Two mechanics that bite in production. Effort does not shorten output — Anthropic, verbatim: "on Claude Opus 5, changing effort does not reliably shorten responses, so prompt for length instead." And changing effort mid-conversation invalidates the prompt cache, because effort shapes the rendered prompt. Pick one level at the start of a long cached session and stay there.

Where it actually sits — five sources, three different winners

This is the most confused question of the release, and the confusion is legitimate: the evidence genuinely splits. Every gap below falls inside the evaluators' own stated confidence intervals.

Source Tier Winner The gap
Anthropic docsvendorFable 5"the highest available capability" — but start with Opus 5
Artificial AnalysisindependentOpus 560.69 vs 59.86 — 0.83 points, against a stated ±1%
Vals AI IndexindependentFable 575.14% vs 74.82% (±1.35) — 0.32 points, inside the interval
Arena TextcrowdFable 51508±6 vs 1495±8 — intervals overlap
tbench.ai Terminal-Bench 2.1independentFable 5Claude Code + Fable 5 at 83.8% — Opus 5 has no submission
Anthropic's own Table 8.1.AvendorFable 5SWE-bench Pro 80.0 vs 79.2

Fable 5 remains the vendor-declared ceiling and holds both the crowd crown and the official Terminal-Bench crown. Opus 5's one uncontested win is ARC-AGI-3 — 30.16% against GPT-5.6 Sol's 13.33% on the same Public Demo set — and that is the one to trust, because ARC Prize administered it, not Anthropic. Read the config even there: ARC Prize evaluated high effort only, "due to the short testing window." No max-effort ARC-AGI-3 number for Opus 5 exists.

Against Sonnet 5 ($2/$10 through August 31, then $3/$15) the split is cleaner. Per-Index-task, Sonnet 5 costs $1.53 to Opus 5's $2.03 — but scores 53.4 to 60.7, and loses badly exactly where this audience lives: FrontierBench 14.6 vs 43.5 on the public board, and Toolathlon Pass@1 74.7 vs 80.6. Sonnet 5 is the volume tier. Opus 5 is the long-horizon tier.

The rows it loses — six of seventeen, in Anthropic's own table

Secondary coverage buried these. They are in Anthropic's own summary table, and they are the fastest way to calibrate what the launch is and isn't.

  • SWE-bench Pro — Fable 5 wins, 80.0 to 79.2
  • DeepSWE v1.1 — GPT-5.6 Sol wins, 72.7 to 68.8
  • FrontierCode Main — Fable 5 wins by 0.1 (53.5 to 53.4)
  • Humanity's Last Exam, no tools — Fable 5 wins by 0.2 (56.5 to 56.3)
  • HealthBench Professional, length-adjusted — Mythos 5 wins, 66.0 to 59.8
  • ARC-AGI-2 — GPT-5.6 Sol wins, 92.5 to 90.42

And one row that needs its own warning

Benchmarks Anthropic published no Opus 5 number for, in either the launch post or the 194-page system card: GPQA Diamond, AIME, MMMU, MMLU-Pro, τ-bench and its variants, LiveCodeBench, and Terminal-Bench at any version. If you see an Opus 5 figure for one of these attributed to Anthropic, it is not real. Terminal-Bench appears to have been superseded internally by FrontierBench v0.1 — described as "a successor to Terminal-Bench 2.1 developed by the same team." Likewise, METR has published no time horizon for Opus 5; its page was last updated 2026-05-08, and circulating figures trace to a prediction market, not a measurement.

Four things to do before you migrate anything

  1. 1. Raise max_tokens. Adaptive thinking is now on by default, and max_tokens has always been a hard limit on thinking plus response text — so workloads that ran without thinking on Opus 4.8 now hit the ceiling. Anthropic recommends starting at 64K for xhigh and max.

    This is the number-one migration footgun. Code that moved over without raising the ceiling truncates mid-sentence, and the failure looks like a model regression rather than a config error.

  2. 2. Delete every verification instruction you carried over. Anthropic, verbatim: "If your prompt contains explicit verification instructions ('include a final verification step for any non-trivial task,' 'use a subagent to verify'), remove them: instructions like these cause over-verification on Claude Opus 5, and removing them reduces wasted tokens with no loss in quality."

    Same for "double-check your answer," and the same for legacy harness scaffolding. The behaviour you were compensating for is gone; the compensation is now pure cost.

  3. 3. Cap subagent spawning before you upgrade Claude Code past v2.1.219. Nesting depth silently went from 1 to 3 on the same day as a model Anthropic describes as delegating to subagents "more readily than prior models."

    Set CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH=1 to disable nesting; CLAUDE_CODE_MAX_SUBAGENTS_PER_SESSION defaults to 200. A depth-3 tree of Opus 5 leaves at high is the documented anti-pattern — Anthropic's own effort table names low as the subagent setting, and its model matrix names Haiku 4.5. See the swarm chapter for the shape of the bill.

  4. 4. Run a fresh effort sweep. Anthropic explicitly says not to inherit xhigh from Opus 4.7 or 4.8, and Cognition's data says Opus 5 peaks at medium on FrontierCode.

    This is a Ch 25 job, and it is the cheapest hour you will spend this quarter — the ladder above says the wrong default costs 1.94× for 1.8 points.

FAQ

What is Claude Opus 5?

Claude Opus 5 is Anthropic's Opus-tier model, released July 24, 2026. Model id claude-opus-5, 1M-token context window, 128K max output, May 2026 training cutoff — the freshest of any Anthropic model. It prices at $5 per million input tokens and $25 per million output, unchanged from Opus 4.8, and Anthropic positions it as coming close to the frontier intelligence of Claude Fable 5 at half the price. It is the default model on Claude Max and the strongest model available on Claude Pro.

How much does Claude Opus 5 cost?

API pricing is $5 per million input tokens and $25 per million output tokens — identical to Claude Opus 4.8 and exactly half of Claude Fable 5. Cache writes are $6.25 (5-minute) or $10.00 (1-hour), cache hits $0.50, and the Batch API halves input and output to $2.50 and $12.50. One rate carries a premium: Fast mode, a research preview available on the first-party Claude API only, is $10 per million input and $50 per million output — double the base rate. There is no long-context surcharge: a 900,000-token request bills at the same per-token rate as a 9,000-token one.

What is the effort parameter on Claude Opus 5?

Effort has five settings — low, medium, high, xhigh and max — set via output_config. The API default is high, and Anthropic documents high as equivalent to not setting the parameter at all. Effort shapes all tokens, including tool calls and thinking, and it is a behavioral signal rather than a strict token budget. It does not reliably shorten visible responses on Opus 5, so length must be prompted for separately.

Is Claude Opus 5 better than Claude Fable 5?

They are statistically indistinguishable in aggregate capability, and Opus 5 costs half as much. Independent aggregate indices disagree about the order, and every gap sits inside the evaluators’ own stated confidence intervals. Anthropic’s own routing guidance keeps Fable 5 as the highest available capability while recommending Opus 5 as the starting point for complex agentic coding and enterprise work.

Does Claude Opus 5 deprecate Claude Opus 4.8?

No. Opus 5 deprecates nothing. Opus 4.8, 4.7, 4.6 and 4.5 all remain active, and Opus 4.8 is the automatic fallback target when an Opus 5 safety classifier flags a request in the Claude apps, Claude Code and Cowork. Two capabilities do go backwards versus Opus 4.8: Priority Tier is not supported on Opus 5, and the server-side web_fetch tool is not available on it.

Next

Opus 5 use cases — what to actually run on it: seven ranked jobs with the effort level for each, eleven places it's the wrong choice, and the practitioner reception separated from the measurement. Then the tier list for how it places against everything else.

Stay close

The next edition lands when this list says it does.

No course. No paywall. Operator playbooks weekly. 10K+ subscribers.