Rate Limits

By default, we support:

• Up to 20 new generation requests every 10 seconds
• Typically supports 100+ concurrently running tasks

Request rate is not a concurrency cap

Rate limits control how quickly new tasks are submitted, not how many tasks are queued or running. Tasks already queued or running do not consume the allowance in later time windows; actual execution speed still depends on the selected model and service capacity.

When the limit is exceeded

If too many generation requests are submitted within a short period:

• The request is rejected with HTTP 429
• The response includes Retry-After, indicating the recommended wait time in seconds
• The response error code is RATE_LIMITED
• The rejected request does not enter the task queue

HTTP/1.1 429 Too Many Requests
Retry-After: <seconds>
Content-Type: application/json

{"code":429,"message":"too many requests, retry later","data":null,"error_code":"RATE_LIMITED"}

Wait for the Retry-After interval before retrying, and use exponential backoff with jitter to avoid synchronized retries.

Requesting a higher limit

If you continue to receive HTTP 429 responses, contact HiAPI support to request a higher account request limit. Requests are evaluated based on the intended workload, request pattern, and account requirements.