Redocly Rate Limits
Redocly publishes PLAN QUOTAS but no HTTP rate limits. Seats, projects, pages and Respect Monitoring requests are all bounded and priced; the request-rate behaviour of Redocly's own HTTP APIs is not documented anywhere. No published contract declares a 429 response, and none declares a RateLimit-*, X-RateLimit-* or Retry-After header — so an agent calling a Redocly API has no runtime signal to back off on. This is a notable gap for a vendor that publishes a governance guide on API rate limiting.
Redocly Rate Limits is the machine-readable rate-limit profile for Redocly on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 9 rate-limit definitions, across the enterprise-plus, pro, enterprise, respect-free, and respect-commit-20k tiers, measuring pages, projects, and requests_per_month.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include API Catalog, API Documentation, Arazzo, Developer Portal, and Governance.
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.