> For the complete documentation index, see [llms.txt](https://docs.caval.re/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caval.re/getting-started/building-a-multiswap.md). # Building a Multiswap ## Trade Users can view lists of available assets and pool tokens on the Trade page, along with important information such as the current price and token reserves. In addition, users can search for tokens using their respective ticker symbols, making it easy to find desired tokens. To trade, users can click "Buy" or "Sell," and the asset will be added to the Quote panel.

## Quote Panel

The Quote panel is a familiar "shopping cart" panel on the right-hand side of the screen, displaying all the selected tokens for buying or selling. It allows users to manage multiple tokens in one place with ease. Once the selection is made, users can confirm the transaction with a single click, streamlining the multi-tokens trading process and making it faster and more efficient. With Multiswap, users can quickly execute novel trading mechanisms with a familiar interface. > Note: when **selling**, users need to input the **number of tokens** they want to sell, while when **buying**, users need to input the **allocation in percentage**. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.caval.re/getting-started/building-a-multiswap.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 `automate deployments from our CI pipeline` 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.