Dashboard

Mainnet · JSON-RPC · WebSocket · Archive

Ethereum RPC endpoint with archive data and trace APIs

Authenticated traffic goes to eth.etox.io — Reth in archive mode with Lighthouse — so historical state, eth_getLogs, and debug_ / trace_ calls behave the way indexer and DeFi teams expect, with clear CU metering instead of opaque credits.

Get API key Documentation Pricing
HTTPS host eth.etox.io
Authentication API key as first path segment · /ws/ for WebSocket
Stack Reth archive + Lighthouse consensus

Archive & trace

Historical eth_getBalance, rich log filters, and debug/trace namespaces for production analytics.

WebSocket RPC

Same key-in-path convention as HTTPS — subscriptions for heads, logs, and pending txs where supported.

Transparent CU

Per-method weights in /docs. Forecast cost from traffic shape, not surprise invoices.

Who this Ethereum JSON-RPC endpoint is for

Wallets and dapps that only need the latest block rarely stress an RPC provider. etox shines when you need archive node semantics: reconciliation jobs, MEV analytics, portfolio history, fraud checks, and subgraph-adjacent pipelines. Our gateway enforces per-key rate limits and per-method compute unit (CU) weights, so you can forecast cost from traffic shape instead of guessing from opaque “credits.”

Endpoint shape and authentication

After you create a key in the dashboard, embed it as the first path segment on HTTPS. WebSocket subscriptions use the parallel /ws/ prefix on the same host. Health checks can hit /health without a key. For a zero-friction trial, Ethereum is also available without signup on rpcfree.com under IP-based limits — see our free tier page for quotas.

Method coverage and CU costs (summary)

Lightweight calls such as eth_blockNumber, eth_chainId, and eth_gasPrice are inexpensive. State reads like eth_getBalance cost more; heavy traces and filters are priced highest so abusive log scans cannot crowd out steady production traffic. The full table lives on the docs page and is loaded into Redis for live enforcement at the gateway.

Ethereum WebSocket RPC

Subscriptions for new heads, logs, and pending transactions are supported over WebSocket on eth.etox.io using the same API key path convention as HTTP. This mirrors how teams already run viem, ethers, or web3.js against other providers — only the host and path change.

Related reading