> 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/yield-optimizing.md).
# Yield Optimizing
### How the Autopool Protocol Optimizes Across Destinations for Better Yield
Each **autopool** has a pre‑selected **set of eligible destinations** (these can be DEXs, lending protocols, and soon yield markets). The rebalance logic scores those options using a blended view of return **and** cost—headline APRs, fees, rewards, available liquidity, and the “hidden” stuff like volatility and potential impermanent loss.
Instead of chasing whatever advertises the highest APY today, the logic aims to **beat any single venue over time** on a risk‑aware basis.
\
*The goal is steady, risk‑aware outperformance, not whiplash‑inducing APY chasing.*
**FAQs**
* **How are destinations chosen?** They’re curated for fit (asset type, liquidity depth, integrations, historical behavior) and continuously reviewed.
* **Do you add new destinations?** On occasion, when they meet safety and strategy criteria. Generally only battle tested destinations are chosen.
* **More autopools are continually being added, so check back frequently.**
---
# 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/autopools-tl-dr/yield-optimizing.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 `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.