Fable 5 Exits Subscriptions on July 12: What It Costs and How to Keep Costs Down

TL;DR: Fable 5 stays on Pro/Max/Team plans through July 12 (extended from July 7), then switches to usage-credit billing at $10/$50 per million tokens; Batch API cuts it to $5/$25.

Anthropic originally set July 7 as the date Fable 5 would stop being included in plan usage limits. It extended that deadline by five days; July 12 is the firm cutoff.

After July 12:

• Fable 5 no longer draws from your weekly plan limit
• Prompts bill through usage credits: $10/M input, $50/M output (standard) or $5/M / $25/M (Batch API)
• The 50% usage cap (at most half your weekly calls can go to Fable 5) still applies during the remaining plan-included window

Cost at volume. A typical agentic turn — ~50k input / 15k output tokens — runs about $1.25 per call at standard rates. 30 such calls a day is ~$37.50/day or roughly $1,100/month. Cache repeated system prompts and route to Batch API for anything non-realtime.

Cost controls:

• Batch API: non-realtime Fable 5 calls at $5/$25/M (50% off; completes within 24h)
• Prompt caching: repeated input context (system prompts, large document chunks) at $1/M cached
• Model routing: reserve Fable 5 for tasks that genuinely need it; route to Sonnet 5 ($2/$10/M) or Haiku 4.5 for everything else

Anthropic has said the usage-credit move is temporary and plans to restore Fable 5 to standard plans as capacity grows. No timeline given.

Why it matters: If you have Claude Code sessions or agentic pipelines that default to Fable 5, audit them before July 12 — unmetered session use becomes billed use overnight.

Sources: Fable 5 usage limits — Fable5.app · Fable 5 Usage Credits — Codersera · Fable 5 exits subscriptions — AndroidHeadlines