Skip to main content
When you swap in the web app, you do not pick a pool — routing does. This page explains where your quoted price comes from and what the router optimizes for.

How the app routes a swap

The order router evaluates the available V1 and V2 paths from the input token to the output token and returns the best executable route. That route can be:
  • Direct. A swap through one V1 or V2 pool.
  • Multi-hop. A swap routed sequentially through up to three V1 or V2 pools, either because no direct pool exists or because the indirect path prices better.
  • Split route. A swap divided across multiple paths at the same time to improve executable output and reduce price impact.
The router selects the route with the best executable output for your trade size, accounting for each pool’s fee tier and price impact. Larger trades can route differently than small ones, because price impact grows with size relative to pool depth. The chosen route is shown in the swap details before you confirm.
Quoted output is an estimate as of quote time. Your slippage tolerance bounds the worst execution you will accept; the transaction reverts rather than fill beyond it.

The order book and AMM-backed settlement

The V3 order book has a separate, one-way AMM backstop. Where enabled, a V3 order can opt into settlement against AMM liquidity, subject to the order’s signed parameters. The swap router does not currently compare an AMM swap quote with an order-book quote. Governance thread 385, proposal 6285, and final election 6296 ratified that cross-venue comparison on July 22, 2026, but the change is not verified as deployed.

For integrators

The smart order router is part of the SaucerSwap app and is not exposed as a public API. Integrators quote directly against the venues:

Next steps

Swap tutorial

Make a swap and read the route details before confirming.

SaucerSwap V3

How AMM-backed settlement works on the order book.

Developer quickstart

Get a quote programmatically in under five minutes.