Two numbers came out of the same release on September 1. Anthropic said Claude Fable 5.1 costs up to 45% less than Fable 5. Two days later the r/ClaudeAI megathread’s own summary said Max users were burning the five-hour session limit “in as little as 15-20 minutes.”
Both are true. They are readings from two different meters, and the release moved them in opposite directions.
The Meter That Got Cheaper
The one price change in 5.1 is cache reads: $1.00 per million tokens down to $0.25. Nothing else moved. To see why that one line matters, I pulled ten days of my own Claude Code transcripts and priced every turn at API list rates.
- Fable 5, 8,002 turns: cache reads were 67% of the cost. Cache writes about 20%. Output tokens, the thing everyone calls the monster, 12%.
- Fable 5.1, 1,245 turns: $0.26 per turn against Fable 5’s $0.42. At Fable 5’s cache price the same turns would have cost $0.45.
So the cut saved 43% on my workload, inside Anthropic’s “up to around 45%” for agentic work. An agent re-reads its whole context on every tool call, and that re-reading was two-thirds of the bill. Anthropic cut the line that agentic customers actually pay. That is a real price cut, and a well-aimed one.
Now the sentence around it, from the launch page: the savings apply “wherever usage is billed by token, such as on our API.”
The Meter That Did Not
A Max plan is not billed by token. It is billed in a share of a five-hour window and a weekly cap, and the support article says Fable models “draw from your plan’s regular weekly usage limits and use them faster than other Claude models.” No multiplier is published. The 50% weekly Fable cap from the July settlement is unchanged for 5.1.
And 5.1 uses more. Artificial Analysis ran both models at max effort: Fable 5.1 spent 140 million output tokens on its index where Fable 5 spent 83 million, 1.7 times as many, and cost per task rose from $3.14 to $3.69 despite the cheaper cache. My logs say the same in smaller print: 1,207 output tokens per turn on 5.1 against 990 on Fable 5, 22% more, with cache reads per turn about equal.
On the API, the discount absorbed the appetite. On Max there is no discount to absorb it, so the appetite arrives alone. The megathread has at least six separate reports: 40% of a weekly Max-20 Fable quota in two hours, a five-hour window “in 20 mins,” another “in 30 minutes” on a fresh chat. The most careful one ran two Max-20 accounts:
— r/ClaudeAI, Fable 5.1 megathread, user testing two Max-20 accountsFable 5.1 appears to use substantially more tokens, which are discounted for API but not session, meaning you might have 1/3 to 1/4 the real Fable-minutes that you did yesterday.
Their two data points: a five-subagent fan-out at high effort emptied a window in 16 minutes, and an eight-subagent fan-out in 8. The thread’s most-upvoted question, at 89 points, asked whether the 45% applies to subscriptions. The answer, at 73: “it does not. They snuck it in as ‘wherever usage is billed by token.’”
Where the Tokens Go
The appetite is not mysterious. Anthropic’s prompting guide for 5.1 names three mechanisms, and my transcripts confirm two.
— Anthropic, Prompting Claude Fable 5.1At xhigh and especially max effort, Claude Fable 5.1 can think for longer before it starts writing its reply. When a single request asks for a long deliverable, such as a full rewrite of a long document, it may draft much of that deliverable in its thinking and then write it out again as the reply.
- It drafts twice. The deliverable is written in thinking, then written again as output, both at $50 a million. The guide’s fix is a pasted note telling the model not to. Anthropic’s own advice is to run such requests at high, not max.
- It rewrites whole files. The guide says 5.1 is “more likely than Claude Fable 5 to rewrite an entire text file rather than make a targeted edit.” In my logs, 44% of 5.1’s file operations were full writes against 16% on Fable 5. Small sample, and two of those days created new files by design, but the direction matches.
- Fan-outs multiply it. Eight Fable subagents each re-read their context and each think at Fable rates. Anthropic’s effort docs recommend low effort for subagents. The eight-minute window was eight of them at high.
The counterpoint matters. Every’s Marcus Moretti ran 5.1 at medium effort on a Slack agent and found it “about twice as token-efficient” as Opus 5, doing “the same work on about half the tokens.” At high, Artificial Analysis has 5.1 matching Fable 5’s max score for less than half of max’s cost. The monster lives at the top of the dial. The default is high, and most of the window-in-fifteen-minutes reports came from people who turned it up.
What to Turn Down
The dial post from July still applies. What changed is the reason to touch it. On Fable 5, effort mostly moved output tokens, and output was 12% of cost. On 5.1, output is a quarter of the API cost and, on a subscription, the part that burns.
- Medium for routine work. The guide: at medium, results “roughly match Claude Fable 5 at lower cost.” At low, 5.1 is “often competitive with Claude Opus and Claude Sonnet models on cost per task while scoring higher.”
- Never max for a deliverable. A document, a report, a long file. High is Anthropic’s own recommendation. If you must, paste the guide’s don’t-draft-twice note.
- Fan out on cheaper models. Fable plans, Sonnet or Opus subagents execute at low. The 96%-of-Fable-at-46%-of-price figure was Anthropic’s, and it predates the model that made it urgent.
- Edit, don’t rewrite. One line in your config: rewrite a whole file only when most of it changes. Mine went in on Tuesday.
- Cache hygiene pays only on the API. Change effort per message with the beta header, not at the top level, which restarts the cache. On a subscription this may or may not help, because nobody outside Anthropic knows how the meter weights a cache read.
The subscription meter’s formula is unpublished. Anthropic’s Claude Code plan article says turns after the first are “billed at the much cheaper cache-read rate,” and April’s reverse-engineering of the binary found uncached tokens cost 10 to 20 times more against the quota than cached ones. So cache is discounted on subscriptions, at roughly the API ratio, not free. Whether the meter took the new ratio on September 1 is the open question. If it had, my token mix would burn about 40% slower on 5.1 than on Fable 5. The reports say the opposite, which is the best evidence so far that it did not. The Reddit numbers are self-reported and the loudest ones came from fan-outs at high effort. My per-turn figures compare different days of different work, and a turn is not a task. And on September 14 the weekly limit drops 17% from today’s level for everyone, Fable or not.
One Release, Two Prices
Tomorrow’s post argues that on a flat subscription the limit is the price. This release proves it from the other side. Anthropic moved the price twice on September 1: down 75% on the line that dominates API bills, and up by whatever 1.7 times the output tokens costs against a window that never sees the discount. It announced the first in the headline and the second in a subordinate clause.
If you pay by token, 5.1 is the cheapest Fable has been. If you pay by the month, it is the hungriest, and the only discount you control is the dial.



