Agilix Rate Limits
Buzz throttles on three distinct axes and the provider is explicit that all three can answer 429 with a Retry-After header, so a client must read the other response headers to tell them apart. (1) Time limiting — a per-customer budget of server processing time, bucketed per endpoint hostname, which is what most legitimate 429s are. (2) Rate limiting — per-endpoint call counts in a five-minute window, applied to security-sensitive and expensive-AI commands. (3) Server-busy limiting — 503 when autoscaling has not caught up. Specific rate-limited commands and their numeric limits are deliberately NOT published ("subject to immediate change in response to security and availability issues"); the provider's stated substitute is that the live limit is always readable from the response headers.
Agilix Rate Limits is the machine-readable rate-limit profile for Agilix on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions.
Limit state is signalled in the X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After response headers.
Tagged areas include Company, Education, EdTech, LMS, and K-12.
X-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-ResetRetry-After
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.