Skip to main content
Two independent controls protect the platform and your spend. Both return an OpenAI-compatible error envelope so the standard SDKs surface them cleanly.

Request rate limit (per key)

Each API key is limited to a number of requests per minute (default 60). On overflow you get HTTP 429 with Retry-After plus X-RateLimit-* headers:
The window is counted per serving replica, so the advertised per-key number is a floor, not an exact global ceiling. Contact Mirobody Support to raise a key’s limit.

Usage quota (per account, monthly)

Each account has a monthly usage cap (USD of billed model usage). When the current month’s usage reaches the cap, /v1 requests are refused with HTTP 429 insufficient_quota until the next month, when it resets:
The cap covers all keys under the account together. Cost is metered on provider-true (billed) tokens at the model tier’s rate, with prompt-cache hits billed at the reduced cache rate (see usage.billed_tokens on every response). To raise or lift your cap, contact Mirobody Support.

Client pacing

Client backoff

  • On 429 rate_limit_exceeded, respect Retry-After — never retry immediately; double the backoff after two consecutive hits, up to 5 minutes.
  • On 429 insufficient_quota, do not retry — the cap resets monthly or on a support change; surface it to the operator.