Skip to main content

How rate limiting works

The Mandate API enforces per-agent rate limits to protect service stability. Limits are tracked per runtime key. When you exceed the limit, the API returns a 429 Too Many Requests response with a Retry-After header.

Default limits

These limits apply per runtime key. Different agents with different keys have independent rate limits.

Response headers

Every API response includes rate limit headers:

429 response format

The Retry-After header contains the number of seconds to wait.

Retry strategy

Use exponential backoff when you receive a 429 response:
Do not poll /intents/{id}/status in a tight loop. The SDK’s waitForApproval() and waitForConfirmation() methods use appropriate intervals (5s and 3s respectively) to stay within rate limits.
If your agent needs higher limits for production workloads, contact the Mandate team. Custom rate limits are available for high-volume deployments.

Next Steps

Error Codes

Full HTTP status code reference and error response format.

API Overview

Base URL, authentication, and endpoint summary.