> For the complete documentation index, see [llms.txt](https://docs.term.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.term.finance/terminal-1-execution/integrations/aggregators.md).

# Aggregators

Terminal 1 integrates with DEX aggregators to source swap liquidity when a route requires token conversions (e.g., repaying a debt in one token using proceeds in another). Aggregators are used to construct swap call data and execution paths that are compatible with the route’s constraints.

<figure><img src="/files/Sxgqh21lu73ih7YVWjiU" alt=""><figcaption></figcaption></figure>

### What to expect

* Aggregator steps appear in the route sequence when swaps are required.
* Swap outcomes can differ from preview due to price movement and liquidity changes; constraints and UI buffers are used to reduce avoidable reverts.
* If execution falls outside route bounds (fees, slippage, deadlines), the route will revert rather than partially complete.

### What users should watch

* Slippage and price impact are the primary risk drivers for swap-dependent routes.
* Quotes can become stale, especially with Safe signing latency; re-run preview if execution is delayed.
* Swap availability is chain- and asset-dependent; a given aggregator may not support all routes or tokens.
* Review which tokens are swapped, expected minimums/maximums, and any buffer settings shown by the UI.

### Related pages

* [Routes & atomic execution](/terminal-1-execution/concepts/routes-and-atomic-execution.md)
* [Fees, slippage & buffers](/terminal-1-execution/concepts/fees-slippage-and-buffers.md)
* [Disclosures](/terminal-1-execution/risks-and-failure-modes/disclosures.md)