Frequently asked questions
Should I use a local or managed gateway?
A managed gateway gives you an HTTPS endpoint without installing or operating a process. Direct hosts the gateway and handles its provider connections. It is a quick way to start and works from browser applications.
A local gateway runs under your control and connects directly to providers, without a managed gateway in the request path. You manage its availability, identity, and updates. Its requests are encrypted to providers; managed access also passes through Direct's hosting infrastructure, which can read the requests it handles.
Both use the same supported methods. Follow the quickstart for either option, or host your own gateway for backend access and an HTTPS endpoint you operate. To switch, update your application's RPC URL; methods and parameters stay the same.
Do I need an API key?
The local endpoint does not require an application API key. Access is restricted to your machine, and payment is configured in the client. Managed gateways use a key tied to your account; see Restrict access.
Can I keep using my existing library?
Yes. Configure its RPC transport with your Direct URL. Methods and parameters use the chain's JSON-RPC API. The quickstart includes examples for viem, ethers, and web3.py.
Can I use historical data and trace methods?
Where compatible providers are available. The client matches these requests to providers that support them. See Provider capabilities for the relevant requirements.
How do I choose between speed and cost?
Provider selection supports preferences for lower latency, lower cost, or a balance of both. See Price and latency preference for settings and their effect on selection.
What determines request latency?
The first request to a network can include provider discovery and connection setup. Once connections are established, the gateway keeps them open so later requests do not repeat that setup. Response time then depends on the network path, the provider's load, and the work the node performs.
A local gateway communicates directly with providers. Managed access also passes through the managed gateway. Neither has a fixed response time: historical queries and traces can take longer than lightweight reads, and failover or optional response verification can add delay. Price and latency preferences let you favor faster providers within your price ceiling.
Does RPC access depend entirely on independent providers?
No. Direct operates distributed RPC infrastructure that supplies capacity and redundancy of its own. Independent providers extend that supply and can offer better pricing or faster access for a particular location or workload. Your gateway selects from providers that meet the request’s requirements and your configured price ceiling.
These RPC providers serve blockchain requests; Direct also operates separate infrastructure peers for discovery and verification. Routing requests and handling failures explains how the two roles support the service.
Does Direct work behind a corporate firewall?
The Direct client requires outbound UDP for peer connections. If your environment blocks it, local peer access is unavailable; consider a managed gateway instead.
Is there an SLA?
Direct does not provide a network-wide SLA for independent providers. Automatic recovery depends on compatible providers being available; managed gateways also depend on Direct's hosting. Choose and monitor providers according to your application's reliability requirements.