Claude Fable 5 Usage Credits: What Changes After July 19
Claude Fable 5 Usage Credits: What Changes After July 19
Claude Fable 5 is back, but the return has an expiry date hidden inside it.
Anthropic restored global access on its main first-party surfaces on July 1 after the model's abrupt June suspension. For Pro, Max, Team, and eligible legacy Enterprise seats, the company also opened a temporary subscription allowance. That promotion now ends July 19, 2026 at 11:59:59 PM Pacific Time. After it ends, Fable 5 is no longer included in those plans' weekly usage limits. Continuing with the model requires separately billed usage credits.
That is more than a pricing footnote. It changes the product contract from "this model is part of my plan" to "my plan gives me a surface where I can buy metered access." The button may remain. The model picker may remain. The billable boundary changes.
There is also a genuine documentation trap. Anthropic's June 30 redeployment post still says the promotion runs through July 7. Its newer Help Center article says the offer was extended through July 19 and repeats the precise cutoff several times. As of July 17, the current Help Center article is the source to use for the promotion deadline; the older news post remains useful for the suspension and restoration chronology.
This is not another Fable capability review. We already covered what Fable and Mythos changed and why the shutdown exposed an infrastructure risk. This update is about the access regime that followed: who gets included usage, who pays from the first token, what "usage credits" actually means, and why prompt caching does not undo the model's 30-day retention requirement.
The access event is shared; the billing result depends on the plan architecture underneath it.
The date conflict is real, but it is resolvable
Fable's public history now has four operational dates:
The June 30 redeployment announcement records the original offer through July 7. Anthropic's newer Fable 5 promotional-access guide says the promotion was extended through July 19 at 11:59:59 PM PT. The Help Center page is marked as updated this week and repeats the July 19 cutoff in its note, promotion section, post-promotion section, and FAQ.
That hierarchy matters. A news post is a durable record of what Anthropic announced on June 30. A live support article describes the current commercial behavior. The right editorial move is not to erase the discrepancy; it is to show why one date supersedes the other.
One more date trap is worth calling out. Some developer documentation still presents Fable as generally available from its June 9 launch. That is reasonable for a model-introduction page, but it is not a service-status history. The restoration post is the better source for the June 12 interruption and July 1 return.
The promotion's “50%” is a ceiling, not free extra capacity
Anthropic's wording is precise: during the promotion, eligible users can spend up to 50% of their weekly subscription limits on Fable 5 at no extra charge.
That does not mean Anthropic added a separate half-week of Fable capacity on top of the normal plan. Fable draws from the same regular weekly pool as other Claude models. Anthropic also warns that Fable uses that allowance faster than other models.
Think of the promotion as two overlapping constraints:
Suppose a user's other-model activity has already consumed half of the weekly allowance. That user has only the remaining half available overall, even though the promotional Fable ceiling is also 50%. If the user reaches the Fable ceiling first, they may still have regular plan capacity for another model.
After July 19, the Fable-specific included share disappears. The general subscription may still include other Claude usage, but Fable itself moves to credits.
Who pays, and when?
The model name alone no longer tells you the billing behavior. Plan architecture does.
The promotion guide is the source for the Fable-specific rows. Anthropic's Enterprise billing guide explains the larger contract change: all new Enterprise plans use a single usage-based seat. The annual seat fee provides access to web, desktop, mobile, Claude Code, and Cowork, but includes no usage. Every token is a separate metered charge.
Legacy Standard and Premium seat types are no longer offered for new Enterprise contracts and are moving to the single Enterprise seat at renewal. That is why two companies that both say "we have Claude Enterprise" can get different answers about Fable.
Usage credits are a second meter attached to the product
For Pro and Max users, usage credits are configured on the web under Settings → Usage. The user adds a payment method, enables credits, prepays funds, and chooses a monthly limit or unlimited spending. Auto-reload can buy more funds when the balance falls below a chosen threshold. Anthropic lists a daily redemption limit of $2,000.
The generic usage-credit feature normally begins after a plan's included usage is exhausted. Fable after July 19 is the important exception in practice: the Fable-specific support article says the model is no longer included in weekly limits, so continuing on Fable requires the credit meter even if the subscription still has included capacity for other models.
For Team, an Owner or Primary Owner enables credits, prepurchases the shared balance, chooses which users can consume it, and sets organization or user limits. For legacy seat-based Enterprise, credits are billed monthly in arrears based on actual use, with controls at organization, seat-tier, group, and user levels.
Anthropic warns that a request can slightly overshoot a spend limit. Eligibility is checked before a request runs; the final token cost is known only after processing. The next request is blocked, but the request that crosses the threshold can finish above it.
For current Enterprise, “usage credits” may describe the prepaid pool on self-serve plans, but it is not overflow from an allowance. There is no allowance. Self-serve Enterprise draws every request from a shared prepaid balance; sales-assisted Enterprise meters the same usage into a monthly invoice. AWS Marketplace purchases are invoiced in arrears like sales-assisted plans.
Pro and Max users prepay on the web, set a monthly cap, and can choose auto-reload. A mobile subscription does not let you configure the credit feature inside the mobile app.
Owners buy the balance and govern access. One person's long Fable session can reduce the shared pool available to everyone else.
Standard seats receive no promotional Fable allowance. Premium seats do, but only through July 19; both need organization-enabled credits afterward.
The seat buys access to the product surface, not included inference. Every model request is billed separately, and Fable sits at the high end of Claude's generally available rate card.
Anthropic also sells discounted usage bundles for Pro, Max, and Team: $50 of credit for $45, $250 for $200, or $1,000 for $700. Those are 10%, 20%, and 30% purchase discounts. Individual subscribers can buy up to $2,000 in discounted bundle value per month; Team organizations can buy up to $3,000. Usage beyond those bundle caps returns to standard rates.
That discount changes the effective amount paid for a credit balance, but it does not change the model's metering units. The dashboard still needs a token-aware budget.
The API rate is the reference unit, not the whole bill
Anthropic says usage credits are billed at standard API rates. For Fable 5, the current API price sheet is:
The simple formula is:
cost = (uncached input ÷ 1,000,000 × $10)
+ (cache-write input ÷ 1,000,000 × write rate)
+ (cache-hit input ÷ 1,000,000 × $1)
+ (output ÷ 1,000,000 × $50)
× applicable geography multiplier
If a Fable request processes 100,000 uncached input tokens and generates 10,000 output tokens, the illustrative first-party global cost is $1.50: $1.00 for input plus $0.50 for output. If the same 100,000-token prefix is a valid cache hit, that input portion falls to $0.10, making the request $0.60 before any other feature charges.
That example is deliberately narrow. Real Claude and Claude Code sessions can include growing conversation history, project files, tool definitions, tool results, screenshots, server-tool charges, retries, and fallback behavior. The chat interface does not expose a neat one-prompt-one-price abstraction.
The tokenizer can move the bill before behavior changes
Fable uses Anthropic's newer tokenizer. The pricing documentation says the same text produces approximately 30% more tokens than with models on the previous tokenizer, with the exact increase depending on content and workload shape.
This creates an easy budgeting error. A team migrates a fixed prompt from an older model, multiplies the old token count by Fable's list price, and assumes it has a forecast. Even if output quality and request count stay constant, the billed token quantity can be higher.
Use Anthropic's token-counting endpoint with the Fable model ID on representative production payloads. Count the complete request shape, including system text, tool schemas, files, images, and conversation history. Then compare total task cost, not only the per-million-token label.
This is the most important cost insight in the update:
A price per token is not a price per workload when the tokenizer changes.
Prompt caching helps repeated context, not every expensive session
Prompt caching is compelling at Fable rates. A five-minute cache write costs 1.25 times normal input and a one-hour write costs 2 times normal input. A hit costs 0.1 times normal input. Anthropic says a five-minute cache pays back after one hit; a one-hour cache pays back after two hits.
That works well for stable, repeated prefixes:
- a large system prompt shared across many requests;
- a codebase or document set queried repeatedly;
- tool definitions reused by an agent loop;
- a long conversation prefix followed by several continuations.
It does not turn every long task into a cache hit. The repeated portion must match the cache rules, and the cache must still be alive. A one-off 500,000-token analysis has no second read to discount. A frequently changing prefix can keep paying write prices.
Batch and cache discounts can stack, and the US-only multiplier can stack on top of both. That is useful for non-interactive evaluation or document pipelines, but it is not the billing behavior of an ordinary live subscription chat.
The 30-day retention term survives every billing route
Anthropic designates Fable 5 and Mythos 5 as Covered Models. Its API and data-retention documentation says both require 30-day retention and are not available under zero-data-retention arrangements.
On the direct Claude API, a request from an organization or workspace that has not enabled the required retention returns a 400 invalid_request_error. An organization with a ZDR agreement can opt a specific workspace into 30-day retention while leaving other workspaces on ZDR. That makes a separate Fable workspace a practical governance boundary.
Anthropic's Covered Models support article says prompts and outputs are retained for 30 days on every platform where covered models are offered. For direct Claude API and Claude Platform on AWS, Anthropic handles the retained data. On Amazon Bedrock and Google Cloud's Agent Platform, retained data stays in the provider environment. Azure Foundry has its own subscription-level configuration path.
Consumer Pro and Max surfaces already had retention, so the operational change is most visible for commercial organizations that previously relied on ZDR. The model can be affordable enough and technically accessible, yet still be disallowed for a particular dataset.
That means the real Fable admission check is three-part:
Use it when completion quality or long-horizon reliability can repay the higher meter. Simple routing, extraction, and short summaries usually do not.
Forecast with the new tokenizer, real context growth, cache behavior, tool overhead, fallback, and a hard spend boundary.
If the answer is no, Fable is the wrong route regardless of model quality, subscription tier, or available credit balance.
“Usage credit” and “fallback credit” are not the same thing
Anthropic uses the word credit in two unrelated billing mechanisms.
Usage credits are money-like account balance. They pay for metered Claude use beyond an included allowance—or, for Fable after the promotion, for a model that is no longer included in the allowance.
Fallback credit is an API billing adjustment. Fable and Opus prompt caches are model-specific. When a Fable request is refused and retried on Opus 4.8, the same prefix normally has to be written into a second model's cache. Anthropic's Fallback credit documentation describes a token that lets the retry be billed as though the conversation had been on the fallback model all along, avoiding a duplicate prompt-cache write charge.
On Anthropic's consumer and work-product surfaces, automatic switching is enabled by default when Fable safeguards block a request. The billing guide for switched conversations says:
- if the request is blocked before Fable produces output, only Opus rates apply;
- if it is blocked midstream, Fable input and streamed output before the block are charged at Fable rates, with the remainder charged at Opus rates;
- API switching is not automatic unless the developer opts in and configures it.
This matters because a Fable session may not be billed entirely at one model's rate. For security, biology, chemistry, model-distillation, or certain frontier-ML workflows, routing behavior belongs in both the quality trace and the cost trace.
RohitAI's read: the subscription is becoming a control plane
The obvious story is that Anthropic gave paid users a short trial and then started charging. The more useful interpretation is that the company is separating three products that used to be bundled together:
- the interface;
- the model entitlement;
- the inference spend.
Your plan can give you the interface without including Fable entitlement. Your organization can enable the entitlement but cap or withhold the spend. Your credit balance can fund the model, while a retention rule still blocks the data.
That separation has several consequences.
1. A visible model is no longer proof that it is included
After July 19, some users may still see Fable in a model picker because credits make it available. That does not mean their subscription pays for it. Product availability and included usage are now separate states.
Procurement documents, onboarding guides, and internal support scripts should stop using “available” as a synonym for “included.” The right questions are:
- Is the model visible?
- Is the model enabled?
- Is any usage included?
- Which meter pays after the included amount?
- Who can raise that meter?
2. Enterprise AI is converging on cloud economics
The current Enterprise seat is a platform fee plus consumption. That resembles cloud software more than traditional per-seat SaaS. A seat grants identity, collaboration, governance, and interfaces; compute is billed separately.
This architecture makes advanced models easier to expose without pretending their marginal cost fits a flat subscription. It also moves FinOps practices into ordinary knowledge work. Teams need cost attribution, spend limits, workload routing, and alerts for an assistant used in chat.
3. Promotions are becoming migration windows
The July allowance is not merely a sample. It gives users time to discover which tasks genuinely benefit from Fable before the meter becomes mandatory. A good organization will use that window to build a routing policy. A bad one will let habits form, enable unlimited credits, and learn the workload shape from the invoice.
The practical model is:
The earlier frontier access-regime analysis argued that capability, permission, and deployment are becoming separate competitive layers. Fable's post-restoration billing makes the same pattern visible at the checkout screen.
A practical Fable budget test
Before keeping Fable enabled after July 19, run a small workload audit:
- Select 20 to 50 real tasks where Fable appears to outperform the default model.
- Count full input payloads with the Fable tokenizer.
- Record output tokens, retries, tool calls, cache categories, and fallback events.
- Compare successful-task rate and human review time against Opus and Sonnet.
- Estimate monthly volume using the 75th or 90th percentile task, not only the average.
- Apply the plan's actual payment model: prepaid individual credits, Team pool, Enterprise credits, or monthly invoice.
- Add a hard ceiling and a cheaper fallback route.
The decision metric should be:
incremental cost of Fable ÷ incremental successful outcomes
If Fable saves an engineer three hours on a difficult migration, a $20 session can be cheap. If it adds polish to routine summaries, the same meter is waste. The model should earn its escalation.
Frequently asked questions
When does the Claude Fable 5 promotion end?
Anthropic's current Help Center says July 19, 2026 at 11:59:59 PM Pacific Time. Its older June 30 redeployment post says July 7, but the support article explicitly says the promotion was extended and is the current source for the cutoff.
Is Fable 5 included with Claude Pro or Max after July 19?
No. Anthropic says Fable 5 will no longer be included in weekly plan limits. Pro and Max users can continue through separately billed usage credits, if enabled and funded, or switch to another model within their regular plan usage.
Does “up to 50%” mean I get 50% more weekly usage?
No. During the promotion, Fable draws from the same weekly plan limit as other models and may consume it faster. The 50% figure caps how much of that shared limit can be spent on Fable at no extra charge.
Do current Claude Enterprise seats include any model usage?
No. Anthropic's current Enterprise billing guide says the seat fee provides access to Claude's product surfaces but includes no usage. Every token is billed separately at standard API rates. Older legacy Enterprise contracts can behave differently until they transition.
How much does Fable 5 cost through usage credits?
Anthropic says usage credits use standard API rates. Fable's base rate is $10 per million input tokens and $50 per million output tokens. Cache writes, cache hits, Batch API requests, US-only inference, tools, and fallback behavior can change the final amount. Discounted credit bundles can reduce the effective purchase price for Pro, Max, and Team users.
Does prompt caching avoid the 30-day retention requirement?
No. Prompt-cache TTL controls reuse for cost and latency. Fable's Covered Model policy separately retains prompts and outputs for 30 days and does not support ZDR.
What happens if Fable switches to Opus 4.8?
On Claude product surfaces, an input-blocked request is charged only at Opus rates. A midstream block can produce a mixed bill: Fable rates for the input and streamed portion, then Opus rates for the remainder. API customers must opt in to and configure fallback behavior.
Can an administrator prevent surprise spend?
Yes, though controls depend on the plan. Individuals can set monthly limits and manage auto-reload. Team and legacy Enterprise owners can set organization and user limits, with additional seat-tier or group controls on legacy Enterprise. Current Enterprise organizations can set organization and individual spend limits. One request may slightly exceed a cap because its cost is calculated after it runs.
The useful way to read the return
Fable's July restoration fixed the access outage. It did not restore the simple commercial story people thought they bought on June 9.
The stable picture as of July 17 is:
- Fable is globally available again.
- The temporary paid-plan allowance ends July 19 at 11:59:59 PM PT.
- After that, most subscription users need a second, metered balance.
- Current Enterprise users already pay from the first token.
- API rates are only the starting point; tokenizer, cache, batch, residency, tools, and fallback shape the real bill.
- Thirty-day retention remains a non-negotiable eligibility condition.
The lesson is not “Fable is too expensive.” It is that frontier models are becoming explicit escalation products. They sit behind a policy boundary, a data boundary, and now a spend boundary.
Treat July 19 as the moment to decide where Fable earns that escalation—not as the moment to turn on unlimited credits and hope the invoice explains the architecture later.