MCP server
MCP results carry no HTTP headers, so a tool call over the limit comes back as an error result instead. Its text says the call was rate limited with status
429. Wait a second and call the tool again.
Tools that start long-running work, such as enrich_worksheet, return a job id right away. Read the job’s status with its status tool every few seconds instead of in a tight loop.
Bulk API
These are the free tier limits, counted per workspace.
Only uploads that were completed count toward the upload limits. One upload carries a whole file, so 100 uploads a day is up to 12.8 GB.
Need more? Contact your Rippit point of contact, or ask in the Rippit Community, and we can raise them for your workspace.
When you reach a limit
The request returns429 with a Retry-After header that gives the number of seconds to wait:
Retry-After is the only rate limit header the Bulk API sends. There are no X-RateLimit-* headers, so a script cannot read how much of a limit is left before it reaches it. The total upload limit does not reset, so its 429 has no Retry-After; ask us to raise it.
429 is returned before anything is written, so retrying after one never duplicates data. See Idempotency and retries.
Other limits
- Pipeline rules and limits covers test samples, agent runs, and search results.
- Errors lists every status the MCP server and the Bulk API return.