Claude Sonnet 5
Anthropic — Claude Sonnet 5
Model Details
Claude Sonnet 5 is the most capable Sonnet model from Anthropic, built for coding, agents, and professional work at scale. It brings near-Opus intelligence to the model teams run every day, with the same balance of capability, cost, and speed teams already rely on Sonnet for.
Model launch date: June 30, 2026
Model EOL date: N/A
End User License Agreements and Terms of Use: Third-party model terms
Model lifecycle: Active
Context window: 1M tokens
Max output tokens: 128K
Reasoning: Supported (adaptive thinking is always on and cannot be disabled; effort level is configurable)
Knowledge cutoff: January 2026
Marketplace product ID:
prod-4ezhkeia6k2cs
| Input Modalities | Output Modalities |
|---|---|
Endpoints and APIs supported
The following tables show which endpoints and APIs are supported for Claude Sonnet 5. For more information, see APIs supported by Amazon Bedrock and Endpoints supported by Amazon Bedrock.
Endpoint support
| Endpoint | Supported |
|---|---|
bedrock-runtime |
|
bedrock-mantle |
APIs supported on bedrock-runtime endpoint
| Messages | Responses | Chat Completions | Converse | Invoke |
|---|---|---|---|---|
APIs supported on bedrock-mantle endpoint
| Messages | Responses | Chat Completions | Converse | Invoke |
|---|---|---|---|---|
Tip
Whenever possible, we recommend using the bedrock-runtime endpoint for new applications. See Endpoints supported by Amazon Bedrock for details.
Capabilities and Features
Bedrock Features
Features supported using bedrock-runtime endpoint
Features supported using bedrock-mantle endpoint
Prompt caching
For more information, see Prompt caching for faster model inference.
| Prompt caching supported | Min tokens per cache checkpoint | Max cache checkpoints per request | Supported TTL | Fields that accept prompt cache checkpoints |
|---|---|---|---|---|
| Yes | 4,096 | 4 | 5 minutes, 1 hour | system, messages, and tools |
Computer use using bedrock-runtime and bedrock-mantle endpoints
For more information, see Computer use.
| Tool type | Beta header |
|---|---|
computer_20251124 |
computer-use-2025-11-24 |
Pricing
For pricing, see the Amazon Bedrock Pricing
Programmatic Access
Use the following model IDs and endpoint URLs to access this model programmatically. For more information about the available APIs and endpoints, see APIs supported and Endpoints supported.
| Endpoint | Model ID | In-Region endpoint URL | Geo inference ID | Global inference ID |
|---|---|---|---|---|
bedrock-runtime |
anthropic.claude-sonnet-5 |
N/A |
|
global.anthropic.claude-sonnet-5 |
bedrock-mantle |
anthropic.claude-sonnet-5 |
https://bedrock-mantle.{region}.api.aws/anthropic/v1/messages |
N/A | N/A |
For example, if the Region is us-east-1 (N. Virginia), the bedrock-runtime endpoint URL is "https://bedrock-runtime.us-east-1.amazonaws.com" and the bedrock-mantle endpoint URL is "https://bedrock-mantle.us-east-1.api.aws/anthropic/v1/messages".
Service Tiers
Amazon Bedrock offers multiple service tiers to match your workload requirements. Standard provides pay-per-token access with no commitment (set "service_tier": "default" or omit the field). Priority delivers the fastest response times for a price premium (set "service_tier": "priority"). Flex provides lower-cost access for flexible, non-time-sensitive workloads (set "service_tier": "flex"). Reserved provides dedicated throughput with a term commitment for predictable workloads; it is set at the account level rather than per request (contact your AWS account team to enable). For more information, see service tiers.
| Standard | Priority | Flex | Reserved |
|---|---|---|---|
Regional Availability
Regional availability at a glance
Amazon Bedrock offers three inference options:
In-Region keeps requests within a single Region for strict compliance.
Geo Cross-Region routes across Regions within a geography (such as US, EU, and APAC) while respecting data residency.
Global Cross-Region routes anywhere worldwide when there are no residency constraints.
For more details, see the Regional availability by models page.
| Region | In-Region | Geo | Global |
|---|---|---|---|
us-east-1 (N. Virginia) | |||
us-east-2 (Ohio) | |||
us-west-1 (N. California) | |||
us-west-2 (Oregon) | |||
ca-central-1 (Canada) | |||
ca-west-1 (Calgary) | |||
eu-central-1 (Frankfurt) | |||
eu-central-2 (Zurich) | |||
eu-north-1 (Stockholm) | |||
eu-south-1 (Milan) | |||
eu-south-2 (Spain) | |||
eu-west-1 (Ireland) | |||
eu-west-2 (London) | |||
eu-west-3 (Paris) | |||
ap-east-2 (Taipei) | |||
ap-northeast-1 (Tokyo) | |||
ap-northeast-2 (Seoul) | |||
ap-northeast-3 (Osaka) | |||
ap-south-1 (Mumbai) | |||
ap-south-2 (Hyderabad) | |||
ap-southeast-1 (Singapore) | |||
ap-southeast-2 (Sydney) | |||
ap-southeast-3 (Jakarta) | |||
ap-southeast-4 (Melbourne) | |||
ap-southeast-5 (Malaysia) | |||
ap-southeast-6 (New Zealand) | |||
ap-southeast-7 (Thailand) | |||
il-central-1 (Tel Aviv) | |||
me-central-1 (UAE) | |||
me-south-1 (Bahrain) | |||
af-south-1 (Cape Town) | |||
sa-east-1 (São Paulo) | |||
mx-central-1 (Mexico) | |||
us-gov-west-1 (GovCloud West) | |||
us-gov-east-1 (GovCloud East) |
Data residency
US geo (
us.anthropic.claude-sonnet-5): Keeps data within US and Canada regions.EU geo (
eu.anthropic.claude-sonnet-5): Keeps data within EU regions.AU geo (
au.anthropic.claude-sonnet-5): Keeps data within Australia regions.Global (
global.anthropic.claude-sonnet-5): Routes worldwide with no residency constraints.
Quotas and Limits
Your AWS account has default quotas for Amazon Bedrock. These quotas might change depending on regional factors, payment history, or approval of a quota increase request. For more details, see Quotas for Amazon Bedrock and the limits for the model.
Sample Code
Step 1 - AWS Account: If you have an AWS account already, skip this step. If you are new to AWS, sign up for an AWS account
Step 2 - API key: Open the Amazon Bedrock console
Step 3 - Get the SDK: To use this getting started guide, you must have Python already installed. Then install the relevant software depending on the APIs you are using.
Step 4 - Set environment variables: Configure your environment to use the API key for authentication.
Step 5 - Run your first inference request: Save the file as bedrock-first-request.py