Claude Mythos 5 API Access: Who Can Get It and What to Use Instead

You cannot turn on Claude Mythos 5 with a normal Claude API key. As of July 22, 2026, claude-mythos-5 remains limited to approved Project Glasswing customers. There is no public signup, guaranteed waitlist, Console toggle, or cloud region that bypasses that approval.

The old claude-mythos-preview route is no longer current either: Anthropic scheduled it for retirement on July 21, 2026. If your organization already had Preview access, your job is to confirm migration to Mythos 5 with the account team that owns that relationship. If you were never approved, the generally available model with the same stated capabilities is Claude Fable 5 (claude-fable-5), which adds safety classifiers.

Use this decision table before touching an SDK:

Availability, pricing, and data terms were checked against current first-party documentation on July 22, 2026. Restricted access can change, so recheck the linked status sources before procurement or deployment.

Start with the current model, not an April access guide

Search results still mix Mythos Preview, unofficial “Mythos 1” references, the June launch, a June suspension, and current Mythos 5 pages. Those are different states, not several names for a public endpoint.

Anthropic's current model documentation calls Mythos 5 the successor to Preview. It says Fable 5 offers the same capabilities while adding safety classifiers for restricted dual-use areas. If Mythos is missing from your Console, that does not usually mean you need a new key, more billing, or another region. It means your organization does not have the gated entitlement.

The two current models share a 1M-token context window, up to 128K output, and published pricing of $10 per million input tokens and $50 per million output tokens. The $25/$125 figures still visible on the April Project Glasswing page describe the earlier Mythos Preview phase, not current Mythos 5 pricing.

The July restoration did not make Mythos public

The access timeline matters because “restored” and “generally available” are not synonyms:

1. April 7: Mythos Preview launched for selected Project Glasswing participants.
2. June 9: Anthropic launched Mythos 5 as Preview's successor and Fable 5 as the public same-capability route.
3. June 12: access to both models was suspended after a US export-control directive.
4. June 30: the controls were lifted.
5. July 1: Fable 5 returned globally; Anthropic confirmed Mythos 5 restoration for a set of US organizations and said broader domestic and international Glasswing access was still being coordinated.

That last boundary comes from Anthropic's redeployment update. Historical participation by an international organization does not prove that its access was restored on a particular account. An account team must confirm the current cohort and geography.

Who can realistically request access

The strongest case is an existing Project Glasswing approval or a relationship through an organization Anthropic treats as a trusted partner. Glasswing was built around defensive cybersecurity and critical software infrastructure. Anthropic expanded the initiative, but it did not convert it into click-to-enable model access.

The current official intake instruction is to contact an Anthropic, AWS, or Google Cloud account team. Contact is an intake channel, not a promise of approval or timing. A useful request should let the team evaluate:

1. the legal organization and its existing provider relationship;
2. the defensive-security or other explicitly eligible research use case;
3. who controls the environment and reviews model output;
4. the data classes involved and their handling boundaries;
5. the intended delivery surface after approval;
6. whether the organization can accept the model's retention and monitoring contract.

Do not send private repositories, credentials, or sensitive samples in an initial message. Ask for the qualification criteria and an authorized intake channel first.

Anthropic has also discussed a broader trusted-access program. That is a forward-looking program direction, not evidence of a public application that guarantees review today. In this audit, the current platform documentation still sends prospective qualified customers to account teams.

Cloud model pages are delivery evidence, not approval

AWS and Microsoft publish technical pages for Mythos 5. Those pages prove that a delivery surface exists for authorized customers; they do not grant access to every account.

The safe order is eligibility → explicit approval → assigned delivery surface → credentials → bounded test. Starting with sample code reverses that logic. A permission or model-not-found error can show that your account lacks access; it cannot reveal a legitimate bypass.

After approval, ask the account team to identify the exact model ID, allowed region, credential owner, billing owner, quota, data contract, and support path. Claude API, Bedrock, Google Cloud, and Foundry remain different operational contracts even when the model name is the same.

Fable 5 is the public build-now route

For most developers, Fable 5 is the practical answer—not an unofficial downgrade. Anthropic offers it generally through the Claude API and supported cloud platforms. The integration-level difference to plan for is its classifiers.

When a classifier declines a request before generation, the Messages API can return HTTP 200 with stop_reason: "refusal" rather than a transport error. Production code should inspect the stop reason, keep a safe diagnostic, and use an allowed fallback. Repeating the same request indefinitely or buying a “filter-free Mythos” proxy does not solve the access contract.

If your actual task is creating and protecting a public Claude credential, rather than obtaining gated Mythos entitlement, use the separate guide to create your own Claude API key safely. Do not buy a pregenerated or shared secret.

There is also a hard data stop rule. Anthropic currently assigns 30-day data retention to Fable 5 and Mythos 5 and does not offer either under zero data retention. The AWS route additionally requires the relevant provider data-sharing mode. If your policy requires ZDR or a specific cloud-only data boundary, do not treat Fable 5 as an automatic replacement; choose another current model or approved contract before sending production data.

If you already used Mythos Preview

An approved customer should not restart as an anonymous applicant. Ask the owner of the existing Anthropic or cloud relationship to confirm migration and restored access.

Use this minimum checklist:

1. replace claude-mythos-preview with the authorized claude-mythos-5 identifier;
2. use the endpoint and credentials for the assigned delivery surface;
3. account for always-on adaptive thinking—manual thinking: enabled with a token budget and thinking: disabled are not supported;
4. recheck token counting, quota, billing, and retention;
5. run one bounded request with no sensitive data;
6. move traffic only after a valid response and written contract confirmation.

Public sample code describes a request shape. It is not evidence that your account has entitlement.

Reject these false access signals

• “The model ID appears in documentation.” A product description is not a grant.
• “I created another API key.” A key identifies an account; it does not create Glasswing membership.
• “The model is listed on AWS, Azure, or Google.” A platform can deliver it after approval.
• “Claude for Open Source has an application.” That is a historically referenced maintainer intake, not a guaranteed Mythos 5 route.
• “A reseller offers unrestricted Mythos.” Require the contract owner, official model ID, retention terms, and proof of authorized supply before paying.

The answer is deliberately simple: Mythos Preview is retired; Mythos 5 exists but remains gated; Fable 5 is the public route for building now. Establish organizational eligibility first. Only after approval should you choose a cloud, region, and SDK.