Skip to main content
Darwin Search currently allows 100 requests per minute per caller across API, MCP, and web entry points. Pagination and retries count as requests.

When a request is limited

A limited HTTP request returns 429 Too Many Requests and Retry-After when the transport supports it. Successful Search API responses also advertise the current limit, remaining requests, and reset window.

Retry safely

  1. Respect Retry-After.
  2. Use exponential backoff with jitter.
  3. Cap retry count and maximum delay.
  4. Debounce interactive Search input.
  5. Cache identical read-only requests for an appropriate interval.
  6. Reuse the same requestId when retrying the same Action mutation.
Do not retry 400, 401, 403, or 404 without changing the request, credential, or authority.
Never generate a new Action requestId merely because the transport failed. A changed ID can create duplicate work.
Contact Darwin with your expected request volume and traffic pattern when you need higher capacity.
Last modified on September 21, 2026