/exchange action payload your agent is about to send and the harness will deterministically classify it, judge it against your mandate with Hyperliquid’s own documentation in the loop, and return a signed verdict whose requestHash binds to those exact bytes.
What gets recognized
Every exchange-endpoint action type is classified into a family:
For orders, the classifier resolves asset indices against a snapshot of the perp universe, decodes side/tif/reduce-only, and computes notional — so the judge reasons over
SELL/SHORT MATIC-PERP, size 5000 @ 2.1 ≈ $10,500 notional, not over {"a":3,"b":false,…}.
Use it from your bot
Wrap the call you were already going to make:venue is optional — Hyperliquid payload shapes are auto-detected — but passing it is good hygiene. Freeform action strings still work and are judged semantically (mode: "semantic").
Use it from Claude or ChatGPT
Add the hosted connector (https://harness.chance.cc/api/mcp, see Connectors) and give your agent one standing instruction:
Before executing any Hyperliquid action, callAgents with Hyperliquid execution tools then get gated automatically; agents without them still give you provable pre-trade checks in chat.verify_intentwith my rules as the intent and the exact API payload as the action, withvenue: "hyperliquid". Only proceed on ALLOW; on BLOCK or ESCALATE, stop and tell me why.
How the harness knows Hyperliquid
The judge works from a versioned snapshot of Hyperliquid’s own docs (exchange endpoint, orders, margining, fees and funding, staking, vaults, transfers and withdrawals — ingested from HL’s published markdown), plus a curated brief of common footguns (asset-index confusion,b side semantics, string-typed prices, lockup windows, the privilege weight of approveAgent). Docs are never fetched at verdict time: the snapshot is reviewed like code, its version is hashed into every transcript, and each page the judge consults is recorded as a chained agent.doc event — the receipt proves exactly which knowledge informed the verdict. See Architecture for the full picture.
What the receipt adds for Hyperliquid
On top of the standard proof bundle (transcript root, judge signature, onchain anchor), venue-aware verdicts carryvenue: "hyperliquid", the actionFamily, the venue actionType, mode: "structured", and the knowledge-snapshot version — all inside the hash-chained transcript.
Roadmap: escrowed execution via Hyperliquid API wallets — same contract, but an ALLOW triggers submission by a Chance-held agent wallet and a BLOCK physically never reaches a signer. The payload-first contract above is forward-compatible with it.
