Skip to main content
Intention applies rate limits at multiple layers: the public RPC layer, the order-flow layer, and the protocol layer. This page will document how those limits are surfaced through the API — the headers, the response codes, the windowing rules, and how clients should back off.
Status: not yet published. The exact limits and headers will be confirmed at the public-testnet launch. Treat the descriptions below as planning documentation.

​
What this page will contain

  • Limit categories. Per-IP, per-account, per-session, and per-endpoint limits, and how they compose.
  • Headers. The response headers that expose remaining quota, reset time, and the active limit category.
  • Error codes. How 429 responses are structured and what fields are returned, cross-referenced with errors.
  • Backoff. Recommended client backoff strategies, including jitter and the relationship between retry timing and nonces.
  • Order flow. How order placement, modification, and cancellation rate limits differ from read-endpoint limits, and how they interact with transaction sequencing.
For early integration questions, email contact@intention.xyz.