> For the complete documentation index, see [llms.txt](https://bubblefi.gitbook.io/bubblefi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bubblefi.gitbook.io/bubblefi/features/full-range-amm/our-additions/multi-asset-swap.md).
# Multi-Asset Swap
Multi Asset Swap Schema
Multi-asset swap is centered around pools built with at least one LP token from other BubbleFi bubble pools. LP tokens of other BubbleFi pools can be registered as supported tokens, which will allow creation of multi-asset pools.
Multi-asset pools can be classified based on their degree.
* **Degree 1:** These pools hold at least one LP token type. For example, Monad <=> USDC LP token + BAT token pool allows swapping out Monad <=> USDC LP tokens by providing some BAT. Degree 1 pools can also include LP token + LP token pools which can hold virtually a maximum of 4 assets.
* **Degree 2:** These pools are built with LP tokens of degree 1 BubbleFi bubble pools, and can support a maximum of virtually 8 tokens per pool.
Generalizing, degree `N` pools can be created with LP tokens of degree `N - 1` pools, and can support virtually a maximum of
$$
2^{(N+1)} \text{ assets}
$$
However, BubbleFi will only support degree 1 pools at launch.
---
# 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://bubblefi.gitbook.io/bubblefi/features/full-range-amm/our-additions/multi-asset-swap.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.