Skip to main content
Three limits apply. Each counts requests in a fixed one-minute window. The numbers are defaults. Your deployment may be set differently.

How each limit behaves

Caller. Each API key has its own window. A signed-in account has its own window across its sessions. Address. A ceiling above the caller limit. Many keys behind one address share it. Refused credentials. After the limit of refused credentials from one address in a minute, further requests from that address without a valid credential get 429 until the window ends. Requests with a valid credential from the same address still pass.

The 429 response

Handle a 429

  • Wait for Retry-After seconds, then send the same request.
  • A 429 is refused before any work. Nothing was charged, and a retry cannot charge twice.
  • Send records in batches: up to 1,000 emails in one validate call and up to 100 contacts in one enrich call. One batch counts as one request.
  • The MCP server and the CLI wait and retry a 429 once for you.
There are no rate-limit headers on successful responses. Related: Errors, Idempotency.