> 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/why-build-hyperlink.md). # Why Build HyperLink Why HyperLink is building the prime brokerage layer for Hyperliquid: pooled volume for lower fees, private execution, and a familiar API for serious trading teams. HyperLink is building the prime brokerage layer for Hyperliquid. We started with a private trading gateway for algorithmic traders because that is where the need is clearest. Serious teams want Hyperliquid's liquidity, speed, API, and lowest protocol-available fees without broadcasting wallet-linked strategy, inventory, and execution flow. Prime brokers give clients economies of scale by pooling activity to win lower fees than any single account could. HyperLink brings that to Hyperliquid, aggregating volume and HYPE staking across users to reach the lowest fee rates available to the protocol. The broader goal is a Hyperliquid-native VIP trading experience: familiar API access, self-custodied exits, and infrastructure built by traders, for traders. For users, HyperLink makes Hyperliquid feel like a professional venue. For the ecosystem, it helps bring more serious flow on-chain without leaving Hyperliquid's markets. --- # 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.hyperlink.xyz/start/why-build-hyperlink.md?ask=&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.