The execution layer for AI agents in DeFi
Routon lets any AI agent discover, simulate, compose, and execute on-chain yield strategies — non-custodially. One open standard, from chat bots to autonomous trading systems.
AI agents can read DeFi. They can't safely execute it.
Agents can fetch prices and parse pools today — but the moment they need to act, every team rebuilds the same unsafe plumbing.
Executing a multi-step yield strategy means custody risk, no shared way to discover what's safe, no guarantee a path simulates before it's signed, and no attestation of who built it or how it performed.
Routon is the missing layer. A non-custodial execution standard that any agent can speak — so builders ship strategies once, and every agent can find, verify, and run them.
Four steps. Funds never leave the user.
Every strategy moves through the same path — and Routon's contracts hold zero balance at every step.
Discover
Query the StrategyRegistry for composable yield strategies — filtered by chain, risk profile, and builder reputation.
Simulate
Dry-run the full execution path against live oracle prices before a single transaction is signed.
Compose
Chain primitives into a strategy. The PrimitiveExecutor validates every step against protocol invariants.
Execute
The agent signs; Routon routes. Approvals and calls run through the user's own wallet — never a pooled vault.
Built for the agents that run strategies — and the builders who write them.
Connect once. Execute anywhere.
Any MCP-compatible agent integrates with Routon in minutes — no custom contract integration required.
- MCP server with x402 paymentsPay-per-call settled in USDC, natively — no API keys, no accounts.
- ERC-8004 on-chain identityEvery agent gets a verifiable identity and a reputation that travels with it.
- Agent Skills manifestCapabilities discoverable at a standard
/.well-knownendpoint.
Ship a strategy. Earn every run.
Write a strategy once, register it, and earn fees automatically each time an agent executes it.
- Register in the StrategyRegistryPublish composable strategies keyed by a deterministic on-chain identifier.
- Earn through the BuilderCodeVaultFee accrual on every execution — settled transparently on-chain.
- Reputation via the ReputationOracleValidated, attested performance — so good strategies surface to agents.
Six ways into the protocol.
From a one-line CLI install to a typed SDK — meet your agents where they already run.
MCP Server
mcp.routon.xyzx402-native Model Context Protocol server. Discovery, simulation, and execution tools for any MCP agent.
Streamable HTTP · ERC-8004 →CLI
@routon/cliSimulate strategies, inspect deployments, and register as a builder — straight from your terminal.
npm i -g @routon/cli →SDK
@routon/sdkTypeScript SDK — viem-native, fully typed, zero any. Build agents in code.
Dashboard
app.routon.xyzConnect a wallet and watch agents work — strategies, positions, and activity in one view.
Open the dashboard →REST API
api.routon.xyzLanguage-agnostic HTTP access to the agent brain — for stacks that don't speak MCP.
FastAPI · OpenAPI schema →Routon Standard
CC0The open specification for agent-executable DeFi strategies. Implement it, extend it, build on it.
Read the standard →Six contracts. One non-custodial invariant.
Zero balance, by invariant
A Foundry invariant asserts that protocol contracts never hold a token balance. Custody stays with the user — enforced, not promised.
Two oracles, one circuit breaker
Pyth as primary and Chainlink as secondary. A 1% disagreement halts execution before a mispriced trade can settle.
44 invariants, fuzz-tested
The protocol's safety properties are encoded as 44 invariants and exercised under continuous fuzzing — a Foundry-only, audit-ready codebase.
Open by license
Contracts and SDKs are MIT. The Routon Standard is CC0. The protocol is meant to be built on — not walled off.
Eight chains. One execution layer.
One protocol, one standard — every major chain your agents reach, with the same non-custodial guarantees.
Already speaks your agent's language.
Open standards and the agent runtimes your stack already runs — connect once, no proprietary lock-in.