RPC operator referenceHTTPS · JSON-RPC 2.0

SolidRPC documentation

SolidRPC replaces the provider pool, fallback router, RPC monitoring, and recovery runbooks with one integration. Use the same endpoint shape across supported EVM networks; we select and monitor upstreams, route by capability and health, fail over, and recover the layer behind it.

These docs cover everything the API does. If something here is wrong or missing, tell us.

Agents and code generators can use the SolidRPC OpenAPI 3.1 contract. The developer resource index also links the live plan, network, and telemetry JSON sources.

30-second quickstart

Use an API key in the familiar endpoint path, or keep it out of the URL with a Bearer or X-API-Key header.

Request example

https://rpc.solidrpc.io/YOUR_API_KEY/evm/{chainId}

Every account starts on the Free plan: 10K responses per day, no card required. Copy its API key and call a supported chain. Current quotas and rate limits come from the live plan catalog:

Request example

curl https://rpc.solidrpc.io/YOUR_API_KEY/evm/1 \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

That is the whole application integration. The getting started guide covers all authentication styles, viem, ethers, batching, and the method policy. The routing and failover guide explains what happens behind the endpoint and how to retire an existing provider stack.