> For the complete documentation index, see [llms.txt](https://docs.hipposwap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hipposwap.finance/product/dex-aggregator.md). # Dex Aggregator Hippo Swap stands as a pioneering DEX aggregator within the SCROLL and now BASE. That the great protocol compared to other DEXes. Hippo Swap gets liquidity from various exchanges and is capable of splitting a single trade transaction across multiple DEXes to ensure the best rates. The protocol provides aggregation information services on exchange protocols and networks which performs runtime verification of transaction execution.This ensures that users' funds remain secure, even when interacting with potentially unsafe liquidity sources.Since the smart contract ensures security, the protocol can be used in various aggregation information services. Additionally, traders have the option to define trade routes in the swap settings. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hipposwap.finance/product/dex-aggregator.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.