Hyperliquid

Category: Trading

Hyperliquid perpetuals are exposed through the governed action catalog under provider hyperliquid. Orders are signed by an off-chain API wallet (venue signer), not by ERC-7710 Gator grants.

Credential model

Discovery

curl "https://api.thirdfy.com/api/v1/agent/actions/catalog"

Use it

Ask your agent:

Using Thirdfy, check whether my agent is ready to trade on Hyperliquid and show the top of the ETH order book. Do not place any order.

Check the venue. Readiness reports funding, credentials, approvals and the blockers that stop an order.

getVenueReadiness { venue: "hyperliquid", agentKey: "0x<your agent key>" }

thirdfy-agent venue readiness hyperliquid --json

Trimmed result from a real read on 2026-10-08, for a wallet with no Hyperliquid margin yet:

{
  "venue": "hyperliquid",
  "ready": false,
  "fundingReady": false,
  "credentialsReady": true,
  "approvalsReady": true,
  "nextAction": "HYPERLIQUID_DEPOSIT_REQUIRED",
  "minimumDepositUsd": 5,
  "blockingReasons": ["HYPERLIQUID_DEPOSIT_REQUIRED"]
}

ready is true only when blockingReasons is empty. Fix each blocker before you place an order. setupStatus in the same reply carries the account value and warnings.

One read. The L2 book takes a perps symbol in coin:

agentRun { action: "get_hyperliquid_l2_book", params: { coin: "ETH" } }

thirdfy-agent run --action get_hyperliquid_l2_book --provider hyperliquid --params '{"coin":"ETH"}' --json

curl -s -X POST https://mcp.thirdfy.com/tool/agentRun \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $AGENT_API_KEY" \
  -d '{"action":"get_hyperliquid_l2_book","params":{"coin":"ETH"}}'

Trimmed result from a real read on 2026-10-08:

{
  "success": true,
  "book": {
    "coin": "ETH",
    "time": 1791471246296,
    "levels": [
      [{ "px": "2528.5", "sz": "207.8095", "n": 31 }, { "px": "2528.4", "sz": "49.2424", "n": 10 }],
      [{ "px": "2528.6", "sz": "17.6952", "n": 3 }, { "px": "2528.7", "sz": "50.5769", "n": 3 }]
    ]
  }
}

What to check: levels[0] is bids and levels[1] is asks, best price first. px and sz are strings. time is in milliseconds; skip a stale book.

One write. A limit order on the perps book:

agentRun { action: "place_hyperliquid_perps_order", params: { coin: "ETH", isBuy: true, size: 0.01, limitPx: 2400, orderType: "limit" } }

thirdfy-agent run --action place_hyperliquid_perps_order --provider hyperliquid --run-mode agent_wallet --params '{"coin":"ETH","isBuy":true,"size":0.01,"limitPx":2400,"orderType":"limit"}' --estimated-amount-usd 24 --confirm-writes --json

isBuy: true opens or adds to a long. size is in contracts and limitPx in USD. orderType is limit or market. Run thirdfy-agent preflight with the same flags to check the params before you send it.

Readiness checklist

• Trading wallet holds at least 5 USDC on a supported source chain, or perps margin is already funded.
• Onboarding complete (complete_hyperliquid_onboarding or setup/status actions). Follow nextAction from get_hyperliquid_funding_status. When that write is deposit_hyperliquid_cctp, pass sourceChainId (no default) and quote first with quote_hyperliquid_cctp_deposit.
• Builder fee approval only when builder monetization is active. Unfunded builder config returns HYPERLIQUID_BUILDER_WALLET_UNFUNDED and orders proceed without builder attachment.
  • Active monetization: get_hyperliquid_onboarding_plan includes approve_hyperliquid_builder_fee, and setup status shows builder.enabled: true. An order that fails with HYPERLIQUID_BUILDER_APPROVAL_REQUIRED needs that approval from the main wallet.
  • Unfunded builder treasury: get_hyperliquid_setup_status can return ready: true with the warning, get_hyperliquid_builder_fee_status returns monetizationEnabled: false, and place_hyperliquid_perps_order needs no builder approval.
  • Re-run get_hyperliquid_setup_status after funding, API wallet approval and any builder step.
• Preflight and delegationStatus (or agentWalletBootstrap) before live writes.
• Amount and coin allowlists enforced by venue policy (allowedCoins, max notional).

Execution lanes

MetaMask/Gator delegation protects EVM calldata paths. It is not the signing authority for Hyperliquid order / cancel calls.

MCP sequence (summary)

1. getProviderActions { provider: "hyperliquid" }
2. Discovery / L2 / user state reads
3. get_hyperliquid_funding_status, then the write named by nextAction
4. Orders via walletExecute or executeIntent with chosen runMode

See Thirdfy MCP for the full recommended sequence.

Hosted deploy

Hyperliquid perps templates are on EarnOrg (earnorg.com). EarnOrg hosts. Thirdfy governs execution.

Related

• Trading category
• Venue matrix
• Delegation and protection
• Agent CLI