Agent Native RouteMesh
What shipped
Two things that work together:
Management tokens let you authenticate to the RouteMesh API programmatically. Create them in the dashboard, authenticate via X-Api-Key, and revoke instantly. Tokens are prefixed rmtm_, stored hashed, and the plaintext is shown once at creation. Each token is scoped to your account — you control exactly what it can access.
MCP server customer tools — @routemesh/mcp now exposes get_usage when ROUTEMESH_MGMT_TOKEN is set. Ask Cursor "what's my RouteMesh usage?" and get balance, per-chain breakdown, top methods, and time series back — all from natural language.
What you can do
- Ask your agent about usage. Open Cursor, type "show my RouteMesh balance and top chains this month," and get a real answer. No login, no export, no dashboard tab.
- Manage API keys programmatically. Create and revoke RPC service keys via the API. Hook it into CI/CD, scripts, or internal tooling.
- Scoped, revocable access. Each token only works on the routes you allow. Revoke instantly from the dashboard if a token leaks or you no longer need it.
- Query usage with filters. Break down by chain, API key, method, or time window. Hourly granularity for one key, or a 30-day summary across everything.
How management tokens differ from RPC keys
RPC service keys authenticate your dApp's traffic to the RouteMesh routing layer (Atlas). Management tokens authenticate *you* to the RouteMesh API — usage, keys, account operations. Different scope, different header, different purpose. Your dApp uses RPC keys; your tools use management tokens.
This separation matters for security. If a management token leaks, your RPC traffic is unaffected. If an RPC key leaks, your management API is unaffected. Each layer has its own auth, its own scope, and its own revocation path.
Get started
- Create a management token at routeme.sh/app/settings/mgmt-tokens
- Set ROUTEMESH_MGMT_TOKEN in your environment
- Install the MCP server: npx @routemesh/mcp
- Ask your agent: "What's my RouteMesh usage this month?"
For the full API reference, see our documentation. The MCP server is stdio-based and works with Cursor, Claude, or any MCP-compatible client. It's on npm at @routemesh/mcp.