Rate limits
Last updated: 2026-10-22
Every plan has the same limits.
| Limit | Value | When exceeded |
|---|---|---|
| Tasks waiting or processing per account | 50 | 429 inflight_limit_exceeded |
| Queries per task | 3 per second | 429 rate_limited with Retry-After |
| Queries per account | 150 per second, across all keys | 429 rate_limited with Retry-After |
| Request body | 64 KiB | 413 request_too_large |
| Image URL | 4,096 bytes | 422 invalid_image_url |
| Image file | 20 MiB; 8,192 px per side; 40 million px | task fails with invalid_image |
| Task time | starts within 10 minutes and finishes within 20 minutes of submission | task fails with processing_timeout |
Handling 429
inflight_limit_exceeded— the account already has 50 unfinished tasks. Nothing was created or charged. Wait until some of your tasks reach a final status, then submit again.rate_limited— you are querying too often. Wait for the number of seconds in theRetry-Afterheader, then query again. Polling every 1–2 seconds per task stays well within the limit.
Failed tasks return their credit, so tasks that end with invalid_image or processing_timeout cost nothing.