Supra Rate Limits
Supra publishes almost no rate-limit information. The REST node API declares no 429 response and no rate-limit headers on any of its 56 operations, so a client has no contract for behaviour under load. The one place throttling is declared is the WebSocket upgrade, which is modelled properly — 429 with Retry-After and a reason header — but with no published numbers. The price feeds APIs document none at all.
Supra Rate Limits is the machine-readable rate-limit profile for Supra on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 1 rate-limit definition.
Tagged areas include Blockchain, Layer 1, Oracles, Web3, and Market Data.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.