> 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-builder-codes.md).

# 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** (Ultra HYPE, Ultra UBTC, lstHYPE and USD+)
* **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
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-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.
