Welcome to the Routescore help center. Routescore is a non-custodial DeFi decision-support workbench: it helps you score a route before you trade, model your MEV exposure, stress-test supported holdings, keep a hash-recorded decision journal, and watch public detector signals. These guides walk through each surface and the thinking behind it.
Routescore never holds your assets, never executes trades, and never asks for a private key or seed phrase. Everything here is decision support — every transaction you choose to make stays entirely your decision.
Choose your task
| I want to… | Start here | Capability state |
|---|---|---|
| Check a route before signing elsewhere | Getting started | Supported route classes are live; unsupported pairs remain explicit |
| Add a read-only pre-sign check to an agent | API & MCP access | Production API live; local behavior depends on configured fixtures and sources |
| Verify a persisted evidence record | Verifiable pre-sign evidence records | Keyed owner-scoped records; persistence failures return an in-band caveat |
| Understand a score or trust state | Methodology | Published method; public calibration remains gated until sample and drift gates clear |
| Review the security boundary | Security | Read-only and non-custodial; no execution or private-key access |
Use the search field in the left navigation to filter guide titles. Every
developer example is paired with an environment or capability boundary so
partial, unavailable, and unsupported do not disappear behind setup prose.
Fast path
If this is your first session, Getting started is the quickest orientation. If you are integrating code or an agent, go directly to API & MCP access for keys, copyable examples, environment URLs, response trust envelopes, and the OpenAPI contract.
A standing caveat
Scenario and score outputs are modeled, point-in-time, and not investment advice. Routescore is built to make your own reasoning sharper and your own records cleaner — not to tell you what to trade.