Skip to main content
How fast you can call search and fetch depends on how you authenticate. An API key removes the hourly cap and gives your organization its own per-second limit. See Authentication for how to send a key.
  • All keys in an organization share the organization’s per-second limit.
  • Without a key, you share the per-IP pool with all other traffic from your IP address. That traffic uses up part of your limit. See Keyless access for the paths and the required header.
  • On the pay-per-request paths, the per-IP limit counts both the unpaid request that returns the offer and the paid retry. That’s why it’s twice the per-wallet limit. For a worked example of the paid path, see Agent pays with x402.

Raise your limit

Your organization’s limit rises from 10 to 25 requests per second once its completed top-ups reach $1,000 within 90 days. Card purchases and auto top-up both count. Refunded payments don’t. The higher limit lasts 90 days from the top-up that crossed $1,000, and each later top-up that leaves the last 90 days at $1,000 or more restarts those 90 days. It takes effect within about five minutes of the payment. Top up under Billing in the console. The same page shows how far your top-ups are from 25 requests per second, and when a raised limit ends. A plan with a higher limit keeps it, and a limit agreed with Keenable applies instead of either. For more than 25 requests per second or zero data retention, contact Keenable.

Monitors

The Monitors API has its own limit: 120 requests per minute per organization, of which at most 10 may create monitors. Every key in the organization shares it, including the keys your agents use. Over the limit, the API returns 429 with rate_limited. Wait, then retry. An organization can have at most 100 active monitors. See Monitors limits.

Parallel calls

Searches and fetches count against the same limit. If you send calls in parallel, keep each batch under your per-second limit. After a 429, wait for its Retry-After before you retry. The MCP server tells agents to send at most 5 calls at once. See High-volume research for a sample with a cap and retries.

When you hit a limit

If you go over a limit, the API returns 429 with a Retry-After header. The body’s code says which limit you hit: The body also has retry_after_seconds, which matches Retry-After, and a limit object with the limit’s scope, window, max and resets_at. Wait that long, then retry. Retry rules covers every retryable error, not only 429s. A keyless hourly 429 keeps coming back until resets_at. To continue sooner, send an API key. See 429 Rate limit exceeded for the rate-limit headers, the SDK errors and the 429s that aren’t your limit.

Rate limits and your balance

Rate limits cap how fast you can call the API. Your balance caps how much: with an API key, your organization gets 100,000 free requests a month, then pays $4 per 1,000 from a prepaid balance. See Balance and usage.