The Routescore API & MCP server.
Power plans include a keyed REST API and a one-line MCP server: call cover quotes and the what-if simulator from your own stack, or drop Routescore tools straight into Claude, Cursor, and your agents. Read-only public snapshots and account exports live below.
Call Routescore from your own stack
- Generate a key in Account → Developer → API & MCP (Power tier).
- Send it as Authorization: Bearer rs_live_… to any endpoint below, or
- Drop the MCP config into your client to expose the same tools to your agent.
MEV cover quote
Premium + expected/CVaR loss for sandwich protection on a swap.
Bridge refund quote
Cover pricing for cross-chain bridge execution failure.
LRT slashing quote
Slashing cover pricing for an LRT position given AVS exposure.
What-if scenario
Monte-Carlo expected premium vs refund/loss over a horizon.
Detector manifest
Latest public detector run: version hash + eligible universe.
Whoami
Verify your key works and see its plan tier.
curl -X POST https://routescore.io/api/public/v1/quote/mev \
-H "Authorization: Bearer rs_live_..." \
-H "Content-Type: application/json" \
-d '{"notional_usd": 10000, "asset_pair": "USDC/ETH"}'{
"mcpServers": {
"routescore": {
"command": "npx",
"args": ["-y", "@routescore/mcp"],
"env": { "ROUTESCORE_API_KEY": "rs_live_..." }
}
}
}Ships as @routescore/mcp. Rate limits apply per key (X-RateLimit-* headers).
{
"score_state": "partial",
"source_freshness": {
"state": "partial",
"checked_at": "2026-06-21T00:00:00.000Z",
"sources": [
{ "name": "routescore_backend", "freshness_state": "fresh" },
{ "name": "bridge_risk_labels", "freshness_state": "unknown" }
]
},
"methodology_version": "routescore-public-api-v0.1",
"confidence_band": { "low": null, "high": null, "unit": "bps" },
"caveats": [
"Modeled, point-in-time decision support. Not an execution guarantee.",
"Unsupported or stale inputs widen uncertainty instead of hiding risk."
],
"commercial_disclosure": {
"paid_placement": false,
"score_influenced_by_partner": false
}
}Quotes and scenarios are modeled, point-in-time, user-controlled decision support — not investment advice. The export surfaces below are read-only. Routescore does not custody assets, execute transactions, or recommend financial actions. API and MCP responses include score state, source freshness, methodology version, caveats, confidence, and commercial disclosure so downstream tools can keep the trust contract visible. Known limitations are published at /limitations.
Public read-only surfaces
Public snapshot list
Lists available public detector and benchmark snapshots with freshness metadata.
Public snapshot payload
Returns an allowlisted public scanner payload, such as mev_loss_index, stablecoins, bridges, or oracle_map.
Supported-token prices
Prices only the supported launch token universe. This is not a universal token pricing API.
Route score quote race
Returns supported route quote comparison data with rate limits and short cache windows.
User-owned exports
Account export
Authenticated JSON export containing account, saved wallets, and hash-recorded journal records.
Journal CSV export
Authenticated CSV export for durable hash-recorded journal entries.
Alert threshold rules
Power-tier public-detector threshold rules. Not wallet-specific alert monitoring.
Detector refresh requests
Power-tier queue for supported public detector snapshots. Not a contractual freshness guarantee.
{
"generated_at": "2026-06-19T00:00:00.000Z",
"source": "routescore",
"coverage": {
"mode": "supported",
"not_included": ["unsupported tokens", "wallet-specific MEV reconstruction"]
},
"scenario": {
"kind": "stress_test",
"modeled": true,
"point_in_time": true,
"not_investment_advice": true
}
}- Copy scenario JSON into a notebook or internal memo.
- Export journal and wallet records for personal archives.
- Build public detector dashboards from snapshot endpoints.
- Call quotes & what-if from your own agents via the API / MCP (Power).