JSON-RPC Overview
JSON-RPC
JSON-RPC Overview
Use BlockDB as an EVM JSON-RPC endpoint compatible with standard Ethereum execution-client methods.
POST
JSON-RPC Overview
Documentation Index
Fetch the complete documentation index at: https://docs.blockdb.io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
BlockDB exposes a drop-in compatible Ethereum JSON-RPC endpoint for EVM networks. Use it when you want to connect existing tooling (web3 libraries, indexers, bots) without rewriting to BlockDB’s REST endpoint format. This page documents the BlockDB entrypoint and the key conventions you need to call Ethereum JSON-RPC successfully.Endpoint
Authentication
Send your API key on every request:Pricing
JSON-RPC access is included in all BlockDB plans.- Basic Plan: Shared infrastructure, standard rate limits.
- Standard & Platinum Plans: High-throughput access with dedicated support options.
Method Compatibility
We support the classic Ethereum execution-client JSON-RPC method families, including:eth_*net_*
Conventions (important)
Hex encoding
Ethereum JSON-RPC uses hex encoding with specific rules:- Quantities (block numbers, integers): hex with
0xprefix, most compact form (0x0for zero) - Byte arrays (hashes, addresses, calldata): hex with
0xprefix, two hex digits per byte
Block parameter
Many methods accept a “block parameter”. Common values include:"earliest","latest","safe","finalized","pending"- A specific block number encoded as a hex quantity (e.g.,
"0x12A05F").
Examples
Example: eth_getBlockByNumber
Example: eth_call
See also
Last modified on March 21, 2026