Relevance Ai Rate Limits
Relevance AI publishes NO HTTP rate limit. There is no requests-per-second or requests-per-minute figure anywhere in the documentation, and a live call returned no rate-limit header of any kind. What the provider does publish, and what actually constrains a caller, is a set of hard system quotas plus per-tier consumption quotas and a per-tier concurrency ceiling. Exceeding concurrency QUEUES work rather than rejecting it, so there is no 429 to back off from. This file REPLACES a 2026-05-04 scaffold that invented requests-per-minute figures and X-RateLimit-* headers the API does not send.
Relevance Ai Rate Limits is the machine-readable rate-limit profile for Relevance AI on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 10 rate-limit definitions, measuring concurrent_tasks, actions, vendor_credits, seconds, and bytes.
The profile also includes response codes documented for throttled, quotaExceeded, observed, and note.
Tagged areas include AI Agents, Quotas, and Concurrency.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.