> For the complete documentation index, see [llms.txt](https://about.mirai.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://about.mirai.app/core-functional-components/multi-chain-yield-aggregator-earn.md).

# Multi-Chain Yield Aggregator (“Earn”)

The yield aggregator abstracts away complex DeFi strategies, presenting them as simple, risk-profiled options to users. Instead of learning liquidity pools, farming strategies, or staking mechanics, users are prompted with intuitive decisions—how much to deposit, for how long, and at which approximate APY. Under the hood, the aggregator:

* **Sources Yield Across Chains:** Identifies competitive yield opportunities on various blockchains, ensuring users always have access to optimal rates.
* **Abstracts Complexity:** Handles protocol interactions, ensuring that even novice users can safely participate in DeFi.
* **Integrates with Sticky Balances:** Funds already stored within Mirai (e.g., from P2P transactions) can seamlessly flow into yield opportunities.


---

# 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://about.mirai.app/core-functional-components/multi-chain-yield-aggregator-earn.md?ask=<question>&goal=<endgoal>
```

`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.