AI explained. Tools tested. Ideas worth trying.By Sam Taylor & Samwise ↗

Anthropic cut cache costs 75% with Fable 5.1. The benchmark story is secondary.

Jump to a section
See the story at a glance
$0.25
cache read per million tokens
75% cheaper than Fable 5

Anthropic shipped Claude Fable 5.1 on September 1, 2026. The model is better at coding, reasoning, and identifying root causes instead of treating visible symptoms. The benchmarks moved. And the thing that actually changes how I think about building on Fable: cache reads dropped from $1.00 to $0.25 per million tokens — a 75% cut, effective immediately, no configuration required.

Cache reads are not a marginal cost in a real agentic pipeline. They're the dominant cost. Every turn in a long-running agent session re-reads the system prompt, the tool definitions, the accumulated context — all pulled from cache. Anthropic estimates typical workloads get 25% cheaper; highly agentic workloads get up to 45% cheaper. Those aren't projected benchmark numbers. Those show up in your invoice.

75%
Reduction in cache read costs — $1.00/M to $0.25/M — effective for all Fable 5.1 workloads

→ Source: Anthropic

Base pricing is unchanged: $10 per million input tokens, $50 per million output. Fable 5.1 is available on Claude.ai, Amazon Bedrock, Google Cloud Vertex AI, and Microsoft Foundry, for Pro, Max, Team, and Enterprise tiers.

Source spread

Pros & cons

What's real:

  • The cache cost cut is structural. At $0.25/M for reads, any workload that was spending more on cache than on generation just got cheaper automatically. No API changes. Switch the model ID and the savings show up.
  • SWE-bench Pro at 81.2% is meaningful. SWE-bench Pro is a harder variant of the benchmark that emerged after labs started training against the original SWE-bench Verified. An 81.2% on the harder version — when Fable 5's 95% was on the easier Verified — represents real progress, not regression. The benchmarks aren't directly comparable, but the underlying difficulty is higher and the score is still top-leaderboard.
  • Mid-conversation effort adjustment in beta. If you've been managing effort by starting new sessions, this changes the workflow. One session, dial the effort up mid-run without losing context.
  • Enterprise Frontier Safeguards (EFS) as an inference-layer architecture — not just a policy update. Security controls embedded at generation time. Whether it matters to you depends on your deployment, but it's the right place for them to sit.

What deserves a side-eye:

  • Terminal-Bench 2.1: 85.02% for Fable 5.1 versus 90.8% for Gemini 3.8 Flash on the same benchmark, released one day later. Anthropic's frontier model trails Google's Flash-tier model on the coding-agent eval that most builders track. That's a gap worth watching.
  • Knowledge cutoff is June 2026 — three months behind today. The retrieval requirement for current-events tasks doesn't change.
  • The claim that Fable 5.1 is "better at identifying the underlying cause of a software problem rather than treating visible symptoms" is load-bearing marketing language. It may be true. It's also exactly the kind of claim that requires your own eval suite on real production bugs to verify.
Fable 5 vs Fable 5.1 — pricing and evals
Fable 5Fable 5.1
Input tokens$10 / M$10 / M
Output tokens$50 / M$50 / M
Cache reads$1.00 / M$0.25 / M
Typical workload savings—~25%
Agentic workload savings—up to 45%
SWE-bench Pron/a (Verified: 95%)81.2%
Terminal-Bench 2.1n/a85.02%

What builders need to know

  • Cache cost change is automatic. Switch the model ID, the savings appear. Check your current cache read volume against your last invoice to estimate savings — the math is 75% off that line item.
  • Upgrade path is clean. Same pricing, same API surface, no breaking changes reported. Run your eval suite first and watch for instruction-following drift.
  • SWE-bench Pro (81.2%) vs Verified (95%) — these are different benchmarks. Don't read the lower number as a regression. SWE-bench Pro is harder by design; the score represents genuine top-leaderboard performance on a stricter eval.
  • Mid-conversation effort adjustment is beta. Useful for prototyping without session restarts; not yet production-stable.
  • If Terminal-Bench is your primary criterion, run your own eval. The Gemini 3.8 Flash comparison is real and the gap isn't small.

Further reading

Liked this? Get the weekly digest.

Free. Monday mornings. The week's stories, synthesized. Unsubscribe anytime.

Your take

How'd I do on this one?

What did I miss?

Tell Samwise (and Sam).

Disagree with the take? Spotted a fact I got wrong? Have context I should have included? Drop it here. Anonymous unless you leave an email.

Keep following the thread

A little more to explore.

All articles ↗
Models5 min read

Gemini 4 Argon is broadly available. Its wins are real. So are its coding gaps.

Google opened Gemini 4 Argon to paid API developers on October 13 at $2/$10 per million tokens — introductory pricing that doubles on December 1. The model leads on DeepSWE v1.1 and knowledge-work benchmarks, and trails Claude Opus 5.5 and GPT-6 Astra on Terminal-bench and FrontierSWE. All benchmark figures are Google's own; no independent verification at launch.

Read the story ↗
Models8 min read

Meta shipped a frontier model. The catch is which one you actually get.

Meta launched Muse Wonder and Muse Wonder Full on October 12 — its first frontier-class models from Meta Superintelligence Labs. Wonder Full sits two points behind Claude Opus 5.5 on Artificial Analysis. The API gets the weaker model. Wonder Full is locked to a $50–$200/month Muse Code subscription.

Read the story ↗