Add comprehensive model card for Anthropic's Claude Haiku 4.5 on AWS Bedrock, including model details, capabilities, pricing, programmatic access examples, and regional availability information.
23 KiB
Claude Haiku 4.5
Anthropic — Claude Haiku 4.5
Model Details
Claude Haiku 4.5 is Anthropic's lightweight model optimized for speed and efficiency with strong coding and agent performance. For more information about model development and performance, see the model/service card.
- Model launch date: Oct 16, 2025
- Model EOL date: No sooner than 10/1/2026
- End User License Agreements and Terms of Use: View
- Model lifecycle: Active
- Context window: 200K tokens
- Max output tokens: 64K
- Reasoning: Supported
- Knowledge cutoff: Feb 2025
- Marketplace product ID:
prod-xdkflymybwmvi
| Input Modalities | Output Modalities | APIs supported | Endpoints supported |
|---|---|---|---|
Capabilities and Features
Bedrock Features
Features supported using bedrock-mantle endpoint
| Supported | Not Supported |
|---|---|
| See the AWS documentation website for more details | See the AWS documentation website for more details |
Features supported using bedrock-runtime endpoint
| Supported | Not Supported |
|---|---|
| See the AWS documentation website for more details | See the AWS documentation website for more details |
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 |
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-haiku-4-5-20251001-v1:0 | https://bedrock-runtime.{region}.amazonaws.com | us.anthropic.claude-haiku-4-5-20251001-v1:0``eu.anthropic.claude-haiku-4-5-20251001-v1:0``au.anthropic.claude-haiku-4-5-20251001-v1:0 |
global.anthropic.claude-haiku-4-5-20251001-v1:0 |
| bedrock-mantle | anthropic.claude-haiku-4-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 |
|---|---|---|---|
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 (US, EU, etc.) for higher throughput while respecting data residency, and Global Cross-Region routes anywhere worldwide for maximum throughput when there are no residency constraints. Refer to the Regional availability page for more details.
Geo inference details
Geo: US
Geo Inference ID: us.anthropic.claude-haiku-4-5-20251001-v1:0
| Source Region | Destination Regions |
|---|---|
| us-east-1 (N. Virginia) | us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
| us-east-2 (Ohio) | us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
| us-west-1 (N. California) | us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-1 (N. California), us-west-2 (Oregon) |
| us-west-2 (Oregon) | us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
| ca-central-1 (Canada) | ca-central-1 (Canada), us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
Geo: EU
Geo Inference ID: eu.anthropic.claude-haiku-4-5-20251001-v1:0
| Source Region | Destination Regions |
|---|---|
| eu-central-1 (Frankfurt) | eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris) |
| eu-central-2 (Zurich) | 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-3 (Paris) |
| eu-north-1 (Stockholm) | eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris) |
| eu-south-1 (Milan) | eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris) |
| eu-south-2 (Spain) | eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris) |
| eu-west-1 (Ireland) | eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris) |
| eu-west-2 (London) | eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-2 (London), eu-west-3 (Paris) |
| eu-west-3 (Paris) | eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris) |
Geo: AU
Geo Inference ID: au.anthropic.claude-haiku-4-5-20251001-v1:0
| Source Region | Destination Regions |
|---|---|
| ap-southeast-2 (Sydney) | ap-southeast-2 (Sydney), ap-southeast-4 (Melbourne) |
| ap-southeast-4 (Melbourne) | ap-southeast-2 (Sydney), ap-southeast-4 (Melbourne) |
| ap-southeast-6 (New Zealand) | ap-southeast-2 (Sydney), ap-southeast-4 (Melbourne), ap-southeast-6 (New Zealand) |
Global inference details
| Global Inference ID | Americas | EMEA | Asia Pacific |
|---|---|---|---|
| global.anthropic.claude-haiku-4-5-20251001-v1:0 | See the AWS documentation website for more details | See the AWS documentation website for more details | See the AWS documentation website for more details |
Quotas and Limits
Your AWS account has default quotas to maintain the performance of the service and to ensure appropriate usage of Amazon Bedrock. The default quotas assigned to an account might be updated depending on regional factors, payment history, fraudulent usage, and/or approval of a quota increase request. For more details, please refer to Quotas for Amazon Bedrock documentation and see 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-haiku-4-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='anthropic.claude-haiku-4-5-20251001-v1:0',
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='anthropic.claude-haiku-4-5-20251001-v1:0',
messages=[
{
'role': 'user',
'content': [{'text': 'Can you explain the features of Amazon Bedrock?'}]
}
]
)
print(response)