2026-08-22 03:48 UTC · anthropic/rate-limits · live page
Summary by fallback. It may be wrong; the diff below is what actually changed. Raw: 6eb6ef909c-anthropic-rate-limits.diff · commit 6eb6ef909c
diff --git a/snapshots/anthropic/rate-limits.md b/snapshots/anthropic/rate-limits.mdindex 181d60e..0ede788 100644--- a/snapshots/anthropic/rate-limits.md+++ b/snapshots/anthropic/rate-limits.md@@ -23,7 +23,7 @@ The API enforces service-configured limits at the organization level, but you ma ## 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.+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. 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.+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. | Usage tier | Monthly spend cap |@@ -35,4 +35,26 @@ Each of the Start, Build, and Scale tiers carries a monthly spend cap, which is Organizations on the Custom tier have no monthly spend cap; limits are arranged with their account team. +### Reaching your spend cap++Once you reach your tier's spend cap, API usage pauses until 00:00 UTC on the first day of the next month, unless you request a higher limit sooner. While usage is paused, API requests return HTTP 429:++```+{+ "type": "error",+ "error": {+ "type": "rate_limit_error",+ "message": "You have reached your API usage limits: your organization has crossed its monthly API usage threshold, set based on your organization's API tier. You will regain access on 2026-09-01 at 00:00 UTC.",+ "details": { "error_code": "enforced_spend_limit_reached" }+ },+ "request_id": "req_018EeWyXxfu5pfWkrYcMdjWG"+}+```++- The error type is `rate_limit_error`, the same as for a rate limit, but the response has no `retry-after` header. Retrying, including the SDKs' automatic retries, fails until access resumes.+- On the Messages API, `error.details.error_code` is `enforced_spend_limit_reached`. Use it to tell this response apart from a rate limit.+- Moving to a higher tier restores access; see Requesting higher limits.++### Setting your own spend limit+ You can also set your own spend limit below your tier's cap to control costs: @@ -44,4 +66,8 @@ 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.++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.+ ## Rate limits @@ -119,4 +145,8 @@ Claude Managed Agents endpoints are rate-limited per organization. These limits | Read endpoints (for example, retrieve, list, and stream) | 1,200 requests per minute | +### Files API++Files API requests have their own per-organization limit, shared across upload, list, retrieve, download, and delete operations and separate from the Messages API limits described earlier on this page. See Files API rate limits for the current value.+ ### Fast mode rate limits @@ -170,5 +200,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. |+| `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). | | `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. |