Eosio Rate Limits
EOSIO/Antelope has no centralized rate-limit authority. The nodeos HTTP plugins (chain_api, history_api, producer_api) are operated by independent block producers and infrastructure providers; each operator sets its own throttle policy. On-chain, write throughput is bounded by the account's CPU/NET resource budget rather than a request-per-second limit. The values below are illustrative of what an operator typically configures rather than a centrally-published quota.
Eosio Rate Limits is the machine-readable rate-limit profile for EOSIO on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring varies, microseconds_cpu, and bytes_net.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.
Tagged areas include Rate Limiting, Blockchain, Antelope, EOS, and Open Source.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/eosio-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.