The situation, in three sentences
Through July 7, 2026, Fable 5 is included on paid claude.ai plans (Pro, Max, Team, select Enterprise) at 50% of weekly usage limits. After July 7, using Fable 5 on any claude.ai plan requires usage credits — standard Enterprise seats are credits-only already, and premium Enterprise seats have it included through July 7 and then move to credits like everyone else. The Claude API is separate and unchanged: normal metered billing at $10 in / $50 out per MTok, model id claude-fable-5.
What credits actually are
Usage credits are pay-as-you-go top-ups that sit on top of your subscription and are drawn down each time you use Fable 5. Your plan fee stays the ceiling for every other model; Fable becomes the one thing in the account that bills by consumption.
One thing this page will not do is quote you a credit price: the exact credit rates and denominations aren't publicly documented — current rates are shown in claude.ai's billing settings on your own account. For a sense of what Fable-class compute costs, use the API as the reference anchor: $10 per million input tokens, $50 per million output tokens — twice Opus 4.8's $5/$25. Whatever the credit denomination works out to, that's the neighborhood of compute you're buying.
Should you buy them?
This is most people. Opus 4.8 covers serious daily work at half Fable's API rate, and the new Sonnet 5 — $2/$10 per MTok intro pricing through August 31, then $3/$15 — covers most agent work. If Fable was a treat rather than a tool, let the meter pass you by. And while the included window is still open, route your hard jobs to it deliberately.
The case exists: revenue work that cheaper models demonstrably fail at — the multi-day autonomous builds, whole-codebase audits, and first-shot-correct implementations that are Fable's actual territory. But before you buy, compare against simply using the API directly at the published $10/$50 — same model, transparent metering, and it never touched your claude.ai plan. If your Fable work is programmatic anyway, the API may be the cleaner meter.
A subscription's worst month costs the subscription. A meter's worst month costs whatever you didn't notice. If you do buy credits, treat them like any metered bill — set a budget, check the drawdown, and decide in advance what happens when it's gone. Meters need watching; that vigilance is part of the price.
- Pick the projects that actually justify Fable — the long, hard, self-directed ones. The full triage is at /what-to-run/.
- Run them this week, while Fable is included at 50% of weekly limits on your plan.
- Note which of them a cheaper model genuinely couldn't do. That list — not habit — is your credits decision.
- Brief the big runs properly: Recipe 07 covers effort, checkpoints, and memory files.
The after-July-7 fallback ladder
If you skip credits, nothing breaks — Fable just disappears from your plan's model list, and everything else stays. Route down the ladder:
1 · claude-opus-4-8 — the dependable default for serious daily work, half Fable's API rate
2 · claude-sonnet-5 — most agent and app work; $2/$10 intro through Aug 31, then $3/$15
3 · claude-haiku-4-5 — instant, tiny, high-volume
And if a specific job truly needs Fable, the API is always there at $10/$50 — no plan gate, no credits, ordinary metered billing.
Moral: buy compute for the work that failed without it, not for the model you'll miss. The billing page can wait until the failure list can't.