Anthropic now offers two frontier tiers: Mythos-class Fable 5 and Opus-class Opus 4.8. They are closely linked — Fable's safeguards fall back to Opus — but priced and positioned very differently. Short answer: Fable 5 for hard, long, autonomous jobs; Opus 4.8 as the cost-and-latency default.
At a glance
- Class: Mythos vs Opus
- Best for: long-running autonomous work vs strong everyday frontier work
- SWE-Bench Pro: 80.3% vs 69.2%
- FrontierCode: 29.3% vs 13.4%
- Input/output: $10/$50 vs $5/$25 per million tokens
- Context: 1M tokens (Fable) · API ID: claude-fable-5 vs claude-opus-4-8
How big is the gap?
The longer and more complex the task, the larger Fable 5's lead. On short, well-scoped work the two are much closer — why Opus 4.8 remains sensible for high-volume production traffic.
Pricing nuances
- Fable is ~2× Opus on all token types including cache writes and hits
- Token efficiency: Fable often uses fewer turns — net cost gap can shrink on the right tasks
- Safeguard reroutes to Opus are not billed at Fable rates
The fallback relationship
When Fable classifiers flag cyber, bio/chem, or distillation content, Opus 4.8 answers instead (under 5% of sessions). API customers configure this via the Fallback API. Treat the pair as a system, not either/or.
When to use which
Reach for Fable 5 when
- Tasks are long-running or multi-stage (migrations, multi-day agents)
- Quality on hard problems matters more than per-token cost
- Opus has plateaued on complex analysis or high-fidelity coding
Stick with Opus 4.8 when
- Tasks are routine and well-scoped
- Latency or cost per request is the priority
- High volume where 2× pricing compounds quickly
Best pattern: route by task complexity behind one gateway endpoint — hard jobs to Fable, everything else to Opus — with budgets and automatic fallback on errors or capacity limits.