2026-06-27 08:24 UTC · anthropic/rate-limits · live page
Summary by fallback. It may be wrong; the diff below is what actually changed. Raw: 4180326e38-anthropic-rate-limits.diff · commit 4180326e38
diff --git a/snapshots/anthropic/rate-limits.md b/snapshots/anthropic/rate-limits.mdindex b18898b..abf2768 100644--- a/snapshots/anthropic/rate-limits.md+++ b/snapshots/anthropic/rate-limits.md@@ -1,5 +1,5 @@ <!-- fineprint snapshot: anthropic/rate-limits | source: https://platform.claude.com/docs/en/api/rate-limits --> -Claude Platform on AWS: The rate limits on this page apply. Billing and spend limits differ: spend limits are not available, and billing is through AWS Marketplace (not Anthropic credit purchases). Organizations start at Tier 1. Rate limit increases go through your Anthropic account representative; there is no automatic tier advancement, and per-workspace rate limit configuration is not available. Fast mode is not available on Claude Platform on AWS.+Claude Platform on AWS: The rate limits on this page apply. Billing and spend limits differ: spend limits are not available, and billing is through AWS Marketplace (not Anthropic credit purchases). Organizations on Claude Platform on AWS are placed on the Start tier and do not move between usage tiers automatically. To request higher limits, contact your Anthropic account representative. Per-workspace rate limit configuration and fast mode are not available on Claude Platform on AWS. There are two types of limits:@@ -10,40 +10,29 @@ There are two types of limits: The API enforces service-configured limits at the organization level, but you may also set user-configurable limits for your organization's workspaces. -These limits apply to both Standard and Priority Tier usage. For more information about Priority Tier, which offers enhanced service levels in exchange for committed spend, see Service Tiers.+These limits apply to both Standard and Priority Tier usage. For more information about Priority Tier, see Service Tiers. ## About rate 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.+- Limits are defined by usage tier. Your organization is placed on a tier automatically and can move to a higher tier over time as you use the API.+- Limits are set at the organization level. You can see your organization's tier and current limits on the Limits page 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.+- The API uses the token bucket algorithm to do rate limiting. This means that your capacity is continuously replenished up to your maximum limit, rather than being reset at fixed intervals.+- All limits described here represent maximum allowed usage, not guaranteed minimums. These limits are intended to reduce unintentional overspend 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.+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 on the Limits page. -To qualify for the next tier, you must meet a deposit requirement. 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 | Max credit purchase | Monthly spend limit |-|---|---|---|---|-| Tier 1 | $5 | $500 | $500 |-| Tier 2 | $40 | $500 | $500 |-| Tier 3 | $200 | $1,000 | $1,000 |-| Tier 4 | $400 | $200,000 | $200,000 |-| Monthly Invoicing | N/A | N/A | No limit |--Credit purchase shows the cumulative credit purchases (excluding tax) required to advance to that tier. You advance immediately upon reaching the threshold.--Max credit purchase limits the maximum amount you can add to your account in a single transaction to prevent account overfunding.--Monthly spend limit is the maximum you can spend on the API each calendar month at that tier.--## Increasing your spend limits--Your organization has two kinds of spend limits: a customer-set limit you control directly, and a tier-enforced ceiling set by your usage tier. Each has a different process for increasing it.+| Usage tier | Monthly spend cap |+|---|---|+| Start | $500 |+| Build | $1,000 |+| Scale | $200,000 | -### Customer-set spend limits+Organizations on the Custom tier have no monthly spend cap; limits are arranged with their account team. -You can set a spend limit lower than your tier's ceiling to control costs. To adjust it:+You can also set your own spend limit below your tier's cap to control costs: 1. Navigate to the Limits page@@ -52,13 +41,5 @@ You can set a spend limit lower than your tier's ceiling to control costs. To ad In the Spend limits section, click Change Limit (or Set spend limit if no limit is currently set). 3. Adjust your spend limit- Enter a new value. Your customer-set limit cannot exceed your current tier's limit.--### Tier-enforced spend limits--When you need a limit higher than your tier's ceiling (Tier 4's ceiling is $200,000 per month), click Contact Sales on the Limits page. This opens the contact form in a new tab, and a member of the sales team will follow up by email when your organization is upgraded.--Monthly Invoicing removes the monthly spend cap entirely and uses Net-30 payment terms by default.--Support can also raise tier-enforced limits. For urgent needs, contact support.+ Enter a new value. Your spend limit cannot exceed your current tier's cap. ## Rate limits@@ -113,5 +94,5 @@ Rate limits are applied separately for each model; therefore you can use differe 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. -* - Opus rate limit is a total limit that applies to combined traffic across Claude Opus 4.8, Opus 4.7, Opus 4.6, Opus 4.5, and Opus 4.1 (deprecated).+* - Opus rate limit is a total limit that applies to combined traffic across Claude Opus 4.8, Opus 4.7, Opus 4.6, and Opus 4.5. ** - Sonnet 4.x rate limit is a total limit that applies to combined traffic across Sonnet 4.6 and Sonnet 4.5.@@ -130,5 +111,5 @@ Claude Managed Agents endpoints are rate-limited per organization. These limits |---|---| | Create endpoints (for example, agents, sessions, and environments) | 300 requests per minute |-| Read endpoints (for example, retrieve, list, and stream) | 600 requests per minute |+| Read endpoints (for example, retrieve, list, and stream) | 1,200 requests per minute | ### Fast mode rate limits@@ -152,4 +133,10 @@ In addition to providing token and request charts, the Usage page provides two s - Your current output tokens per minute rate limit +## Requesting higher limits++To request higher rate limits or a higher monthly spend cap, use Request rate limit increase on the Limits page.++Support can also raise limits. For urgent needs, contact support.+ ## Setting lower limits for Workspaces