Claude Fable 5 Pricing Guide: $10/$50 & Free Window

TL;DR

Claude Fable 5 is priced at 10 dollars per million input tokens and 50 dollars per million output tokens. That is exactly double Claude Opus 4.8's 5 and 25 dollar rates, but less than half the price of Claude Mythos Preview. From June 9 to June 22, 2026, it is included free on Pro, Max, Team, and Enterprise plans; from June 23 it requires usage credits.

The Numbers

Model

Input per 1M tokens

Output per 1M tokens

Claude Fable 5

$10

$50

Claude Opus 4.8

$25

Fable 5 sits at a 2x premium over Opus 4.8 on both input and output. Compared to its own lineage, though, it is a price cut: Anthropic notes it costs less than half of what Claude Mythos Preview did, while being more capable and far more widely available.

The Free Window: June 9 to June 22

For two weeks after launch, Fable 5 is included at no extra charge on Pro, Max, Team, and Enterprise plans. From June 23, 2026, continued use on those plans requires usage credits. Practical advice for the window:

Run your hardest real workloads, not toy prompts - Fable 5's edge is on long and complex tasks

Benchmark it against your current Opus 4.8 pipelines so you have a like-for-like quality comparison before paying

Capture token counts during trials so you can project post-window costs accurately

API usage is billed at standard rates from day one; the free window applies to the subscription plans.

Is the 2x Premium Worth It?

Per-token price is the wrong unit for agentic work; cost per completed task is the right one. Fable 5 scores 80.3 percent on SWE-Bench Pro versus 69.2 percent for Opus 4.8, and early users consistently report it needs fewer turns. Equinox CTO Luke Anderson put it directly: "Claude Fable 5 delivers more capable engineering in fewer turns than prior models." Lyzr CTO Fabian Hedin went further: "Apps that took a hundred prompts a year ago, it now one-shots."

If a task that took Opus 4.8 three attempts now completes in one, the 2x token premium nets out cheaper. The Stripe early test is the extreme case: a 50-million-line Ruby codebase migration finished in one day instead of an estimated two-plus months of team time. Token costs are a rounding error against that kind of engineering-time saving.