Verified · Sep 2, 2026
Independently verifiedAnthropic ships Fable 5.1: ~25% cheaper via cache reads, looser safeguards, and a US-only twin called Mythos 5.1
2 sourcesAnthropic released Claude Fable 5.1 and Claude Mythos 5.1 on September 1, 2026 — the same underlying model with different safeguards. Fable 5.1 is generally available today on all platforms; Mythos 5.1 is restricted to trusted-access programs, currently a set of US organizations. Pricing otherwise matches Fable 5 ($10/M input, $50/M output), but cache reads now cost 75% less at $0.25 per million tokens — an estimated ~25% total-cost cut for typical workloads, up to ~45% for highly agentic work (Anthropic's own measurement over four weeks of August usage). Safeguards loosened in specific ways: Fable 5.1 can identify software vulnerabilities but not develop exploits, Claude Code sees ~60% fewer cyber interventions per session, biology safeguards fire 85% less often on benign questions, and the new Enterprise Frontier Safeguards give customer-side zero-retention-style privacy rolling out this fall. Anthropic's benchmarks put Fable 5.1 at 52.6% on Terminal-Bench-Science 0.1 (Fable 5: 24.7%) and 55.8% on Terminal-Bench 4.0 (Mythos 5.1: 60.9%).
Why now
The release landed yesterday with the pricing math already reshaping choices: Cognition says it is moving its Opus 5 traffic in Devin to Fable 5.1 on launch day because 'with the new cache read pricing a Fable-class model is finally economical.' This week is when tool vendors reroute model traffic and when audiences ask 'should I switch' — before reviews catch up. It also lands one day after Anthropic's alignment-and-security report, so the safeguard loosening (60% fewer interventions, vulnerability identification allowed) arrives with an unusual amount of context about why the company says that is now safe.
Why it is worth publishing
Broadest practical impact of the day: every creator running agent workloads, long-context coding, or API billing feels the cache-read repricing directly, and the workload math (25% vs 45%) is an executable explainer nobody else has walked yet. Two strong sources — the full announcement read plus TechCrunch's same-day framing — and a genuinely newsworthy caveat structure (the pricing nuance) that makes the card trust-building rather than hype.
Evidence basis
Anthropic announcement page read in full on 2026-09-02 (newsroom-dated September 1, 2026; fetched via curl) + TechCrunch full read on 2026-09-02 (posted 12:39 PM PDT September 1, 2026).
“By Anthropic's own estimate, Fable 5.1 cuts typical workloads about 25% — and the base price didn't move.”
Angle
Do the billing math on camera: what actually got cheaper (cache reads, 75% less), what did not (input/output prices), and whose workload benefits most (cache-heavy agentic work, up to ~45%) versus least (fresh-prompt chat, closer to ~25% or less). Fold in the safeguard loosening as the second beat — what Fable 5.1 can now do (find vulnerabilities) and still cannot (develop exploits).
Format
Long-form explainer
Demo idea
Pull up an API billing dashboard or the announcement's indexed-cost chart, mark which line is cache reads, and recompute a realistic week of your own usage under the new price — then run the same task against Fable 5 and Fable 5.1 and compare the invoices.
Platform notes
Every savings figure is Anthropic's own estimate — say 'estimated' and name the mechanism (cache reads now cost 75% less) and scope (typical workloads vs highly agentic). Input/output prices are unchanged. Benchmark numbers are Anthropic's own, measured with safeguards enabled and footnote caveats; the 'records' framing is TechCrunch's. Mythos 5.1 is vetted-access only, US organizations for now — do not present it as an option viewers can sign up for.
Usable claims
- Anthropic released Claude Fable 5.1 and Claude Mythos 5.1 on September 1, 2026 — the same underlying model with different safeguard levels: Fable 5.1 is generally available today on all platforms including AWS, Google Cloud, and Microsoft Azure (API id claude-fable-5-1), while Mythos 5.1 is available only through trusted access programs and currently only to a set of US organizations. Pricing otherwise matches Fable 5 — $10 per million input tokens, $50 per million output tokens — but cache reads now cost 75% less, at $0.25 per million tokens; Anthropic estimates that reduces costs by around 25% for typical workloads and up to around 45% for complex coding and highly agentic tasks, measured at default effort over four weeks of actual August 2026 usage.
- Alongside the release, Anthropic loosened safeguards and restructured data privacy: Fable 5.1 may now be used to identify software vulnerabilities (defensive work) though not to develop exploits, and Claude Code users can expect an average of around 60% fewer cyber-safeguard interventions per session than with Fable 5's safeguards; penetration testing, exploit generation, and binary-based vulnerability scanning still redirect to Opus models. Biology safeguards fire 85% less often on benign elementary biology and medical questions relative to Fable 5's launch safeguards, with life-sciences R&D queries still redirected to Opus. The new Enterprise Frontier Safeguards (EFS) store customer data on the customer's own cloud infrastructure with human review done by the customer by default — equivalent to zero data retention while Anthropic retains misuse monitoring — developed with more than 100 customers and AWS, Google Cloud, and Microsoft Azure, rolling out in phases starting this fall; until then eligible customers can use Fable 5.1 with zero data retention. Per TechCrunch, Anthropic also states it 'has never trained on enterprise data without explicit permission, and never will.'
- Anthropic's published benchmarks (with production safeguards enabled) put Fable 5.1 at 52.6% on Terminal-Bench-Science 0.1 versus 24.7% for Fable 5 and 29.0% for Opus 5; 55.8% on Terminal-Bench 4.0 versus 42.0% for Fable 5 and 52.3% for Opus 5, with the restricted Mythos 5.1 at 60.9%; and 60.9% without tools / 65.0% with tools on Humanity's Last Exam. Anthropic states Fable 5.1 and Mythos 5.1 are the same underlying model, and that the gap between them reflects the tasks where the earlier, less precise cyber safeguards intervened. Per TechCrunch's account of the system card, Mythos 5.1 is 'a slight regression on overall misaligned behavior compared to Opus 5, and an improvement over Mythos 5 and Claude Sonnet 5'; Anthropic's announcement says Mythos 5.1 carries the strongest cyber capabilities of any model it has released while staying in the lower risk category of its Frontier Compliance Framework, and that its automated behavioral audit found it better aligned than Mythos 5 across most metrics — though it can still sometimes bypass approvals and auto-mode classifiers.
Evidence pipeline
From the news
Breakdown
Anthropic's September 1 announcement ships Fable 5.1 (generally available) and Mythos 5.1 (the same model, vetted-access only, currently US organizations), reprices cache reads 75% lower to $0.25 per million tokens, and estimates ~25%/~45% total-cost reductions for typical and highly agentic workloads. This breakdown separates the mechanisms from the headlines: input/output prices are unchanged, the savings are Anthropic's own estimates with a stated measurement window, the benchmark table is Anthropic's own with safeguard-enabled caveats, and the safeguard loosening (vulnerability identification allowed, ~60% fewer Claude Code interventions, 85% fewer biology false positives) arrives one day after the company's alignment-and-security report — with EFS privacy restructured around customer-side storage rolling out this fall.
Sources
Risks
- Always pair the percentage with its mechanism ('cache reads now cost 75% less') and its scope ('typical workloads' / 'highly agentic work'), and say plainly that input/output prices did not change — then invite viewers to sanity-check against their own invoice.
- Label the numbers 'Anthropic's own benchmarks', keep at least one caveat on screen (safeguard interventions zeroing tasks, or the ±3.5–4.5 standard error), and attribute the 'records' framing to TechCrunch rather than stating it as fact.
- Introduce Mythos 5.1 as 'the same model, vetted-access only, US organizations for now', and route viewers who need the capability to Fable 5.1 or the Opus redirect path instead.
Demo ideas
- Invoice-reenactment card: same workload priced on Fable 5 vs Fable 5.1, cache reads line highlighted, ending 'your mileage depends on how much of your bill is cache reads'
- Allowed-vs-still-blocked card for the safeguard changes: vulnerability identification now allowed on Fable 5.1, exploit development / pentesting / binary scanning still redirect to Opus, plus Mythos 5.1's vetted-access ladder