Inference
Caps on how much traffic an organization can send to a model API, measured in requests per minute (RPM) and tokens per minute (TPM).
Caps on how much traffic an organization can send to a model API, measured in requests per minute (RPM) and tokens per minute (TPM). Anthropic splits the token cap into input tokens per minute (ITPM) and output tokens per minute (OTPM), refills capacity continuously with a token bucket rather than resetting each minute, and does not count cached input reads toward ITPM on most models. Exceeding any limit returns HTTP 429, usually with a retry-after header, and limits rise with your usage tier.
Primary source: platform.claude.com
Example
In practice, developers reach for Rate Limits (RPM and TPM) when they need the capability described above as part of an AI feature or workflow.
Hands-on guides, comparisons, and tutorials that cover Inference.
FAQ
Caps on how much traffic an organization can send to a model API, measured in requests per minute (RPM) and tokens per minute (TPM).
Rate Limits (RPM and TPM) sits in the Inference part of the AI stack. Understanding it helps you make better decisions when building, debugging, and shipping AI features.
Developers Digest publishes tutorials and videos that cover Inference topics including Rate Limits (RPM and TPM). Check the blog and YouTube channel for hands-on walkthroughs.
Related
The split pricing model where LLM APIs charge one rate per million tokens you send (input) and a higher rate per million tokens the model generates (output).
An API setting that tells a reasoning model how much work to put into a response, trading answer quality against latency and token cost.
Two methods for controlling the randomness of model output during token generation.

New tutorials, open-source projects, and deep dives on coding agents - delivered weekly.