← Reddit

Fable 5 is insanely good but watch your usage, I was burning 2% a minute on 20x

Reddit · Complete-Sea6655 · June 10, 2026
Fable 5, released recently, represents a significant capability improvement over previous models like Opus 4.8, though its pricing is double at $10 per million input tokens and $50 per million output tokens. Users on the Max 20x plan are experiencing rapid token consumption rates due to the model's reasoning-heavy nature and increased token generation per request, with reported burn rates of approximately 2% per minute during intensive sessions. The higher effective costs per task have made cost-aware routing strategies—using cheaper models by default and reserving Fable 5 for critical problems—a necessity for enterprise deployments rather than an optional optimization.

Detailed Analysis

A Reddit post in the r/Anthropic community is generating discussion around the token consumption and cost implications of a newly released model identified as "Fable 5," which the author describes as a meaningful capability improvement over its predecessor, referred to as Opus 4.8. The author, operating on a Max 20x subscription plan, reports burning through approximately 2% of their usage allocation per minute during intensive agentic sessions — a dramatically higher rate than experienced with prior models performing equivalent workloads. The pricing structure cited in the post places Fable 5 at $10 per million input tokens and $50 per million output tokens, exactly double the rates attributed to Opus 4.8, establishing a clear pricing tier escalation that tracks with increased model capability.

The more significant cost dynamic the author identifies is not merely the higher rate card but the compounding effect of how reasoning-heavy models operate at a structural level. Frontier models optimized for complex reasoning generate substantially more tokens per task than their predecessors, both because they engage in longer internal reasoning chains and because agentic deployments inherently fan requests out into multiple sub-calls — planning passes, tool use loops, self-verification steps, and retries. A single user-facing query in an enterprise agentic system can therefore trigger tens of millions of tokens of actual compute, creating a severe mismatch between the apparent simplicity of an interaction and its underlying cost. The author references a reported case of Uber exhausting an annual AI budget in four months as illustrative of how quickly these costs can scale even before models at this pricing tier existed.

The practical implication drawn in the post is that cost-aware routing — directing queries to cheaper models by default and escalating to frontier models only when task complexity genuinely warrants it — has shifted from an optimization strategy to an operational necessity. This reflects a broader maturation in how organizations must think about AI infrastructure. The flat-rate utility framing that characterized earlier cloud AI adoption, where developers could query powerful models freely without granular cost accounting, is increasingly incompatible with deploying genuinely capable reasoning systems at scale. The economic pressure to build intelligent routing layers introduces a new engineering discipline: accurately classifying task complexity in advance well enough to make routing decisions, which is itself a non-trivial problem.

The tension the author surfaces connects to a wider industry pattern in which capability and cost advance together rather than in opposition. Each new generation of frontier AI models has been more expensive on a per-token basis even as cost per unit of useful work may improve, because the models consume more tokens to produce higher-quality outputs. For enterprises, this means that the procurement and budgeting models used for earlier AI integrations are likely to underestimate spending on newer deployments. The mention of Claude Code specifically — Anthropic's developer-facing agentic coding tool — is notable, as agentic coding workflows are among the highest token-consumption use cases, running continuous loops of code generation, execution, error interpretation, and revision that can sustain elevated token throughput for extended periods. Users running such workflows all day on Max plans represent precisely the cohort most exposed to the burn dynamics the author describes, and the community response seeking comparative usage data suggests this is a widely shared concern rather than an edge case.

Read original article →