vLLM Rate Limits
vLLM does not impose project-level API rate limits. Throughput is bounded by GPU memory, model size, batch settings (--max-num-seqs, --max-model-len), and tensor/pipeline parallelism. Optionally, set --api-key to require auth and put a reverse proxy (Nginx, Envoy) in front to enforce per-client throttles.
vLLM Rate Limits is the machine-readable rate-limit profile for vLLM on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring n/a and concurrent-requests.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include LLM, Inference, Open Source, GPU, and OpenAI Compatible.
generated, dated 2026-05-08.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.