Rate Limits

To ensure efficient resource usage, Rate Limits are introduced to guarantee service availability and stability.

Resource Details

We implement rate limiting across the following dimensions:

  • RPM: Limit on the number of requests sent per minute
  • TPM: Limit on the number of input + output tokens per minute
  • Concurrency: Number of requests that have been received but have not yet returned a final result

Text

Modelu2-flashu2u2-decisionkimi-k3glm-5.2u2-med
Limit TypeRPM / TPMRPM / TPMRPM / TPMRPM / TPMRPM / TPMRPM / TPM
Limit Amount100 / 10,000,000100 / 10,000,000100 / 10,000,000100 / 10,000,000100 / 10,000,000100 / 10,000,000

Speech

Modelu2-asru2-ttsu2-tts-cloneu2-tts-design
Limit TypeConcurrencyConcurrencyConcurrencyConcurrency
Limit Amount20202020

Vision

Modelu1-ocru1-ocr-med
Limit TypeRPM / TPMRPM / TPM
Limit Amount100 / 100,000100 / 100,000

Notes

1. What are rate limits?

Rate limits are restrictions placed by the API on the number of times a user can access the server or consume tokens within a specified time period. Common metrics are RPMandTPM.

2. Why do we have rate limits?

  • Prevent API abuse and misuse, avoiding malicious overloads that lead to service interruptions
  • Ensure fair resource allocation, preventing a single user from consuming too many resources and affecting others
  • Help maintain a consistent and stable calling experience for all users

3. What happens if I hit the rate limit?

When you make too many requests or consume too many tokens/characters in a short period, the API will reject further requests until the specified time window has passed.

4. How to better use the API under rate limiting policies?

We recommend centralizing requests as much as possible: if RPM is near the limit but TPM still has capacity, you can increase throughput by batching tasks, allowing you to process more tokens under the same RPM.