2026-08-15 15:32 UTC · anthropic/rate-limits · live page
Summary by fallback. It may be wrong; the diff below is what actually changed. Raw: 08c6714cf1-anthropic-rate-limits.diff · commit 08c6714cf1
diff --git a/snapshots/anthropic/rate-limits.md b/snapshots/anthropic/rate-limits.mdindex aaf9dfb..181d60e 100644--- a/snapshots/anthropic/rate-limits.md+++ b/snapshots/anthropic/rate-limits.md@@ -78,14 +78,5 @@ Claude Haiku 3.5 (marked with † in the following rate limit tables) also count 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. -Maximize your rate limits with prompt caching--See prompt caching for guidance on increasing effective throughput by caching repeated content such as:--- System instructions and prompts-- Large context documents-- Tool definitions-- Conversation history--With effective caching, you can dramatically increase your actual throughput without increasing your rate limits. Monitor your cache hit rate on the Usage page to optimize 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 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.@@ -150,7 +141,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 rate limit increase on the Rate limits page.--Support can also raise limits. For urgent needs, contact Anthropic support.+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.@@ -201,3 +190,3 @@ The following headers are returned: | `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.+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.