Build on Direct
Direct is an RPC provider for web3. You send JSON-RPC, exactly like you always have — but behind that endpoint is a peer-to-peer network of RPC nodes and a Direct client running right next to your app, working together to make every request faster, more reliable, and cheaper.
No central endpoint. No single point of failure. No code changes — it takes two lines to integrate.
How Direct Works
- → Overview
- → Local-first architecture
- → The Network
Integration & Guides
- → Getting started
- → Using Direct
Reference
- → FAQ
Start here
- Getting started — the shortest path to your first request.
- How Direct works— the network and the clients, explained.
- Local-first architecture — what happens on a single request.
- The Network— the peer-to-peer node network.
- Using Direct— the browser and backend clients.
- FAQ— common questions.
What makes Direct different
Traditional RPC sends every request through one central endpoint. Direct doesn’t. It pairs a peer-to-peer network of RPC nodes with a client that runs next to your app, and the two work together to route each request across the network instead of funneling it through a single point.
You don’t have to think about any of that. The client speaks plain JSON-RPC, so your app talks to Direct like it would any endpoint.
What you get
- Drop-in.It’s plain JSON-RPC. Two lines in the browser, or a local endpoint on your backend — no other code changes.
- No single point of failure. Requests route across many nodes instead of depending on one endpoint.
- Great performance. Direct connections to nearby nodes, many at once, with popular data served instantly from a local-first cache.
- Better pricing. Direct buys efficiently across a competitive network of providers and passes the savings on to you.