Claix Dev Rate Limits
One published rate limit: the A2A endpoint allows 60 requests per minute per API key and answers HTTP 429 with a Retry-After header (JSON-RPC error -32000). The REST routes and the MCP server publish no numeric limit and no rate-limit headers; the OpenAPI declares no 429 response. The official Python SDK nevertheless retries on 429, 502, 503 and 504, which is the only evidence that REST throttling exists. Payload size limits are published per endpoint and are recorded as policies because they are the limits an agent actually hits.
Claix Dev Rate Limits is the machine-readable rate-limit profile for Claix on the APIs.io network, in the API Commons Rate Limits shape.
It captures 1 rate-limit definition, measuring requests_per_minute.
Limit state is signalled in the retryAfter, rateLimitLimit, rateLimitRemaining, and rateLimitReset response headers, and an exhausted limit returns HTTP 429.
The profile also includes 6 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Rate Limiting and Document Processing.
retryAfterrateLimitLimitrateLimitRemainingrateLimitReset
Limits
Policies
Sources
- https://www.claix.dev/documentation/a2a
- https://www.claix.dev/documentation/sdks
- https://www.claix.dev/openapi.yaml
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.