To ensure platform stability, fair resource allocation, and optimal performance, rate limits are enforced across all incoming requests. These limits apply universally whether you are interacting with our services via the standard API or through the Model Context Protocol (MCP).Rate limits are tracked and restricted on a per-user basis (x-api-key) and are categorized by the type of operation being performed (Read, Trading Write, or Staking Write).If your application exceeds the rate limit, subsequent requests will be rejected and return a 429 Too Many Requests HTTP status code until the rate limit resets.
Rate Limit Overview#
| Operation Category | Scope | Limit |
|---|
| Read (prices, portfolio, history, asset browsing) | Per user | 50 req/s |
| Trading Write (request quote, accept quote) | Per user | 5 req/s |
| Staking Write (stake, unstake) | Per user | 5 req/s |
Modified at 2026-10-01 12:51:48
