Tuna.ai

Rate Limits

Rate limits apply to the combined request traffic of an organization. All projects and API keys share the limit. Requests above it receive HTTP 429.

Limits Are Shared by the Organization

An organization has one rate limit. Requests from every project and API key in the organization count toward that limit, so creating more keys doesn't raise it. See Organizations and projects.

Limits Grow with Your Balance

Your organization's rate limit depends on its balance. A larger balance gives a higher limit. If you often hit the limit, adding credit raises it. See Billing.

For limits beyond that, see Enterprise.

When You Hit the Limit

A request over the limit fails with status 429. This doesn't mean anything is wrong with your account. It means the organization is sending requests faster than its limit allows right now. The response has a Retry-After header with the number of seconds to wait. After that, send the request again. The OpenAI SDKs and the Vercel AI SDK do this for you. See Retries.

To hit the limit less often:

  • Limit how many requests run at once. For batch jobs, use a queue with a fixed number of workers instead of sending the whole batch at once.
  • Spread requests out. A steady flow of requests is less likely to hit the limit than bursts.
  • Combine small tasks. Many small tasks, like labeling 20 short texts, can often be done in one request instead of 20.