Rate Limits

• As of this writing, the API does not enforce strict per-key or per-workspace rate limits.
• To avoid overloading the service, avoid burst traffic and space out large batch submissions.

Recommendations:

• For single-lead generate: One request can take 3–10 minutes. Use a long client timeout; do not retry too aggressively.
• For batch: Submit batches at a reasonable pace (e.g. avoid hundreds of batch requests in a few seconds). Poll list status at a sensible interval (e.g. every 10–30 seconds) until completed.

Generate-batch: The API returns 429 with error WORKSPACE_LIMIT when the workspace has too many concurrent batch jobs. Retry after some jobs complete.

If additional rate limits are added later, they will use HTTP status 429 and a JSON body describing the limit. This document will be updated when that is introduced.