Unverified50% confidenceFactExact time
LLM APIs rate-limit on two independent dimensions, requests per minute and tokens per minute; even with monthly budget to spare, an endpoint can still return 429 during traffic peaks.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedModern LLM rate limiting is a multi-dimensional throughput constraint that evaluates RPM, TPM, RPD and TPD/consumption limits simultaneously, returning HTTP 429 as soon as any dimension hits its ceiling.74% similarUnverifiedRate limiting (429) on free LLM APIs is usually metered simultaneously across four dimensions—RPM, TPM, RPD and concurrency—and different dimensions require different remediation strategies.73% similarUnverifiedThe billing dimension of LLM gateways has changed from "number of requests" to "number of input and output tokens," requiring precise metering and quota management.69% similarUnverifiedCounting throughput by counting streaming chunks will be severely underestimated (43 tok/s measured), because under speculative decoding vLLM sends the entire accepted batch (about 2.5 tokens per chunk); the correct approach is to read usage.completion_tokens from the final chunk and enable stream_options: include_usage.67% similarUnverifiedRPM and TPM are two orthogonal dimensions of model API rate limiting: RPM constrains call frequency, independent of request body size; TPM constrains the total number of Tokens consumed per unit of time, and both take effect simultaneously, with a 429 returned as soon as either is hit first.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1052067API
curl https://kongchang.com/api/v1/knowledge/claims/1052067MCP
get_claim(id=1052067)