Skip to main content
RouteMesh gives agents one integration for blockchain RPC across providers, published service prices, and account management. Use the MCP server inside a compatible assistant, or call the HTTP APIs from your own agent. Economy routing prioritizes cost; performance routing prioritizes latency. Both include retries and failover across available providers.
The pricing MCP tools are included in the source for version 1.2.0; npm publication is pending. Until that release is available, use the public HTTP pricing endpoints below or build the MCP server from source. Account balance, usage, and provider tools are already available in published releases.

​
Choose your interface

Public HTTP endpoints do not need credentials. The local MCP server requires ROUTEMESH_API_KEY at startup; add ROUTEMESH_MGMT_TOKEN to enable its customer tools. See MCP setup for client configuration.

​
Compare prices before choosing a route

Discover the chain ID using rpc_list_chains, then ask:
Compare economy and performance prices for eth_call on Base.
Call rpc_get_pricing with chainId: 8453 and method: "eth_call". Omit routingStrategy to return both strategies. The equivalent public request is:
Each result identifies vm, chain_id, method, routing_strategy, and price_per_million. RPC prices are USD per million requests, separate from blockchain gas fees. For a workload of N requests at a published price P, the service cost estimate is N / 1,000,000 * P. Sum across methods and chains for mixed workloads; account discounts and future price changes can affect the final bill. For WebSocket subscriptions, use rpc_get_ws_pricing with a numeric chainId and optional subscriptionType, or:
WebSocket prices are USD per million notifications, not per request. An empty pricing array means no matching price is published; it does not mean a zero price or guaranteed support. Public pricing endpoints are rate-limited and can return HTTP 429; retry later. HTTP 503 means pricing data is temporarily unavailable.

​
Inspect account balance and spending

Create a customer management token in Mgmt Tokens. It authenticates account operations through the X-Api-Key header. Your RPC API key is a separate credential used for blockchain requests. With ROUTEMESH_MGMT_TOKEN configured, ask your assistant:
Show my RouteMesh account balance, request count, and usage by chain for the last seven days.
Call get_usage with include: ["summary", "balance", "by_chain"] and an RFC3339 from/to window. To call the API directly, set ROUTEMESH_MGMT_TOKEN in your environment and run:
Without a time window, usage defaults to the last 30 days. You can also request breakdowns by API key, method, day, or hour. See MCP usage parameters and the usage API for filters and limits. Your RouteMesh account balance pays for RPC service. A wallet balance from rpc_get_balance is the native token balance of an on-chain address. They are different values.

​
Manage keys from your agent

Use list_api_keys to get key IDs, names, active status, allowed domains, and routing strategy. Listing does not reveal the key secrets. To create a key, call create_api_key with allowed_domains, routing_strategy (economy or performance), and an optional name. The response includes a secret once, at creation. Store it securely. To change a key, pass its numeric id from the list response to update_api_key, along with name, allowed_domains, or active. For example, { "id": 42, "active": false } deactivates key 42. The HTTP equivalent is PUT /api-keys/42. Do not put the secret key string in this management URL.

​
Integration references