How RouteMesh Works

Before we understand how RouteMesh works, there are a few pieces of terminology that are important to understand:

1. Provider: refers to an entitiy that runs nodes (Alchemy, Quicknode etc)
2. Node: the actual URL of the machine that runs the client software of a particular blockchain
3. Route: a combination of a {chainId}-{method} ie: Polygon eth_call would be a route described as polygon:eth_call or 137:eth_call
4. Pathway: the node-method combination that can be used to serve a route

Our job at RouteMesh is to aggregate as many providers as possible to offer you the greatest number of routes at the lowest possible latency or price, reliably.

Your Request

When you send a request to RouteMesh, it hits our load balancer, which will determine the closest cloud provider to forward it to. We ensure that at least 2 cloud providers are operational so that redundancy is always baked into our systems.

The actual machine that routes your request will be dependent on where in the world you're calling from. We have geo-location-based routing tables that maintain their own location-dependent data. Nodes that are optimal from Europe will not be the same ones for US East (for latency at least).

When routing a request, there are a few things we do behind the scenes to make your life easy:

1. Knowing which providers can serve the route based on their chain and method support. We keep track of this in our databases for all provider/chains/methods.
2. Tracking costs to understand how to serve the route economically. Many providers use compute units and inconsistent pricing mechanisms to charge their customers. RouteMesh abstracts all of this away for you.
3. Automatically falling back to the next most optimal node should any failures occur. If no providers can serve a request, then either the blockchain is down or your request was invalid.
4. Many providers treat their error and response handling differently. We ensure that you are protected from this chaos and ensure you get uniform responses, the way you expect them to be.
5. Our rate limits are dependent on the chain you're calling and the aggregate capacity of all providers on that chain. This often means that we can handle higher loads than most RPC providers. Reach out if this sounds like you!

Once your request is delivered, you'll simply be billed for that route based on the route's price for that month. Our pricing can be viewed here.