Claude Fable 5.1 now sits above Opus 5 at exactly twice the base input and output token rates. It also cuts cache reads by 75 percent, improves Anthropic’s science and agent benchmark results, and changes which long-running jobs can plausibly earn the premium.
The routing decision is no longer the original Fable 5 launch question. Opus 5 remains the cheaper default for difficult work. Fable 5.1 is the escalation tier for science, long autonomous sessions, or workflows where a better completion rate covers the extra bill after cache savings and human repair time.
This article preserves the original Opus 5 comparison and adds the September 1 Fable 5.1 evidence. The useful question remains the same: where does the frontier tier produce a measurable outcome that the cheaper model does not?
Anthropic squeezed a lot of Fable into the Opus price
Opus 5 is now the default model on Claude Max and the strongest model offered on Claude Pro. Developers can call it with claude-opus-5. It has a 1 million-token context window, can return up to 128,000 tokens in one response, and has a May 2026 reliable knowledge cutoff.
Those specifications are already serious. The launch table is where the product line gets uncomfortable.
On Frontier-Bench v0.1, which Anthropic describes as agentic terminal coding, Opus 5 scored 43.3%. Fable 5 reached 33.7%, GPT-5.6 Sol 34.4%, and Opus 4.8 21.1%. On GDPval-AA v2 knowledge work, Opus 5 led the same group with 1861.
| Model | Mean reward |
|---|---|
| Claude Opus 5 | 43.3% |
| GPT-5.6 Sol | 34.4% |
| Claude Fable 5 | 33.7% |
| Claude Opus 4.8 | 21.1% |
ARC-AGI-3 is the wild-looking result: 30.2% for Opus 5, compared with 7.8% for GPT-5.6 Sol and 1.5% for Opus 4.8. Fable 5 was not reported in that row, so it would be wrong to turn this into an Opus-versus-Fable win.
There are more:
- Opus 5 scored 90.8% on BrowseComp, just ahead of GPT-5.6 Sol at 90.4%.
- It reached 70.6% on OSWorld 2.0, ahead of Fable 5 at 66.1%.
- It posted 26.0% on AutomationBench, while the next result in Anthropic’s table was GPT-5.6 Sol at 18.1%.
- On Humanity’s Last Exam with tools, Opus 5 scored 64.7% and Fable 5 scored 63.9%.
These are Anthropic-published launch evaluations, not independent MustHave.ai testing. Some also depend on effort settings, tools, harnesses, and fallback behavior. I would use them to choose which models deserve an internal trial, not to skip that trial.
This is not a clean sweep
The same table contains the reasons not to delete Fable from your router.
Fable 5 edged Opus 5 on DeepSWE v1.1, 69.7% to 68.8%. GPT-5.6 Sol led that row at 72.7%. Fable also beat Opus by a tenth of a point on FrontierCode v1.1 Main, 53.5% to 53.4%, and led the held-out Legal Agent Benchmark, 13.3% to 11.7%.
Without tools, Fable scored 56.5% on Humanity’s Last Exam and Opus scored 56.3%. In health, Mythos 5 led HealthBench Professional at 66.0%, while Opus 5 reached 59.8%.
That pattern matters. Opus 5 looks like the better default, but a default is not a universal winner. If your business depends on one narrow task, the average benchmark story is almost irrelevant. Your own pass rate is the benchmark.
This is the same discipline I recommend in our guide to choosing an AI model without losing a weekend to benchmarks: test the work you actually sell or ship, include failure cases, and count the human repair time.
The real control knob is effort
Anthropic is not presenting Opus 5 as one fixed cost-performance point. The model can spend different amounts of effort on a task, and the launch charts plot quality against cost at those settings.
That changes how I would deploy it. I would not send every email draft, classification job, and one-line code edit to maximum effort. Anthropic’s prompting guide says low and medium effort can preserve strong quality with fewer tokens and lower latency. For difficult coding and agentic work, it recommends starting at xhigh, then measuring.
The important word is measuring.
Run the same representative task set at low, medium, high, and xhigh. Record final correctness, tool failures, retries, latency, tokens, and the minutes a human spends repairing the answer. The cheapest setting is the one with the lowest completed-task cost, not the smallest API line item.
Anthropic also says Opus 5 verifies its work without needing the old “check everything again” scaffolding many agent prompts accumulated. Keeping redundant verification instructions can make it over-check and burn tokens. The model may also expand a task’s scope or narrate more than prior Opus releases, so concise scope and response-length rules are worth adding.
That is an unusually practical migration note. A smarter model can cost more because your old prompt tells it to do work it already does by default.
What the 2x price gap means in a real budget
The base API prices are straightforward:
- Opus 5: $5 per million input tokens, $25 per million output tokens.
- Fable 5.1: $10 per million input tokens, $50 per million output tokens; cache reads cost $0.25.
- Sonnet 5: $2 per million input tokens and $10 per million output tokens.
| Tier | Model | Input | Output |
|---|---|---|---|
| High-volume | Claude Sonnet 5 | $2 | $10 |
| Hard-work default | Claude Opus 5 | $5 | $25 |
| Frontier premium | Claude Fable 5.1 | $10 | $50 |
Sonnet 5 pricing was checked again on September 1, 2026.
Take a modest monthly agent workload that consumes 10 million input tokens and 2 million output tokens. Opus 5 would cost $100: $50 in and $50 out. The same base-token volume on Fable 5.1 would cost $200 before cache savings.
That is a $1,200 annual difference for one workload of that size. Ten similar production workflows turn it into $12,000. This is simple arithmetic, not a promise about anyone’s actual bill, but it gives the benchmark debate a useful unit: Fable has to save more than $100 per month in errors, labor, or missed outcomes on that workload.
Fast mode needs its own line in the budget. Anthropic says Opus 5 Fast runs about 2.5 times the default speed, but its token prices double to $10 and $50. That is exactly Fable 5’s base token rate. You are buying speed, not moving up to the Fable capability tier.
For background on why this kind of routing is becoming normal, our recent AI price-war breakdown explains how quickly model families are spreading across price and performance tiers.
The behavior change may save more than the token discount
The strongest part of Anthropic’s launch case is not a chart. It is the claim that Opus 5 keeps working until the job is genuinely checked.
In one reported evaluation, the model had to reconstruct a machine part from an image it could not inspect through the normal visual interface. It built a computer-vision pipeline to extract the geometry from pixel data, then created the part in FreeCAD. In another case, it found the root cause of a real package-manager bug and caught an edge case missed by an existing community patch.
Anthropic also describes an engineer asking Opus 5 to build a market-data feed for a new exchange. With no live feed available, the model created a test harness to validate its parser.
These are hand-picked vendor examples, so I would not treat them as a reliability guarantee. They do point at the right evaluation target: does the agent find a way to prove its own work, or does it stop when the output merely looks finished?
For builders, I would test four things:
- Give Opus 5 the full task, the completion criteria, and the tools it needs.
- Remove repeated verification instructions unless your eval shows they still help.
- Put a hard boundary around scope, permissions, and what the agent must not change.
- Score the evidence it returns alongside the final answer.
That is also why our plain-English guide to agentic AI focuses on the job boundary and proof of completion rather than the “autonomous” label.
Safety here is a routing system, not one big refusal switch
Anthropic reports that Opus 5 scored 2.3 on its automated behavioral audit for overall misaligned behavior, the lowest result among its recent models. The company says it followed Claude’s Constitution more consistently, showed less deceptive behavior, and was harder to trick into misuse than Opus 4.8, Sonnet 5, or Fable 5.
That is an Anthropic assessment, not a neutral certification. Still, the implementation details are worth understanding.
Anthropic says it deliberately avoided cyber-specific training for Opus 5. General capability gains still made it much better at finding software vulnerabilities, where it approaches Mythos 5. It remains well behind Mythos at turning those findings into working exploits.
The cyber classifiers reflect that split. They allow source-code vulnerability discovery, while blocking binary-based scanning, penetration testing, and exploit generation. Anthropic expects those classifiers to intervene about 85% less often than Fable 5’s classifiers.
If a request is flagged in Claude.ai, Claude Code, or Claude Cowork, it falls back to Opus 4.8 by default. API users can opt into automatic fallbacks. Anthropic also launched mid-conversation tool changes that do not invalidate the prompt cache, which should make it easier to tighten or expand an agent’s tool set as the job changes.
There is another operational difference hiding below the benchmarks: Opus 5 has no general-access data-retention requirement. Fable 5 requires 30-day retention and is not available under zero-data-retention arrangements. For some enterprise workloads, that policy decides the route before a benchmark does.
Update: Fable 5’s biology fallbacks dropped sharply
Update, August 8, 2026: Anthropic says classifier changes have reduced biology-related fallbacks across its products by about 85% compared with Fable 5’s launch. More ordinary health, education, and clinical questions should now stay on Fable instead of dropping to Opus.
This is a company-reported product result, not an independent benchmark. It also does not mean the biology boundary disappeared. Anthropic says professional or dual-use work in areas such as virology, toxicology, molecular design, and drug development may still fall back to Opus 5.
| Surface | Expected reduction | Read carefully |
|---|---|---|
| Claude.ai | About 67% | Estimate covers total fallbacks, not biology alone. |
| Cowork | About 55% | Workflow context can still trigger routing. |
| Claude Code | About 17% | Repositories can contain technical material that keeps the boundary relevant. |
| Claude Platform | About 7% | API behavior depends on configured fallback handling. |
The surface-level percentages are not another way of stating the 85% biology figure. Anthropic describes them as expected reductions in all fallbacks after the classifier update. Mixing those denominators would make the improvement look more uniform than the company reports.
The routing recommendation below therefore changes only at the margin. Fable should be less frustrating for benign biology-adjacent work, especially in Claude.ai. Teams doing consequential scientific work still need to log when a fallback occurs, rerun their own representative tasks, and avoid assuming the answer came from the model they originally selected.
Read Anthropic’s biology safeguard update. Reddit users reported that some previously blocked tasks began working, but those posts are anecdotal observations, not a substitute for the company’s product documentation or independent testing.
Update: Fable 5.1 keeps the premium price and changes the evidence
Update, September 1, 2026: Claude Fable 5.1 replaces Fable 5 as Anthropic’s generally available frontier tier. It keeps the $10 per million input-token and $50 per million output-token rates, a 1 million-token context window, and a 128,000-token maximum output. The API model ID is claude-fable-5-1.
The important cost change is caching. Cache reads now cost $0.25 per million tokens, 75 percent below Fable 5. Anthropic estimates that the lower rate reduces typical token-billed workloads by about 25 percent and highly agentic workloads by as much as roughly 45 percent. Your result depends on how much stable context can actually be reused.
| Fable 5.1 field | Current value | Routing implication |
|---|---|---|
| Base input and output | $10 and $50 per million tokens | Still twice Opus 5’s base rates |
| Cache reads | $0.25 per million tokens | Long stable contexts can narrow the effective gap |
| Context and output | 1M context, 128K maximum output | Capacity matches the large-workflow tier |
| Thinking | Adaptive thinking is always on | Benchmark and cost tests need the production effort setting |
Anthropic reports 52.6 on Terminal-Bench-Science 0.1, compared with 29.0 for Opus 5 in its setup. The standard error is about 3.5 to 4.5 points per model. Fable 5.1 also leads Anthropic’s published Terminal-Bench 4, AutomationBench, and CursorBench 3.2 comparisons, although safeguard fallbacks and task-version changes complicate several rows.
Adaptive thinking is always enabled. Anthropic says Claude Code defaults to high effort, while Claude, Cowork, and web experiences default to medium. Do not compare a high-effort API run with a medium-effort product run and call the difference model quality.
The routing rule below still holds, but the burden has shifted. Opus 5 remains the lower-cost hard-work default. Fable 5.1 should get science, long-running, or difficult agent jobs where your own evaluation shows a gain large enough to cover the premium after cache savings and human repair time.
My routing recommendation
| Route | Role | Use it when |
|---|---|---|
| Sonnet 5 | Routine volume | High-frequency jobs already meet your quality bar at the lower rate. |
| Opus 5 | Hard-work default | Difficult coding, long documents, computer use, and agentic jobs need careful verification. |
| Fable 5.1 | Prove the premium | Your evaluation shows enough gain to cover the 2× token-price premium and policy permits its use. |
If you are on Opus 4.8, Opus 5 deserves the first migration test. The price is unchanged, the context window stays at 1 million tokens, and Anthropic says existing Opus 4.8 prompts should work well. Do not flip production traffic blindly; re-run your effort sweep and watch for longer narration, broader scope, and extra self-checking.
If you use Sonnet 5, keep it for routine volume that already passes your eval. Opus 5 should earn the harder cases: multi-file coding, long documents, computer use, difficult tool loops, and work where the cost of a plausible-but-wrong answer is high.
If you pay for Fable 5.1, make it defend the premium. Keep it on the few workloads where it wins your tests by enough to offset double the token rate, or where its long-horizon autonomy changes the outcome. Route the rest to Opus 5.
This is how I already think about Claude versus ChatGPT in real work: choose by task, not by team jersey. Opus 5 makes that approach more important inside Anthropic’s own lineup.
Opus 5 is the model that makes routing boring
Fable 5.1 still has a job. Sonnet 5 still has a job. Opus 5 simply takes a much larger share of the middle, including some tasks that no longer look “middle” at all.
That is why this launch matters to me. The useful result is not that Anthropic won another benchmark screenshot. It is that builders can put a near-frontier model on more everyday work without paying the frontier rate every time.
Start with Opus 5 at a sensible effort level. Keep Sonnet underneath it for cheap volume. Let Fable prove where it earns the premium. Then revisit the router when the next model lands, because at this release pace, it will not stay settled for long.
Check the sources before you switch
- Read Anthropic’s Claude Opus 5 launch announcement for its benchmark methodology, safety claims, platform updates, and footnotes.
- Compare current specifications in the Claude model overview.
- Use Anthropic’s Opus 5 prompting guide before migrating an existing agent.
- Check the live Claude API pricing table.
Which workload would you trust to Opus 5 first, and what would Fable have to do better to stay in your router?
Research note: benchmark results, behavioral-audit findings, safety behavior, and launch examples in this article are reported by Anthropic. Prices and model specifications were checked against Anthropic’s documentation on July 24, 2026. The monthly workload calculation is a MustHave.ai example, not a customer case study.
