ERPC

Pay for RPC one request at a time with x402

x402.erpc.global sells RPC for 16 chains one request at a time. Send a request, pay the price it answers with in USDC or EURC, and get the result. You need no ERPC account, RPC key or plan.
Make a paid request See how requests are priced
bash
curl -i https://x402.erpc.global/v1/solana-mainnet \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"getSlot"}'

What you can do with x402

  • Call 16 chains at one host, each at its own route.
  • Pay for every chain with the same stablecoin from your own wallet: USDC on Solana, or USDC or EURC on Base. You need no SOL or ETH for network fees.
  • See the price before you pay. The 402 response states it, and /pricing lists each route's method prices for free.
  • Pay nothing for a request x402.erpc.global refuses. It checks the method, the body and the batch size before it asks for payment.
  • Keep a settlement receipt. Every paid answer carries one in the X-Payment-Response header.

How a paid request works

  1. Send the RPC request as usual. x402.erpc.global answers 402 Payment Required, with the price and the payment options.
  2. Your x402 client, the software that turns the 402 into a payment signed from your wallet, signs a payment for that price: a USDC transfer on Solana, or a USDC or EURC transfer authorization on Base.
  3. Send the same request again, with the signed payment in the X-Payment header.
  4. Once the payment is verified and settled, x402.erpc.global sends the request on to the chain and returns the answer with the receipt in the X-Payment-Response header.
Whichever chain you call, the payment settles on Solana or Base.

Chains and routes

Every route takes HTTP POST at https://x402.erpc.global. JSON-RPC routes take a single call or a batch of up to 100 calls.
ChainRouteRequests
Solana/v1/solana-mainnetJSON-RPC
Ethereum/v1/eth-mainnetJSON-RPC
Avalanche/v1/ava-mainnetJSON-RPC (a batch holds C-Chain calls only), and the AvalancheGo APIs at /v1/ava-mainnet/ext/…
Arbitrum/v1/arbitrum-mainnetJSON-RPC
Base/v1/base-mainnetJSON-RPC
Bitcoin/v1/bitcoin-mainnetJSON-RPC
Hyperliquid/v1/hyperliquid-mainnetJSON-RPC, also at /v1/hyperliquid-mainnet/evm and …/nanoreth
Kaia/v1/kaia-mainnetJSON-RPC
Monad/v1/monad-mainnetJSON-RPC
NEAR/v1/near-mainnetJSON-RPC
Optimism/v1/optimism-mainnetJSON-RPC
Polygon/v1/polygon-mainnetJSON-RPC
Robinhood Chain/v1/robinhood-mainnetJSON-RPC
Soneium/v1/soneium-mainnetJSON-RPC
Sui/v1/sui-mainnet/sui.rpc.v2.<Service>/<Method>gRPC-web unary calls, one per request
TRON/v1/tron-mainnetJSON-RPC, also at /jsonrpc, and the HTTP API at /wallet/<method> and /walletsolidity/<method>, one call per request
WebSocket subscriptions, such as eth_subscribe, are not sold.

Payment options

StablecoinNetworkContract or mint address
USDCSolanaEPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
USDCBase0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
EURCBase0x60a3E35Cc302bFA44Cb288Bc5a4F316Fdb1adb42
Each 402 response also carries a howToPay block with the stablecoins that request accepts and their contract addresses, so an agent can pay from the response alone.

Free endpoints

EndpointWhat it returns
GET /pricingThe price of every method on every route
GET /.well-known/x402The routes and the payment options, for x402 clients
GET /docThe OpenAPI document of every route
GET /scalarThe same document as a browsable reference

Scope of use

The paid routes on this page are for paying ERPC RPC usage fees through x402. They do not provide crypto asset exchange, brokerage, custody or wallet services.
PreviousUnlimited / Avalanche / UnlimitedNextQuickstart