[metadata]
apple-mobile-web-app-status-bar-style: default
description: To mitigate misuse and manage capacity on the API, limits are in place on how much an organization can use the Claude API.
mobile-web-app-capable: yes
og:description: To mitigate misuse and manage capacity on the API, limits are in place on how much an organization can use the Claude API.
og:image: https://platform.claude.com/docs/og?locale=en&path=api/rate-limits&design-rev=1
og:image:alt: Rate limits
og:image:height: 630
og:image:type: image/png
og:image:width: 1200
og:locale: en
og:site_name: Claude Platform Docs
og:title: Rate limits
og:type: article
og:url: https://platform.claude.com/docs/en/api/rate-limits
twitter:card: summary_large_image
twitter:description: To mitigate misuse and manage capacity on the API, limits are in place on how much an organization can use the Claude API.
twitter:image: https://platform.claude.com/docs/og?locale=en&path=api/rate-limits&design-rev=1
twitter:title: Rate limits
viewport: width=device-width, initial-scale=1, maximum-scale=1, viewport-fit=cover

[canonical-links]
https://platform.claude.com/docs/en/api/rate-limits

[document-links]
429 error: /docs/en/api/errors
AI agents: https://claude.com/solutions/agents
API reference: /docs/en/api/overview
Admin: /docs/en/api/admin
Admin: /docs/en/manage-claude/admin-api
Anthropic support: https://support.claude.com
Anthropic: https://www.anthropic.com/company
Archive Tunnel: /docs/en/api/beta/tunnels/archive
Availability: https://www.anthropic.com/supported-countries
Best practices: /docs/en/about-claude/use-case-guides/overview
Beta headers: /docs/en/api/beta-headers
Billing: /settings/billing
Blog: https://claude.com/blog
CLI, SDKs, and libraries: /docs/en/cli-sdks-libraries/overview
Careers: https://www.anthropic.com/careers
Claude API skill: /docs/en/agents-and-tools/agent-skills/claude-api-skill
Claude Console: /
Claude Managed Agents: /docs/en/managed-agents/overview
Claude Platform Docs: /docs
Claude Platform Docs: /docs/en/home
Claude Platform on AWS: /docs/en/build-with-claude/claude-platform-on-aws
Claude on AWS: https://claude.com/partners/amazon-bedrock
Claude on Google Cloud: https://claude.com/partners/google-cloud-vertex-ai
Code modernization: https://claude.com/solutions/code-modernization
Coding: https://claude.com/solutions/coding
Completions: /docs/en/api/completions
Compliance API: /docs/en/api/compliance
Connectors: https://claude.com/partners/mcp
Count tokens in a Message: /docs/en/api/beta/messages/count_tokens
Courses: https://claude.com/resources/courses
Create Enrollment URL: /docs/en/api/beta/user_profiles/create_enrollment_url
Create Skill: /docs/en/api/beta/skills/create
Create Tunnel: /docs/en/api/beta/tunnels/create
Create User Profile: /docs/en/api/beta/user_profiles/create
Create a Message: /docs/en/api/beta/messages/create
Create a Text Completion: /docs/en/api/completions/create
Customer stories: https://claude.com/customers
Customer support: https://claude.com/solutions/customer-support
Delete File: /docs/en/api/beta/files/delete
Delete Skill: /docs/en/api/beta/skills/delete
Discord: https://www.anthropic.com/discord
Download File: /docs/en/api/beta/files/download
Economic Futures: https://www.anthropic.com/economic-futures
Engineering at Anthropic: https://www.anthropic.com/engineering
Errors: /docs/en/api/errors
Events: https://www.anthropic.com/events
Fast mode rate limits: /docs/en/build-with-claude/fast-mode#rate-limits
Fast mode: /docs/en/build-with-claude/fast-mode#supported-models
Features overview: /docs/en/api/overview
Files : /docs/en/api/beta/files
Financial services: https://claude.com/solutions/financial-services
Get File Metadata: /docs/en/api/beta/files/retrieve_metadata
Get Skill: /docs/en/api/beta/skills/retrieve
Get Tunnel: /docs/en/api/beta/tunnels/retrieve
Get User Profile: /docs/en/api/beta/user_profiles/retrieve
Get a Model: /docs/en/api/beta/models/retrieve
Government: https://claude.com/solutions/government
Higher education: https://claude.com/solutions/education
IAM actions (Claude Platform on AWS): /docs/en/api/claude-platform-on-aws-iam-actions
IP addresses: /docs/en/api/ip-addresses
K-12 teachers: https://claude.com/solutions/teachers
Life sciences: https://claude.com/solutions/life-sciences
List Files: /docs/en/api/beta/files/list
List Models: /docs/en/api/beta/models/list
List Skills: /docs/en/api/beta/skills/list
List Tunnels: /docs/en/api/beta/tunnels/list
List User Profiles: /docs/en/api/beta/user_profiles/list
Log in: /login?returnTo=%2Fdocs%2Fen%2Fapi%2Frate-limits
Managed Agents: /docs/en/managed-agents/overview
Messages: /docs/en/api/beta/messages
Messages: /docs/en/intro
Models & pricing: /docs/en/about-claude/models/overview
Models: /docs/en/api/beta/models
News: https://www.anthropic.com/news
Powered by Claude: https://claude.com/partners/powered-by-claude
Privacy policy: https://www.anthropic.com/legal/privacy
Rate Limits API: /docs/en/manage-claude/rate-limits-api
Rate limits and quotas on Claude Platform on AWS: /docs/en/build-with-claude/claude-platform-on-aws#rate-limits-and-quotas
Rate limits: /docs/en/api/rate-limits
Rate limits: /settings/limits
Release notes: /docs/en/release-notes/overview
Research: https://www.anthropic.com/research
Responsible Scaling Policy: https://www.anthropic.com/news/announcing-our-updated-responsible-scaling-policy
Responsible disclosure policy: https://www.anthropic.com/responsible-disclosure-policy
Reveal Tunnel Token: /docs/en/api/beta/tunnels/reveal_token
Rotate Tunnel Token: /docs/en/api/beta/tunnels/rotate_token
Security and compliance: https://trust.anthropic.com
Service partners: https://claude.com/partners/services
Service tiers: /docs/en/api/service-tiers
Settings > Billing: /settings/billing
Skills : /docs/en/api/beta/skills
Spend limits on Claude Platform on AWS: /docs/en/build-with-claude/claude-platform-on-aws#spend-limits
Startups program: https://claude.com/programs/startups
Status: https://status.claude.com/
Support: https://support.claude.com/
Supported regions: /docs/en/api/supported-regions
Terms of service: Commercial: https://www.anthropic.com/legal/commercial-terms
Terms of service: Consumer: https://www.anthropic.com/legal/consumer-terms
Transparency: https://www.anthropic.com/transparency
Trigger a routine: /docs/en/api/claude-code/routines-fire
Tunnels : /docs/en/api/beta/tunnels
Update User Profile: /docs/en/api/beta/user_profiles/update
Upload File: /docs/en/api/beta/files/upload
Usage page: /usage
Usage policy: https://www.anthropic.com/legal/aup
Usage: /usage
Use cases: https://claude.com/resources/use-cases
User Profiles : /docs/en/api/beta/user_profiles
Versions: /docs/en/api/versioning
Webhooks : /docs/en/api/beta/webhooks
Workspaces: /docs/en/manage-claude/workspaces
fast mode: /docs/en/build-with-claude/fast-mode
https://instagram.com/claudeai
https://www.linkedin.com/showcase/claude
https://www.threads.com/@claudeai
https://www.youtube.com/@anthropic-ai
https://x.com/claudeai
prompt caching: /docs/en/build-with-claude/prompt-caching
response header: /docs/en/api/overview#response-headers
retired, except on Bedrock and Google Cloud: /docs/en/about-claude/model-deprecations
token bucket algorithm: https://en.wikipedia.org/wiki/Token_bucket
 API reference: /docs/en/api/overview
 Console: /

[content]
Rate limits - Claude Platform Docs
Claude Platform Docs
Messages
Managed Agents
Admin
Resources

Best practices
Models & pricing
CLI, SDKs, and libraries
Claude API skill
Release notes

API reference

English


Console
Log in


Search
Ctrl
K

Include beta APIs
Using the API
Features overview
Beta headers
Errors
Messages
Create a Message
Count tokens in a Message
Batches

Managed Agents

Agents

Environments

Sessions

Deployments

Deployment Runs

Vaults

Memory Stores

Dreams

Models
List Models
Get a Model
Files

Upload File
List Files
Download File
Get File Metadata
Delete File
Skills

Create Skill
List Skills
Get Skill
Delete Skill
Versions

Tunnels

Create Tunnel
Get Tunnel
List Tunnels
Archive Tunnel
Reveal Tunnel Token
Rotate Tunnel Token
Certificates

User Profiles

Create User Profile
List User Profiles
Get User Profile
Update User Profile
Create Enrollment URL
Webhooks

Admin
Organizations

Invites

Users

RBAC Groups


RBAC Roles


Workspaces

API Keys

External Keys

Usage Report

Cost Report

Analytics

Spend Limits

Rate Limits

Service Accounts

Federation Issuers

Federation Rules

MCP Tunnels


Compliance API
Activities

Organizations

Groups

Apps

Code

Completions
Create a Text Completion
Claude Code
Trigger a routine
Support & configuration
Rate limits
Service tiers
IAM actions (Claude Platform on AWS)
Versions
IP addresses
Supported regions

Console
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Claude Platform Docs


Solutions
AI agents
Code modernization
Coding
Customer support
Financial services
Government
Higher education
K-12 teachers
Life sciences
Partners
Claude on AWS
Claude on Google Cloud
Learn
Blog
Courses
Use cases
Connectors
Customer stories
Engineering at Anthropic
Events
Powered by Claude
Service partners
Startups program
Company
Anthropic
Careers
Economic Futures
Research
News
Responsible Scaling Policy
Security and compliance
Transparency
Learn
Blog
Courses
Use cases
Connectors
Customer stories
Engineering at Anthropic
Events
Powered by Claude
Service partners
Startups program
Help and security
Availability
Status
Support
Discord
Terms and policies
Privacy policy
Responsible disclosure policy
Terms of service: Commercial
Terms of service: Consumer
Usage policy
API reference

Support & configuration
Rate limits

Copy page

To mitigate misuse and manage capacity on the API, limits are in place on how much an organization can use the Claude API.

Copy page


Claude Platform on AWS
:
The rate limits on this page apply to Claude Platform on AWS, but billing and limit management differ. Billing is through AWS Marketplace (not Anthropic credit purchases). Organizations on Claude Platform on AWS are placed on the Start tier and do not move between usage tiers automatically. To request higher limits, contact your Anthropic account representative or
Anthropic support
; the
Request rate limit increase
flow is not available. Per-workspace rate limit configuration and
fast mode
are not available on Claude Platform on AWS. For details, see
Rate limits and quotas on Claude Platform on AWS
.
There are two types of limits:
Spend limits
set a maximum monthly cost an organization can incur for API usage.
Rate limits
set the maximum number of API requests an organization can make over a defined period of time.
The API enforces service-configured limits at the organization level, but you may also set user-configurable limits for your organization's workspaces.

About rate limits
Limits are designed to prevent API abuse, while minimizing impact on common customer usage patterns.
Limits are defined by
usage tier
. Organizations are placed on a tier automatically based on usage history and account standing and can move to a higher tier over time as they use the API.
New organizations and organizations with limited usage history may start in the Evaluation tier, with limits below the standard limits shown on this page while account history is established. These starting limits are part of how Anthropic prevents fraud and abuse, and they increase automatically as your organization builds usage history.
Limits are set at the organization level. You can see your organization's tier and current limits on the
Rate limits
page in the
Claude Console
.
You might hit rate limits over shorter time intervals. For instance, a rate of 60 requests per minute (RPM) might be enforced as 1 request per second. Short bursts of requests can exceed the limit and trigger rate limit errors.
The following limits are the standard limits for each tier. If you need higher limits, see
Requesting higher limits
.
The API uses the
token bucket algorithm
to do rate limiting. This means that your capacity is continuously replenished up to your maximum limit, rather than being reset at fixed intervals.
All limits described here represent maximum allowed usage, not guaranteed minimums. These limits are intended to reduce unintentional overspend and ensure fair distribution of resources among users.

Spend limits

Claude Platform on AWS
:
Spend limits work differently on Claude Platform on AWS. See
Spend limits on Claude Platform on AWS
for how spend caps and self-set spend limits apply to your organization.
Each of the Start, Build, and Scale tiers carries a monthly spend cap, which is the maximum your organization can spend on the API each calendar month. Once you reach your tier's spend cap, API usage pauses until the next month unless you request a higher limit. You can view your organization's monthly spend cap and set your own limit on the
Billing
page.
Usage tier
Monthly spend cap
Start
$500 USD
Build
$1,000 USD
Scale
$200,000 USD
Organizations on the Custom tier have no monthly spend cap; limits are arranged with their account team.
You can also set your own spend limit below your tier's cap to control costs:
1
Navigate to the Billing page
Go to
Settings > Billing
in the Claude Console.
2
Open the spend limit editor
In the
Spend limits
section, click
Adjust limit
(or
Set limit
if no limit is currently set).
3
Adjust your spend limit
Enter a new value. Your spend limit cannot exceed your current tier's cap.

Rate limits
The rate limits for the Messages API are measured in requests per minute (RPM), input tokens per minute (ITPM), and output tokens per minute (OTPM) for each model class. If you exceed any of the rate limits you will get a
429 error
describing which rate limit was exceeded, along with a
retry-after
header indicating how long to wait.

You might also encounter 429 errors because of acceleration limits on the API if your organization has a sharp increase in usage. To avoid hitting acceleration limits, ramp up your traffic gradually and maintain consistent usage patterns.

Cache-aware ITPM
Many API providers use a combined "tokens per minute" (TPM) limit that may include all tokens, both cached and uncached, input and output.
For most Claude models, only uncached input tokens count toward your ITPM rate limits.
This is a key advantage that makes the rate limits effectively higher than they might initially appear.
ITPM rate limits are estimated at the beginning of each request, and the estimate is adjusted during the request to reflect the actual number of input tokens used.
Here's what counts toward ITPM:
input_tokens
(tokens after the last cache breakpoint) ✓
Count toward ITPM
cache_creation_input_tokens
(tokens being written to cache) ✓
Count toward ITPM
cache_read_input_tokens
(tokens read from cache) ✗
Do NOT count toward ITPM
for most models

The
input_tokens
field only represents tokens that appear
after your last cache breakpoint
, not all input tokens in your request. To calculate total input tokens:
total_input_tokens = cache_read_input_tokens + cache_creation_input_tokens + input_tokens

This means when you have cached content,
input_tokens
will typically be much smaller than your total input. For example, with a 200k token cached document and a 50 token user question, you'd see
input_tokens: 50
even though the total input is 200,050 tokens.
For rate limit purposes on most models, only
input_tokens
+
cache_creation_input_tokens
count toward your ITPM limit, making
prompt caching
an effective way to increase your effective throughput.
Example:
With a 2,000,000 ITPM limit and an 80% cache hit rate, you could effectively process 10,000,000 total input tokens per minute (2M uncached + 8M cached), because cached tokens don't count toward your rate limit.

Claude Haiku 3.5 (marked with † in the following rate limit tables) also counts
cache_read_input_tokens
toward ITPM rate limits.
For all models without the † marker, cached input tokens do not count toward rate limits and are billed at a reduced rate (10% of base input token price). This means you can achieve significantly higher effective throughput by using
prompt caching
.
To make the most of your rate limits, cache repeated content such as system instructions and prompts, large context documents, tool definitions, and conversation history; see
prompt caching
for guidance. With effective caching, you can substantially increase your actual throughput without raising your rate limits. Monitor your cache hit rate on the
Usage page
to tune your caching strategy.
OTPM rate limits are evaluated in real time as output tokens are produced, counting only the actual tokens generated. The
max_tokens
parameter does not factor into OTPM rate limit calculations, so there is no rate limit downside to setting a higher
max_tokens
value.
Rate limits are applied separately for each model; therefore you can use different models up to their respective limits simultaneously. You can check your current rate limits and behavior on the
Rate limits
page in the Claude Console, or read the configured limits programmatically with the
Rate Limits API
.

Rate limits are currently shared across all
inference_geo
values. Requests with
inference_geo: "us"
and
inference_geo: "global"
draw from the same rate limit pool.
Start tier
Build tier
Scale tier
Custom tier
Model
Maximum requests per minute (RPM)
Maximum input tokens per minute (ITPM)
Maximum output tokens per minute (OTPM)
Claude Fable 5
1,000
500,000
100,000
Claude Opus 5
1,000
2,000,000
400,000
Claude Opus 4.x
*
1,000
2,000,000
400,000
Claude Sonnet 5
1,000
2,000,000
400,000
Claude Sonnet 4.x
**
1,000
2,000,000
400,000
Claude Haiku 4.5
1,000
2,000,000
400,000
Claude Haiku 3.5 (
retired, except on Bedrock and Google Cloud
)
1,000
100,000
†
20,000
* Opus rate limit is a total limit that applies to combined traffic across Claude Opus 4.8, Opus 4.7, Opus 4.6, and Opus 4.5. Claude Opus 5 has a separate rate limit and is not part of this combined bucket.
** Sonnet 4.x rate limit is a total limit that applies to combined traffic across Sonnet 4.6 and Sonnet 4.5. Claude Sonnet 5 has a separate rate limit and is not part of this combined bucket.
† Limit counts
cache_read_input_tokens
toward ITPM usage.

Message Batches API
The Message Batches API has its own set of rate limits which are shared across all models. These include a requests per minute (RPM) limit to all API endpoints and a limit on the number of batch requests that can be in the processing queue at the same time. A "batch request" here refers to part of a Message Batch. You may create a Message Batch containing thousands of batch requests, each of which count toward this limit. A batch request is considered part of the processing queue when it has yet to be successfully processed by the model.
Start tier
Build tier
Scale tier
Custom tier
Maximum requests per minute (RPM)
Maximum batch requests in processing queue
Maximum batch requests per batch
1,000
200,000
100,000

Managed Agents
Claude Managed Agents
endpoints are rate-limited per organization. These limits are separate from the Messages API rate limits above.
Operation
Limit
Create endpoints (for example, agents, sessions, and environments)
300 requests per minute
Read endpoints (for example, retrieve, list, and stream)
1,200 requests per minute

Fast mode rate limits
When using
fast mode
(research preview) with
speed: "fast"
on Claude Opus 5 or Opus 4.8, dedicated rate limits apply that are separate from standard Opus rate limits. When fast mode rate limits are exceeded, the API returns a
429
error with a
retry-after
header. Fast mode is not available on Claude Opus 4.7 (requests return an error) or Claude Opus 4.6 (requests to
claude-opus-4-6
with
speed: "fast"
run at standard speed). See
Fast mode
.
The response includes
anthropic-fast-*
headers that indicate your fast mode rate limit status. See
Fast mode rate limits
for details on these headers.

Monitoring your rate limits in the Console
You can monitor your rate limit usage on the
Usage
page of the
Claude Console
.
In addition to providing token and request charts, the Usage page provides two separate rate limit charts. Use these charts to see what headroom you have to grow, identify when you may be hitting peak use, understand what rate limits to request, and learn how to improve your caching rates. The charts visualize a number of metrics for a given rate limit (for example, per model):
The
Rate Limit - Input Tokens
chart includes:
Hourly maximum uncached input tokens per minute
Your current input tokens per minute rate limit
The cache rate for your input tokens (that is, the percentage of input tokens read from the cache)
The
Rate Limit - Output Tokens
chart includes:
Hourly maximum output tokens per minute
Your current output tokens per minute rate limit

Requesting higher limits
To request higher rate limits or a higher monthly spend cap, use
Request rate limit increase
on the
Rate limits
page. Anthropic support can also raise limits; for urgent needs, contact
Anthropic support
.

Claude Platform on AWS
:
The
Request rate limit increase
flow is not available. Contact your Anthropic account representative or
Anthropic support
, and include the models you need raised, your peak input and output tokens per minute for each model, and roughly what share of your input is cached or repeated context. See
Rate limits and quotas on Claude Platform on AWS
.

Setting lower limits for Workspaces
For more about workspaces, see
Workspaces
.
To protect Workspaces in your Organization from potential overuse, you can set custom spend and rate limits per Workspace.
Example: If your Organization's limit is 40,000 input tokens per minute and 8,000 output tokens per minute, you might limit one Workspace to 30,000 input tokens per minute. This protects other Workspaces from potential overuse and ensures a more equitable distribution of resources across your Organization. The remaining unused tokens per minute (or more, if that Workspace doesn't use the limit) are then available for other Workspaces to use.
Note:
You can't set limits on the default Workspace.
If not set, Workspace limits match the Organization's limit.
Workspace limits are set per limiter type (such as requests per minute, input tokens per minute, or output tokens per minute).
Organization-wide limits always apply, even if Workspace limits add up to more.
To read your current organization and workspace rate limits programmatically, use the
Rate Limits API
.

Response headers
The API response includes headers that show you the rate limit enforced, current usage, and when the limit will be reset.
The following headers are returned:
Header
Description
retry-after
The number of seconds to wait until you can retry the request. Earlier retries will fail.
anthropic-ratelimit-requests-limit
The maximum number of requests allowed within any rate limit period.
anthropic-ratelimit-requests-remaining
The number of requests remaining before being rate limited.
anthropic-ratelimit-requests-reset
The time when the request rate limit will be fully replenished, provided in RFC 3339 format.
anthropic-ratelimit-tokens-limit
The maximum number of tokens allowed within any rate limit period.
anthropic-ratelimit-tokens-remaining
The number of tokens remaining (rounded to the nearest thousand) before being rate limited.
anthropic-ratelimit-tokens-reset
The time when the token rate limit will be fully replenished, provided in RFC 3339 format.
anthropic-ratelimit-input-tokens-limit
The maximum number of input tokens allowed within any rate limit period.
anthropic-ratelimit-input-tokens-remaining
The number of input tokens remaining (rounded to the nearest thousand) before being rate limited.
anthropic-ratelimit-input-tokens-reset
The time when the input token rate limit will be fully replenished, provided in RFC 3339 format.
anthropic-ratelimit-output-tokens-limit
The maximum number of output tokens allowed within any rate limit period.
anthropic-ratelimit-output-tokens-remaining
The number of output tokens remaining (rounded to the nearest thousand) before being rate limited.
anthropic-ratelimit-output-tokens-reset
The time when the output token rate limit will be fully replenished, provided in RFC 3339 format.
anthropic-priority-input-tokens-limit
The maximum number of Priority Tier input tokens allowed within any rate limit period. (Priority Tier only)
anthropic-priority-input-tokens-remaining
The number of Priority Tier input tokens remaining (rounded to the nearest thousand) before being rate limited. (Priority Tier only)
anthropic-priority-input-tokens-reset
The time when the Priority Tier input token rate limit will be fully replenished, provided in RFC 3339 format. (Priority Tier only)
anthropic-priority-output-tokens-limit
The maximum number of Priority Tier output tokens allowed within any rate limit period. (Priority Tier only)
anthropic-priority-output-tokens-remaining
The number of Priority Tier output tokens remaining (rounded to the nearest thousand) before being rate limited. (Priority Tier only)
anthropic-priority-output-tokens-reset
The time when the Priority Tier output token rate limit will be fully replenished, provided in RFC 3339 format. (Priority Tier only)
The
anthropic-ratelimit-tokens-*
headers display the values for the most restrictive limit currently in effect. For instance, if you have exceeded the Workspace per-minute token limit, the headers will contain the Workspace per-minute token rate limit values. If Workspace limits do not apply, the headers will return the total tokens remaining, where total is the sum of input and output tokens. This approach ensures that you have visibility into the most relevant constraint on your current API usage. To see which Workspace a request counted against, read the
anthropic-workspace-id
response header
, which carries the ID of the Workspace that your API key or access token resolved to.
Was this page helpful?


About rate limits
Spend limits
Rate limits
Cache-aware ITPM
Message Batches API
Managed Agents
Fast mode rate limits
Monitoring your rate limits in the Console
Requesting higher limits
Setting lower limits for Workspaces
Response headers
