Pricing

This page provides detailed pricing information for Anthropic's models and features. All prices are in USD.

For the most current pricing information, please visit claude.com/pricing.

Model pricing

The following table shows pricing for all Claude models across different usage tiers:

Third-party platform pricing

Claude models are available on AWS Bedrock, Google Vertex AI, and Microsoft Foundry. For official pricing, visit:

• AWS Bedrock pricing
• Google Vertex AI pricing
• Microsoft Foundry pricing

Feature-specific pricing

Data residency pricing

For Claude Opus 4.6 and newer models, specifying US-only inference via the inference_geo parameter incurs a 1.1x multiplier on all token pricing categories, including input tokens, output tokens, cache writes, and cache reads. Global routing (the default) uses standard pricing.

This applies to the Claude API (1P) only. Third-party platforms have their own regional pricing. See AWS Bedrock, Google Vertex AI, and Microsoft Foundry for details. Earlier models retain their existing pricing regardless of inference_geo settings.

For more information, see the data residency documentation.

Fast mode pricing

Fast mode for Claude Opus 4.6 (resesarch preview) provides significantly faster output at premium pricing (6x standard rates). Currently supported on Opus 4.6:

Fast mode pricing stacks with other pricing modifiers:

• Prompt caching multipliers apply on top of fast mode pricing
• Data residency multipliers apply on top of fast mode pricing

Fast mode is not available with the Batch API.

For more information, see the fast mode documentation.

Batch processing

The Batch API allows asynchronous processing of large volumes of requests with a 50% discount on both input and output tokens.

For more information about batch processing, see the batch processing documentation.

Long context pricing

When using Claude Opus 4.6, Sonnet 4.5, or Sonnet 4 with the 1M token context window enabled, requests that exceed 200K input tokens are automatically charged at premium long context rates:

Long context pricing stacks with other pricing modifiers:

• The Batch API 50% discount applies to long context pricing
• Prompt caching multipliers apply on top of long context pricing
• The data residency 1.1x multiplier applies on top of long context pricing

To check if your API request was charged at the 1M context window rates, examine the usage object in the API response:

{
  "usage": {
    "input_tokens": 250000,
    "cache_creation_input_tokens": 0,
    "cache_read_input_tokens": 0,
    "output_tokens": 500
  }
}

Calculate the total input tokens by summing:

• input_tokens
• cache_creation_input_tokens (if using prompt caching)
• cache_read_input_tokens (if using prompt caching)

If the total exceeds 200,000 tokens, the entire request was billed at 1M context rates.

For more information about the usage object, see the API response documentation.

Tool use pricing

Tool use requests are priced based on:

1. The total number of input tokens sent to the model (including in the tools parameter)
2. The number of output tokens generated
3. For server-side tools, additional usage-based pricing (e.g., web search charges per search performed)

Client-side tools are priced the same as any other Claude API request, while server-side tools may incur additional charges based on their specific usage.

The additional tokens from tool use come from:

• The tools parameter in API requests (tool names, descriptions, and schemas)
• tool_use content blocks in API requests and responses
• tool_result content blocks in API requests

When you use tools, we also automatically include a special system prompt for the model which enables tool use. The number of tool use tokens required for each model are listed below (excluding the additional tokens listed above). Note that the table assumes at least 1 tool is provided. If no tools are provided, then a tool choice of none uses 0 additional system prompt tokens.

These token counts are added to your normal input and output tokens to calculate the total cost of a request.

For current per-model prices, refer to the model pricing section.

For more information about tool use implementation and best practices, see the tool use documentation.

Specific tool pricing

Bash tool

The bash tool adds 245 input tokens to your API calls.

Additional tokens are consumed by:

• Command outputs (stdout/stderr)
• Error messages
• Large file contents

See tool use pricing for complete pricing details.

Code execution tool

Code execution tool usage is tracked separately from token usage. Execution time has a minimum of 5 minutes. If files are included in the request, execution time is billed even if the tool is not used due to files being preloaded onto the container.

Each organization receives 1,550 free hours of usage with the code execution tool per month. Additional usage beyond the first 1,550 hours is billed at $0.05 per hour, per container.

Text editor tool

The text editor tool uses the same pricing structure as other tools used with Claude. It follows the standard input and output token pricing based on the Claude model you're using.

In addition to the base tokens, the following additional input tokens are needed for the text editor tool:

See tool use pricing for complete pricing details.

Web search tool

Web search usage is charged in addition to token usage:

"usage": {
  "input_tokens": 105,
  "output_tokens": 6039,
  "cache_read_input_tokens": 7123,
  "cache_creation_input_tokens": 7345,
  "server_tool_use": {
    "web_search_requests": 1
  }
}

Web search is available on the Claude API for $10 per 1,000 searches, plus standard token costs for search-generated content. Web search results retrieved throughout a conversation are counted as input tokens, in search iterations executed during a single turn and in subsequent conversation turns.

Each web search counts as one use, regardless of the number of results returned. If an error occurs during web search, the web search will not be billed.

Web fetch tool

Web fetch usage has no additional charges beyond standard token costs:

"usage": {
  "input_tokens": 25039,
  "output_tokens": 931,
  "cache_read_input_tokens": 0,
  "cache_creation_input_tokens": 0,
  "server_tool_use": {
    "web_fetch_requests": 1
  }
}

The web fetch tool is available on the Claude API at no additional cost. You only pay standard token costs for the fetched content that becomes part of your conversation context.

To protect against inadvertently fetching large content that would consume excessive tokens, use the max_content_tokens parameter to set appropriate limits based on your use case and budget considerations.

Example token usage for typical content:

• Average web page (10KB): ~2,500 tokens
• Large documentation page (100KB): ~25,000 tokens
• Research paper PDF (500KB): ~125,000 tokens

Computer use tool

Computer use follows the standard tool use pricing. When using the computer use tool:

System prompt overhead: The computer use beta adds 466-499 tokens to the system prompt

Computer use tool token usage:

Additional token consumption:

• Screenshot images (see Vision pricing)
• Tool execution results returned to Claude

Agent use case pricing examples

Understanding pricing for agent applications is crucial when building with Claude. These real-world examples can help you estimate costs for different agent patterns.

Customer support agent example

When building a customer support agent, here's how costs might break down:

For a detailed walkthrough of this calculation, see the customer support agent guide.

General agent workflow pricing

For more complex agent architectures with multiple steps:

1. Initial request processing

   • Typical input: 500-1,000 tokens
   • Processing cost: ~$0.003 per request

2. Memory and context retrieval

   • Retrieved context: 2,000-5,000 tokens
   • Cost per retrieval: ~$0.015 per operation

3. Action planning and execution

   • Planning tokens: 1,000-2,000
   • Execution feedback: 500-1,000
   • Combined cost: ~$0.045 per action

For a comprehensive guide on agent pricing patterns, see the agent use cases guide.

Cost optimization strategies

When building agents with Claude:

1. Use appropriate models: Choose Haiku for simple tasks, Sonnet for complex reasoning
2. Implement prompt caching: Reduce costs for repeated context
3. Batch operations: Use the Batch API for non-time-sensitive tasks
4. Monitor usage patterns: Track token consumption to identify optimization opportunities

Additional pricing considerations

Rate limits

Rate limits vary by usage tier and affect how many requests you can make:

• Tier 1: Entry-level usage with basic limits
• Tier 2: Increased limits for growing applications
• Tier 3: Higher limits for established applications
• Tier 4: Maximum standard limits
• Enterprise: Custom limits available

For detailed rate limit information, see the rate limits documentation.

For higher rate limits or custom pricing arrangements, contact our sales team.

Volume discounts

Volume discounts may be available for high-volume users. These are negotiated on a case-by-case basis.

• Standard tiers use the pricing shown above
• Enterprise customers can contact sales for custom pricing
• Academic and research discounts may be available

Enterprise pricing

For enterprise customers with specific needs:

• Custom rate limits
• Volume discounts
• Dedicated support
• Custom terms

Contact our sales team at [email protected] or through the Claude Console to discuss enterprise pricing options.

Billing and payment

• Billing is calculated monthly based on actual usage
• Payments are processed in USD
• Credit card and invoicing options available
• Usage tracking available in the Claude Console

Frequently asked questions

How is token usage calculated?

Tokens are pieces of text that models process. As a rough estimate, 1 token is approximately 4 characters or 0.75 words in English. The exact count varies by language and content type.

Are there free tiers or trials?

New users receive a small amount of free credits to test the API. Contact sales for information about extended trials for enterprise evaluation.

How do discounts stack?

Batch API and prompt caching discounts can be combined. For example, using both features together provides significant cost savings compared to standard API calls.

What payment methods are accepted?

We accept major credit cards for standard accounts. Enterprise customers can arrange invoicing and other payment methods.

For additional questions about pricing, contact [email protected].