Skip to main content
Yelu applies request limits to protect platform reliability. Limits can vary by account group, model, deployment configuration, and whether a request succeeds. The dashboard and your account configuration are authoritative for your effective limits.

When a request is limited

The API returns HTTP 429 Too Many Requests. Parse the OpenAI-compatible error body, wait, and retry only when the operation is safe to repeat.

Retry strategy

Use exponential backoff with random jitter and a strict retry cap. A practical sequence is approximately 0.5, 1, 2, and 4 seconds, randomized so concurrent workers do not retry together.

Reduce limit pressure

  • Queue bursts and control worker concurrency instead of releasing all work at once.
  • Cache deterministic application results where your data policy allows it.
  • Stream long generations to improve user-perceived latency, but remember that streaming does not necessarily reduce quota usage.
  • Use separate keys for independent workloads so one batch job does not starve interactive traffic.
  • Bound retry attempts; repeated failures consume capacity and can amplify incidents.
  • Avoid retrying 400, 401, 403, and 404 responses without changing the request.

Retryable status codes

See Errors for the complete handling model.
Last modified on July 13, 2026