Claude on AWS Bedrock vs Anthropic API: Cost Compared
Token prices for Claude are identical on AWS Bedrock and the Anthropic API. Here's where the costs actually diverge, and what to pick for your workload.
The short answer: Claude costs the same per token on AWS Bedrock and on the Anthropic API, at global endpoint rates. The two platforms list identical input and output prices for every current Claude model. Costs diverge in specific situations: if you need regional data residency, Bedrock charges a 10% premium for region-locked routing (Anthropic's own API charges the same 10% for US-only inference). Beyond price, the platforms differ in feature availability, model freshness, and what you can build on top, and those differences affect total cost more than the per-token rate does.
The Baseline: Token Prices Are at Parity
Anthropic's pricing documentation is explicit that AWS Bedrock and Google Cloud use the same per-token rates as the direct Claude API for global endpoint traffic. Every figure in the table below reflects that: identical numbers on both platforms, on-demand, at standard global routing.
| Model | Input (per 1M tokens) | Output (per 1M tokens) | Cache read (per 1M tokens) |
|---|---|---|---|
| Claude Haiku 5.5 (≤100K tokens) | $0.10 | $0.50 | $0.01 |
| Claude Haiku 4.5 | $1.00 | $5.00 | $0.10 |
| Claude Sonnet 5.5 | $2.00 | $10.00 | $0.10 |
| Claude Sonnet 5 | $2.00 | $10.00 | $0.20 |
| Claude Opus 5.5 | $4.00 | $20.00 | $0.20 |
| Claude Opus 5 / Opus 4.8 | $5.00 | $25.00 | $0.50 |
| Claude Fable 5.1 | $10.00 | $50.00 | $0.25 |
Prices per million tokens, on-demand, global endpoints. Source: Anthropic pricing documentation, October 2026.
Claude Sonnet 5's $2/$10 rate, which launched as introductory pricing with a scheduled increase to $3/$15 on September 1, 2026, had that increase cancelled. That permanent $2/$10 price applies on both platforms.
Where the Price Actually Diverges
Regional routing adds 10% on both sides
Starting with Claude Haiku 4.5, Sonnet 4.5, and Opus 4.5, Anthropic's pricing documentation specifies that Bedrock regional and multi-region endpoints carry a 10% premium over global endpoints. The global endpoint routes dynamically across available regions; a regional endpoint guarantees that inference stays within a specific geography for data residency. If you need data to stay in EU-West or US-East, you pay 10% more.
The same logic applies to the Anthropic direct API. Using the inference_geo: "us" parameter on Claude 4.6 and later models applies a 1.1x multiplier across all token categories, including input, output, cache writes, and cache reads. Neither platform is cheaper when you constrain geography: they both add 10% for data residency.
Batch processing: identical 50% discount
Both the Anthropic API and Bedrock offer a Batch API at 50% off on-demand rates. Sonnet 5 drops from $2/$10 to $1/$5 per million tokens in batch mode on both platforms. There is one important caveat on Bedrock: the Batch API is available only through the legacy InvokeModel integration for older models (Opus 4.6 and earlier). For newer models accessed via Bedrock's Messages API integration (Opus 4.7 and later), the Batch API is not currently available on Bedrock. If your workload runs on current-generation Claude models and you want batch pricing, the Anthropic direct API gives you access that Bedrock does not.
Prompt caching: same rates, same math
Prompt caching rates match across platforms. A 5-minute cache write costs 1.25x the base input price; a 1-hour write costs 2x; a cache read costs 0.1x (dropping to 0.05x on Claude Opus 5.5 and Sonnet 5.5, and 0.025x on Claude Fable 5.1). The prompt caching savings math is identical regardless of which platform you use.
Let each request use the cheapest model that's just as good
PromptUnit checks each request your app sends. When a cheaper model is just as good for that request, it uses it; otherwise your model answers. Free until it has saved you money.
Try it free →Feature Differences That Drive Real Cost
Beyond token prices, the platforms differ in what they let you do, and those gaps affect your architecture and therefore your total bill.
New models arrive on Anthropic's API first
Anthropic releases new Claude models to its own API first. Bedrock availability follows, sometimes by weeks, sometimes by months depending on the AWS integration effort required. If a new model is meaningfully faster or cheaper than its predecessor, every week you spend waiting on Bedrock is a week you pay the old rate. Teams that depend on current-generation capabilities, or who want to benchmark new models immediately at launch, can only do that through the Anthropic direct API.
Server-side tools are not available on Bedrock
The Anthropic API's built-in web search and code execution tools are not available through Amazon Bedrock's standard integration. This matters for cost because server-side tools can replace agent loop architectures that otherwise compound token usage. If your agent needs web search at every step, the multi-agent cost spiral of hand-rolling that capability with API calls can add up quickly, and Bedrock does not give you a shortcut.
Rate limits are set independently
Bedrock and Anthropic set their own rate limits, and the limits differ by model and tier. Anthropic's direct API uses usage tiers (Start, Build, Scale) with explicit requests-per-minute and tokens-per-minute limits, and these scale automatically as you build usage history. Bedrock has its own quota system, managed through the AWS console, with separate limits per region and inference profile. For teams already on AWS with committed spend, Bedrock reserved throughput is an option for high-volume steady workloads, though it requires contacting AWS for pricing. Neither platform is obviously better here: it depends on your volume, region, and whether you already have AWS enterprise agreements that affect capacity.
The Third Option: Claude Platform on AWS
There is a middle path worth knowing about: Claude Platform on AWS, which launched in general availability in May 2026. Anthropic operates the stack, not AWS. It uses the standard Anthropic Messages API, gets new models on the same day as the direct API, and includes the same server-side tools and beta features. Billing runs through AWS Marketplace using Claude Consumption Units (CCUs), where 100 CCUs equals $1.00 at standard Anthropic per-model rates. If your team needs AWS-native billing and IAM authentication but also needs the latest features on day one, Claude Platform on AWS is worth evaluating separately from standard Bedrock.
The Practical Decision
For most teams running current-generation Claude models, the token-level cost comparison is a wash at global rates. The decision comes down to three non-price factors:
Use the Anthropic direct API if you: want the Batch API on current models (Opus 4.7 and later), need new models immediately on launch, use or plan to use server-side tools like web search, or prefer simpler billing without AWS.
Use AWS Bedrock if you: already have AWS infrastructure and want data within AWS boundaries, need IAM-based authentication or AWS CloudTrail for audit, or want to combine Claude with AWS-native services like Bedrock Guardrails and Bedrock Knowledge Bases. Be aware that Bedrock's standard integration does not currently support the Batch API for newer Claude models, so if 50% batch discounts matter for your workload, plan accordingly.
Use both if failover matters. Because the same Claude model sits on separate capacity pools, calling Anthropic direct as primary and Bedrock as failover keeps requests succeeding when one platform returns rate limit errors. A proxy or gateway layer handles the routing transparently. This is a common production pattern and worth considering if Claude is on the critical path of your application. The failover guide for AI APIs covers the error codes and retry logic for exactly this setup.
If you are trying to reduce the total Claude spend regardless of platform, the levers are the same on both sides: prompt caching, batch for async work, model tiering by task complexity, and output length control. The Claude API cost reduction guide walks through those steps in detail, and every technique in it applies whether your requests go to Anthropic or Bedrock. A cost optimization proxy like PromptUnit can also route calls to a cheaper model automatically when the task does not need the full capability of the model you asked for, connecting keys from multiple providers to widen the options.
The platform choice affects your architecture, compliance posture, and feature access. The token price, at global rates, is not the thing that distinguishes them.