> 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/auto-rebalancing.md). # Auto-Rebalancing ### How Autopools Auto‑Rebalances Between DeFi Destinations Autopools spread your deposit across a curated set of pools and protocols (we call these **destinations**) and **adjusts** that mix as conditions change. When a different destination looks better **after** accounting for costs like swaps, the autopool shifts only what makes sense. **What’s happening under the hood:** * It continuously **monitors** yield signals and market conditions. * It **compares** potential improvements vs. the cost of moving. * It **moves** only when the expected benefit outweighs the costs. > **Autopools mean you're not getting chopped up!**\ > You’re not stuck in yesterday’s “best pool,” and you’re not paying churny fees. Rebalances aim to be **infrequent but meaningful**. **A single deposit, and the autopool takes it from there: monitoring, comparing, and only moving when it's worth it.** **FAQs** * **How often does it rebalance?** Only when the improvement is meaningful net of costs. There’s no fixed cadence; it’s opportunity‑driven. * **Will it ever move everything at once?** Usually not; it prefers measured shifts to keep costs and slippage low. * **Who pays the transaction costs?** Costs are part of the decision logic—rebalances simply won’t happen unless the expected benefit clears those costs. --- # 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.auto.finance/auto-pools-protocol/autopools-tl-dr/auto-rebalancing.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.