Rate limits
Three limits apply. Live keys get the limits of the largest API pack the account has bought.
| Key | Create requests / min | Images at once | Reads / min |
|---|---|---|---|
| Test key | 5 | 2 | 60 |
| API 60 pack | 10 | 3 | 120 |
| API 220 pack | 20 | 6 | 300 |
| API 700 pack | 40 | 10 | 600 |
| API 3500 pack | 60 | 20 | 1200 |
- Create requests (edits, cancel, uploads) and reads (jobs, account, catalog) are counted per key and per minute. Over the limit:
429 rate_limited. - Images at once counts the images of your account still rendering, across all keys. A request that would go over it:
429 concurrency_limited. Send fewer images per request, or wait for jobs to finish. - When Garmo is under heavy load a request may get
429 overloadedeven within your limits.
Headers
Every answer has X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (Unix seconds when the minute ends). A 429 also has Retry-After in seconds.




