Pypi Rate Limits
PyPI does not publish a hard per-second rate limit. The JSON, Index, and RSS APIs are heavily cached and CDN-fronted via Fastly, so PyPI states there is "currently no rate limiting of PyPI APIs at the edge." The legacy XML-RPC API may be rate-limited if usage degrades service. PyPI reserves the right to ban irresponsible consumers.
Pypi Rate Limits is the machine-readable rate-limit profile for PyPI on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring varies.
Limit state is signalled in the cache, cacheHits, and etag response headers, and 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 5 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Package Registry, Python, Open Source, and Rate Limiting.
cachecacheHitsetag
generated, dated 2026-05-05.
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.