EOSIO · Rate Limits

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, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring varies, microseconds_cpu, and bytes_net.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingBlockchainAntelopeEOSOpen Source

Limits

Operator-configured HTTP throttle client-ip
varies
operator-defined per public RPC endpoint
On-chain CPU budget account
microseconds_cpu
account's staked or PowerUp-rented CPU
Transaction throughput per account is enforced on-chain by CPU consumption, not by HTTP throttling.
On-chain NET budget account
bytes_net
account's staked or PowerUp-rented NET

Policies

Open-source operator autonomy
Each public-RPC operator sets its own per-IP and per-method throttles; the upstream project does not publish quotas.
Resource-based on-chain throttling
Write throughput is governed by the account's CPU and NET budget; running out triggers tx_cpu_usage_exceeded or tx_net_usage_exceeded errors at submission time.
Self-host alternative
Operators wanting predictable throughput typically run their own nodeos node rather than relying on shared public RPC.

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/eosio-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.