Skip to Content

EVM REST API

Use the EVM family when you need direct JSON-RPC access on the current gateway baseline without splitting EVM chains into separate top-level docs sections.

Default auth stays on Authorization: Bearer <api_key>. Keep the compatibility URL form only for clients that cannot send custom headers.

Current route family

  • POST /rpc/ethereum
  • POST /rpc/bnbchain
  • POST /rpc/base
  • POST /rpc/arbitrum
  • POST /rpc/optimism
  • POST /rpc/polygon

Method examples use POST /rpc/ethereum. Switch the route to another enabled EVM chain when needed.

Try the default method

Try send

Try eth_blockNumber

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.

Method groups

Chain and identity

Current route identity and gateway-visible client information.

Current state and execution support

Read current route state and perform basic execution simulations.

History and transaction inspection

Read blocks, transactions, receipts, and event logs.

Transaction submission

Submit signed raw transactions through the hosted route.

Last updated on