API3 · Rate Limits

Api3 Rate Limits

API3's primary integration surface is on-chain smart contract reads of Api3ReaderProxyV1 proxy contracts, which are not subject to HTTP rate limits — they are standard EVM CALL operations gated only by gas. The API3 Market web application and its backing REST API are not published as a public developer API with documented rate limits; throttling exists but specifics are not disclosed. The Airnode HTTP gateway is self-hosted by each data provider and rate limits are set by the individual operator at deployment time. The reconciled flag is set to false until API3 publishes explicit numeric limits for the Market API or a shared Signed API endpoint.

Api3 Rate Limits is the machine-readable rate-limit profile for API3 on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring calls_per_block, requests_per_minute, and requests_per_second.

Tagged areas include Rate Limiting, Blockchain, Oracle, Data Feeds, and dAPI.

3 Limits
Rate LimitingBlockchainOracleData FeedsdAPI

Limits

On-chain dAPI read (IProxy.read) contract
calls_per_block · block
-1
Smart contract reads are EVM CALL operations; there is no API3-imposed limit. Rate is bounded only by network gas limits and the calling contract's budget.
API3 Market web API IP
requests_per_minute · minute
-1
The API3 Market backing API is not documented as a public developer API. Throttling is applied but specific numeric limits are not publicly disclosed.
Airnode HTTP Gateway IP
requests_per_second · second
-1
Self-hosted per operator. Rate limits are configured by the Airnode operator in their nodeSettings and vary by deployment. No API3-level limit applies.

Sources