> For the complete documentation index, see [llms.txt](https://docs.auto.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.auto.finance/auto-pools-protocol/autopool-receipt-tokens.md).

# Autopool Receipt Tokens

## Enter the Auto Pools Protocol

Users gain access to autonomous LP optimization by depositing into an autopool, which use the highly composable ERC-4626 standard and can be configured with a set of destinations (pools/DEXs and lending markets for some autopools) to which assets may be deployed to. \
\
Assets deposited into an autopool are not subject to any lock ups or cooldown periods, meaning that users can withdraw their funds at any time.\
\
The architecture was designed to be modular, allowing for plug-and-play integration of new assets and destinations. As a result, the system can adapt to the market swiftly by launching autopools which include e.g. a new pairings, or cater to specific ecosystems.

***

## Composable Receipt Tokens

LPs depositing into an autopool receive reward bearing receipt tokens, which are composable across DeFi. Examples of common DeFi integrations include utilizing receipt tokens as collateral, integration into yield marketplaces to trade liquidity rates, and leverage them.

<figure><img src="https://916337868-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2A6wmAnkpzrcydAUxLkR%2Fuploads%2FAluV1BK9Qxd7tir2Mm3E%2F12.jpg?alt=media&amp;token=814c191c-34d6-4629-9c2c-f03d75be2ff0" alt=""><figcaption><p>LATs are tokenized of the underlying option set of destinations</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.auto.finance/auto-pools-protocol/autopool-receipt-tokens.md?ask=<question>&goal=<user_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.
