> For the complete documentation index, see [llms.txt](https://pool-party-xyz.gitbook.io/pool-party-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/core-concepts/multi-asset-and-adapters.md).

# Multi-asset & Adapters

Pool Party is multi-asset and open by design, and adapters are what make that possible.

#### **What an adapter is**

An adapter is a standardized integration that lets a pool hold or interact with a given asset or protocol without changing the pool's core logic. Each adapter connects the pool to an asset source or an external protocol in a controlled way.

#### **Open architecture**

New adapters expand what pools can allocate to. As adapters are added, pools can reach different asset classes, from tokens to fixed income and real-world assets (RWAs). The assets actually available at any moment depend on the adapters that are deployed.

{% hint style="info" %}
The adapter layer is what keeps Pool Party extensible: a pool's logic stays the same, and the universe of assets grows as new adapters come online.
{% endhint %}


---

# 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://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/core-concepts/multi-asset-and-adapters.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.