> 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/autopools-tl-dr.md). # Autopools tl;dr ## **A New Way to LP** **The Auto Pools protocol, a novel LP Aggregator, unlocks a new way to LP through automated yield optimization.**\ \ Users deposit assets into an autopool, each representing a set of potential deployment destinations for the autonomous rebalance logic. From there, the Autopool Rebalance Logic takes over, autonomously monitoring the underlying pools and leveraging its powerful framework to rebalance – thus abstracting the complexity associated with rebalancing, compounding, and staking of LP tokens away from the user.\ \ The autopool receipt tokens (e.g., autoETH) are yield-bearing and can be seamlessly integrated across DeFi. ### Effortless Access to LP Optimization The user experience is simple: 1. LP chooses an autopool, deposit any asset via a simple, gas-optimized transaction and gets back the yield-bearing receipt token (e.g. autoETH) 1. The autopool monitors the underlying destinations and rebalances 2. Rewards auto-compound back into the autopool 2. LP uses Dashboard to keep track of the autopool's performance and other metrics Providing liquidity to a set of destinations becomes as simple as swapping tokens or making a simple deposit. > **"What DEX aggregators did for traders, autopools are doing for LPs."** Learn more about using autopools in the [App Guide.](/using-the-app/app-guide.md) --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.auto.finance/auto-pools-protocol/autopools-tl-dr.md?ask=&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 `build a script that syncs our docs to a CMS` 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.