Call Solana and other chains with Edge RPC

Edge RPC takes requests for 16 chains at edge.erpc.global. The path after the host selects the chain: Solana at the root, Ethereum at /eth, Polygon at /polygon.

Get an RPC key Choose a chain

bash

curl https://edge.erpc.global/eth?api-key=<YOUR_RPC_KEY> \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}'

curl https://edge.erpc.global/eth?api-key=<YOUR_RPC_KEY> \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}'

What you can do with Edge RPC

Use the root of edge.erpc.global for Solana and a path for each other chain, such as /base, /sui or /tron.
Send JSON-RPC as an HTTP POST on every chain except Sui. Sui takes gRPC-web unary calls, one call per request, and TRON also takes its HTTP API under /tron/wallet and /tron/walletsolidity.
Open a WebSocket connection on Solana, Ethereum, Avalanche or Base. The other chains take HTTP requests.
Point a client at a chain's own host. Every chain except Solana also takes requests at its own host, such as eth.erpc.global for Ethereum and polygon.erpc.global for Polygon.

Make a request

You need an ERPC account and an RPC key. Copy the key from the RPC keys tab of the ERPC Web Dashboard. On the Free plan, requests start after you pay the one-time €5 verification fee in the dashboard.

Send a JSON-RPC request to the chain's path, with your RPC key as the api-key query parameter. This asks Ethereum for its latest block number:

bash

curl https://edge.erpc.global/eth?api-key=<YOUR_RPC_KEY> \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}'

curl https://edge.erpc.global/eth?api-key=<YOUR_RPC_KEY> \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}'

The result is the block number in hexadecimal:

json

{ "jsonrpc": "2.0", "id": 1, "result": "0x..." }

{ "jsonrpc": "2.0", "id": 1, "result": "0x..." }

To call another chain, use its path. This sends the same request to Polygon:

bash

curl https://edge.erpc.global/polygon?api-key=<YOUR_RPC_KEY> \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}'

curl https://edge.erpc.global/polygon?api-key=<YOUR_RPC_KEY> \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}'

Solana is at the root of the host, so its request has no path. This asks for the current block height:

bash

curl https://edge.erpc.global?api-key=<YOUR_RPC_KEY> \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"getBlockHeight"}'

curl https://edge.erpc.global?api-key=<YOUR_RPC_KEY> \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"getBlockHeight"}'

Each chain's quickstart, linked in the table below, walks through the request that suits that chain.

How Edge RPC handles a request

edge.erpc.global reads the path and passes the request to that chain's service. The service checks your RPC key and your plan, sends the request to the chain, and returns the chain's response.

Authentication

Use the same RPC key on every chain; the path selects the chain.

Pass the key as the api-key query parameter. Every chain reads it, and WebSocket connections take the key this way.
On HTTP requests, you can send Authorization: Bearer <YOUR_RPC_KEY> instead. For Base, use the query parameter.

bash

curl https://edge.erpc.global/eth \
  --header 'Authorization: Bearer <YOUR_RPC_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}'

curl https://edge.erpc.global/eth \
  --header 'Authorization: Bearer <YOUR_RPC_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}'

Supported chains

Chain	Path on edge.erpc.global	Protocol	WebSocket	Bearer header	Quickstart
Solana	`/`	JSON-RPC	Yes	Yes	Solana
Ethereum	`/eth`	JSON-RPC	Yes	Yes	Ethereum
Avalanche	`/ava`	JSON-RPC	Yes	Yes	Avalanche
Arbitrum	`/arbitrum`	JSON-RPC	No	Yes	Arbitrum
Base	`/base`	JSON-RPC	Yes	No	Base
Bitcoin	`/bitcoin`	JSON-RPC	No	Yes	Bitcoin
Hyperliquid	`/hyperliquid`	JSON-RPC	No	Yes	Hyperliquid
Kaia	`/kaia`	JSON-RPC	No	Yes	Kaia
Monad	`/monad`	JSON-RPC	No	Yes	Monad
NEAR	`/near`	JSON-RPC	No	Yes	NEAR
Optimism	`/optimism`	JSON-RPC	No	Yes	Optimism
Polygon	`/polygon`	JSON-RPC	No	Yes	Polygon
Robinhood Chain	`/robinhood`	JSON-RPC	No	Yes	Robinhood Chain
Soneium	`/soneium`	JSON-RPC	No	Yes	Soneium
Sui	`/sui`	gRPC-web	No	Yes	Sui
TRON	`/tron`	JSON-RPC and HTTP API	No	Yes	TRON

Each chain other than Solana has an endpoint page that covers its endpoints, supported methods, batch requests and response status codes.

Pricing

Usage is metered in tokens, and each call in a batch is metered on its own. See RPC and Pricing for plans.

Explore Edge RPC

API reference: Solana RPC methods, each with a live try-it-out.
Unlimited: Unlimited Endpoints and the methods they support.
SWQoS: Send Solana transactions with stake-weighted quality of service.
Solana RPC FAQ: Answers on token use, 401 and 429 errors, WebSocket and regions.