Skip to main content
Limits apply over a sliding minute, both per credential (an API key or a connected app) and per workspace. Each operation belongs to a class: Each response carries the budget closest to running out:
Over the limit, the answer is 429 rate_limited with Retry-After (seconds). Wait that long, then retry; use the same Idempotency-Key when retrying a change. The MCP server also limits requests to 300 per minute per connection. Separate daily limits apply to file uploads and content agent runs.
If CaptureFlow can’t check the limits, agent calls are refused until it can (429 with Retry-After: 60); reads and writes keep working.