Hyperliquid

This is a reference for the verification API’s payload adapter. For apps you can use inside a Desk, see Desk apps.

venue: hyperliquid. Over HTTP, hl and names starting with hyperliquid (such as Hyperliquid perps) also resolve to it.

What to send

The action you are about to post to Hyperliquid’s /exchange endpoint: either the bare action {type, ...} or the full signed request {action: {type, ...}, nonce, signature}. It is detected without venue when type is one of the values below or the object has an orders array. actionType is the action’s type.

`actionFamily`	`type`
`order`	`order`, `modify`, `batchModify`, `cancel`, `cancelByCloid`, `scheduleCancel`, `twapOrder`, `twapCancel`
`margin`	`updateLeverage`, `updateIsolatedMargin`
`withdrawal`	`withdraw3`
`transfer`	`usdSend`, `spotSend`, `usdClassTransfer`
`staking`	`tokenDelegate`, `cDeposit`, `cWithdraw`
`vault`	`vaultTransfer`, `createVault`
`subaccount`	`subAccountTransfer`, `subAccountSpotTransfer`, `createSubAccount`
`permission`	`approveAgent`, `approveBuilderFee`

Any other type is classified unknown when venue is set.

What the classifier renders

Orders: side from b (true is buy or long, false is sell or short), the asset named from index a, size s, price p, time in force or trigger from t, reduce-only from r, and notional as p × s.
Withdrawals and transfers: amount and destination.
Staking: validator and amount, and whether it undelegates.
Vault actions: vault address, deposit or withdrawal, and amount.

It adds a note when an order has no numeric a or no boolean b.

No live lookup

Asset indices resolve against a copy of Hyperliquid’s perp universe (the meta info response, 230 assets) fetched on 2026-07-02. Perps listed after that date and spot assets show as asset #N. The brief tells the judge to treat an unresolved asset as unverified and lean ESCALATE.

Venue facts the judge is given

Prices and sizes are decimal strings. There is no notional field; notional is p × s, and leverage does not change it.
withdraw3 leaves Hyperliquid for Arbitrum through the bridge with a 1 USDC fee. usdSend and spotSend move funds to another Hyperliquid address instantly. A mandate that forbids withdrawals is read as covering both unless it says otherwise.
Delegations have a 1-day lockup and unstaking takes 7 days. User vaults have a 1-day withdrawal lockup, HLP 4 days.
An action carrying vaultAddress acts on a vault or subaccount, not the main account.
approveAgent lets an agent wallet sign every future trading action for the account.

Example

const action = {
  type: "order",
  orders: [{ a: 3, b: false, p: "2.1", s: "5000", r: false, t: { limit: { tif: "Gtc" } } }],
  grouping: "na",
};

const res = await fetch("https://harness.chance.cc/api/v1/intent", {
  method: "POST",
  headers: { "x-api-key": process.env.CHANCE_API_KEY!, "Content-Type": "application/json" },
  body: JSON.stringify({
    intent: "Trend-follow BTC and ETH only. Longs only. Max 3x leverage. Max $500 notional per position.",
    venue: "hyperliquid",
    action,
  }),
});
const result = await res.json();
if (result.verdict !== "ALLOW") throw new Error(result.reasoning ?? result.error);
// Only now sign the action and post it to /exchange.

The judge receives this summary, which breaks the mandate on asset, direction and size:

Hyperliquid order: 1 order(s)
  1. SELL/SHORT MATIC-PERP, size 5000 @ 2.1 (limit (Gtc)) ≈ $10,500 notional

From an MCP client

Instruct the agent to call verify_intent before any Hyperliquid action, with your rules as intent, the exact action object as action and venue: "hyperliquid", and to act only on ALLOW.

Integrate

Chance verification

Payload adapters

HTTP endpoints

What to send

What the classifier renders

No live lookup

Venue facts the judge is given

Example

From an MCP client

​What to send

​What the classifier renders

​No live lookup

​Venue facts the judge is given

​Example

​From an MCP client

What to send

What the classifier renders

No live lookup

Venue facts the judge is given

Example

From an MCP client