Claude Fable 5.1's base price did not move. It still bills $10 per million input tokens and $50 per million output, exactly as Fable 5 did. What changed is that cache reads now cost a quarter of what they used to, and for anyone running long agent sessions that single change is worth more than a headline price cut would have been. A developer who analyzed 22,022 of their own API calls over 21 days found their cost per prompt fell roughly 31% even as tokens per prompt rose 31%.
Key facts
- Fable 5.1 keeps Fable 5's $10 input / $50 output per million tokens; only cache-read pricing changed.
- Anthropic's pricing documentation bills cache hits at 10% of standard input, with five-minute cache writes at 1.25x base input and one-hour writes at 2x.
- One developer's measurement across 22,022 API calls over 21 days: about 31% cheaper per prompt, 31% more tokens per prompt.
- Primary source: the Claude Fable 5.1 overview.
To see why this matters, you have to know what a cache read is. When you send a long prompt to a model, the model has to process every token of it before it can write a single word of response. If you send nearly the same prompt again, that work is wasted. Prompt caching lets the provider store the processed state of a prompt prefix and reuse it, so the second call skips straight to the new part. The saving is real compute, not a discount, which is why providers bill cached tokens at a fraction of fresh ones.
Now think about what an agent session looks like. A coding agent working on a repository holds the same system prompt, the same tool definitions, and a growing conversation history across dozens or hundreds of turns. Almost every call re-sends a prefix the model has already seen. Under Fable 5's pricing that prefix was cheap. Under 5.1's it is very cheap. A short, one-off API call, by contrast, has no reusable prefix at all and gets exactly nothing from the change.
The clearest independent evidence came from a developer posting under the name tenequm in the r/ClaudeAI community, who pulled three weeks of their own billing data and found the counterintuitive result: more tokens, lower bills. Their explanation was blunt: "almost all of the extras are cache reads and 5.1 bills only 25% of price per cached-read tokens compared to what Fable 5 priced." That is a single workload and it should be read as one data point, not a general law. But it is a data point with 22,022 calls behind it, which is more than most launch-day cost analyses have.
The most useful thing in Anthropic's own documentation is the part that argues against using the newest model. On the Fable 5.1 overview page, Anthropic says most workloads should start with Opus 5 and reserve Fable 5.1 for demanding reasoning and long-horizon agentic work. Model vendors rarely tell you to use the older model, and this is a cleaner counter to the launch-day hype than any skeptic's blog post. The customer testimonials Anthropic published point the same direction: lower cost per task, better code review, better readability over long runs, stronger unattended multi-step work. Every one of those is a claim about long sessions.
There is a second cost trap that the pricing page does not surface. Anthropic's plan documentation says Max and premium Team and Enterprise users can spend up to 50% of their weekly limit on Fable models at no extra charge. That is a ceiling on a shared budget, not extra headroom, and it is a common source of confusion. A model that got cheaper per cached token can still exhaust a weekly allowance faster if it is also being pointed at longer jobs.
The honest caveat is about quality, not price. A thread in r/ClaudeAI collected users reporting instruction-following regressions, invented terminology, and answers compressed to the point of being unhelpful, with several replies recommending a fall back to Opus 4.8 or Sonnet. That is a real signal about day-to-day usability, and it is worth weighing against the billing math. It is also, strictly, a separate question. Nothing in those complaints challenges the pricing analysis; a cheaper cache read on a model you do not want to use is not a saving.
So the practical rule is short. If your work is long-lived sessions with heavy prefix reuse, your invoice can genuinely drop, and you should check whether your caching is actually configured before assuming it did. If your work is short, independent API calls, nothing about your costs changed on this release. The model did not get cheaper. Repetition did.
Originally published on Ground Truth, where every claim is checked against the primary source.
Top comments (0)