Rout for developers
Rout runs snipers, declarative JSON definitions that say what to watch, when to buy, how to exit, what to spend and how transactions are sent.
Status
Rout has not traded on mainnet. The API is specified and Rout's app client calls it, but no execution result is published.
rout-next/src/domain/capabilities.ts:44-45 · rout-automation-ui@61469bfYou create a definition, enable it, and a host runs it. Everything here is generated from, or cited against, Rout's own interface files and app client. Nothing is retyped.
Quickstart
Create, enable, watch and stop a sniper through
/agents.Sniper definition
Every field and type, generated from Rout's schema.
Errors
Every refusal and what a client should do about it.
Execution model
Nonce vs blockhash, tips and floors, executed vs pre-execution detection.
Protective exit
An exit that fires on outside flow, with its own tip and bounded slippage.
Resend without buying twice
Durable nonce makes a resend land at most once.
Exits inside a price bound
Explicit slippage with a ceiling, never unbounded.
Publishing results
From an engine run to a figure on /benchmarks.
Benchmark data
The files a benchmark run publishes and how /benchmarks reads them.
Three rules
| Rule | In practice |
|---|---|
| Base units, always | Every amount is an integer in the smallest unit: lamports for SOL, 10⁻⁶ for USDC. 2.5 SOL is 2500000000. Strings and decimals are refused. Use a BigInt-safe JSON parser above 2⁵³. |
| Explicit nulls, never omissions | A key that may be "none" is sent as null. Only sells, exits and a sell rule's tip_lamports may be left out. |
| No defaults on the backend | Rout fills in no tip, limit, slippage, window, wallet policy or nonce choice. execution and limits are required. |
Source: interface/README.md, "The three rules".