Dashboard

Base mainnet · OP Stack · JSON-RPC · WebSocket

Base RPC endpoint with trace and debug where the chain allows

We expose op-reth’s debug and txpool namespaces where the build supports them — validate trace depth in staging the same way you would on our Arbitrum stack. Historical reads and subscriptions follow the same API-key-first path pattern as Ethereum.

Get API key Documentation Pricing
HTTPS host base.etox.io
Authentication API key as first path segment · /ws/ for WebSocket
Stack op-reth · bare-metal fleet

Debug & txpool today

Namespaces exposed where op-reth supports them — treat trace like “hot data” until you validate block depth in staging.

OP Stack on bare metal

Rollup-aware traffic with the same gateway semantics as Arbitrum — predictable limits instead of opaque shared pools.

Gateway & CU clarity

Per-key limits and Base-specific weights in /docs under rpc:cu:weights:base.

Trace depth and archive semantics

Base inherits Ethereum’s JSON-RPC surface. Heavy traces behave like other execution clients: confirm the blocks you care about on staging before you rely on deep-window debug_traceTransaction in production. When in doubt, pair Base with our Ethereum archive RPC for L1 anchor reads.

Endpoint: base.etox.io

Authenticated requests use the same API-key-first path pattern as Ethereum and Arbitrum. WebSocket RPC is available under the /ws/ prefix for subscriptions op-reth supports. Rate limits and CU weights are enforced per key at the gateway; chain-specific methods are listed in our documentation.

Why Base teams evaluate etox

  • Transparent bare-metal footprint instead of anonymous shared pools
  • Aligned Pro pricing ($49/mo) with published CU tables
  • Honest comparison vs splash-page providers — see vs Competitor 2

Related chains

Multiplex Ethereum for L1, Arbitrum for Nitro traffic, and watch Polygon as we bring that host online behind the same control plane.