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

# Connect Hyperliquid

Hyperliquid trading is enabled by a short setup you complete once. The order ticket walks you through it: until the session is ready, the ticket's submit button is replaced by whichever step comes next, so you always see the real ticket rather than an empty placeholder.

The steps are:

1. **Sign in.** Connect the wallet you want to trade with.
2. **Add the Hyperliquid account.** This points Wire at your address.
3. **Fund it.** Perpetuals are margined in USDC on Hyperliquid.
4. **Approve the builder fee.** A one-time signature setting a fee ceiling.
5. **Approve the trading session.** A one-time signature enabling order signing.

Steps 4 and 5 are single wallet signatures, not transactions, and neither moves funds.

## Approving the builder fee

Hyperliquid requires you to approve a **maximum builder fee** for Wire's builder address before any order can carry one. This is a **ceiling, not a charge**.

You approve **0.1%**, which is exactly the highest fee Wire ever charges (on spot sells). Perpetuals are charged 0.025%, and spot buys are charged nothing. Hyperliquid enforces the ceiling at the protocol level — Wire cannot charge above it, regardless of what the app does.

The order ticket shows the actual fee for the specific order in front of you, before you place it. See [Fees](/trading/fees.md).

### Revoking it

Approve a new maximum builder fee of **0%** for Wire's builder address — on Hyperliquid directly, or through any third-party interface. That disables trading through Wire until you approve a fee again. Nothing else about your account changes.

## Approving the trading session

Signing every order with your main wallet would mean a wallet popup per order. Instead, Wire generates a **session key** in your browser and you approve it once with your wallet. Orders and cancels are then signed locally, with no popup.

What the session key can and cannot do is set by Hyperliquid, not by Wire:

* It can **place and cancel orders**.
* It **cannot withdraw or transfer funds**. There is no path from this key to moving money out of your account.
* It **expires after 7 days**, after which you approve a new one.

The key is generated in your browser and stored in that browser tab's session storage only. It is never sent to Wire's backend, never logged, and never written to disk. It is cleared when you sign out, when you switch wallets, and when you disconnect the Hyperliquid account.

### Revoking it

Signing out clears this browser's copy of the key, which is the right first move but only half a revocation — it does not withdraw Hyperliquid's approval. To revoke properly, revoke the agent at Hyperliquid. Otherwise the approval lapses on its own at the 7-day expiry.

See [Security](/accounts/security.md) for the fuller picture.

## Funding

Perpetuals are margined in USDC held in your Hyperliquid **perps** account. If your USDC is on another chain, or sitting in your Hyperliquid **spot** account, the setup flow includes the deposit and spot-to-perps transfer steps.

Spot and perps are separate balances on Hyperliquid. Having USDC in one does not make it available to the other.


---

# 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.usewire.xyz/getting-started/hyperliquid.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.