> 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-staking/staking-api.md).

# Staking API

<figure><img src="https://721067793-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fsp6RnXDjniKct5WCnbtk%2Fuploads%2FHe0R7KwJmMHTGH10gweo%2FStaking%20API%20Banner.png?alt=media&amp;token=9d000479-be8a-4ad5-9859-afbd03558cce" alt=""><figcaption></figcaption></figure>

Hyperbeat offers institutional clients a robust HYPE staking product via its validator on Hyperliquid, powered by the P2P.org Staking API. Built for funds, custodians, and fintechs, this solution delivers secure, scalable staking infrastructure without the constraints of frontend integrations.

**Already the most robust and widely used institutional staking solution supporting billions of dollars of institutional stake**, **now on Hyperliquid.**

## Key Benefits

1. Seamless Backend Integration and fast integration speed&#x20;

Stake HYPE programmatically using the Staking API — ideal for exchanges, fintech platforms, and custodians. Full UX & brand ownership — We manage the backend; you own the frontend, the customer relationship, and the value capture.

2. Revenue share

Powered by [Hyperbeat Builder Codes](https://docs.hyperbeat.org/hyperbeat-builder-codes). Integrators programatically earn revenue share on stake routed through the API.

3. Liquid Stake HYPE

Liquid stake HYPE directly via the staking API. Purpose built to be compliant with institutional grad custodial support, the integration handles all reporting and data flows on your behalf. Speed of execution and agility, on demand.

4. Institutional-Grade Performance - proven to handle billions of dollars of stake.

Built on P2P.org’s globally ranked validator infrastructure with industry-leading uptime, performance, and responsiveness.

5. Dedicated Support

Priority integration and support channel for onboarding, custom validator requests, and technical troubleshooting.

6. On-chain incentives

Earn Hyperbeat Hearts, Hypio Points (Hyperliquid’s leading NFT ecosystem), and future airdrops for staking HYPE via the API.

**Integration Architecture**

Clients connect directly to Hyperbeat’s validator node through P2P.org’s Staking API:

* Programmatic initiation of staking flows
* Real-time validator performance and status endpoints
* Withdrawal request support
* Secure handling of validator keys<br>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfZqWbolPjCLrkNXLpEeAS6KQyk8lkBMRq6kZlwj3OyTz5LTwUaIyXSZqDzpAtKw4USSoXW3qbcrwR3o-OnZjlo5PLiJQLDKlP_kh0Qyf-5akqB3AjDxeeA_XpX8wpqse51cLq7WA?key=abx1B7LaswEuGWjF-4RNKQ" alt=""><figcaption></figcaption></figure>

Get started

For onboarding, validator configuration, and custom deployments: <institutional@hyperbeat.org>

<br>


---

# 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-staking/staking-api.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.