Clarifications and Additions to Claude API Rate Limit Documentation
Detected October 15, 2026, 05:15 UTC · Claude API rate limits
The documentation for Claude API rate limits now includes specific console navigation paths for viewing and managing limits and spend caps, and clarifies that not all 429 errors will include a retry-after header, specifically noting its absence for spend-cap related errors.
The updated Anthropic documentation for Claude API rate limits provides enhanced guidance on how users can manage and understand their API usage. It specifies that limits are applied at the organizational level and directs users to the 'Rate limits' page within the Claude Console at a precise URL (platform.claude.com/usage/limits) to view their tier and current limits. For managing monthly spend caps, the document now explicitly guides users to the 'Billing' page in the Claude Console (platform.claude.com/settings/billing). The explanation for 429 errors has been refined, clarifying that while such errors indicate exceeding a rate limit, the `retry-after` header, which advises on waiting times, will not be present when a spend cap has been reached. Furthermore, it clarifies that each row in the rate limit tables has its own RPM, ITPM, and OTPM limits, and some rows consolidate several models under a single limit. The process for requesting higher limits or spend caps also specifies using the 'Request tier increase' option on the 'Rate limits' page.
We compare this page once a day and record every difference. The text above is written by Claude Network from that comparison; none of it is copied from the source.
Source: Claude API rate limits