> For the complete documentation index, see [llms.txt](https://docs.collection.xyz/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collection.xyz/guides/collection-concepts/liquidity-pool/basic-pool.md).

# Basic Pool

Basic Pool provides liquidity for a collection without specifying any Merkle root filter. Anyone can buy or sell if there is enough stuff in the pool to buy/sell against. However, since there is no Merkle root filter, it will not make sense to deposit NFTs much more valuable than the floor price, since they will be valued exactly the same as floor price NFTs.

Liquidity providers should skip the filtering interface, if they hold NFTs that they consider valued at floor price and are willing to trade against the whole collection.

<figure><img src="/files/AcJc5AG1FigAMhY8xf61" alt=""><figcaption><p>Create a basic pool</p></figcaption></figure>


---

# 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.collection.xyz/guides/collection-concepts/liquidity-pool/basic-pool.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.
