> For the complete documentation index, see [llms.txt](https://docs.yo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yo.xyz/welcome-to-yo/why-should-i-use-yo.md).
# Why should I use YO?
Yield optimizer 101
If you’re tired of constantly chasing the highest yields across multiple blockchains and DeFi protocols: YO is designed specifically for you. Manually searching for yield opportunities is exhausting, time-consuming, and expensive, forcing you to pay bridging fees, endure trading slippage, and deal with volatile yields that change without notice.
YO eliminates these pain points by automatically seeking and investing in the best risk-adjusted yield opportunities across multiple blockchains. No manual chasing, bridging headaches, or slippage losses involved for you. Using a smart, risk-adjusted approach, YO delivers more consistent yield earnings and helps you achieve a steadier, predictable DeFi earnings.
Say goodbye to endless research, complex interfaces, high gas costs, and frustrating yield chasing. With YO, you get clarity, simplicity, and peace of mind knowing your crypto is continuously optimized in a safe, transparent environment. It’s your trusted companion to finally making DeFi earnings reliable, stress-free, and efficient.
---
# 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.yo.xyz/welcome-to-yo/why-should-i-use-yo.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.
