Rate limits
To mitigate against misuse and manage capacity on our API, we have implemented limits on how much an organization can use the Claude API.
We have 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.
We enforce service-configured limits at the organization level, but you may also set user-configurable limits for your organization’s workspaces.
About our limits
- Limits are designed to prevent API abuse, while minimizing impact on common customer usage patterns.
- Limits are defined by usage tier, where each tier is associated with a different set of spend and rate limits.
- Your organization will increase tiers automatically as you reach certain thresholds while using the API. Limits are set at the organization level. You can see your organization’s limits in the Limits page in the Anthropic Console.
- You may hit rate limits over shorter time intervals. For instance, a rate of 60 requests per minute (RPM) may be enforced as 1 request per second. Short bursts of requests at a high volume can surpass the rate limit and result in rate limit errors.
- The limits outlined below are our standard limits. If you’re seeking higher, custom limits, contact sales through the Anthropic Console.
- We use the token bucket algorithm to do rate limiting.
- All limits described here represent maximum allowed usage, not guaranteed minimums. These limits are designed to prevent overuse and ensure fair distribution of resources among users.
Spend limits
Each usage tier has a limit on how much you can spend on the API each calendar month. Once you reach the spend limit of your tier, until you qualify for the next tier, you will have to wait until the next month to be able to use the API again.
To qualify for the next tier, you must meet a deposit requirement and a mandatory wait period. Higher tiers require longer wait periods. Note, to minimize the risk of overfunding your account, you cannot deposit more than your monthly spend limit.
Requirements to advance tier
| Usage Tier | Credit Purchase | Wait After First Purchase | Max Usage per Month |
|---|---|---|---|
| Tier 1 | $5 | 0 days | $100 |
| Tier 2 | $40 | 7 days | $500 |
| Tier 3 | $200 | 7 days | $1,000 |
| Tier 4 | $400 | 14 days | $5,000 |
| Monthly Invoicing | N/A | N/A | N/A |
Updated rate limits
Our rate limits are measured in requests per minute, input tokens per minute, and output tokens per minute for each model class. If you exceed any of the rate limits you will get a 429 error. Click on the rate limit tier to view relevant rate limits.
Rate limits are tracked per model. Therefore, models within the same tier do not share a rate limit.
| Model | Maximum requests per minute (RPM) | Maximum input tokens per minute (ITPM) | Maximum output tokens per minute (OTPM) |
|---|---|---|---|
| Claude 3.5 Sonnet 2024-10-22 | 50 | 40,000 | 8,000 |
| Claude 3.5 Sonnet 2024-06-20 | 50 | 40,000 | 8,000 |
| Claude 3.5 Haiku | 50 | 50,000 | 10,000 |
| Claude 3 Opus | 50 | 20,000 | 4,000 |
| Claude 3 Sonnet | 50 | 40,000 | 8,000 |
| Claude 3 Haiku | 50 | 50,000 | 10,000 |
Setting lower limits for Workspaces
In order 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 48,000 tokens per minute (40,000 input tokens and 8,000 output tokens), you might limit one Workspace to 30,000 total 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.
- Organization-wide limits always apply, even if Workspace limits add up to more.
- Support for input and output token limits will be added to Workspaces in the future.
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 |
|---|---|
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 reset, 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 reset, 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 reset, 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 reset, provided in RFC 3339 format. |
retry-after | The number of seconds until you can retry the request. |
The anthropic-ratelimit-tokens-* headers display the values for the most restrictive limit currently in effect. For example, 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.
Legacy rate limits
Our rate limits were previously measured in requests per minute, tokens per minute, and tokens per day for each model class. If you exceed any of the rate limits you will get a 429 error. Click on the rate limit tier to view relevant rate limits.
Rate limits are tracked per model, therefore models within the same tier do not share a rate limit.
| Model | Maximum requests per minute (RPM) | Maximum tokens per minute (TPM) | Maximum tokens per day (TPD) |
|---|---|---|---|
| Claude 3.5 Sonnet 2024-10-22 | 50 | 40,000 | 1,000,000 |
| Claude 3.5 Sonnet 2024-06-20 | 50 | 40,000 | 1,000,000 |
| Claude 3.5 Haiku | 50 | 50,000 | 5,000,000 |
| Claude 3 Opus | 50 | 20,000 | 1,000,000 |
| Claude 3 Sonnet | 50 | 40,000 | 1,000,000 |
| Claude 3 Haiku | 50 | 50,000 | 5,000,000 |