Rate limits

​

How it works

​

What counts as a request

• POST /quote
• POST /submit
• POST /execute

​

What you get on overflow

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{
  "error": "rate limit exceeded",
  "limit": 120,
  "windowSec": 60
}

​

Recommended retry

async function fetchWithBackoff(req: () => Promise<Response>, maxAttempts = 3) {
  for (let attempt = 1; attempt <= maxAttempts; attempt++) {
    const res = await req();
    if (res.status !== 429) return res;

    if (attempt === maxAttempts) return res;

    // Linear backoff with jitter is fine here. Don't go below 1 second.
    const delay = 1000 + Math.random() * 500;
    await new Promise((r) => setTimeout(r, delay));
  }
  throw new Error("unreachable");
}

​

Capacity planning

​

Per-pair caching tips

1. Debouncing user input. Don’t quote on every keystroke; quote 300ms after the last input.
2. Coalescing identical quotes. If two components need the same (tokenIn, tokenOut, amountIn) quote, share one fetch.
3. Pausing polling when the tab is hidden. Use document.visibilityState === "hidden" to skip ticks.

​

What does NOT scale your quota

• Adding more API keys for the same product. The o1 team can detect related keys and apply combined limits if abuse is suspected.
• Spreading requests across IPs while reusing one key. The limit is keyed on the key, not the IP.