> For the complete documentation index, see [llms.txt](https://docs.hyperlink.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperlink.xyz/start/readme.md).

# Introduction

HyperLink is a prime broker for Hyperliquid. You trade through a shared smart contract from inside a secure enclave (TEE), so your balances, positions, and orders stay confidential, while your orders route into Hyperliquid's order book for full liquidity and execution. The goal is to give traders a VIP trading experience on Hyperliquid by pooling economies of scale, without leaving Hyperliquid's markets.

## What you get

| Feature                        | What it means                                                                                                                                                         |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Confidential trading**       | Balances, positions, and orders never touch the public chain. You trade through a shared contract, so only the contract is visible on Hyperliquid, never your wallet. |
| **Hyperliquid-compatible API** | `POST /exchange` mirrors Hyperliquid's API and EIP-712 signing. Point existing Hyperliquid tooling at the HyperLink base URL.                                         |
| **Lowest Hyperliquid fees**    | HyperLink pools volume and staking benefits so users can access the lowest Hyperliquid trading fee rates available to the protocol. See [Fees](/trade/fees.md).       |
| **Provable solvency**          | HyperLink commits reserve data on-chain. You can verify your own backing without revealing anyone's totals.                                                           |
| **Always exitable**            | You can withdraw on-chain even if HyperLink goes offline. Funds are never trapped.                                                                                    |

## How it works

You deposit on-chain, trade confidentially through the shared contract, and withdraw on-chain. Only the two on-chain steps are public.

1. **Deposit (public).** Transfer funds on HyperCore to HyperLink. Your balance is credited once the transfer confirms.
2. **Trade (confidential).** Sign orders client-side. The enclave validates them, then routes them into Hyperliquid through the shared contract. Your activity stays off the public chain.
3. **Withdraw (public).** Request a withdrawal; HyperLink submits it on-chain for you (gasless).

| Confidential (inside the enclave) | Public (on-chain on HyperCore) |
| --------------------------------- | ------------------------------ |
| Balances, positions, open orders  | Deposits                       |
| Order and fill history            | Withdrawals                    |

## Start here

* **Trade in the app:** [Getting Started](/start/getting-started.md), then open [app.hyperlink.xyz](https://app.hyperlink.xyz).
* **Build on the API:** [API Quickstart](/api/setup.md). HyperLink mirrors Hyperliquid's API and signing, so existing tooling works against the HyperLink base URL.
* **Trust model:** [Security](/security/security.md) and [Risks](/security/risks.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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperlink.xyz/start/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.