Reqkey Rate Limits
What ReqKey enforces on ITS OWN API. ReqKey advertises "no rate limits on any plan" for the metered request surface (/key/validate and /ingest) — the meter is a monthly request allowance, not a per-second cap, and crossing the allowance does not hard-stop traffic. The analytics endpoints are the one exception: they are rate-limited per customer, though ReqKey does not publish the numeric limit. Consumer-level rate limits configured through /consumer/create are a PRODUCT FEATURE ReqKey offers its customers for their own APIs, not a limit on the ReqKey API; they are recorded separately below so the two are never conflated.
Reqkey Rate Limits is the machine-readable rate-limit profile for ReqKey on the APIs.io network, in the API Commons Rate Limits shape.
It captures 6 rate-limit definitions, measuring requests_per_month, keys, and requests.
Limit state is signalled in the requestId, rateLimitLimit, rateLimitRemaining, and rateLimitWindow response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and quotaExceeded.
Tagged areas include Rate Limiting, API Management, and Usage Metering.
requestIdrateLimitLimitrateLimitRemainingrateLimitWindow
Limits
Sources
- https://www.reqkey.com/pricing
- https://www.reqkey.com/docs/errors
- https://www.reqkey.com/docs/api/analytics
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.