Keygen Rate Limits
Keygen enforces sliding-window rate limits that differ by whether requests originate client-side (unauthenticated, license, or user tokens) or server-side (admin, environment, or product tokens). Client-side traffic is the more constrained tier - roughly a 60-request burst per 30 seconds with a sustained ceiling around 500 requests per 5 minutes - while server-side tokens receive substantially higher, undocumented ceilings suited to back-end automation. Limits and the current window are surfaced on every response via X-RateLimit-* headers, and throttled requests return 429 with a Retry-After header.
Keygen Rate Limits is the machine-readable rate-limit profile for Keygen on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests.
Limit state is signalled in the X-RateLimit-Window, X-RateLimit-Count, X-RateLimit-Limit, and X-RateLimit-Remaining 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 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Software Licensing, Distribution, Rate Limiting, Quotas, and Throttling.
X-RateLimit-WindowX-RateLimit-CountX-RateLimit-LimitX-RateLimit-Remaining
generated, dated 2026-07-01.
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.