Skip to main content
Follow these steps to send your first request through RouteMesh.

1. Sign up and get your API key

  1. Go to the RouteMesh app and sign in or create an account.
  2. In the dashboard, open API Keys (under Workspace) and create your first key.
  3. Choose a routing strategy:
    • Economy — Most competitive prices across the widest set of chains, with redundancy baked in. Great for high volume and cost-sensitive use cases.
    • Performance — We route to the fastest nodes. Expect low latencies (e.g. 50–75 ms) with redundancy baked in.
You can create multiple API keys and set a different strategy per key. See Routing strategies for details.

2. Top up your account

  1. In the app, go to Billing (under Finance): Billing.
  2. Click Buy More Credits and purchase the credits you need. Credits are applied immediately.
Credits never expire. One credit = one dollar.

3. Make your first request

One URL — Adding a chain is just a path. We use a consistent URL scheme so you don’t have to juggle mapping files. Your RPC URL is: POST /rpc/{chain_id}/{api_key} Use a supported chain_id (e.g. 1 for Ethereum) and your API key:
For allowed domains, cooldowns, and batch requests, see Request behavior. For error handling, see RPC error codes. For real-time event streams, see WebSocket API.

Public RPC (no API key)

You can call RouteMesh without an API key for a limited free tier using the public path POST /rpc/evm/{chain_id}. This is intended for light, anonymous access:
The public route is rate-limited per IP. If you hit the limit or it is temporarily unavailable, the response points you to sign up for a free account for full access. For higher volume, use an API key as shown in Make your first request.

Supported networks

RouteMesh supports 1000+ chains across all major EVM networks. See the full list at routeme.sh/chains.

Next steps

  • How it works — How we route your requests and what happens behind the scenes.
  • Request behavior — Cooldowns, rate limiting, and batch requests.
  • Debugging — Use X-Batch-Id and the Logs page when something goes wrong.
  • MCP Server — Let AI coding agents query RouteMesh directly.