A blockchain RPC API is an interface that lets your application read blockchain data and send transactions without running your own node. GetBlock provides ready-to-use RPC endpoints for 130+ chains, so developers can connect wallets, dApps, analytics tools, and trading systems directly to blockchain networks.
GetBlock supports 130+ blockchains including Ethereum, BNB Smart Chain, Solana, Polygon, Avalanche, Arbitrum, Optimism, TRON, Bitcoin, TON, and many more. Shared and dedicated RPC access is available across mainnets, testnets, EVM chains, Layer 2s, and non-EVM protocols.
Yes. GetBlock provides full archive node access on all major chains, including Ethereum, BSC, Polygon, and others. You can query historical blockchain state, transactions, logs, traces, and balances from any block height — without extra surcharges on shared plans.
Every endpoint supports HTTPS (JSON-RPC), WebSocket, gRPC, and GraphQL on the same URL and API key. WebSocket subscriptions push new blocks, pending transactions, and contract events in real time with no polling. The full debug and trace namespace is available on all EVM chains.
Shared nodes are optimized for general use and cost efficiency, while dedicated nodes provide isolated infrastructure with guaranteed throughput, no shared limits, and full control over performance.
Requests are automatically routed to the nearest available node, delivering sub-100ms response times on average, depending on region and network conditions.
Yes. GetBlock holds SOC 2 Type 1 certification. Request payloads are not stored or logged. API keys support per-key rate limits, chain restrictions, domain whitelisting, and IP allowlists. Crypto payments are accepted on all plans.
Every paying customer gets a custom SLA and tech team access. Free plan: 24-hour ticket response. Paid plans: up to 4x faster, with direct tech team access from the first $49/month tier. Enterprise: about 5-minute response time.
One line of code. Replace your existing RPC URL with your GetBlock endpoint URL. It is fully compatible with ethers.js, viem, web3.py, web3.js, wagmi, Hardhat, Foundry, and every major Web3 library. Most teams complete migration in under an afternoon.