User: "Buy $20 of Bitcoin with 5x leverage"
Agent: [checks balance → sets leverage → places order → reports fill]
Result: "✓ Bought 0.0002 BTC at $95,432 with 5x leverage. Position opened."

User: "Long NVIDIA with $50, 10x"
Agent: [auto-detects NVIDIA = xyz:NVDA → executes → verifies]
Result: "✓ Bought 0.25 NVDA at $198.50 with 10x leverage. Filled at $198.62."

User: "Sell my ETH position"
Agent: [checks position size → closes → reports PnL]
Result: "✓ Sold 0.5 ETH at $3,421. Realized PnL: +$12.50"

• Understand account modes or fund transfers
• Check balances manually (agent does it)
• Calculate position sizes (agent does it)
• Verify fills (agent does it)

1. Check available funds - Use

   hl_total_balance

   before EVERY trade to see total available margin
2. Detect asset type - Recognize if user wants crypto (BTC, ETH, SOL) or stocks/RWA (NVIDIA→xyz:NVDA, TESLA→xyz:TSLA)
3. Set leverage - Always call

   hl_leverage

   before placing orders (unless user specifies not to)
4. Verify fills - After placing ANY order, immediately call

   hl_fills

   to check if it filled
5. Report results - Tell user the outcome: filled price, size, and any PnL
6. Suggest risk management - For leveraged positions, remind users about stop losses or offer to set them

• Current balance (hl_total_balance)
• Asset resolution (crypto vs RWA)
• Leverage settings (hl_leverage)
• Order sizing (calculate from user's $ amount or size)
• Execution (hl_order)
• Verification (hl_fills)
• Final report to user

• ✅ Use

  hl_total_balance

  - shows ACTUAL available margin regardless of account mode
• ❌ Don't use

  hl_account

  for balance - may show $0 even if funds available
• ❌ Don't use

  hl_balances

  for margin - only shows spot tokens

• Don't wait for user to ask "did it fill?" - check automatically
• Don't ask "should I check your balance?" - just do it
• Don't explain account modes - user doesn't care, just execute

1. Known crypto → use plain name:

   "BTC"

   ,

   "ETH"

   ,

   "SOL"

   ,

   "DOGE"

   ,

   "HYPE"

   , etc.
2. Known stock/commodity/forex → use

   xyz:

   prefix:

   "xyz:NVDA"

   ,

   "xyz:TSLA"

   ,

   "xyz:GOLD"

   , etc.
3. Unsure → resolve with tool calls:
   • First try

     hl_market(coin="X")

     — if it returns a price, it's a crypto perp
   • If not found, try

     hl_market(dex="xyz")

     to list all RWA markets and search the results
   • Use whichever returns a match

xyz:NVDA

xyz:TSLA

xyz:AAPL

xyz:MSFT

xyz:AMZN

xyz:GOOG

xyz:META

xyz:TSM

xyz:GOLD

xyz:SILVER

xyz:SPY

xyz:EUR

xyz:GBP

xyz:JPY

If a user says "buy NVDA" or "trade GOLD", use

xyz:NVDA

/

xyz:GOLD

. These are real-world assets, not crypto.

1. Recognize NVIDIA = stock → use

   xyz:NVDA

2. hl_market(coin="xyz:NVDA")

   — Check current price, leverage limits

3. hl_leverage(coin="xyz:NVDA", leverage=3)

   — Set leverage (builder perps use isolated margin)

4. hl_order(coin="xyz:NVDA", side="buy", size=0.5, price=188)

   — Place limit buy

5. hl_fills()

   — Check if filled

• Builder perps (HIP-3) use isolated margin only —

  hl_leverage

  handles this automatically
• The

  dex

  prefix (e.g.

  xyz

  ) identifies which builder deployed the perp
• All tools (candles, orderbook, funding, etc.) work the same way with prefixed names

1. hl_total_balance()

   → Check available funds

2. hl_leverage(coin="BTC", leverage=5)

   → Set leverage

3. hl_order(...)

   → Place order

4. hl_fills()

   → Verify fill and report result

1. Detect asset type → Convert "NVIDIA" to "xyz:NVDA"

2. hl_total_balance()

   → Check available funds

3. hl_leverage(coin="xyz:NVDA", leverage=10)

   → Set leverage

4. hl_order(coin="xyz:NVDA", ...)

   → Place order

5. hl_fills()

   → Verify fill and report result

1. hl_account()

   → Get current position size

2. hl_order(coin="BTC", side="sell", size=X, reduce_only=true)

   → Close position

3. hl_fills()

   → Report PnL

1. hl_total_balance()

   → Check available USDC

2. hl_spot_order(coin="HYPE", side="buy", size=100)

   → Buy tokens

3. hl_balances()

   → Verify purchase

1. Order Placement: Place a dormant trigger order with a trigger price
2. Monitoring: Order sits inactive, watching the market price
3. Trigger: When market price reaches

   trigger_px

   , order activates
4. Execution: Order executes immediately (as market or limit order)

hl_tpsl_order(coin="BTC", side="sell", size=0.1, trigger_px=90000, tpsl="sl")

• trigger_px=90000: Activates when BTC drops to $90k
• side="sell": Closes your long position
• tpsl="sl": Marks this as a stop loss order
• Default: Executes as market order when triggered (instant exit)

hl_tpsl_order(coin="ETH", side="sell", size=1.0, trigger_px=3500, tpsl="tp")

• trigger_px=3500: Activates when ETH rises to $3,500
• side="sell": Closes your long position
• tpsl="tp": Marks this as a take profit order
• Default: Executes as market order when triggered (instant exit)

hl_tpsl_order(
    coin="BTC",
    side="sell",
    size=0.1,
    trigger_px=90000,
    tpsl="sl",
    is_market=false,
    limit_px=89900
)

• trigger_px=90000: Activates at $90k
• is_market=false: Use limit order (not market)
• limit_px=89900: Limit price when triggered ($89,900)

1. Always use

   reduce_only=true

   (default) - ensures TP/SL only closes positions, never opens new ones
2. Match size to position - TP/SL size should equal or be less than your position size
3. Set both TP and SL - protect both upside (take profit) and downside (stop loss)
4. Account for volatility - don't set stops too tight or they'll trigger on normal price swings
5. Check open orders - use

   hl_open_orders

   to verify TP/SL orders are active

• Always check account state before trading — know your margin usage and existing positions
• Set leverage explicitly before opening new positions (default may vary)
• Use reduce_only when closing to avoid accidentally opening the opposite direction
• Monitor funding rates — high positive funding means longs are expensive to hold
• Start with small sizes — Hyperliquid has minimum order sizes per asset (check szDecimals)
• Post-only (ALO) orders save on fees (maker vs taker rates)
• Check fills after market orders — IoC orders may partially fill or not fill at all