Base
Base is an EVM rollup in the Gateway catalog and uses ETH for gas. Its Mainnet and Sepolia networks each have their own Gateway, Access Point, and Routes.
Networks and hosts
| Network | Chain ID | JSON-RPC Host |
|---|---|---|
| Mainnet | 8453 | base-jsonrpc |
| Sepolia | 84532 | base-sepolia-jsonrpc |
Take the deployed Access Point from the dashboard. Base Sepolia is chain 84532 and is unrelated to Ethereum Sepolia (11155111), even though both carry the Sepolia name.
Provider coverage
| Provider | Mainnet | Sepolia | Notes |
|---|---|---|---|
| Alchemy | Yes | Yes | Enable Base for the API key in the Alchemy dashboard |
| QuickNode | Yes | Yes | A multichain Endpoint is expanded into one Gateway Endpoint per network |
| Chainstack | Yes | Yes | Only nodes in the running state are imported |
| dRPC | Yes | Yes | Generated from the dRPC public network catalog |
| Tenderly | Yes | Yes | Matched to the Gateway catalog by EVM chain ID |
Reads without an Endpoint
Base uses the shared EVM Endpoint-free set: eth_blockNumber, eth_getBlockByNumber with ["latest", false] or an explicit hexadecimal height and false, and debug_traceBlockByNumber with the callTracer configuration. Other parameter variants continue through the Route. Endpoint-free RPC lists the exact forms and cache behavior.
Verify the network
curl '<base_access_point>' \
-H 'Authorization: Bearer <app_api_key>' \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'Mainnet returns 0x2105; Sepolia returns 0x14a34.
Coverage boundary
One JSON-RPC 2.0 object per HTTP POST. Base-specific methods, trace output, and historical state follow the upstream node and plan.
See Endpoints for lifecycle management and Errors and recovery for Gateway error codes.