Observed source change · Anthropic
Claude API rate limits documentation changed
Published documentation; runtime behavior and legal interpretation not established.
Last unchanged check: 2026-10-21T18:50:12Z
First changed check: 2026-10-21T20:55:12Z
Before
The API enforces service-configured limits at the organization level, but you may also set user-configurable limits for your organization's workspaces. 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. The rate limits for the Messages API are measured in requests per minute (RPM), input …
After
The API enforces service-configured limits at the organization level, but you can also set user-configurable limits for your organization's workspaces. When usage reaches a spend limit you set, requests return HTTP 400 with error type `invalid_request_error`. The message starts with `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. The rate limits for the Messages API are measured in requests per minute (RPM), …
Capture provenance and limitations
Raw before SHA-256: 00194eb8ec221f26de4c135941be011edfa77e565dc3ef0b00bd385affe39827
Raw after SHA-256: 959581b9f4e162affc25823058a10d89d01f588908556a5e85674770d47d91ac
Full source responses are retained in the private evidence archive. Public excerpts show changed wording and may be truncated. The observed interval does not establish the vendor’s exact edit time. Hashes identify retained bytes; they are not an independent timestamp certificate.
Download archived excerpts and capture metadata · Back to the tracker