Skip to content

One RPC gateway for the providers and nodes you already use.

Free to use across 20 chain · network pairs. Keep one API Key while routing traffic through your own upstreams.

Open the consoleRead the docs

Cut RPC Costs with Intelligent Caching

Cache frequently requested blockchain data and reduce unnecessary upstream RPC calls.

One JSON-RPC read: a hit returns from the Gateway, a miss goes on to your endpoints.A JSON-RPC read arrives at the Gateway and is checked against the shared cache. On a hit the result returns straight away and no endpoint is called — this works even when your gateway has no endpoint configured. On a miss the request carries on through your own endpoints to their upstream nodes.Your appRPC GatewayShared cacheYour endpointsUpstream nodesHIT0 endpoint callsMISSyour endpoints take overOne JSON-RPC read: a hit returns from the Gateway, a miss goes on to your endpoints.A JSON-RPC read arrives at the Gateway and is checked against the shared cache. On a hit the result returns straight away and no endpoint is called — this works even when your gateway has no endpoint configured. On a miss the request carries on through your own endpoints to their upstream nodes.Your appRPC GatewayShared cacheYour endpointsUpstream nodesHIT0 endpoint callsMISSyour endpoints take over

  • Get More From Every RPC Endpoint

    Cached responses cut repeated requests and extend your existing providers' capacity.

  • Popular Data Stays Fast

    Frequently accessed blockchain data stays cached: faster for users, fewer upstream calls.

  • Handle Traffic Spikes Efficiently

    Duplicate requests are combined into one upstream call, cutting RPC usage during spikes.

Explore Gateway RPC coverage

Keep providers, routing and failover in one layer.

Change upstreams behind the Gateway while your application keeps the same API Key, Access Point and calling convention.

  • Bring your own upstreams

    Multi-provider routing

    Synchronize supported providers or add Endpoints manually, then choose which matching targets each Route can use.

    Multi-provider RPCProvider integrationsSelf-hosted nodes

  • Built for failover

    Routing & reliability

    Use ordered failover or weighted balancing with bounded retries, health observations and Circuit protection.

    RPC failoverLoad balancingReliability docs

  • One key across your App

    Keys & auth

    The same App API Key works across its enabled Gateways, with header and path placement for supported requests.

    AuthenticationManagement API

  • Ten chains, one shape

    Chains & protocols

    Use single-call JSON-RPC 2.0 over HTTP POST across every pair, plus native HTTP API access for TRON.

    Chain guidesJSON-RPC

Every network in one place, less to configure.

Endpoint inventory can sync from five vendors, and all 20 chain · network pairs share one key and one calling convention.

See every host and chain ID

Endpoint inventory syncs straight fromAlchemyQuickNodeChainstackdRPCTenderly

One key. Twenty networks. Free to use.

Create an App and copy its API Key. Connect a Provider or add an Endpoint for complete RPC access.

Open the console