Opus 5: frontier intelligence just went half-price — and Reddit showed up to mock the chart

Anthropic released Claude Opus 5 today. The sales pitch is on the first screen of the announcement: the model "comes close to the frontier intelligence of Claude Fable 5 at half the price". The community's top-voted reaction, a few hours later, was a jab at the benchmark chart that ships with the announcement.

I went to check the chart. The jab does not hold up — and the reason is more interesting than the joke.

What actually changed

The official announcement carries the verifiable facts, no adjectives:

Note the price: it is exactly the same as Opus 4.8's. The announcement's "half the price" is not a cut relative to the previous model — it is a comparison with Fable 5, which costs US$ 10 / US$ 50. That distinction slipped past much of the coverage and produced legitimate confusion in the community itself.

In other words: for the same money you were already spending on Opus 4.8, Anthropic claims to deliver something close to the top of its line. If that holds up in real use, the practical effect is not "the model got better" — it is the cost of running long, autonomous tasks just dropped a tier.

The API changes nobody puts in the press release

Five details that only surface when you read the documentation instead of the announcement, and that matter more than any bar in a chart for anyone with code in production:

1. Thinking became the default. On Opus 4.8, omitting the thinking parameter meant running without extended reasoning. On Opus 5, omitting it means thinking. That is a silent change in cost and — worse — in truncation: max_tokens is a ceiling over the reasoning plus the answer. Every endpoint that never configured thinking and squeezed max_tokens around the size of the answer may start cutting text mid-sentence.
2. Turning reasoning off now has a ceiling. thinking: {type: "disabled"} is only accepted with effort high or lower. Combined with xhigh or max, the API returns a 400 error. And validation is per request: a later call that raises the effort breaks on its own, even if the previous ones went through.
3. The cache minimum dropped from 1024 to 512 tokens. A prompt you had written off as "too short to cache" now caches — without changing a line of code.
4. Refusal became part of the contract. Opus 5 ships with elevated cybersecurity safeguards and classifiers that can refuse the request: it comes back HTTP 200, with stop_reason: "refusal" and a category. Anyone reading content[0] directly breaks. There is a fallbacks parameter that reroutes the refused request to another model within the same call — and for the cyber category the recommended destination is Opus 4.8 itself.
5. You can swap the tool set mid-conversation without invalidating the prompt cache (beta mid-conversation-tool-changes-2026-07-01). Before, touching tools midway reprocessed the entire prefix.

And two operational details worth money: Opus 5 has its own rate-limit bucket, separate from the combined Opus 4.x pool — migrating traffic there frees no headroom in the old bucket and inherits none of its quota. And Priority Tier does not cover Opus 5, although it covers Fable 5 and Opus 4.8.

There is also a fast mode (speed: "fast"), which runs the same model with much faster output at double the price — US$ 10 / US$ 50. Claude API only: it does not exist on Bedrock, Google Cloud or Foundry.

The numbers

The announcement's text publishes almost everything as a relative claim ("three times the runner-up", "at half the cost"). The absolute values live in the charts — which are images. I opened the images and transcribed them. The table below is the announcement's own, in full:

The real jump is in the first two rows and the third. On Frontier-Bench, Opus 5 more than doubles Opus 4.8. On ARC-AGI-3 — the test of genuinely novel problems, which the model cannot have seen in training — it scores 30.2% against the runner-up's 7.8%, almost four times as much.

Methodological note. The table puts Opus 4.8 at 21.1% on Frontier-Bench; the effort chart in the same announcement puts the same model near 18.8%. It is not a contradiction — the chart declares a different setup (mini-SWE-agent harness, GKE backend, average of five attempts per task). Part of the press published the chart's number as if it were the table's.

The chart that matters is not the bar chart

The announcement carries a family of charts the coverage ignored: cost per task against performance, one point per effort level. That is where the launch's thesis either shows up or does not.

Two readings jump out of it, and neither is in the announcement's text:

Opus 5 at its cheapest effort beats Opus 4.8 at its most expensive. About 25.7% at US$ 5.60 per attempt against 18.8% at US$ 17. A better result, spending roughly a third. It is the entire launch argument condensed into two points — and it shows up in no bar.

max effort makes the result worse. The curve climbs up to xhigh (44.3%) and drops at max (43.3%). The same happens on Artificial Analysis's coding index. The documentation warns that max can hit diminishing returns and "overthink" simple tasks; here it is measured, in the manufacturer's own material. Anyone who inherits the habit of pinning max "because it is the best" is paying more to score less.

How these two numbers were obtained. The table above is a direct transcription. The curve's values, however, were read off the published chart, which ships with no table — they are visual-reading approximations on a log scale, not tabulated data. The shape of the curves is what matters; the decimals are not.

And a chart footnote worth more than the chart: "Opus 4.8 served as fallback on safety-classifier refusals for Opus 5 and Fable 5." Anthropic itself had to trigger the refusal-fallback mechanism inside the benchmark run. That item 4 in the API list is not a defensive hypothesis: it is normal operation.

About the Reddit mockery

The official thread on r/ClaudeAI racked up hundreds of points, and the top-voted comment — by a wide margin — was not about capability. It was a parody of Claude's own sycophantic tone applied to the benchmark chart, with the joke that "the numbers being bigger or smaller than one another is load-bearing". Right below it, a user points out that the bar highlighted as the winner in agentic coding scored 53.4% against the competitor's 53.5%, and sums it up: "Typical Anthropic math".

I went to verify that specific accusation, and it does not hold. Both numbers exist — they are FrontierCode v1.1 Main, in the eighth row of the table above. Except the highlight sits on Fable 5's 53.5%, not on Opus 5's 53.4%. The table marks the competitor as the winner in five of the eleven rows, including one where the winner is GPT-5.6 Sol. It is not a chart that hides defeats; it is a chart that puts its defeats in the spotlight.

The skepticism remains well calibrated — a vendor's chart is marketing material, even when the numbers are right, and the habit of checking is the right one. But the result of the check deserves the record: this time the material held up. What did not hold up was the version that circulated about it.

And there is the fatigue, which also surfaced at the top of the thread: "I'm tired boss". It is July 2026 and this is Anthropic's fifth frontier model in a few months — Opus 4.7, Opus 4.8, Sonnet 5, Fable 5, now Opus 5. There is a human cost to re-evaluating prompt, effort, cost and limits every six weeks, and it enters no benchmark.

The top-of-the-line paradox

The most interesting point in the discussion was not the chart; it was a naive question from one user: if Opus 5 is almost as good as the top of the line, why is the top of the line treated as an elevated-risk model while this one ships as a normal release, on the Pro plan?

The answer is in the announcement itself, and it is more specific than I expected. Opus 5, Anthropic says, "does not advance the frontier in dangerous dual-use capabilities" and trails Mythos 5 — Fable 5's sibling, restricted to a closed program — in biology research and in offensive cybersecurity. The decisive detail is how that "trails" is distributed: at identifying a vulnerability, Opus 5 is described as similar to Mythos 5; at exploiting it, it falls behind.

That is an engineering choice, not an accident — and it is the most plausible explanation for the release being cheap and broad: the two capabilities were separated. Finding the flaw and producing the exploit no longer travel together. If that turns out to be reproducible, it is a more important result than any percentage point of benchmark.

With one caveat the marketing does not make: "normal release" does not mean release without a lock. The model ships with elevated cybersecurity safeguards and with classifiers that refuse requests — as the benchmark chart's footnote shows without meaning to.

What I would do with this

I will not pretend I tested the model in production four hours after launch. What can honestly be said is where I would look first:

Effort became the real lever. With five levels and a reasonable default (high), the variable that decides cost, latency and quality stopped being "which model" and became "how much effort on this route". Anthropic's own recommendation is to start at xhigh for code and agent work, high for the rest — and then sweep downward, because low and medium are surprisingly strong on this model. The chart above shows why, and it also shows that the top of the ladder is not the best place on the ladder.

Before swapping the model string, audit four things: routes that never set thinking (max_tokens can truncate now), routes that combine disabled reasoning with xhigh/max effort (they turn into 400 errors), the rate-limit sizing in the new bucket, and the handling of stop_reason before reading the response content.

And delete the double-check instructions. This one is counterintuitive: the migration documentation recommends removing from prompts instructions like "verify your work before answering". Opus 5 already self-verifies, and telling it to verify again produces rework with no gain. By the same logic, anyone with an instruction telling the model to delegate more to subagents should drop it: Opus 5 delegates more than 4.8 did, and the problem now is the excess.

And wait for the third-party test. What decides whether Opus 5 is what it says it is is not the taller bar or the honest table; it is the cost per completed task on your own code, measured by you, a week after the hype passes.

Sources

• Official announcement: anthropic.com/news/claude-opus-5
• Community discussion: r/ClaudeAI — Introducing Claude Opus 5
• Independent coverage: VentureBeat · Decrypt · The Decoder

Price, context, API behavior and limits verified against the official documentation on Jul 24, 2026. The benchmark table's numbers were transcribed from the announcement's figures; the cost curve's were read visually off the chart and are marked as approximations in the text. I did not re-verify the Reddit thread's vote counts.