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

# About Hyperbeat

Powered by Hyperliquid, Hyperbeat utilizes smart contracts to automate strategies that generate real and sustainable returns through Meta-Yield vaults, Delta-Neutral strategies, HYPE liquid staking, money-markets and onchain payment rails.\
\
We are early Hyperliquid users turned builders, that believe Hyperliquid represents a ground-breaking shift for onchain finance and is the biggest opportunity since Bitcoin and Ethereum.<br>

What Hyperbeat offers:

* [Liquid banking](/liquid-banking.md), a **modular, permissionless, fully on-chain financial stack**.
* [HYPE liquid staking](https://app.hyperbeat.org/staking/behype) built natively on Hyperliquid, enabling users to stake HYPE and receive [Hyperbeat x Ether.fi HYPE](/hyperbeat-staking/behype.md) (beHYPE) in return.
* [Earn](https://app.hyperbeat.org/vaults), smart-contract vaults generating real and sustainable returns through two types of vaults, [Meta Vaults](/hyperbeat-earn.md) that continuously optimize across HyperEVM and HyperCore. The vaults offer higher base yields through greater capital flexibility, manage risk and simplify the yield experience.
* [Mainnet validator node](/hyperbeat-staking.md), originally launched as a early testnet validator, today operating on mainnet in collaboration with P2P.org with [institutional staking support](/hyperbeat-staking/staking-api.md).


---

# 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 dynamically 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/readme.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 `build a script that syncs our docs to a CMS` 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.