One API key, one URL pattern, every chain below. The latency you see is measured against the live gateway, right now.
The only thing that changes between chains is the path segment. Same key, same JSON-RPC semantics, same error format. Switch chains by editing a single string.
Connection details in the docs →https://endpoints.boltrpc.io/rpc/KEY/ethereum
https://endpoints.boltrpc.io/rpc/KEY/arbitrum
https://endpoints.boltrpc.io/rpc/KEY/base
https://endpoints.boltrpc.io/rpc/KEY/polygon
https://endpoints.boltrpc.io/rpc/KEY/solana5M request units free for 14 days, no credit card. Your API key is ready within seconds.
Swap the slug in the URL for the network you need: ethereum, arbitrum, solana and 33 more.
Point your existing JSON-RPC client at the endpoint. Your production code stays the same. Only the URL changes.
curl -X POST https://endpoints.boltrpc.io/rpc/KEY/ethereum \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'import { JsonRpcProvider } from "ethers";
const provider = new JsonRpcProvider(
"https://endpoints.boltrpc.io/rpc/KEY/ethereum"
);
const blockNumber = await provider.getBlockNumber();from web3 import Web3
w3 = Web3(Web3.HTTPProvider(
"https://endpoints.boltrpc.io/rpc/KEY/ethereum"
))
block_number = w3.eth.block_numberSame pattern for every chain. Change the slug, keep everything else.
Most teams start on a public RPC endpoint and outgrow it fast: shared rate caps, inconsistent latency, no support when something breaks. The next decision is what to move to. Our guide to shared vs dedicated RPC nodes breaks down the cost and performance trade-offs, while decentralized RPC vs dedicated RPC covers when a distributed provider network helps and when it gets in the way.
Every endpoint in the list above runs on dedicated BoltRPC infrastructure with automatic multi-region failover: one API key, published request-unit weights, no per-request throttling within your quota.
36 networks are live today, covering the major EVM L1s and L2s (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, Linea, Scroll, zkSync Era) plus Solana, Starknet, Bitcoin, Sui, Aptos and more. The full live list with live latency is at the top of this page.
Our monitors run a lightweight RPC call (a standard read method) against every endpoint about once per second, around the clock, and the page mirrors those measurements live. What you see is the real gateway round-trip at this moment, not a periodic average.
Yes. Our infrastructure is operator-neutral, so adding a chain is usually a matter of days once there is a use case behind it. Reach out via the contact form with the chain name and the workload you are planning, and we will scope it with you.
Our node operator (Matrixed.Link, ISO/IEC 27001:2022 certified) tracks upgrade schedules for every supported chain and rolls out client updates ahead of fork blocks. You do not need to change the URL, the API key or your client code. If anything requires your attention we announce it in advance.
Yes. Testnets are available on every paid plan using the same URL pattern, just with the testnet slug (for example ethereum-sepolia, ethereum-hoodi, polygon-amoy). Testnet traffic counts against your monthly request units the same way as mainnet.
Archive access (full historical state, debug_*, trace_*) is available on the Enterprise plan and on select networks on request. If your workload only needs recent state, every standard endpoint already covers it.
HTTPS and WebSocket endpoints share the same URL pattern and are both included on every paid plan. Use WebSocket when you need to subscribe to new blocks, pending transactions, or contract events without polling.
Yes. Sui (sui.rpc.v2, Beta) and Tron (protocol.Wallet and the finalized WalletSolidity mirror) are served over native gRPC on endpoints.boltrpc.io:443 with your API key in the x-api-key metadata header, plus gRPC-Web for browsers at https://endpoints.boltrpc.io/grpc/sui and /grpc/tron. Use the official generated clients unchanged. A unary gRPC call costs the same request units as the matching JSON-RPC or HTTP method; Sui streams bill by delivered data at 1 RU per 24 KB. Chains with a gRPC door carry a "Native gRPC" chip in the list above.
No rate limit on monthly plans. The free trial and on-demand usage without a plan are limited to 100 requests per second (burst 200). On a monthly plan you pay for monthly request units, not for bursts: if your traffic spikes, requests still go through at full speed until you hit your monthly RU allocation.
Yes. A single key authenticates you across every supported network. You do not provision a new key per chain, and you do not need separate billing per chain.
Automatic failover is built in on every plan. A node that fails, falls behind or stops advancing is taken out of rotation and traffic moves to a healthy one with no code changes on your side; WebSocket subscriptions replay what they missed across the switch. Custom SLA terms are available on Enterprise and Custom contracts.
Start the trial and hit any of the 36 networks above in the next five minutes.