Your RPC endpoint.
A market behind it.
RPC access through a peer-to-peer network of competing providers. Direct keeps your application connected as availability changes, while you control the balance of price and performance - all through the RPC libraries you already use.
01 / Install
02 / Run
Run the gateway alongside your application for direct peer-to-peer connections to providers.
Hosted access
We run the gateway.
Use a hosted HTTPS endpoint to reach the same RPC marketplace. Connect your application without running a gateway yourself.
Talk to us about getting accessMake an RPC request · Ethereum
curl "http://127.0.0.1:1337/service/ethereum" \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'Use the address reported by your local gateway.
- Resilience through major outages
- Providers competing for every request
- Your balance of speed and cost
01 The marketplace
A market that works
for your application.
Providers compete on price and performance. Your gateway compares suitable offerings and adapts as the market changes, so your application can draw on the network without managing each provider itself.
One integration.
Access offerings across operators through the same RPC URL, without integrating with each provider separately.
The right capabilities.
The gateway matches requests to providers that support the work, from everyday queries to archive access and tracing.
A choice that adapts.
As prices, performance and availability change, the gateway reassesses providers within your preferences and price limits.
02 Provider capacity
Independent providers.
Established capacity.
A network built to scale, backed by independent providers, Direct’s own RPC infrastructure and bridges to established providers. Capacity across operators and regions keeps requests flowing even through major outages and gives your gateway a competitive market to draw from when balancing cost and performance.
Access through provider bridges
The gateway ranks providers using observed performance and announced prices. Values shown are illustrative, not quotes for an individual request.
03 Availability
A provider goes offline.
Requests keep moving.
Your gateway maintains connections to multiple providers. When one becomes unavailable, it routes requests to another suitable provider.
Illustration: a shared gateway compared with direct provider connections through a local gateway.
04 Networks
More networks.
Same connection.
One Direct gateway gives your application access to every supported network, each with its own service URL. Build across chains with a consistent way to connect.
Ethereum
Base
Arbitrum One
OP Mainnet
Polygon PoS
05 Service quality
Verified quality.
Continually checked.
Direct verifies provider health, data integrity and performance, then monitors them throughout operation. Your gateway uses those checks to select providers that meet your application’s requirements.
Health.
Do requests complete successfully, fail or time out?
Integrity.
Does the provider return the correct on-chain state?
Performance.
How quickly does the provider respond to requests?
06 Connect your application
Get started
in minutes.
Use a managed gateway for a hosted endpoint, or run the Direct gateway alongside your application for direct peer-to-peer access.
Use your existing stack.
Direct speaks standard JSON-RPC. Connect by configuring an RPC URL in your application’s tools or libraries.
- viem
- ethers
- web3.py
01 / Install
02 / Run
Run the gateway alongside your application for direct peer-to-peer connections to providers.
Hosted access
We run the gateway.
Use a hosted HTTPS endpoint to reach the same RPC marketplace. Connect your application without running a gateway yourself.
Talk to us about getting accessMake an RPC request · Ethereum
curl "http://127.0.0.1:1337/service/ethereum" \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'Use the address reported by your local gateway.