TL;DR (July 18, 2026): Included Fable 5 access on Claude subscriptions ends July 19; from July 20 every Fable 5 token beyond your plan's included window bills as metered usage credits at the API rate: $10 per million input tokens, $50 per million output - 2x Opus 4.8. During the included period Fable 5 could draw at most 50% of a plan's weekly credits (Pro's 200 weekly credits meant at most 100 on Fable). The switch already had a dress rehearsal: on July 17 a bug walled Fable 5 behind usage credits two days early, spawning an 85-comment Ask HN and a wave of bug reports before Anthropic's status-page fix landed at 18:48 UTC. The math below shows what "metered Fable" costs at real orchestration volumes - one Max 20x subscriber has already burned $3,900 in credits in a month on top of the subscription.
Anthropic's Fable 5 launch bundled the frontier model into consumer subscriptions as a promotion: first with promotional credits (originally through July 7, extended to July 12), then as an included allowance capped at half of each plan's weekly credits, with the end date pushed twice - to July 12, then July 19. That runway ends this weekend. What replaces it is the purest version of the subscription-to-metered cliff we have covered all year: the model stays in the product, but the marginal token moves from "included" to $10/$50 per million.
The mechanics, precisely
- Through July 19: Fable 5 is included in Pro, Max, Team, and select Enterprise plans, capped at 50% of the plan's weekly credits. Example from Anthropic's own framing: a Pro plan with 200 weekly credits can spend at most 100 of them on Fable 5. Other models keep drawing from the plan's normal allowance.
- From July 20: Fable 5 usage beyond what a plan includes bills as usage credits - the metered mechanism - at the confirmed API rate of $10 per million input tokens and $50 per million output tokens.
- The rate in context: exactly 2x Opus 4.8 ($5/$25), 5x Sonnet 5's introductory rate ($2/$10 through August 31), and 10x Haiku 4.5 ($1/$5).
July 17: the accidental preview
Two days before the announced date, subscribers opened Claude Code to find Fable 5 demanding usage credits. The result was a same-day case study in how much this model tier matters to its users: an Ask HN thread ("Did Fable disappear from your Claude usage?") collected 87 points and 85 comments in hours, a GitHub issue titled "Fable 5 → API-only: please reconsider a subscription path" gathered upvotes-and-testimonials, and a 290-point r/ClaudeAI thread filled with confused Max subscribers. Anthropic's status page called it what it was - an erroneous requirement for usage credits, fixed by 18:48 UTC - and access came back after a relaunch.
The bug matters for one reason: it surfaced, a weekend early and with perfect clarity, exactly which workflows die when the meter turns on. If your team spent July 17 unable to work, that was your Fable 5 exposure assessment running itself.
What metered Fable 5 costs at real volumes
| Workload | Tokens (in / out) | Fable 5 metered | Same tokens on Opus 4.8 |
|---|---|---|---|
| One heavy agentic session | 120K / 40K | $3.20 | $1.60 |
| Daily driver (10 sessions/day, 22 days) | 26.4M / 8.8M | $704 | $352 |
| Orchestrator running subagent fleets | tens of millions/mo | $2,000-4,000+ | half that |
That last row is not hypothetical. A Max 20x subscriber filed pricing feedback with Anthropic mid-July after burning ~$3,900 in usage credits in one month, almost entirely on Fable-tier orchestration sessions, raising their credit cap four times along the way (1,000 → 2,000 → 3,000 → 4,500). Their verdict - "not sustainable for a solo developer" - is the honest summary of frontier-tier metering: the model is priced for work whose output justifies frontier cost per token, not for being your default.
The subscriber-fatigue backdrop
The switch lands on users already juggling more meters than any other AI product asks of them. The most-shared post of the window (162 likes, from a consultant running Claude for 50+ clients) lists them: "Weekly credits. Sonnet limits. Opus limits. Fable credits. 5-hour windows. Temporary increases that last 'a few more days.' The rules change every other week." That is the real cost of promotional pricing mechanics: each extension bought goodwill in the moment and spent it on predictability. If you budget AI spend for a team, treat included-model promotions as what they are - a marketing window with an end date - and model the metered rate from day one.
What to do before Monday
- Measure your Fable share now. Pull your usage breakdown by model for the last two weeks. Whatever fraction is Fable 5 is about to acquire a unit price of $10/$50.
- Re-route the routine. The standard pattern holds: Sonnet 5 (still at intro pricing) for everyday agent traffic, Opus 4.8 for hard-but-bounded work, Fable 5 reserved for tasks where the frontier delta is worth 2x Opus. Our Claude API pricing guide has the full rate card and routing thresholds.
- Set the credit cap deliberately. The $3.9K case escalated through four cap raises - each one a decision made under workflow pressure. Decide your monthly ceiling while calm, and wire a budget alert at 60% and 85% of it.
- If you saw the July 17 wall: that was the bug, not the policy - but note which of your sessions it blocked. Those are the sessions to re-route or budget for first.
The bigger pattern - GitHub's June 1 Copilot cutover, OpenAI's July 6 Workspace Agents meter, and now Anthropic's July 20 switch - is the subject of our companion piece on AI credits as the new pricing primitive. Three vendors, three quarters, one direction.