# Hyperbeat Builder Codes

**Builder Codes** allow developers to earn fee revenue by building on top of the Hyperbeat ecosystem—across vaults, liquid staking, and vanilla staking—while leveraging the **Hyperfolio API** for real-time portfolio tracking and data integration.

Builders can route user activity into:

* **Vaults** (HYPE, USDT, BTC, wVLP, dnHYPE and XAUt)
* **Liquid staking** (e.g. beHYPE minting)
* **Vanilla staking** (Direct delegation to the Hyperbeat validator)

Every eligible transaction can include a Builder Code, enabling transparent attribution and revenue sharing. Combined with the Hyperfolio API, builders can create custom frontends, bots, dashboards, and structured products—while tracking user balances, rewards, and performance. This is how you build on yield—and get paid for it.

## How to get started <a href="#how-to-get-started" id="how-to-get-started"></a>

To get started, you’ll need to register a builder address with Hyperbeat:

1. Apply by [filling in this form](https://docs.google.com/forms/d/e/1FAIpQLSd0UdtBSwnweUCFJnuXDe1UoX_ho6jAutdK-6eiTXhJemCBUQ/viewform)
2. Once approved, your builder address will be whitelisted and you’ll be eligible for fee revenue.
3. Start building

### &#x20; <a href="#how-to-get-started" id="how-to-get-started"></a>


---

# Agent Instructions: 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:

```
GET https://docs.hyperbeat.org/hyperbeat-builder-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
