Direct Client

We’ve built Direct Client as a plug-and-play solution for popular Web3 libraries. No code changes are required. Just integrate our clients, and your RPC usage will be automatically optimized for better performance and reliability.

Supported Libraries

Direct Client has dedicated integrations for the most widely used Web3 libraries:

Each version works as a drop-in replacement, with no changes required in your app code.

What’s in the Box

When you integrate Direct Client, your app instantly benefits from:

🧩 Access to Direct infrastructure
🚀 Starter Pack for faster initial load
🔮 Predictive prefetching based on traffic patterns
🔌 Batch Streaming for low-latency batching
📦 Direct Wire Protocol for faster and leaner payloads
🔁 Automatic failover across providers and infrastructure
⚡ Instant finality detection with real-time UI updates
🌐 Peer-assisted delivery for speed and savings

🧩 Access to Direct Infrastructure

At its core, Direct Client connects your app to our infrastructure, focused on delivering Web3 data faster and with fewer requests.

Every time your app makes a call through Direct Client, it benefits from our global infrastructure. This includes edge locations worldwide, real-time optimizations, and intelligent routing. It ensures that requests are resolved quickly and efficiently, often without even reaching your provider.

All the advanced features, like predictive prefetching, Batch Streaming, Direct Wire Protocol, failover, and more, are layered on top of this foundation, enhancing performance without requiring you to change anything in your codebase.

🚀 Starter Pack

Initial page loads often trigger a cascade of requests. With Direct Client, this is handled in advance. Our RPC Agents prepare a prebuilt package of critical data, delivered at startup, so your app loads faster and feels more responsive from the first interaction.

🔮 Predictive Prefetching

By analyzing traffic patterns through our RPC Agents, Direct Client is able to anticipate future requests and prefetch data. This turns common requests into instant local cache hits, giving your app zero-latency access.

Direct Client gathers contextual awareness in the client layer, which is processed by RPC Agents to predict upcoming data needs. This prefetching happens quietly in the background, improving responsiveness without interfering with your normal traffic or overwhelming your bandwidth.

🔌 Batch Streaming

Batching is a widely used optimization technique across many Web3 libraries. It reduces the number of HTTP requests by grouping multiple calls together. However, it introduces added delay because clients must wait for the batch window to close before anything is sent.

Direct Client eliminates that delay by introducing Batch Streaming, a streaming channel that starts processing requests immediately, even while the batch is still open.

It works similarly to WebSockets, allowing streaming requests and responses, but without the overhead or need for special handling. It’s automatic and works out of the box.

📦 Direct Wire Protocol

Wire is our custom data exchange format, purpose-built for JSON-RPC. It strips away redundant structure, drastically reduces payload size, and supports streaming. This makes it both fast and lean.

Wire consistently reduces bandwidth by 30–50%, and in some cases even more. These savings aren’t just nice to have, they give us a budget. With smaller payloads, we’re able to deliver more value (like predictions) without increasing load times or consuming excess bandwidth.

Wire is used throughout our infrastructure, from the client all the way to backend processing. It plays a key role in helping us scale efficiently to handle hundreds of thousands of requests per second.

Examples

Below are examples of common requests encoded in JSON versus Wire, with payload size comparisons.

eth_blockNumber

Request body (91% smaller payload)


json > {"jsonrpc":"2.0","method":"blockNumber","id":1,"params":[]}
wire > 1#1:1

Response body (62% smaller payload)


json > {"jsonrpc":"2.0","id":1,"result":"0x427dadd"}
wire > 2#1:1!9:0x427dadd

🔁 Automatic Failover

Direct is connected to all the major RPC providers, and Direct Client uses this infrastructure automatically. Every request is routed through the fastest, most reliable provider at the time it’s made.

If one of your providers fails, we reroute traffic instantly to another working provider. If all of them are unavailable, we fall back to Direct’s own global node network. And if we experience issues, Direct Client bypasses our system entirely and sends requests directly to your configured providers.

This ensures full failover, a model we call decentralization of risk.

⚡ Instant Finality Detection

When your users send transactions, they expect your app to reflect changes as soon as those transactions are confirmed. Especially on fast chains, UI feedback should match the speed of the network.

Direct Client tracks propagation and settlement across multiple providers in real time. This allows it to detect confirmations earlier and reflect updates in the UI without delay.

Traditionally, apps rely on a single provider and wait for it to catch up. But because Direct controls both the client and the infrastructure, we can observe many providers in parallel and reflect confirmed state changes instantly.

And the best part? You don’t have to do anything. No WebSockets to manage. No polling. Direct Client handles it all automatically.

This feature will be available in Beta.

🌐 Peer-Assisted Delivery

Direct already eliminates most requests to your RPC provider, and with edge locations worldwide, we deliver data from locations close to your users with minimal latency.

Peer-assisted delivery takes this even further. Using WebRTC in the browser, your users can securely relay data between each other. Each one becomes a peer, helping distribute responses without relying solely on centralized infrastructure.

Because we can dynamically connect your users that are geographically close, peer-assisted delivery brings data even closer - often from one user to another in the same region.

The more your users use your app, the faster and more resilient it becomes. New users contribute to performance instead of putting additional load on your provider, and help reduce infrastructure costs in the process.

Best of all, any request fulfilled through peer-assisted delivery is completely free - it doesn’t count toward your usage or billing.

This makes peer-assisted delivery especially useful for high-traffic environments like GameFi, where speed, efficiency, and cost control are critical.