> 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/what-is-yo.md).

# What is YO?

Yield Optimizer 101

YO stands for Yield Optimizer. YO is a DeFi protocol that helps you easily boost your crypto earnings without the hassle. YO automatically moves funds across the best-performing pools no matter the blockchain, so you’re always getting the **highest risk-adjusted yield**.&#x20;

YO leverages [Exponential.fi's Risk Ratings](https://exponential.fi/learn/risk-rating) to smartly balance risks and reward—so you don’t have to spend time managing risk yourself. YO is fully decentralized, meaning you’re always in control of your assets from your own wallet. If you want a simple, secure way to earn more from your crypto, YO’s got you covered.


---

# 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.yo.xyz/welcome-to-yo/what-is-yo.md?ask=<question>&goal=<user_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.
