> For the complete documentation index, see [llms.txt](https://docs.osero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.osero.com/osero-product/overview/use-cases.md).

# Use Cases

Osero Earn is designed for any platform that holds or distributes stablecoins for its users. The SDK is platform-agnostic, so the same integration can work across different products, from consumer neobanks and wallets to exchanges and institutional custodians.

## Who should integrate Osero Earn?

### Neobanks

|              |                                                                 |
| ------------ | --------------------------------------------------------------- |
| **Use case** | Add stablecoin savings as a native product for their customers. |

Neobanks holding customer stablecoin balances can turn those balances into a savings product that competes with traditional high-yield savings accounts. Osero Earn provides the infrastructure to offer the Sky Savings Rate directly to retail customers, without requiring the neobank to build or maintain its own DeFi infrastructure.

### Custodians

|              |                                                                         |
| ------------ | ----------------------------------------------------------------------- |
| **Use case** | Enable institutional clients to earn yield on idle stablecoin holdings. |

Institutional clients often hold significant stablecoin balances in custody without earning yield. Osero Earn allows custodians to offer a yield-bearing option on those balances, backed by a Basel III-inspired capital-protection structure and transparent risk reporting designed to meet institutional clients' expectations.

### Exchanges

|              |                                                                                                          |
| ------------ | -------------------------------------------------------------------------------------------------------- |
| **Use case** | Give users a way to earn on stablecoins when they’re not trading, without moving funds off the exchange. |

Exchanges hold large stablecoin balances for users who aren’t always actively trading. Osero Earn gives those users a way to earn the Sky Savings Rate directly through the exchange, so they don’t need to move their funds elsewhere to find yield. This helps exchanges keep more user assets and activity on the platform.

### Wallets

|              |                                                                                |
| ------------ | ------------------------------------------------------------------------------ |
| **Use case** | Let users earn on the stablecoins they already hold, directly from the wallet. |

Wallets can use Osero Earn to add stablecoin savings directly to their existing product. Users can earn the Sky Savings Rate on the stablecoins they already hold, without leaving their wallet or seeking yield elsewhere. The SDK is designed to work with existing transaction flows, including account abstraction setups.

## Integration requirements

To integrate Osero Earn, a platform needs:

* A TypeScript-capable development environment
* Support for user wallets holding stablecoins on at least one supported network
* The `@osero/client` SDK ([installation guide](/osero-sdk/getting-started/installation.md))

No smart contract deployment, DeFi expertise, or onchain infrastructure management is required from the platform.


---

# 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.osero.com/osero-product/overview/use-cases.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 `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.