Get started

Introduction

AI agents are good at reading DeFi. They can fetch prices, parse pools, and compare yields across dozens of protocols. But the moment an agent needs to act — to actually move capital into a multi-step yield strategy — every team rebuilds the same fragile, unsafe plumbing from scratch.

Routon is the layer that closes that gap.

The problem

Executing a yield strategy on behalf of a user is hard for reasons that have nothing to do with the strategy itself:

  • Custody risk. Most “automation” layers ask the user to deposit funds into a pooled vault. That vault becomes a honeypot, and the user is no longer the owner of record.
  • No shared discovery. There is no common way for an agent to ask “what composable strategies exist for this asset, on this chain, at this risk level?”
  • No pre-flight guarantee. An agent has no standard way to know that a multi-step path will simulate cleanly before a transaction is signed.
  • No attestation. There is no record of who built a strategy, whether it has been validated, or how it has performed.

Every agent team solves these privately, badly, and again.

What Routon is

Routon is an open execution layer: a non-custodial standard that any AI agent can speak. Builders publish a strategy once; every agent on the network can then discover it, verify it, simulate it, and run it.

The defining property is in the architecture, not the marketing:

Routon’s contracts hold zero token balance at all times. This is asserted by a Foundry invariant that runs under continuous fuzzing. Custody never leaves the user’s own wallet.

Routon does not fork or replace Aave, Morpho, Uniswap, or CoW. It composes them — orchestrating calls into allow-listed, independently audited protocols where the user remains the depositor of record.

What you can do with it

  • Build an agent that finds and runs yield strategies for its users — connecting once and executing across six chains.
  • Publish a strategy as a builder, register it on-chain, and earn a fee every time an agent executes it.
  • Integrate the protocol through an MCP server, a typed SDK, a CLI, or a plain REST API — whichever fits your stack.

Who it’s for

Routon has two kinds of participants:

  • Agents — the autonomous systems that discover and execute strategies on behalf of users.
  • Builders — the developers who write strategies, register them, and earn from their use.

The protocol is designed so that neither side needs to trust the other: a builder cannot move an agent’s funds, and an agent cannot misattribute a builder’s work.

Next

Continue to the Quickstart to install the tools, or read Core concepts for the full mental model.