RPC Gateway

A stable access layer between your app and blockchain nodes

RPC Gateway takes JSON-RPC and TRON HTTP API calls through one entry point. Upstream selection, health checks, load balancing, and failover happen inside the gateway — your app keeps a single App API Key.

Read the docs
Coverage

One gateway across 4 protocol families

Every network speaks single-call JSON-RPC over HTTP, with a dedicated Access Point per chain and network in the console.

10
chains
Major networks and testnets
20
chain·network pairs
Mainnets alongside testnets
4
protocol families
EVM · SVM · UTXO · TRON
5
providers
Endpoint auto-sync for EVM
EthereumPolygonBNB Smart ChainArbitrumOptimismBaseSolanaBitcoinLitecoinTRON
  • TRON Mainnet and Nile additionally expose the TRON HTTP API (/wallet, /walletsolidity, and /v1 path families).
  • EVM endpoints can be auto-synced from Alchemy, QuickNode, Chainstack, dRPC, and Tenderly.
Capabilities

Routing, reliability, and observability built in

Upstream governance lives in the gateway, while your application keeps one unchanging entry point.

One entry point, App-scoped keys

A dedicated Access Point per chain and network. Authenticate with a Bearer header or a path key; keys can be revoked, and rotation has a 24-hour grace period.

Two routing strategies

Priority failover or weighted load balancing per route, with up to 100 endpoints on a single route.

Retries with boundaries

Two retry policies — safe_only and idempotent. Write calls are never replayed blindly.

Health checks and circuit breaking

Endpoint health observation with circuit breaking: failing upstreams are isolated and stop receiving traffic.

Rate limits, isolated per protocol

JSON-RPC and TRON HTTP API quotas are independent of each other.

Usage by every dimension

Calls, success rate, and traffic broken down by app, chain, network, and method over 24h / 7d / 30d windows.

Integration

First call with a single curl

Copy the Access Point and App API Key from the console and send a request — upstream selection and failover happen inside the gateway.

  1. Create an appCreate an App in the console and pick its networks; you get an API Key and a Gateway per network.
  2. Configure endpoints and routingSync endpoints from a provider or add them manually, then attach them to the default JSON-RPC route.
  3. Copy the Access Point and callThe host encodes chain and protocol; the API key attributes the request to your app.
Read the quickstart →
bash
# copy both values from the console
export RPC_URL='https://ether-jsonrpc.<gateway-domain>'
export APP_API_KEY='<app_api_key>'

curl "$RPC_URL" \
  -H "Authorization: Bearer $APP_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
Response
{"jsonrpc":"2.0","id":1,"result":"0x1"}
Boundaries

Clear boundaries, documented up front

Deliberate trade-offs in the current version, stated before you integrate.

Protocol scope

Single JSON-RPC 2.0 calls over HTTP only; JSON-RPC batch, WebSocket, and public gRPC are not supported.

Upstream capacity

The gateway handles routing, health checks, and failover; node capacity comes from the upstreams you configure.

Provider sync

Auto-sync currently covers EVM networks only; Solana, Bitcoin, Litecoin, and TRON endpoints are added manually.

Account provisioning

Accounts are provisioned by a platform administrator; there is no self-service signup.

Ready to integrate?

Follow the quickstart to create an app, configure endpoints, and send your first request.

Read the docs

The service is currently free to use; accounts are provisioned by a platform administrator.