Aimlapi Rate Limits
The honest finding is a gap. AIMLAPI documents exactly one numeric rate limit, on one reporting endpoint, and returns NO rate-limit headers of any kind on any response we observed. A client cannot discover its remaining budget, its window, or its backoff interval from the API — it can only discover that it has already been throttled, from a 429 with no Retry-After.
Aimlapi Rate Limits is the machine-readable rate-limit profile for AIMLAPI on the APIs.io network, in the API Commons Rate Limits shape.
It captures 1 rate-limit definition.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, quotaExceeded, quotaExceededNote, and serviceUnavailable.
Tagged areas include Artificial Intelligence, Machine Learning, AI Models, LLM, and Image Generation.
limitremainingresetretryAfter
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.