TL;DR (June 2026): Claude Mythos 5 is the same underlying model as Claude Fable 5 with specific safety guardrails lifted for vetted users, not a stronger secret model. Anthropic describes it as having the strongest cybersecurity capabilities of any model in the world; access runs through Project Glasswing (a US-government collaboration), an existing Claude Mythos Preview program, and a trusted-access program expanding in stages, you apply and get vetted, you cannot just buy it. Pricing, for those who do get access, is identical to Fable 5: $10 per million input tokens, $50 per million output tokens. Everyone else already has the answer to "how do I try Mythos": Fable 5 is Mythos-class, with classifier-triggered safeguards that route to Opus 4.8 in under 5% of sessions, and all Mythos-class traffic carries a mandatory 30-day retention policy. Here is the full map: what Mythos is, who qualifies, what it costs, and what the two-model structure means for your bill.
Since the June 9 announcement, the search queries have piled up: "claude mythos access," "claude mythos pricing," "claude mythos release date," "claude mythos preview." The r/ClaudeAI threads oscillate between awe and conspiracy. And the confusion is understandable, because Anthropic shipped two names for what is, in the most important sense, one model, then explained the difference in terms of safeguard architecture rather than capability tiers. This page is the plain-language version, with the billing implications usagebox readers actually came for.
What Claude Mythos 5 actually is
Per Anthropic's own announcement: Mythos 5 is the same underlying model as Fable 5, with safeguards lifted in some areas for qualified users. There is no separate, smarter network behind the curtain. The difference is policy, enforced at the serving layer:
- Fable 5 (what you can use today) ships with a safeguard system: classifiers watch for high-risk content in cybersecurity, biology/chemistry, and model-distillation attempts, and when one triggers, the request is automatically routed to Claude Opus 4.8 instead. Anthropic says this fallback engages in fewer than 5% of sessions; over 95% of sessions never touch it.
- Mythos 5 (what the vetted get) removes specific guardrails per audience. Project Glasswing partners get the cyber safeguards lifted while other protections remain; a planned program for biology researchers lifts the bio/chemistry safeguards while keeping the cyber ones. Selective unlocking, not general jailbreak.
That framing also explains the marketing line: "the strongest cybersecurity capabilities of any model in the world" is a claim about what the model can do when the cyber safeguards are off, which is exactly the configuration only vetted partners receive.
Who gets access, and how
- Project Glasswing: the initial deployment, in collaboration with the US government, focused on cybersecurity work. Not a sign-up form.
- Claude Mythos Preview: organizations already holding Mythos Preview access received the Mythos 5 upgrade at launch. This is the existing vetted cohort.
- The trusted-access program: Anthropic says broader access expands in stages, with the bio-research track explicitly planned. Expect vetting, use-case review, and contractual terms, the shape of an export-controlled product, not a SaaS tier.
If your team is wondering whether to apply: the program is built for organizations whose legitimate work trips the safeguards, security research, biosafety research, defense. If Fable 5's sub-5% fallback rate never bites your workload, Mythos buys you nothing, because the other 95%+ of the model is the same model.
The pricing, and the billing fine print
Mythos 5 is priced identically to Fable 5: $10 per million input tokens, $50 per million output tokens. The exclusivity is in the vetting, not the rate card. Three billing-relevant details that apply across the Mythos class:
- The fallback is also a billing event. When Fable 5 routes a triggered request to Opus 4.8, your workload silently shifts to a different model with different pricing ($5/$25) and different output characteristics. At under 5% of sessions this is noise for most budgets, but per-task metering will show it as model-mix drift, and for compliance-sensitive workloads, knowing which model answered matters beyond cost. If your meter tracks cost per task per model, the fallback is visible; if you watch only the invoice, it is not.
- 30-day mandatory retention on all Mythos-class traffic. Anthropic retains the data for safety purposes (explicitly not for training). If your data-governance posture assumes zero retention or customer-managed deletion, Mythos-class models, including Fable 5, change your compliance answer, and your DPA review belongs before the migration, not after.
- All the Fable 5 economics carry over. The 1M-token context billed at standard rates, the 90% cache discount as the survival lever, the subscription mechanics (free on plans through June 22, then usage credits), all covered in our Fable 5 pricing breakdown and usage-limits guide, apply to the Mythos class wholesale.
"When can I get Mythos?" answered honestly
The queries say people expect a release date, and the structure says there will not be one in the consumer sense. Mythos access is widening by cohort (government, preview holders, vetted researchers), not counting down to a launch day. Three scenarios for what "release" eventually means:
- Most likely: the trusted-access program keeps expanding by vertical (security firms, biosafety labs, critical-infrastructure operators) while the public product remains Fable 5, whose safeguard scope quietly narrows as classifiers improve. The public gets Mythos capability incrementally, through Fable.
- Possible: a paid enterprise tier with vetting attached, Mythos as a contractual SKU with audit requirements, priced above $10/$50 not in tokens but in compliance overhead.
- Unlikely: general availability of an unsafeguarded frontier model. Everything in Anthropic's positioning, and its IPO-era risk posture, points away from it.
What this two-model structure signals about pricing
The Mythos/Fable split is the first time a frontier lab has shipped capability-identical models differentiated purely by safeguard policy, and it quietly establishes a precedent that matters for buyers: the serving layer, classifiers, routing, retention, access tiers, is now a product surface. Once safeguard configuration is a differentiator, it is a short step to it being a priced differentiator: vetted tiers, compliance SKUs, per-domain unlocks. The 2026 pattern we keep documenting, flat plans unbundling into meters, premium surfaces multiplying, applies here too: Mythos is a premium surface whose price today is vetting, and prices denominated in vetting have a way of becoming prices denominated in dollars. When that happens, the buyers who know their per-task, per-model costs will know exactly what the unlock is worth to them. Everyone else will be told.
The honest take
Mythos is less mysterious and more interesting than the speculation suggests. Less mysterious: it is Fable 5 with permission slips, same weights, same prices, same retention rules. More interesting: it formalizes safety tiering as a product axis, and it makes the safeguard fallback a real (if small) billing and compliance event inside every Fable 5 deployment. For 99% of teams the practical guidance is short: use Fable 5, meter it per task and per model so the Opus fallback and the June 23 credit transition are visible, review the 30-day retention against your data commitments, and stop watching for a Mythos release date that is structurally never coming. The model you are waiting for is the one you already have, minus a guardrail you almost certainly do not need lifted.