> For the complete documentation index, see [llms.txt](https://docs.hyperbeat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperbeat.org/hyperbeat-earn/usd+/usd+-builder-codes.md).

# USD+ Builder Codes

USD+ is Hyperbeat's dollar vault, built to deliver the best risk-adjusted yield in the Hyperliquid ecosystem. Builder Codes let any frontend offer it natively: your traders earn on idle USDC without leaving your app, and you receive 50% of the fees their deposits generate.

#### Built for trading frontends

Traders hold idle USDC between positions. Add an Earn tab next to Trade and that balance earns yield inside your product. The integration is one contract call to deposit, one to withdraw, and a public API for everything you display.

<figure><img src="https://721067793-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fsp6RnXDjniKct5WCnbtk%2Fuploads%2FXu8JJI2n9rEjRqMzI2G3%2Fusd-plus-architecture.svg?alt=media&#x26;token=6be824e3-8ad5-411c-870c-e71ed1bde477" alt=""><figcaption></figcaption></figure>

#### Why USD+

| Property              | What it means for your traders                                                                            |
| --------------------- | --------------------------------------------------------------------------------------------------------- |
| Risk-adjusted yield   | Yield comes from overcollateralised lending, not from directional or leveraged positions.                 |
| Diversified           | Allocated by risk limits across Morpho markets, HyperLend and HyperCore Earn. Live allocation in the API. |
| Dollar in, dollar out | Deposit USDC, USDT0 or beatUSD. Positions are valued and paid out in USDC.                                |
| Liquid                | Queued withdrawals are processed programmatically, typically within 10 minutes.                           |
| Transparent           | Every allocation and its yield is public through the API.                                                 |

#### How it works

{% stepper %}
{% step %}
**Your app calls the Depositor contract** with the user's amount and your builder code. The user receives USD+ shares.
{% endstep %}

{% step %}
**The contract records your code** in the `Deposit` event. The API returns it on every deposit.
{% endstep %}

{% step %}
**Hyperbeat pays you** 50% of the fees earned on the balance attributed to your code.
{% endstep %}
{% endstepper %}

#### What you build

| Task                        | How                                                      | Guide               |
| --------------------------- | -------------------------------------------------------- | ------------------- |
| Deposit                     | One contract call, with your builder code                | **Deposits**        |
| Deposit from HyperCore      | One signature to move USDC to HyperEVM, then the deposit | **Deposits**        |
| Build with an AI assistant  | One file with the full integration context               | **llms.txt**        |
| Withdraw                    | One contract call to the withdrawal queue                | **Withdrawals**     |
| Show APY, balances, history | Public REST API, no key                                  | **API reference**   |
| Track what you earned       | On-chain events, plus a rewards endpoint                 | **Builder rewards** |

#### Fee share

You receive 50% of the performance fee earned on balances attributed to your code. For $10,000,000 of deposits from your traders, held for one year at the current gross rate:

|                      |                    |
| -------------------- | -----------------: |
| Attributed balance   |        $10,000,000 |
| Gross yield at 5.61% |           $560,550 |
| Performance fee (5%) |            $28,027 |
| **Your share (50%)** | **$14,013 a year** |

The share comes out of the vault's fee. Your users earn the same net rate as on any other frontend.


---

# 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.hyperbeat.org/hyperbeat-earn/usd+/usd+-builder-codes.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.
