Model catalogue · Anthropic
Claude Mythos
The second tier of Anthropic's latest Claude generation, designed for particularly demanding analysis and drafting and so far little proven in practice. For professional secrets no route is available: the platforms list this tier in a model class of its own, and that status brings mandatory retention of inputs for 30 days as well as compulsory data sharing with the model vendor - zero retention cannot be selected. This applies via Google Vertex AI, via Azure and via Amazon Bedrock alike, on Azure additionally for want of evidenced EU processing. For client, patient and personnel data this tier is therefore out, regardless of any contractual arrangement.
The provider excludes something section 203 requires - usually the confidentiality commitment or the purpose limitation on your inputs. With client data this route does not work.
What it is good for
- Frontier tier of the Claude family - listed by the platforms in a model class of its own
Where it stops
- Mandatory 30-day prompt retention and compulsory data sharing with Anthropic (Trust & Safety) - zero retention cannot be selected
- Ruled out for professional-secrecy workloads on all examined routes
Routes examined
The same model, procured differently, is a different legal position. What is examined per route is the contract chain, not the model.
| Route | Section 203 status | Version on this route |
|---|---|---|
| Microsoft Azure | not covered | - |
| Google EU platform (Gemini Enterprise, formerly Vertex AI) | not covered | - |
| AWS Bedrock (EU region Frankfurt) | not covered | - |
The conditions behind a conditional status - which piece is open on which route and who closes it - are set out in the full matrix in the German catalogue, and we go through them in the conversation. The German page for Claude Mythos carries the sources with their retrieval dates.
Is Claude Mythos the right fit?
We go through your tasks and the route that carries them - and say plainly where it does not.
Arrange a conversation