Low-cost archive RPC, under 100 ms
Archive state, debug and trace methods over standard JSON-RPC, on supported mainnet and testnet networks.
RPC usage is measured in Request Units (RU). Every JSON-RPC call costs 1 RU, including trace and debug. A batch of N calls costs N RU. Pricing →
Archive RPC
Archive RPC is a JSON-RPC endpoint with full archive state and debug and trace methods, on supported mainnet and testnet networks. Put your API key in the endpoint URL and your existing client reads historical state or traces a call, no node to run. See the supported chains below.
- Speed
- Under 100 msFor typical requests.
- Usage
- Request UnitsEvery JSON-RPC call costs 1 RU, including trace and debug. A batch of N calls costs N RU.
- Chains
- Archive nodesAvailable on the supported chains listed below.
- Compatibility
- Standard JSON-RPCSwap the endpoint URL. Your client libraries stay the same.
Trace a transaction
- JSON-RPC over HTTPS
- Standard EVM methods
- Archive & debug
- Method availability per chain
- Project API key
- In the endpoint URL
1curl https://rpc.routescan.io/evm/1/rs_7f3a9c2e41d84b6e \2 -H "Content-Type: application/json" \3 -d '{4 "jsonrpc": "2.0", "id": 1,5 "method": "debug_traceTransaction",6 "params": ["0x3d60…c511", { "tracer": "callTracer" }]7 }'
1{2 "jsonrpc": "2.0",3 "id": 1,4 "result": {5 "type": "CALL",6 "from": "0x477b…6b6F",7 "to": "0x9702…8c7",8 "gasUsed": "0xb4f1",9 "input": "0xa9059cbb…",10 "calls": []11 }12}
Past state and call traces
Read state at past blocks and trace calls, with the same API key as your other services.
Read the docs →Archive state
Read balances and storage at past blocks.
Debug & trace
debug_traceTransaction, debug_traceCall and related methods.
Endpoints by network
One endpoint per supported chain.
Shared credentials
Same API key and usage view as other services.
Request Units on every paid plan
JSON-RPC has an RU allowance separate from indexed API request limits, shared across all keys and chains of the same user.
Every JSON-RPC call costs 1 RU, including trace and debug. A batch of N calls costs N RU. Archive RPC docs →
Paid JSON-RPC quotas use fixed 30-day windows, independent of calendar months and Stripe billing cycles. Rate limits are measured in RU and enforced over one-minute windows. Each JSON-RPC call counts toward the rate limit: a batch of N calls uses N RU.
| Plan | RU/s | RU / 30 days |
|---|---|---|
| Standard | 40 | 100M |
| Advanced | 60 | 150M |
| Professional | 80 | 200M |
| Pro Plus | 110 | 275M |
Free API keys can call eth_* methods, without debug, trace or Beacon access: 86,400 RU per day and 1 RU/s.
Without an API key, only eth_blockNumber is available at /evm/{chainId}: 86,400 RU per day and 1 RU/s, counted per client IP (per /64 for IPv6).
Running inside managed solutions
Our team builds these services on Archive RPC, then runs them for you.
Supported chains
Archive RPC is publicly available on these mainnet and testnet networks.
Mainnet · 19
- Ethereum
- Base
- Arbitrum One
- BNB Smart Chain
- Avalanche C-Chain
- Optimism
- Polygon
- Mantle
- Scroll
- FIFA Blockchain
- Robinhood Chain
- Arc
- Beam
- Redbelly
- StraitsX
- Numine
- Numbers
- PLAYA3ULL Games
- Titan
Testnet · 5
- Hoodi
- Sepolia
- Fuji
- Beam
- Redbelly Testnet
What teams usually ask us
How do I start using Archive RPC?
Point your client at https://rpc.routescan.io/evm/{chainId}/{apiKey}. Paid plans include debug and trace. Free API keys can call eth_* methods, without debug, trace or Beacon access: 86,400 RU per day and 1 RU/s. Without an API key, only eth_blockNumber is available at /evm/{chainId}: 86,400 RU per day and 1 RU/s, counted per client IP (per /64 for IPv6).
Which methods does Archive RPC support?
Standard EVM JSON-RPC methods, state at any past block against archive history, and debug and trace methods such as debug_traceTransaction and debug_traceCall. RPC usage is measured in Request Units (RU). Every JSON-RPC call costs 1 RU, including trace and debug. A batch of N calls costs N RU. eth_getLogs spans at most 10,000 blocks per query, and there is no WebSocket endpoint.
How are RPC quotas counted?
RPC usage is measured in Request Units (RU). Every JSON-RPC call costs 1 RU, including trace and debug. A batch of N calls costs N RU. Paid JSON-RPC quotas use fixed 30-day windows, independent of calendar months and Stripe billing cycles. Rate limits are measured in RU and enforced over one-minute windows. Each JSON-RPC call counts toward the rate limit: a batch of N calls uses N RU. JSON-RPC has an RU allowance separate from indexed API request limits, shared across all keys and chains of the same user. Failed requests are not refunded. Beacon API operations keep separate weighted units and counters. The one-call, one-RU rule applies only to JSON-RPC.
Which chains does Archive RPC cover?
Archive RPC is publicly available on the mainnet and testnet networks listed on this page. See the chain directory for the current coverage.
Do I need a new client library for Archive RPC?
No. Swap the endpoint URL. Your client libraries stay the same.
Built on the same index
Your first call in minutes
Create a paid key and point your client at the endpoint URL. Your client libraries stay the same.