> For the complete documentation index, see [llms.txt](https://docs.sierra.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sierra.money/protocol-use-cases/powering-an-earn-offering.md).

# Powering an Earn Offering

**Designed For:** Fintechs, neobanks, exchanges, and card issuers offering stablecoin yield to their end users

Sierra provides the entire yield generation and reserves management layer, while the partner retains full ownership of the user experience, branding, and customer relationship. Deposits from users on a partner's platform are routed through a dedicated Sierra vault into a blend of RWA and DeFi yield sources that was curated by Sierra and the partner. All custody, settlement, compliance, and reporting is handled by Sierra's institutional-grade infrastructure stack.

Partners get a plug-in yield engine that:

* Eliminates the operational burden of building and maintaining in-house solutions
* Unlocks off-chain RWA yield sources that would otherwise be out of reach
* Scales seamlessly across user bases from tens of thousands to million
* Creates a new revenue stream and improves stickiness of user deposits

All of these benefits are achieved without the partner writing a smart contract or changing their existing operational workflows.


---

# 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://docs.sierra.money/protocol-use-cases/powering-an-earn-offering.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.
