Rate Limits

Generation Rate Limits

Rate limits for model inference requests are based on your account tier:

Free-tier teams granted free credits by an operator are raised to 200 RPM for the duration of the grant. The pay-as-you-go credit-purchase floor is 250 RPM — a real purchase always buys more headroom than a free grant. Per-team overrides for custom teams are configured by an operator; contact us to request one.

Batch API Rate Limits

• Batch file upload: 1 per minute
• Batch processing rate limits are separate from generation rate limits. See the Batch API docs for details.

Deployed models share the team's serverless inference RPM bucket rather than having their own per-instance limit.

Ad-supported Model Spend Limits

Ad-supported models (for example moonshotai/kimi-k3-with-ads) have two spend limits on top of the generation rate limit:

• an hourly limit shared by all users of ad-supported models;
• a daily limit for each user (or each team, for requests without a user).

Both reset at the start of the UTC hour or day. Once either is reached, requests to ad-supported models return HTTP 429 with error type GravityAdsDiscountCap, a message naming the limit and when it resets, and a Retry-After header. Standard models are not affected, so you can switch to the standard model instead.

Payload Size Limits

• Request body: up to 32 MiB (33,554,432 bytes), including inline images. Larger requests are rejected with HTTP 413.
• Non-streaming response body: up to 32 MiB. A provider response larger than that is refused with HTTP 502 and error type UpstreamResponseTooLarge. Use stream: true, or smaller batches for embeddings, to stay under it.

Increasing Your Limits

If you need higher rate limits, contact us or use the support chat to request a custom tier.