Supra · Rate Limits
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, in the API Commons Rate Limits shape.
It captures 1 rate-limit definition.
Tagged areas include Blockchain, Layer 1, Oracle, Web3, and Market Data.
1 Limits
Derived by API Evangelist from the provider's contracts on 2026-08-29.
View Source
BlockchainLayer 1OracleWeb3Market DataSmart ContractsVerifiable RandomnessCross-Chain BridgeAutomationMoveCryptocurrencyDeFi
Limits
Supra RPC Node API per-connection / per-auth-token (WebSocket)
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.