Ethereum RPC & APIs
Everything Triport offers on Ethereum behind one key: the full
eth_*JSON-RPC surface withdebug_/trace_/txpool_namespaces, a REST product layer (wallets, mempool, MEV, validator and peer intel, beacon access), and WebSocket pub/sub.
| Method / Endpoint | POST https://triport.io/eth (JSON-RPC) · https://triport.io/v1/eth/… (REST) · wss://triport.io/ws/eth (streaming) |
| Network | Ethereum |
| Authentication | x-token header (SDK-preferred); see Authentication for all forms |
| Required scope | — (tier-gated per method/channel) |
| Tier / rate limit | Any tier; RPS-per-tier with burst, no daily quota — see Rate Limits |
Endpoints
| Surface | Endpoint | Reference |
|---|---|---|
| JSON-RPC | POST https://triport.io/eth | Ethereum JSON-RPC — 58 method pages |
| REST product | https://triport.io/v1/eth/… | Ethereum REST — 24 endpoint pages |
| Pub/Sub WebSocket | wss://triport.io/ws/eth | Ethereum WS (newHeads, logs, newPendingTransactions, syncing) |
| Beacon (consensus-layer) | https://triport.io/rpc/eth-beacon/… | Beacon proxy · Beacon events SSE |
All surfaces share the same API key, error envelope, and rate-limit model.
Quickstart
curl https://triport.io/eth \
-H "x-token: $TRIPORT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'{ "jsonrpc": "2.0", "id": 1, "result": "0x161f1b8" }New to Triport? Getting Started takes you from zero to a verified response in under five minutes.
What is Ethereum-specific here
- Deep-inspection namespaces —
debug_*(raw blocks/headers, call tracing) andtrace_*(block/tx replay traces,trace_filter) on top of the standardeth_*set;txpool_*for pending-pool visibility. Node-admin namespaces (admin_*,personal_*) are documented but intentionally not supported (-32601) — each page states its behavior. - Mempool & MEV — REST mempool snapshot / stats, builder RPC, private-tx RPC, relay intel, MEV-share SSE, and bundle sender.
- Network intel — leak-mesh, validator intel, and connected-peer topology endpoints.
- Consensus layer — beacon REST proxy incl. blob sidecars, plus a live beacon event stream (SSE).
Rate limits
Ethereum requests are budgeted by sustained RPS per tier and request category,
with 2× burst and no daily quota. debug_/trace_ methods sit in heavier
categories. The per-tier numbers live in
Rate Limits & Tiers.
POST Ethereum JSON-RPC
The Ethereum JSON-RPC surface on POST https://triport.io/eth — the standard eth_* set plus debug_, trace_, txpool_, net_ and web3_ namespaces, with node-admin namespaces explicitly documented as not supported.
GET Ethereum REST API
Triport's product layer for Ethereum under https://triport.io/v1/eth/… — wallet data, mempool intel, MEV endpoints, leak-mesh and validator/peer analytics, transaction senders, and consensus-layer beacon access.
GET Platform API
Cross-network Triport endpoints — chain catalog and live metrics, per-key endpoint discovery, a diagnostics runner, and a server-sent events stream of chain status.