Call RPC

Hosted raw RPC keeps direct EVM and Solana JSON-RPC access under the same bearer-auth model. Default to the standard chain route with Authorization: Bearer <api_key>, and use the URL-carried key form only when the client cannot send custom headers.

Raw RPC is grouped by chain family under /services/evm and /services/solana. There is no separate standalone RPC docs tree inside the new docs app.

Access

EVM routes: POST /rpc/ethereum, POST /rpc/bnbchain, POST /rpc/base, POST /rpc/arbitrum, POST /rpc/optimism, POST /rpc/polygon
Solana route (Beta): POST /rpc/solana
Auth: Authorization: Bearer <api_key>
Compatibility route: POST /v1/{chain}/{api_key}

How to call RPC

Create one API key

Open Get API Key and keep the bearer token ready.

Pick one chain family

Use one route from the current EVM family, or use the separate Solana route (Beta) only when you need the Beta lane.

Keep compatibility URL auth as fallback only

Only switch to POST /v1/{chain}/{api_key} when the client cannot send custom headers.

Copy-ready examples

EVM


curl -X POST "https://gw-aql.tomo.services/rpc/ethereum" \
  -H "Authorization: Bearer <api_key>" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "eth_blockNumber",
    "params": []
  }'

Solana (Beta)


curl -X POST "https://gw-aql.tomo.services/rpc/solana" \
  -H "Authorization: Bearer <api_key>" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getHealth",
    "params": []
  }'

Compatibility URL auth


curl -X POST "https://gw-aql.tomo.services/v1/solana/<api_key>" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getHealth",
    "params": []
  }'

Use URL-carried API keys only for clients that cannot send custom headers. Keys in URLs are easier to leak through logs, browser history, and screenshots.

Try it in the docs

Try send

Try EVM RPC

Send one direct browser request to the current hosted gateway base URL so the real network request is visible in devtools. The API key is only stored locally when you provide one.

API key (optional)Request pathPOSTJSON body

Open the EVM family reference with exact method pages.

EVM REST API

Open the Solana reference (Beta) with exact method pages.

Solana REST API (Beta)