Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Anthropic / Claude

Claude Mythos 5

Anthropic Mythos 5 release for text, visual understanding and reasoning workflows.

restrictedClosed weightsReasoningCodingVisionAgents
Official documentation (opens in a new tab)Reviewed 12 Oct 2026
9 of 16 specification fields collected
Context window1M1,000,000 tokens
Maximum output128K128,000 tokens
Input / 1M tokens$10.00Claude API
Output / 1M tokens$50.00USD · observed 12 Oct 2026

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
1,000,000 tokensSource for Context / input limit (opens in a new tab)
Reasoning
SupportedSource for Reasoning (opens in a new tab)

Adaptive (always on) thinking.

Tool calling
Not collected
Structured output
Not collected
Streaming
Not collected
Fine-tuning
Not collected
Parameters
Not collected
Architecture
Not collected
Languages
Not collected
Context caching
SupportedSource for Context caching (opens in a new tab)

Documented on at least one recorded endpoint. See Caching for host, lifecycle and billing restrictions.

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

API model ID
claude-mythos-5
Access
Verification or platform approval required.
Regions
Not collected
INPUT / 1M TOKENS$10.00
OUTPUT / 1M TOKENS$50.00

Claude API base token rates. Batch discounts, cache writes and plan-specific conditions are separate. Cached input price: $1.00 / 1M tokens (base tier).

USD · observed 12 Oct 2026 · Pricing evidence (opens in a new tab)
Published billing units · original currency · observed 12 Oct 2026
CategoryUsageRateUnit
Text tokens · Base rateCache write (5m)1$12.501M tokens
Text tokens · Base rateCache write (1h)1$20.001M tokens

Rate conditions

  1. Claude API standard rates; Base rate. Write rate replaces ordinary input billing for those tokens. Output and uncached input are separate. Batch, residency and service modifiers are not included.
Pricing source (opens in a new tab)

Data & enterprise terms

Retention and data handling depend on the API feature and account agreement.

Read the service policy (opens in a new tab)
API model ID
anthropic.claude-mythos-5
Access
Verification or platform approval required.
Regions
Not collected

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.

API model ID
claude-mythos-5
Access
Verification or platform approval required.
Regions
Not collected

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.

API model ID
claude-mythos-5
Access
Verification or platform approval required.
Regions
Not collected

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

Claude API

claude-mythos-5
Documented
Support evidence (opens in a new tab)
How it works
Opt-in automatic caching + explicit breakpointsSource for How it works (opens in a new tab)
Lifetime & refresh
5 minutes by default; optional 1 hour. Hits refresh the lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Set top-level cache_control for automatic caching or place it on content blocks. Up to four breakpoints; longer-lived blocks must precede shorter-lived blocks.Source for How to enable it (opens in a new tab)
Usage fields
cache_creation_input_tokens and cache_read_input_tokens; creation details separate 5m and 1h writes.Source for Usage fields (opens in a new tab)
Billing rules
5m writes: 1.25× base input. 1h writes: 2×. Reads: 0.025× for Fable/Mythos 5.1, 0.05× for Opus/Sonnet 5.5, otherwise 0.1×. Host prices, long-context tiers and residency modifiers still apply.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Prefix order is tools → system → messages. Cache must exist before concurrent requests can reuse it. Cache isolation is per organization, and also per workspace on Claude API, Claude Platform on AWS and Foundry.Source for Limits & data boundaries (opens in a new tab)
Cache reads, writes & storage
ChargeApplies toRate / unit
Cache read1Text tokens · Base tier$1.00 / 1M tokensPricing evidence (opens in a new tab)
Cache write (5m)2Text tokens · Base rate$12.50 / 1M tokensPricing evidence (opens in a new tab)
Cache write (1h)2Text tokens · Base rate$20.00 / 1M tokensPricing evidence (opens in a new tab)

Rate conditions

  1. Claude API base token rates. Batch discounts, cache writes and plan-specific conditions are separate.
  2. Claude API standard rates; Base rate. Write rate replaces ordinary input billing for those tokens. Output and uncached input are separate. Batch, residency and service modifiers are not included.

Observed 12 Oct 2026. Write rates and storage fees are different charges; use the billing rules above.

Caching reviewed 12 Oct 2026

Amazon Bedrock

anthropic.claude-mythos-5
Documented
Support evidence (opens in a new tab)
How it works
Implicit reuse + explicit cache checkpointsSource for How it works (opens in a new tab)
Lifetime & refresh
5 minutes by default; optional 1 hour. Hits refresh the lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Use the model’s Converse cachePoint or InvokeModel cache_control fields. Legacy InvokeModel does not accept top-level automatic cache_control; use explicit blocks.Source for How to enable it (opens in a new tab)
Usage fields
Converse: cacheReadInputTokens, cacheWriteInputTokens and cacheDetails. Native Messages responses use cache_read_input_tokens and cache_creation_input_tokens.Source for Usage fields (opens in a new tab)
Billing rules
Not collected
Limits & data boundaries
On-demand inference only, not the batch inference API. Cross-region routing can cause additional writes. Check the exact model, route and region.Source for Limits & data boundaries (opens in a new tab)

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Caching reviewed 12 Oct 2026

Google Cloud

claude-mythos-5
Documented
Support evidence (opens in a new tab)
How it works
Opt-in automatic caching + explicit breakpointsSource for How it works (opens in a new tab)
Lifetime & refresh
5 minutes by default; optional 1 hour. Hits refresh the lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Set top-level cache_control for automatic caching or place it on content blocks. Up to four breakpoints; longer-lived blocks must precede shorter-lived blocks.Source for How to enable it (opens in a new tab)
Usage fields
cache_creation_input_tokens and cache_read_input_tokens; creation details separate 5m and 1h writes.Source for Usage fields (opens in a new tab)
Billing rules
5m writes: 1.25× base input. 1h writes: 2×. Reads: 0.025× for Fable/Mythos 5.1, 0.05× for Opus/Sonnet 5.5, otherwise 0.1×. Host prices, long-context tiers and residency modifiers still apply.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Prefix order is tools → system → messages. Cache must exist before concurrent requests can reuse it. Cache isolation is per organization, and also per workspace on Claude API, Claude Platform on AWS and Foundry.Source for Limits & data boundaries (opens in a new tab)

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Caching reviewed 12 Oct 2026

Microsoft Foundry

claude-mythos-5
Documented
Support evidence (opens in a new tab)
How it works
Opt-in automatic caching + explicit breakpointsSource for How it works (opens in a new tab)
Lifetime & refresh
5 minutes by default; optional 1 hour. Hits refresh the lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Set top-level cache_control for automatic caching or place it on content blocks. Up to four breakpoints; longer-lived blocks must precede shorter-lived blocks.Source for How to enable it (opens in a new tab)
Usage fields
cache_creation_input_tokens and cache_read_input_tokens; creation details separate 5m and 1h writes.Source for Usage fields (opens in a new tab)
Billing rules
5m writes: 1.25× base input. 1h writes: 2×. Reads: 0.025× for Fable/Mythos 5.1, 0.05× for Opus/Sonnet 5.5, otherwise 0.1×. Host prices, long-context tiers and residency modifiers still apply.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Prefix order is tools → system → messages. Cache must exist before concurrent requests can reuse it. Cache isolation is per organization, and also per workspace on Claude API, Claude Platform on AWS and Foundry.Source for Limits & data boundaries (opens in a new tab)

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Caching reviewed 12 Oct 2026

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

Proprietary Claude release with developer-operated and documented partner access. No public model weights are supplied in the release documentation.

Classification evidence (opens in a new tab)

Lifecycle dates

Released8 Jun 2026Source (opens in a new tab)

Sources reviewed