Skip to content
Zunder Guard docs

What Zunder Guard is

Zunder Guard is a risk firewall. It sits between your trading bot (or AI agent) and Hyperliquid. Your bot keeps its logic. It only sends its orders to Guard instead of to Hyperliquid.

Guard checks every order against limits you set. It lets the order through, makes it smaller, or refuses it. Then it signs the order with your API wallet key and sends it to Hyperliquid.

An example

Section titled “An example”

Your bot wants to buy 0.5 BTC at 60,000 with a stop at 58,800. Your account holds 2,000 USDC. Your rule says a stop-out may lose at most 2% of equity.

  • At the stop, 0.5 BTC loses 0.5 × 1,200 = 600 USDC. That is 30% of your equity.
  • Guard resizes the order to 0.03144 BTC, which loses about 40 USDC (2%) at the stop, fees included.
  • Guard sends the smaller order and tells your bot why.

The arithmetic is on Sizing from the stop.

What Guard is

Section titled “What Guard is”
  • A gate for new risk. Every order that opens or grows a position passes nine rules first (The nine rules).
  • A circuit breaker. After a daily loss of 6% (default) it refuses new entries until the next UTC day. After a fall of 25% from the peak it refuses them until a person resumes (Daily loss stop and drawdown halt).
  • A key holder. It holds the API wallet key. Your bot never sees it (API wallets).
  • A record. Every change of risk state goes into an append-only, checksum-chained journal (The journal).
  • Self-hosted. It runs on your machine or your own server. We host nothing that holds a key.

What Guard is not

Section titled “What Guard is not”
  • Not a strategy. It never decides to trade. It only decides how much of what your bot asks for is allowed.
  • Not a profit tool. Guard limits losses you have agreed to. It cannot make a losing strategy win. A stop can still fill beyond its price in a gap.
  • Not custody. Your funds stay in your Hyperliquid account. The API wallet cannot withdraw.
  • Not a guarantee. Guard enforces limits you set, on the orders it sees. Orders sent around Guard (from the Hyperliquid app, or from another key) are not checked.
  • Not exit control. Guard never blocks an order that reduces or closes a position. Exits always pass.

How an order flows

Section titled “How an order flows”

Flowchart: Your bot or agent (signs with a Guard client key) → Zunder Guard (your machine) → 1. Check the client signature and nonce → 2. Nine rules (risk engine + policy) → 3. Re-sign with the API wallet key → Journal append-only → Hyperliquid → Hyperliquid-style error → passed through

The same in text:

bot ──/exchange──▶ Guard: client key ok? ─▶ nine rules ─┬─ allow/resize ─▶ re-sign (API wallet) ─▶ Hyperliquid
                                                        └─ veto ─▶ error back to the bot, with the reason
bot ──/info──────▶ Guard ─▶ Hyperliquid (passed through)

Where to go next

Section titled “Where to go next”