2026-10-24 18:19 UTC · anthropic/rate-limits · live page
Summary by fallback. It may be wrong; the diff below is what actually changed. Raw: 9a44a07459-anthropic-rate-limits.diff · commit 9a44a07459
diff --git a/snapshots/anthropic/rate-limits.md b/snapshots/anthropic/rate-limits.mdindex 0a9272a..b37796a 100644--- a/snapshots/anthropic/rate-limits.md+++ b/snapshots/anthropic/rate-limits.md@@ -8,5 +8,5 @@ There are two types of limits: 2. 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.+The API enforces service-configured limits at the organization level, but you can also set user-configurable limits for your organization's workspaces. ## About rate limits@@ -66,5 +66,5 @@ You can also set your own spend limit below your tier's cap to control costs: Enter a new value. Your spend limit cannot exceed your current tier's cap. -When usage reaches a spend limit you set, requests return HTTP 400 with error type `invalid_request_error`. The message begins `You have reached your specified API usage limits`, or `You have reached your specified workspace API usage limits` for a workspace limit, and states when access resumes. Raise or remove the limit to restore access sooner.+When usage reaches a spend limit you set, requests return HTTP 400 with error type `invalid_request_error`. The message starts with `You have reached your specified API usage limits`, or `You have reached your specified workspace API usage limits` for a workspace limit, and states when access resumes. Raise or remove the limit to restore access sooner. Limits on the Claude Code workspace are checked separately: Claude Code requests over that workspace's limit can instead receive a 429 that carries a `retry-after` header.@@ -72,11 +72,11 @@ Limits on the Claude Code workspace are checked separately: Claude Code requests ## 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. When the response has a `retry-after` header, wait that many seconds before retrying.+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. When the response has a `retry-after` header, wait that many seconds before retrying. -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.+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, increase 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.+Many API providers use a combined "tokens per minute" (TPM) limit that might 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.@@ -94,9 +94,9 @@ total_input_tokens = cache_read_input_tokens + cache_creation_input_tokens + inp ``` -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.+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.+Example: With a 2,000,000 ITPM limit and an 80 percent 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 footnote 4 in the following rate limit tables) also counts `cache_read_input_tokens` toward ITPM rate limits.@@ -104,5 +104,5 @@ Claude Haiku 3.5 (marked with footnote 4 in the following rate limit tables) als For all other models, cached input tokens do not count toward rate limits and are billed at the cache read rate, a fraction of the base input 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 in the Claude Console to tune your caching strategy.+To get the highest throughput within 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 in the Claude Console 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.@@ -125,5 +125,5 @@ Start tier | Claude Haiku 5.5 | 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 Google Cloud) | 1,000 | 100,0004 | 20,000 |+| Claude Haiku 3.5 (retired, except on Claude Models on Google Cloud (Google managed)) | 1,000 | 100,0004 | 20,000 | Build tier@@ -140,5 +140,5 @@ Build tier | Claude Haiku 5.5 | 5,000 | 5,000,000 | 1,000,000 | | Claude Haiku 4.5 | 5,000 | 5,000,000 | 1,000,000 |-| Claude Haiku 3.5 (retired, except on Google Cloud) | 2,000 | 200,0004 | 40,000 |+| Claude Haiku 3.5 (retired, except on Claude Models on Google Cloud (Google managed)) | 2,000 | 200,0004 | 40,000 | Scale tier@@ -155,5 +155,5 @@ Scale tier | Claude Haiku 5.5 | 10,000 | 10,000,000 | 2,000,000 | | Claude Haiku 4.5 | 10,000 | 10,000,000 | 2,000,000 |-| Claude Haiku 3.5 (retired, except on Google Cloud) | 4,000 | 400,0004 | 80,000 |+| Claude Haiku 3.5 (retired, except on Claude Models on Google Cloud (Google managed)) | 4,000 | 400,0004 | 80,000 | Custom tier@@ -171,5 +171,5 @@ If you need limits higher than the Scale tier, contact sales through the Rate li ### 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.+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 can create a Message Batch containing thousands of batch requests, each of which counts 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@@ -197,5 +197,5 @@ If you need limits higher than the Scale tier, contact sales through the Rate li ### Managed Agents -Claude Managed Agents endpoints are rate-limited per organization. These limits are separate from the Messages API rate limits above.+Claude Managed Agents endpoints are rate-limited for each organization. These limits are separate from the Messages API rate limits described earlier on this page. | Operation | Limit |@@ -218,5 +218,5 @@ The response includes `anthropic-fast-*` headers that indicate your fast mode ra 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):+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 might 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, for each model): - The Rate Limit - Input Tokens chart includes:@@ -234,9 +234,9 @@ To request higher rate limits or a higher monthly spend cap, use Request tier in Claude Platform on AWS: The Request tier 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+## 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.+To protect Workspaces in your Organization from potential overuse, you can set custom spend and rate limits for each 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.@@ -244,7 +244,7 @@ Example: If your Organization's limit is 40,000 input tokens per minute and 8,00 Note: -- You can't set limits on the default Workspace.+- You can't set spend 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).+- Workspace limits are set for each 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.