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, 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.

3 Limits Throttle: 429
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