> For the complete documentation index, see [llms.txt](https://docs.arcswap.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcswap.fun/overview/introduction.md). # Introduction ArcSwap is a decentralized swapping protocol built to make token exchange simple, efficient, and transparent. The platform focuses on routing optimization and user-first clarity, helping traders achieve better execution outcomes without navigating unnecessary complexity. ArcSwap is designed to seamlessly connect users to liquidity across multiple sources while minimizing slippage and hidden costs. Our interface is intentionally minimal, ensuring that users understand each part of their transaction. Clear pricing data, route previews, and output expectations are presented upfront. By aligning performance engineering with intuitive UX, ArcSwap allows users to swap with confidence. ArcSwap continues to evolve alongside the broader DeFi ecosystem. Through continuous optimization, we aim to deliver an experience that feels stable, predictable, and accessible to both new and experienced users. --- # 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.arcswap.fun/overview/introduction.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.