Claude Pro does not include Fable 5.1 in its normal usage allowance. Claude Max does—but the “50% cap” is a ceiling inside Max's existing weekly allowance, not 50% more usage. That distinction decides whether your next Fable request is covered by the subscription or starts consuming paid usage credits.
Anthropic's current Fable plan guide, checked September 3, 2026, gives the following rules:
| Account type | How Fable 5 and 5.1 are paid for | What happens at the boundary |
|---|---|---|
| Max 5x or Max 20x | Included in the regular weekly pool; Fable models may consume up to 50% of that pool | Switch to another model within remaining plan usage, or continue with usage credits |
| Premium seats on Team or legacy seat-based Enterprise | Same included 50% Fable share, subject to organization controls | Switch models or use organization-enabled credits |
| Pro or Team Standard | Usage credits from the first Fable request | The prepaid balance and spend controls determine continuation |
| Standard seats on legacy seat-based Enterprise | Usage credits from the start, if the organization enables them | No enabled credits means no metered Fable access |
| Usage-based Enterprise or Claude API | Metered at standard API rates | Organization or project billing controls spend |
Fable 5.1 is available only on paid Claude plans. If you are on Free, upgrading is a prerequisite; a model-picker refresh will not unlock it.
The 50% cap is not a second bucket
On Max and eligible Premium seats, Fable and the other Claude models draw from the same regular weekly allowance. The Fable-specific meter stops Fable models from taking more than half of that allowance at no extra cost. It does not add another half on top.
Suppose the weekly allowance is represented as 100% in Settings > Usage. If Fable models consume 40 percentage points and other models consume 25, total plan usage is 65%. Fable can still use at most another 10 percentage points of included usage. The remaining plan capacity can be used by another Claude model, but it is not another 50 percentage points available to Fable.
Do not convert that illustration into a token promise. Anthropic does not publish a fixed consumer-plan token allowance. Model choice, effort, conversation history, files, tools, and product features affect how quickly the meter moves. Anthropic also says Fable models use the plan limit faster than other Claude models, without publishing one universal conversion rate.
The weekly reset does not happen when you subscribe, upgrade, or begin a Fable session. Pro and Max accounts receive an assigned weekly reset day and time. Your actual next reset appears in Settings > Usage. A separate five-hour session limit can also stop work before the weekly counter reaches 100%.
Pro starts with paid credits; Max starts with included usage
For Pro, the practical question is not “How much of my weekly Pro limit can Fable use?” The answer is none: Fable 5 and Fable 5.1 use pay-as-you-go credits from request one. You must enable usage credits, add funds, and accept the metered path before using the model.
For Max, first use the included Fable share. When the Fable meter reaches its 50% ceiling, you can switch to a different model and keep using whatever remains of the shared plan allowance. If you need Fable specifically, you can continue through usage credits after the product warns you that metered billing will begin.
This is also why two screenshots can appear to disagree. A Pro user can have plenty of ordinary weekly allowance left but still pay for every Fable request. A Max user can have ordinary weekly allowance left but be blocked from further included Fable use because the Fable sub-limit is full.
If your real decision is whether the larger subscription pays for itself, compare measured interruption and credit spend in the Claude Pro versus Max guide. Max buys capacity and included Fable access; it does not create unlimited use or guarantee that Fable is economical for every task.
What a metered Fable 5.1 task costs
Usage credits are prepaid account value charged at standard API rates. They are separate from your subscription fee and from credits held in a Claude Console API organization. Anthropic's Fable 5.1 model page currently lists:
- base input: $10 per million tokens;
- output: $50 per million tokens;
- five-minute cache write: $12.50 per million tokens;
- one-hour cache write: $20 per million tokens;
- cache read: $0.25 per million tokens.
The uncached base calculation is:
textcost = input_tokens / 1,000,000 × $10 + output_tokens / 1,000,000 × $50
A run with 50,000 input tokens and 10,000 output tokens costs about $1.00 before cache writes, regional settings, taxes, or third-party platform charges. That is a billing example, not a “messages per dollar” promise: a long agent session can reread context, call tools, retry, and produce multiple outputs.
Fable 5.1 keeps Fable 5's $10/$50 base rate but cuts cache reads from Fable 5's $1 to $0.25 per MTok. Do not apply the new cache-read price to Fable 5 logs. The full Anthropic pricing table also lists a 50% Batch API discount on input and output. Batch pricing belongs to API workloads; it does not enlarge a Pro or Max weekly allowance.
Anthropic recommends starting most workloads on Opus 5 and choosing Fable 5.1 for demanding reasoning or long-horizon agentic work when a cheaper route falls short. That is a useful spending boundary. If Opus or Sonnet passes your tests, the higher-priced model has not earned the extra meter draw merely by being newer.
The July promotion does not apply to Fable 5.1
Older articles and screenshots describe a promotion that put Fable 5 inside paid plans for up to 50% of weekly usage. That promotion ended July 19, 2026 at 11:59:59 PM Pacific and covered Fable 5 only.
Some eligible Pro and Team Standard accounts received a one-time transition credit when Fable 5 moved to usage credits. Fable 5.1 was never part of that promotion and has no equivalent launch credit. Treat any balance that still appears in your account as account-specific value with its displayed expiration; do not plan a new subscription around an expired claim window.
Check these four things before a long run
- Open Settings > Usage in the same Claude account you will use. Confirm the plan or seat type, next reset, Fable meter, credit balance, monthly cap, and auto-reload setting.
- If you use Claude Code, update to version 2.1.250 or later for Fable 5.1 and run
/statusto verify the active account. An API key, gateway, or different login can move billing away from the subscription you inspected. - Run one representative task with a fixed acceptance test. Record the meter or credit balance before and after; do not infer cost from the visible prompt alone.
- Stop or switch models when the remaining budget cannot cover a plausible retry. Raising effort and keeping long context can improve difficult work, but both can consume limits faster.
If Claude Code's billing account is unclear, use the API key versus subscription check before adding funds. If the confusing counter is not Fable-specific, the broader Claude usage-limit guide explains five-hour and weekly reset behavior.
The short answer is stable even when the hidden token allowance is not: Pro pays for Fable 5.1 with usage credits from the start; Max and eligible Premium seats get Fable inside the shared weekly pool, with Fable capped at 50% of that same pool. Verify the meter in your own account before the task, and treat any continuation past the included boundary as a separate spending decision.
