> 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/overview/multiswap-for-traders.md).

# Multiswap: For Traders

1. **Multi-Asset Swaps:**&#x20;

M-to-N multi-asset swaps allow you to natively rebalance your entire cryptocurrency portfolio in a single trade with no batching or liquidity fragmentation.

2. **Unified Liquidity:**&#x20;

By unifying all token liquidity into a single pool, Multiswap delivers better price execution and reduces price slippage on large trades.

3. **No Routing Issues:**&#x20;

Multiswap eliminates the need for trade routing through multiple two-token pools, creating savings on gas costs and enhancing trade execution.

4. **Effortless Hedging:**&#x20;

Multiswap enables traders to hedge their portfolios seamlessly by obtaining consistent, diversified exposure through a single LP token.


---

# 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.caval.re/overview/multiswap-for-traders.md?ask=<question>&goal=<endgoal>
```

`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.
