Overview
Rate limits ensure fair usage and system stability across all users. Limits vary by plan tier.Limits by Plan
Your plan tier determines your rate limits. Higher-tier plans receive increased concurrency, larger request quotas, and bigger backlog allowances.| Plan | Concurrency | Backlog | Rate Limit |
|---|---|---|---|
| Free | Base | Base | Base |
| Pro | Higher | Higher | Higher |
| Enterprise | Custom | Custom | Custom |
Contact sales for Enterprise plan details and custom rate limit configurations.
Job Backlog
When you submit more jobs than your concurrency limit allows, additional jobs are automatically added to your backlog rather than being rejected. As running jobs complete, backlogged jobs are processed in the order they were submitted. This means you can submit a batch of jobs without managing queue logic yourself—the API handles it for you. Your backlog capacity also scales with your plan tier.Best Practices
- Implement exponential backoff - Wait progressively longer between retries
- Queue requests client-side - Don’t submit more jobs than your concurrency allows
- Monitor your usage - Track request counts to stay within limits
- Use webhooks - Reduce polling requests by using webhooks for job completion