Skip to Content

EVM HTTP API

HTTP API

Allowlisted EVM JSON-RPC methods across the current hosted route family.

Use this tree when you need direct JSON-RPC access without splitting every EVM chain into separate top-level docs sections. Examples use <code>POST /v1/ethereum/{`{api_key}`}</code>; switch the route to another enabled EVM chain when needed.

TransportHTTP request-response
Route familyEVM
Public authPOST /v1/{chain}/{api_key}

Public onboarding leads with compatibility-style RPC URLs. Put the API key in the path so mainstream wallets, SDKs, and infrastructure clients can reuse one endpoint string directly.

Current route family

ethereum route
POST /v1/ethereum/{API_KEY}
bnbchain route
POST /v1/bnbchain/{API_KEY}
base route
POST /v1/base/{API_KEY}
arbitrum route
POST /v1/arbitrum/{API_KEY}
optimism route
POST /v1/optimism/{API_KEY}
polygon route
POST /v1/polygon/{API_KEY}

Method examples use POST /v1/ethereum/{api_key}. Switch the route to another enabled EVM chain when needed.

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
Overview