Concepts
Rate limits
Request and concurrency limits for the SateAIs API.
The SateAIs API enforces limits to protect platform stability.
Request throughput
| Limit | Value | Notes |
|---|---|---|
| Requests per second | 10 rps | Burst up to 50 |
| Enforcement | API Gateway throttling | 429 RATE_LIMIT_EXCEEDED on excess |
Concurrent jobs
| Limit | Value | Notes |
|---|---|---|
| Concurrent jobs per API key | 5 | Per-key cap |
Handling 429 RATE_LIMIT_EXCEEDED
When you exceed a limit, the API returns:
{
"error": {
"code": "RATE_LIMIT_EXCEEDED",
"message": "Concurrent job limit reached. Retry later."
}
}System congestion
429 RATE_LIMIT_EXCEEDED can also be returned when the SateAIs platform is under heavy load — even if you are below the per-key concurrency limit. Always implement retry with backoff.
Recommended handling:
- Exponential backoff on retries (start 1 s, cap 30 s).
- Queue in your application layer rather than submitting all jobs at once.
- Monitor the
429rate in your telemetry; sustained rate limiting signals you should batch differently.
Tip
If you consistently hit concurrency limits, contact support about a higher tier.