Blog

Fable 5 pricing, explained: real bills from real requests

If you got the "Fable 5 now runs on usage credits" notification and immediately searched what it actually costs, you are in good company. Here is the straight answer, in dollars per request rather than dollars per million tokens, with every bill measured rather than estimated.

By the Unbiased Team · published July 28, 2026 · updated July 30, 2026 · prices and bills last verified July 28, 2026

Skip the read: get a measured recommendation in a few quick questions. Run the Stack Finder

Claude Fable 5 costs $10 per million input tokens and $50 per million output on the Anthropic API as of July 2026, exactly double Claude Opus 5. Cache reads bill at 10% of the input rate, the Batch API halves both sides, and inside Claude apps Fable 5 now draws usage credits.

How much does Fable 5 cost?

Claude Fable 5 is Anthropic's Mythos-class model, the tier above Opus. On the API it costs $10 per million input tokens and $50 per million output tokens, with prompt-caching discounts on input (Anthropic's pricing page; independent trackers pricepertoken and espressio agree). That is exactly double Claude Opus 4.8's $5 / $25 list.

The confusion is not the rate. It is the July change: Fable 5 moved out of subscription plans and onto usage credits (TechTimes). If you were using it inside a Pro or Max plan, you are now metered. Same model, new meter.

Two levers cut the list price if your workload fits them: prompt-cache reads bill at 10% of the input rate, so a heavily-cached Fable prompt reads at $1 per million input tokens, and the Batch API takes 50% off both sides for asynchronous jobs, which puts batched Fable 5 at $5 / $25, exactly Opus prices (pricing guide). If your Fable workload can wait an hour, that is the cheapest legitimate way to run it.

Fable 5 vs Opus, GPT-5.6, and the rest of the market

Pricing questions are comparison questions. Here is the whole ladder as of July 28, 2026, with each model's list price applied to the same concrete job: the dashboard-generation request we measure below, 77 tokens in and 2,615 out (Anthropic prices, OpenAI prices).

Method: the same token counts priced at each list rate. Real models tokenize and elaborate differently, so treat the column as a price-sheet comparison, not a bake-off. The Pareto row is the one measured bill.

Read the ladder honestly and two things are true at once. Fable 5 is the most expensive API on the market, at 1.7x OpenAI's frontier tier on output. And the volume tiers near the bottom are genuinely cheap: if Haiku-class quality clears your bar for a workload, list price already solves your problem. The expensive mistake is the middle: paying Fable or Sol rates on traffic that a cheaper tier, or a blended model, handles at the same quality. Quality per dollar is the actual question, and that needs receipts rather than a price sheet, which is why we publish benchmark-by-benchmark cost per task.

Test 1: "Build a sortable invoice dashboard"

Nobody thinks in tokens, so we sent the identical prompt to each model and kept everything: the untouched first response, the token counts, and the actual metered bill. One shot, single file, no retries.

Fable 5 via the Anthropic API at list price. Pareto billed at cost. Same prompt, verbatim, 2026-07-28.

Both produced a working, styled, sortable dashboard on the first attempt: summary cards, status badges, click-to-sort. Do not take the screenshots' word for it. These are the live outputs, exactly as returned:

Test 2: "Build me a game"

Same protocol, more ambitious ask: a complete Breakout game with paddle physics, five rows of bricks, lives, win and game-over states, and a restart button.

Play them both. You are playing the two-cent one second:

The honest trade

Look at the time rows: Pareto was cheaper by 7 to 10x on these one-shot generations, and slower by roughly 2x. If you are optimizing wall-clock latency on a single interactive request, Fable 5 wins the stopwatch here. If these requests run thousands of times a day in a pipeline, the arithmetic flips: at 1,000 dashboard-sized generations per day, the difference is $146 a day versus $20 a day, about $46,000 a year, on one workload.

What a real Claude Code session costs on Fable 5

One-shot prompts are not why your credits vanish. Agentic coding sessions are. So we ran one for real: Claude Code, model pinned to claude-fable-5, pointed at a small Python repo with two seeded bugs and a failing test suite, instructed to fix them. It read the code, found both bugs, edited the file, re-ran the tests, and finished in 39 seconds and 5 API calls. Every request, from the actual transcript:

Measured 2026-07-28, Claude Code headless, max 15 turns, no retries. Rates: $10/M input, $50/M output, cache reads $1/M, cache writes $12.50/M.

Scale it: an engineer who runs twenty sessions like this in a day is spending about $12 a day, roughly $260 a month, on a toy-sized repo. Real repos carry far more context per read, and context is the meter. If your credits are draining, this table is why: it is almost never the answer tokens, it is the reading.

Reproduce this yourself

Numbers you cannot check are marketing. Everything above is one API call away from verification: same prompts, default settings, no retries, measured 2026-07-28. Fable 5 was called as claude-fable-5 on the Anthropic API at list price.

The raw outputs are hosted unmodified (the embeds above are the actual files), and the broader benchmark methodology, with pinned dependencies, is in the public evaluation harness. If your run disagrees with ours, publish it.

Everyday tasks, same pattern

Code generation is the expensive end. We metered four ordinary production tasks the same way: invoice-to-JSON extraction came to $0.0148 at Fable 5 list versus $0.0018 on Pareto; a unit-economics analysis $0.026 versus $0.0033; meeting-notes summarization $0.013 versus $0.0016. A useful rule of thumb: a code-generation request lands around a dime to a quarter on Fable 5; short structured tasks a penny or three. Multiply by your daily volume and the credits notification starts making sense.

What would your traffic cost?

Is Fable 5 worth 2x Opus?

For some workloads, genuinely yes. Fable 5 is the strongest generally available model on the hardest reasoning problems, and when a task fails on cheaper models and succeeds on Fable, it is worth every cent. Failed cheap runs are the most expensive tokens you can buy. But most production traffic is not the hardest reasoning problem, and paying the frontier premium on every request means paying it on the many requests that did not need it.

Will Fable 5 get cheaper? The price history says probably.

People are literally searching this question, so here is the pattern instead of a shrug. Anthropic's flagship-tier pricing over the last two and a half years:

Sources: Anthropic's Opus 4.5 announcement, the 67% cut documented, Opus 5 launch coverage.

The pattern: frontier capability holds a premium price while it is scarce, then reprices sharply once a newer tier sits above it and serving costs mature. Opus-class intelligence cost $75 per million output tokens for twenty months, then $25 overnight. Fable 5 occupies the position Opus held in 2024 and 2025: the top of the ladder, priced for scarcity.

Our honest read, dated July 28, 2026: do not architect around today's $10/$50 as permanent. If history rhymes, the price drops when the next Mythos-class model ships above it, and the interim discounts (caching, batch) are how Anthropic lets cost-sensitive workloads in early. What we would not do is wait: if Fable-class quality clears a bar cheaper tiers cannot, the price of waiting is the failed runs in the meantime.

Fable 5 pricing questions, answered

A Fable 5 and Opus alternative