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, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests.
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.
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.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/keygen-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.