> For the complete documentation index, see [llms.txt](https://docs.flowx.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowx.finance/welcome-to-flowx-finance/protocol-overview.md). # Protocol Overview FlowX is the ecosystem-focused decentralized exchange built on the Sui Blockchain. FlowX Finance is an ecosystem-focused decentralized exchange (DEX) built on the Sui blockchain. It is the ultimate destination for all trading needs, designed to provide a seamless, user-friendly experience. For users, they can enjoy a smooth trading experience with the best rates aggregated from all AMMs on SUI. The platform offers an intuitive UI and allows users to participate in various vital services in DeFi, such as token swapping, liquidity contribution, yield farming, and joining IDO campaigns on FlowX launchpad. FlowX Finance also provides listing and market-making services, making it easy to operate farming campaigns with Farming as a Service features. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flowx.finance/welcome-to-flowx-finance/protocol-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.