TriportRPCDashboard

Ethereum REST API

Triport's product layer for Ethereum over plain HTTP: consensus-layer beacon access (REST proxy and live event stream) and the MEV builder and private-transaction routes, with notes on the JSON-RPC transport.

Endpoint and plans: Ethereum RPC endpoint.

Method / Endpoint
Beacon: https://triport.io/rpc/eth-beacon/…; MEV: POST https://triport.io/rpc/eth-private/{forwarder_id}, POST https://triport.io/rpc/eth-builder/…
Network
Ethereum
Authentication
x-token header (recommended); see Authentication
Required scope
— (tier-gated per endpoint)
Tier / rate limit
Any tier; see Rate Limits

What this surface is

Unlike JSON-RPC, which proxies the chain's native methods verbatim, the REST layer is built by Triport: indexed, opinionated endpoints that answer product questions in one call.

Endpoint groups

  • Beacon — consensus-layer REST proxy (incl. blob sidecars) and live event stream (SSE).
  • MEV — builder RPC and the private-transaction forwarder. Bundles (eth_sendBundle, mev_sendBundle) are sent through the private RPC forwarder, not the shared JSON-RPC endpoint.
  • Transport — how the JSON-RPC transport routes reads and writes.

For wallet balances, history and token activity, use JSON-RPC (eth_getBalance) or the cross-chain Wallet Research endpoint. For pending transactions, subscribe to newPendingTransactions over WebSocket. To send a signed transaction, use eth_sendRawTransaction.

The full endpoint list is below.

GET Beacon API reverse proxy (CL path router)
Forwards Ethereum Consensus-Layer (Beacon) REST calls through to Triport's pooled CL nodes (Prysm / Lighthouse / Nimbus), with tier, family, and rate-limit enforcement applied per path.
GET Beacon events SSE stream
Subscribe to Ethereum consensus-layer (beacon chain) events — new heads, finalized checkpoints, and more — as a live Server-Sent Events stream.
POST Block-builder direct RPC
Send a bundle straight to a named Ethereum block builder over JSON-RPC, bypassing the public mempool.
POST Ethereum JSON-RPC transport (POST /rpc/eth)
The raw JSON-RPC 2.0 transport for Ethereum execution-layer (EL) eth_* calls — one HTTP endpoint that classifies each method, routes it across the EL node pool, and falls back automatically.
POST Private RPC forwarder
Submit raw transactions and bundles to MEV-protected private endpoints without ever touching the public mempool.