Query chains through one integration
Discover supported chains, read blocks and logs, inspect transactions, and call contracts. RouteMesh routes requests across providers with automatic retries and failover.
Explore the MCP tools →AI Agents
Give your agent RPC access and the tools to manage it. Connect to 15+ providers and 1000+ chains with live service pricing and account APIs through MCP or HTTP.
Compare current service prices
Read published RPC prices by chain, method, and economy or performance strategy. WebSocket pricing is available by chain and subscription type. Both pricing APIs are public.
Use the pricing APIs →Inspect balance and usage
A customer management token lets your agent read your RouteMesh account balance and usage by chain, API key, method, or time window. This is separate from an on-chain wallet balance.
Query account usage →Manage RPC keys
List key metadata, create keys with a routing strategy and allowed domains, and update or deactivate keys by numeric ID. Use a separate management token for account operations.
Automate key management →Start with a question
- “Compare economy and performance prices for eth_call on Base.”
- “Show my RouteMesh account balance and usage by chain this week.”
- “Find the receipt for this transaction and explain whether it succeeded.”
- “List my RPC keys and deactivate the test key by its ID.”
RPC prices are USD per million requests; WebSocket prices are USD per million notifications. These are service prices, separate from gas fees. Fetch current prices for the chain and method you need; an empty result means no matching price is published.
Choose routing with evidence
Economy routing prioritizes cost. Performance routing prioritizes latency. Both use retries and failover across available providers. Coverage and redundancy vary by chain; check the chain inventory and measured performance for your workload.
Use MCP or call the APIs directly
The local stdio MCP server runs on demand with Node.js 20+ and a RouteMesh RPC API key. Add a customer management token for account tools. Public chain and pricing HTTP endpoints require no credentials. The OpenAPI specification describes the HTTP interfaces for custom integrations.