Skip to main content
Darwin Search is free. Every Search interface currently allows 100 requests per minute for each caller.
We are actively working to increase this free allowance as capacity grows.

​
Search limits

Pagination and retries are requests and count toward the same Search allowance. Search selectors share one allowance on each interface, so changing from a query to an exact lookup does not create a second budget. The first-party web directory also keeps its existing daily discovery safeguards. Those safeguards limit automated extraction of distinct AI records; they do not turn Search into a paid product.

​
When a request is limited

A rate-limited request returns 429 Too Many Requests with a retryAfterSeconds value. HTTP responses also include Retry-After when the transport supports it. Successful Search API responses advertise the policy with these headers:
RateLimit-Remaining and RateLimit-Reset reflect the caller’s current window. MCP clients receive the same policy through the tool’s API-backed enforcement; HTTP-only headers are not exposed by every MCP host.

​
Retry safely

  1. Use exponential backoff with jitter.
  2. Cap both the number of retries and the maximum delay.
  3. Reuse the same requestId when retrying the same Act mutation.
  4. Do not retry validation, authentication, authorization, or approval errors as if they were rate limits.
Debounce interactive searches and cache results when the query and filters have not changed. Use cursor pagination instead of repeatedly starting the same search from the beginning. This Search allowance does not replace Act’s safety controls. For Act mutations, preserve the same requestId when retrying so Darwin can return the current result idempotently.

​
Need more capacity?

Contact Darwin with the interface, expected request volume, and traffic pattern you are planning for. We use this demand to prioritize capacity increases.