Claude Opus 5

Anthropic — Claude Opus 5

Model Details

Claude Opus 5 is Anthropic's most advanced Opus model, powering long-running agents while delivering improvements in coding and professional work.

• Model launch date: July 24, 2026

• Model EOL date: N/A

• End User License Agreements and Terms of Use: View

• Model lifecycle: Active

• Context window: 1M tokens

• Max output tokens: 128K

• Reasoning: Supported (adaptive thinking is on by default; can be disabled but effort is capped at high when thinking is disabled)

• Knowledge cutoff: May 2026

• Marketplace product ID: prod-if5d653ow7ehg

Input Modalities	Output Modalities	APIs supported	Endpoints supported
Audio	Embedding	Responses	bedrock-runtime
Image	Image	Chat Completions	bedrock-mantle
Speech	Speech	Invoke
Text	Text	Converse
Video	Video	Messages

Capabilities and Features

Bedrock Features

Features supported using bedrock-runtime endpoint

Supported	Not Supported
Response streaming Abuse detection Guardrails Prompt optimization Knowledge base Model evaluation Prompt management Flows Agents Computer use	Intelligent prompt routing Count tokens Structured outputs

Features supported using bedrock-mantle endpoint

Supported	Not Supported
Response streaming Abuse detection Count tokens Computer use	Guardrails Prompt optimization Knowledge base Model evaluation Prompt management Flows Agents Intelligent prompt routing Structured outputs

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	512	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, please refer to the Amazon Bedrock Pricing page.

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-opus-5	N/A	us.anthropic.claude-opus-5 eu.anthropic.claude-opus-5 au.anthropic.claude-opus-5	global.anthropic.claude-opus-5
bedrock-mantle	anthropic.claude-opus-5	https://bedrock-mantle.{region}.api.aws/anthropic/v1/messages	N/A	N/A

For example, if region is us-east-1 (N. Virginia), then the bedrock-runtime endpoint URL will be "https://bedrock-runtime.us-east-1.amazonaws.com" and for bedrock-mantle will be "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. Priority offers higher throughput with a time-based commitment. Flex provides lower-cost access for flexible, non-time-sensitive workloads. Reserved provides dedicated throughput with a term commitment for predictable workloads. For more information, see service tiers.

Standard	Priority	Flex	Reserved	Batch

Regional Availability

Regional availability at a glance

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) for higher throughput while respecting data residency.

• Global Cross-Region routes anywhere worldwide for maximum throughput 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-southeast-2 (Sydney)
ap-southeast-4 (Melbourne)
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-3 (Jakarta)
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)

Data residency

• US geo (us.anthropic.claude-opus-5): Keeps data within US and Canada regions.

• EU geo (eu.anthropic.claude-opus-5): Keeps data within EU regions.

• AU geo (au.anthropic.claude-opus-5): Keeps data within Australia regions.

• Global (global.anthropic.claude-opus-5): Routes worldwide for maximum throughput 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: Go to the Amazon Bedrock console and generate a long-term API key.

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.

Messages API

pip install -U "anthropic[bedrock]"

Invoke/Converse API

pip install boto3

Step 4 - Set environment variables: Configure your environment to use the API key for authentication.

Messages API

AWS_BEARER_TOKEN_BEDROCK="<provide your Bedrock API key>"

Invoke/Converse API

AWS_BEARER_TOKEN_BEDROCK="<provide your Bedrock API key>"

Step 5 - Run your first inference request: Save the file as bedrock-first-request.py

Messages API

from anthropic import AnthropicBedrockMantle

client = AnthropicBedrockMantle(aws_region="us-east-1")

message = client.messages.create(
    model="anthropic.claude-opus-5",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Can you explain the features of Amazon Bedrock?"}],
)

print(message.content[0].text)

Invoke API

import json
import boto3

client = boto3.client('bedrock-runtime', region_name='us-east-1')
response = client.invoke_model(
    modelId='global.anthropic.claude-opus-5',
    body=json.dumps({
            'anthropic_version': 'bedrock-2023-05-31',
            'messages': [{ 'role': 'user', 'content': 'Can you explain the features of Amazon Bedrock?'}],
            'max_tokens': 1024
    })
)
print(json.loads(response['body'].read()))

Converse API

import boto3

client = boto3.client('bedrock-runtime', region_name='us-east-1')
response = client.converse(
    modelId='global.anthropic.claude-opus-5',
    messages=[
        {
            'role': 'user',
            'content': [{'text': 'Can you explain the features of Amazon Bedrock?'}]
        }
    ]
)
print(response)