Rate Limits
Throughput guidance for fair and stable OptimAI Search usage.
Design clients to be steady rather than bursty.
Client behavior
- Keep concurrency bounded.
- Retry only when the error is retryable.
- Back off when the API returns
429. - Avoid sending duplicate requests for the same user action.
Known client limits
These are validation limits in the MCP server and SDK, not a promise of an account quota:
| Client setting | Allowed range | Default |
|---|---|---|
| MCP query length | 1–1,000 characters | — |
| Blocking MCP timeout | 10–55 seconds | 45 seconds |
| MCP poll interval | 500–10,000 milliseconds | 2,000 milliseconds |
| MCP list page size | 1–100 records | 10 |
| x402 completion timeout | — | 300,000 milliseconds |
| x402 poll interval | — | 2,000 milliseconds |
Product behavior
Show the user that retrieval is in progress. If a request is delayed, keep source and status context visible instead of hiding the wait.
Exact account quotas and partner policies are enforced by the backend and may vary by plan or environment. For create retries, use a unique idempotency key; reusing a key with a changed route, body, or Search mode returns a conflict.