> For the complete documentation index, see [llms.txt](https://docs.nep.finance/neptune-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nep.finance/neptune-docs/product-features/powerful-dex-aggregator.md). # Powerful DEX Aggregator **Decentralized Exchange (DEX) Aggregators** play a crucial role in decentralized finance (DeFi) by optimizing the trading experience. They scan multiple DEXs to find the best prices, saving users from manually comparing rates across platforms. This is particularly useful in the fragmented and volatile DeFi market. Beyond better prices, aggregators also enhance liquidity, minimize slippage, and speed up transactions, all while maintaining user control over funds and promoting transparency. At Neptune, we pioneer an innovative algorithm to power our DEX aggregator, ensuring optimal trade execution with minimal slippage. This algorithm dynamically evaluates trading pairs and liquidity pools across platforms, using real-time data such as liquidity depth, fees, and market volatility to determine the most efficient transaction path. Unlike traditional order routing, which relies on a single platform and risks slippage, our algorithm splits trades across multiple sources to optimize execution and minimize costs. --- # 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.nep.finance/neptune-docs/product-features/powerful-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.