Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Metric Docs | Swap via Router

Understand the router-based Metric swap flow, including token approvals, route selection, execution limits and transaction validation.

Understand the router-based Metric swap flow, including token approvals, route selection, execution limits and transaction validation.

Metric is built around Active Pools: liquidity pools that use a Price Provider to supply bid, ask and reference prices instead of relying only on reserve ratios. This page focuses on Swap via Router and the practical checks that matter when using or integrating the protocol.

Router flow

A router abstracts venue selection and execution into a single transaction path. The caller still needs correct approvals, token addresses and output protection.

When routers help

Routers are useful when an application wants route selection, multi-pool logic or a stable integration boundary instead of targeting individual pools directly.

Validate the route

Confirm the route refers to the intended chain and tokens and that the final calldata matches the quote you showed to the user.

Last updated