If you are looking for a public Claude Mythos API signup, there is no self-serve path today. As of April 15, 2026, Anthropic says Mythos Preview is invitation-only and has no public self-serve sign-up.
The useful next question is who you are. If your organization is already inside Project Glasswing or another invited cohort, Mythos can appear on Claude API, Amazon Bedrock, Google Vertex AI, or Microsoft Foundry after approval. If you are an ordinary developer outside that group, there is no public form that turns Mythos on for you right now.
There is one narrow gray zone worth checking. Anthropic says maintainers interested in access can apply through Claude for Open Source, but that should be treated as a possible intake path rather than a guaranteed Mythos approval route. If you need a public Claude model today, use the public Claude lineup and treat Mythos as a gated program, not as a missing account setting.
Current access status reflects Anthropic's Models overview, Project Glasswing, Anthropic's Bedrock and Vertex docs, AWS's Mythos Bedrock launch note, Microsoft's Foundry documentation, and Anthropic's Claude for Open Source page as of April 15, 2026.
The Fast Answer
| If you are... | Is there a real path today? | What the route actually looks like |
|---|---|---|
| Already inside Project Glasswing or another invited organization | Yes | Anthropic can make Mythos available on Claude API, Amazon Bedrock, Google Vertex AI, or Microsoft Foundry after approval. |
| A maintainer of significant open-source infrastructure | Maybe | Anthropic points interested maintainers to Claude for Open Source, but the public page does not promise Mythos approval. |
| A normal developer, startup, or team outside the invited audience | No public route | There is no self-serve signup, no public waitlist, and no console toggle that turns Mythos on. |
That is the main correction most quick Mythos access pages miss. The problem is not that you have not found the right dashboard yet. The problem is that Mythos is not currently sold or enabled like a normal public API model.
Anthropic's own wording keeps the access boundary narrow. Project Glasswing frames Mythos Preview around defensive cybersecurity work and organizations that build or maintain critical software infrastructure. Anthropic also says it does not currently plan to make Mythos Preview generally available. So the honest present-tense answer is not "contact sales and see what happens." It is "figure out whether you are already in the audience Anthropic is talking about."
Who can plausibly get access right now
The strongest current route is simple: already invited organizations. Anthropic's Project Glasswing page names launch partners and says access has also been extended to more than 40 additional invited organizations. If your organization is already in that group, Mythos access is a real operational question. At that point the work shifts from "Can I get in?" to "Which approved surface should we use after approval?"
The second route is narrower and less certain: maintainers Anthropic may want to support through the Claude for Open Source channel. This is worth mentioning only because Anthropic itself points interested maintainers there from the Project Glasswing page. But the public Claude for Open Source page is not written as a Mythos access contract. It describes a broader open-source support program around Claude Max rather than a public Mythos intake program with published approval rules. That means maintainers should treat it as a possible entry path, not as a reliable recipe.
Everyone else should read the boundary literally. If you are an ordinary builder, a team that is merely curious, or a company outside Anthropic's currently described access scope, there is no public onboarding flow to follow today. You are not missing a hidden model ID, a region flag, or a support checkbox. The current obstacle is eligibility, not configuration.
That distinction matters because cloud-platform documentation can make the situation look more open than it is. When readers see Bedrock, Vertex, or Foundry setup pages, it is easy to assume the problem is just picking the right platform. It is not. Those pages describe how Mythos can be used after Anthropic or the related partner flow has already cleared your organization for access.
The practical test is this:
- If Anthropic already knows who your organization is in the Project Glasswing context, keep reading.
- If you maintain meaningful open-source infrastructure and Anthropic's open-source route plausibly applies to you, there may be a narrow path worth checking.
- If neither of those is true, stop searching for a public Mythos permission flow and switch to a public Claude model instead.
What the real routes look like after approval
Once approval exists, the platform question becomes real. Before approval exists, platform choice is mostly a distraction.
Anthropic's Project Glasswing materials say Mythos Preview participants can access the model on Claude API, Amazon Bedrock, Google Vertex AI, and Microsoft Foundry. That list is useful, but only if you read it in the right order. It does not mean four separate public signup paths exist. It means approved participants may receive Mythos on one or more of these delivery surfaces.
| Surface | What the official docs say now | What that means for the reader |
|---|---|---|
| Claude API | Project Glasswing lists Claude API as a participant access surface. | If your organization is already approved, direct Anthropic-side API access may be available. This is not a public self-serve Mythos console flow. |
| Amazon Bedrock | Anthropic's Bedrock research-preview doc says customers should contact their Anthropic account executive, use a dedicated AWS account, and then be allow-listed. AWS's launch note says AWS teams reach out directly to allow-listed customers. | Bedrock is a partner and allow-list route for approved organizations, not a public request form any AWS customer can click through. |
| Google Vertex AI | Anthropic's Vertex page says Mythos Preview is a research preview available to invited customers on Vertex AI. | Vertex is a post-approval surface, not an alternate way to bypass Anthropic's access boundary. |
| Microsoft Foundry | Microsoft's Foundry docs say Mythos is a gated research preview granted solely at Anthropic's discretion and prioritized for defensive cybersecurity use cases. The current setup also requires Entra ID auth, supported regions, and eligible paid Azure usage terms. | Foundry has the most visible platform mechanics, but those mechanics still sit below Anthropic's approval decision. |
The easiest mistake here is to confuse platform readiness with eligibility.
Having the right AWS account structure does not create Mythos access on its own. Having a paid Azure subscription does not create Mythos access on its own. Being comfortable with Vertex AI does not create Mythos access on its own. Those are deployment conditions after the approval question is already settled.
This is why many search results feel unsatisfying: they tell you where Mythos can run, but not whether you have any reason to believe you can actually get it there. For most readers, that second question is the one that matters more.
There is also no evidence in the current official docs that a generic enterprise sales conversation guarantees Mythos. The official language remains narrower than that. Anthropic talks about invited organizations, critical software infrastructure, defensive cybersecurity workflows, and a special maintainer path. If your case falls outside those frames, platform setup knowledge alone will not close the gap.
What to use instead if Mythos is not available
If Mythos is not realistically available to you today, the correct next step is usually not "wait and refresh this page tomorrow." It is to switch to the public Claude route that actually matches your real problem.
If you need a public Claude model you can use now, use Anthropic's public Claude lineup rather than chasing a gated preview. For many readers, that is the whole answer. The public route exists today. Mythos does not replace it for ordinary access.
If your real question is how to start with a public Claude API key, read Claude API key free tier. That guide covers the public Console route, starter credits, and what becomes paid after testing.
If your real question is whether Mythos changes the cheapest official Claude path, read Claude Mythos Isn't a Public API. Haiku 4.5 Is the Cheapest Official Claude Route in 2026. That page stays on pricing and public-route economics instead of access eligibility.
If your real question is whether Mythos is something you should track instead of using today's public models, read Claude Mythos Preview vs GPT-5.4. That page is built for the "use now versus track later" decision.
If your real question is what Anthropic has actually confirmed about unreleased higher-end Claude naming, read Claude Capybara in 2026. That guide handles the broader unreleased-model status problem without overloading this access page.
That sibling routing is not housekeeping. It is what keeps this article honest. The job here is not to become a general Mythos encyclopedia. The job is to stop readers from burning time on a public signup flow that does not currently exist.
FAQ
Is there a public waitlist for Claude Mythos API access?
No public waitlist is described in Anthropic's current Mythos materials. Anthropic's Models overview says there is no self-serve sign-up, and Project Glasswing describes invitation-based access rather than a normal queue anyone can join.
Does contacting AWS, Azure, or Google Cloud automatically get me Mythos?
No. The current cloud documents describe partner-side setup and eligibility conditions after Mythos access exists for your organization. They do not convert cloud account ownership into a public Mythos approval path.
Is Claude for Open Source a guaranteed way to get Mythos?
No. Anthropic's Project Glasswing page points interested maintainers there, which makes it worth checking if you maintain meaningful open-source infrastructure. But the public Claude for Open Source page does not promise Mythos approval, publish a Mythos rubric, or describe a standard turnaround path into the preview.
Does Mythos have public pricing right now?
Anthropic does publish participant pricing on Project Glasswing: $25 per million input tokens and $125 per million output tokens after credits. But that is preview-participant pricing, not a normal public buy-now contract.
If I already have a Claude API key, can Anthropic just enable Mythos on my account?
Only if your organization is already inside Anthropic's approved audience. The current docs do not describe Mythos as a model ordinary Claude API users can unlock from the public dashboard by themselves.
Will Mythos become generally available later?
Unknown. Anthropic's current public statement on April 15, 2026 is that it does not plan to make Claude Mythos Preview generally available. Treat that as the present-tense contract, not as a permanent forecast.
The practical takeaway
Claude Mythos API access is not a hidden settings problem. It is a current eligibility boundary.
If your organization is already invited, Mythos can be a real deployment choice across Claude API and selected cloud surfaces. If you are a maintainer in the narrow group Anthropic may want to support through Claude for Open Source, there may be a path worth testing. For everyone else, the honest answer is shorter: there is no public self-serve signup today, so use a public Claude route instead of waiting for Mythos to appear in a menu.
The key rule to remember is this: approval comes before platform setup. Once you keep that order straight, most of the confusion around Claude Mythos API access disappears.