2026-10-17 06:12 UTC · anthropic/rate-limits · live page
Summary by gemma-4-12b. It may be wrong; the diff below is what actually changed. Raw: 0b5445ec85-anthropic-rate-limits.diff · commit 0b5445ec85
diff --git a/snapshots/anthropic/rate-limits.md b/snapshots/anthropic/rate-limits.mdindex dc7c773..0a9272a 100644--- a/snapshots/anthropic/rate-limits.md+++ b/snapshots/anthropic/rate-limits.md@@ -15,5 +15,5 @@ The API enforces service-configured limits at the organization level, but you ma - 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.+- Limits are set at the organization level. You can see your organization's tier and current limits on the Rate limits page (`platform.claude.com/usage/limits`) 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.@@ -25,5 +25,5 @@ The API enforces service-configured limits at the organization level, but you ma Claude Platform on AWS: The same monthly spend caps apply, and requests stop at the cap in the same way. Billing and tier increases work differently; see Spend limits on Claude Platform on AWS. -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. You can view your organization's monthly spend cap and set your own limit on the Billing page.+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. You can view your organization's monthly spend cap and set your own limit on the Billing page in the Claude Console. | Usage tier | Monthly spend cap |@@ -60,5 +60,5 @@ 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.+ In the Claude Console, go to the Billing page (`platform.claude.com/settings/billing`). 2. ### Open the spend limit editor In the Spend limits section, click Adjust limit (or Set limit if no limit is currently set).@@ -72,5 +72,5 @@ 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, along with a `retry-after` header indicating how long to wait.+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.@@ -104,9 +104,9 @@ 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 to tune your caching strategy.+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. 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.+Each row in the following tables has its own RPM, ITPM, and OTPM limits. Some rows cover several models that share one limit; see the notes under the tables. 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.@@ -210,5 +210,5 @@ Files API requests have their own per-organization limit, shared across upload, ### Fast mode rate limits -When using fast mode (research preview) with `speed: "fast"` on Claude Opus 5.5, 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.+When using fast mode with `speed: "fast"` on Claude Opus 5.5, Claude Opus 5, or Claude Opus 4.8, dedicated rate limits apply that are separate from standard Opus rate limits. Claude Opus 5.5 has a default fast mode rate limit in the Start, Build, and Scale tiers, so you don't need to request access to use fast mode with it. Organizations in the Evaluation tier can use fast mode with Claude Opus 5.5 once they move to the Start, Build, or Scale tier. Fast mode for Claude Opus 5 and Claude Opus 4.8 is in research preview. To see your fast mode rate limits, go to the Rate limits page in the Claude Console. When fast mode rate limits are exceeded, the API returns a `429` error with a `retry-after` header. The response includes `anthropic-fast-*` headers that indicate your fast mode rate limit status. See Fast mode rate limits for details on these headers.@@ -230,5 +230,5 @@ In addition to providing token and request charts, the Usage page provides two s ## Requesting higher limits -To request higher rate limits or a higher monthly spend cap, use Request tier increase on the Rate limits page. Anthropic support can also raise limits; for urgent needs, contact Anthropic support.+To request higher rate limits or a higher monthly spend cap, use Request tier increase on the Rate limits page in the Claude Console. Anthropic support can also raise limits; for urgent needs, contact Anthropic support. 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.@@ -259,5 +259,5 @@ 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. Not sent with the spend-cap 429 (see Reaching your spend cap). |+| `retry-after` | The number of seconds to wait until you can retry the request. Earlier retries will fail. Not every 429 carries it; the spend-cap 429 never does (see Reaching your spend cap). | | `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. |