Terminology update for requesting higher API usage tiers
Detected October 9, 2026, 05:15 UTC · Claude API rate limits
The self-service interface option for adjusting account allowances was previously named "Request rate limit increase" and has been updated to "Request tier increase." This wording change applies to standard accounts and the corresponding guidance for AWS Marketplace environments.
The documentation outlines throughput controls, token allowances, and spend boundaries for the Claude API, including administrative procedures for organizations accessing services through AWS Marketplace. Within this guide, instructions for submitting quota and budget adjustments have been revised. Users seeking higher capacity previously followed an interface action designated as requesting a rate limit increase, which has now been renamed to focus on requesting a tier increase. For standard platform developers, this change modifies the label they must locate in the administrative console to raise their throughput parameters and spending caps. For enterprise teams running on AWS Marketplace, self-service adjustments remain unsupported under the new nomenclature. Those AWS users must still contact customer assistance or their account manager directly, supplying operational metrics such as targeted models, peak token volumes per minute, and estimated context caching ratios. The documentation update addresses only the terminology of the submission pathway; it remains unclear whether the operational criteria for tier qualification, review timelines, or underlying resource allocations have been modified alongside the renamed interface link.
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