> For the complete documentation index, see [llms.txt](https://docs.idle.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idle.finance/products/best-yield.md).
# Best Yield
Products > Best Yield
The Best Yield vaults are single-sided liquidity pools that aim to offer the highest yield for supported stablecoins at all times. This is achieved by programmatically allocating these assets across several lending pools.
Best Yield benefits users by socializing gas costs, automating the yield generation and rebalancing process, and automatically shifting capital as opportunities arise. End users and integrators do not need proficient knowledge of the underlying protocols or DeFi.
Users' funds are pooled together in the main contract (one for each supported token) to minimize gas expenses for reallocating funds and provide, at the same time, the highest aggregated APY for all pooled funds.
Interest rates are constantly monitored, and an off-chain bot computes the exact allocations to maximize aggregated APY. If, for a given pool, the current on-chain allocations are different from the newly calculated one, the smart contract receives new allocations, and the pool gets rebalanced.
{% hint style="info" %}
This strategy has been battle-tested since mid-2019, and it’s considered one of the most resilient in the entire DeFi space.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.idle.finance/products/best-yield.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.
