Core Concepts

Rate limits

Per-wallet sliding-window rate limiting and how to handle 429s.

The gateway enforces per-wallet rate limits using a sliding window — a maximum number of requests per minute and per day for each wallet.

When you hit a limit

Exceeding a window returns HTTP 429 with no charge:

{
  "error": "RATE_LIMITED",
  "message": "Rate limit exceeded"
}

Handling 429s

Back off before retrying — exponential backoff with jitter for bursty workloads.
Rate limits are tracked per wallet, so spreading load across wallets does not bypass per-wallet windows for a single wallet.

Rate-limited requests are rejected before any provider call, so they never deduct balance.

Top up (x402)

Fund your balance with USDC or USDT using the x402 payment protocol.

Choosing a model

How provider routing works — pick a provider by prefixing the model ID.

On this page

When you hit a limit Handling 429s