Set Up OpenClaw to Trade on Hyperliquid

Hyperliquid is where crypto's most active perpetuals traders live, and in early 2026 it became the first venue where an AI agent trading pattern got genuinely productized. Senpi launched personal trading agents "powered by OpenClaw" that users chat with directly through Telegram — the exact shape of stack we host every day. As of July 2026 more than 93,000 people sat on the Senpi Samurai waitlist (@betashop). This guide walks the whole setup: sign up for OpenClaw Direct, approve a Hyperliquid agent wallet that can trade but can't drain you, wire in an MCP, and bolt on the guardrails a leveraged 24/7 market actually demands before a single order fills.

Why a Leveraged 24/7 Market Needs a Hosted Agent

Hyperliquid never closes. It's an onchain perpetual-futures exchange, so its markets reprice every second of every day, funding rates flip overnight, and a position drifts toward liquidation while you sleep. Now add leverage. A perp position that's fine at midnight can be underwater by the time your alarm goes off — and a laptop that went to sleep at 1am watched none of it. This is the pain the whole category exists to solve, and it's why a bot that only runs when your machine is awake is a bot that eventually misses the move that mattered.

That's exactly the gap Senpi found. Its pitch is an agent that "runs your Hyperliquid strategy while you sleep" (@betashop), and the reason it resonates is that a human genuinely cannot babysit a 24/7 leveraged book. But you don't need Senpi's hosted product to get always-on: you need any OpenClaw agent that stays online, plus a place to run it that isn't your personal hardware. So where should that agent actually live?

Not on your laptop. OpenClaw Direct runs every agent on its own dedicated machine, isolated from every other user, with your Hyperliquid agent-wallet key encrypted at rest inside the platform's credential vault instead of a plaintext file next to your browser. The infrastructure holds 99.9% uptime with 24/7 monitoring, so the agent keeps watching a market that also never rests, and you can suspend or terminate it from any browser on any device. For software that signs leveraged trades with real money, that's the right amount of surface area — and the right size of blast radius.

What Is Hyperliquid, and How Do Agents Plug Into It?

Hyperliquid is a high-performance onchain perpetuals exchange — think a fully onchain order book with 200-plus perp markets across crypto, and increasingly stocks and commodities. Unlike a brokerage, there's no OAuth login and no support desk; you interact through signed API requests. For an AI agent, the connection point is an MCP server that exposes Hyperliquid's read and trade actions as tools your agent can call in plain language.

You have three realistic ways to wire it up, from most managed to most hands-on:

• Senpi's MCP toolkit. The most complete agent-native interface to Hyperliquid, with 44-plus trading tools across categories like market scanning, trader discovery, position management, and trailing stops. Its open-source skill library is worth reading even if you build your own — it's a field guide to what a Hyperliquid agent should be able to do.
• HyperLiquid-Claw. A Rust-based MCP skill (the hl-mcp binary) that gives an OpenClaw agent read and trade access to every perp on the DEX. It runs read-only with just your public address, and only asks for a signing key when you actually want it to place orders — a clean way to start safe.
• edkdev/hyperliquid-mcp. A straightforward open-source Hyperliquid MCP server if you'd rather run the plumbing yourself and keep every dependency in view.

Whichever you pick, the pattern is the one we cover in our MCP explainer: one server, a menu of tools, a standard handshake. The agent connects, sees the tools it's allowed to call, and — crucially — shouldn't call any of the trading ones yet.

The Agent Wallet: Hyperliquid's Best Safety Feature

This is the step that makes Hyperliquid structurally safer than a self-custody hot wallet, so read it before you fund anything. Hyperliquid lets you approve an agent wallet (also called an API wallet): a permissioned signer that can place and manage trades on your account but does not hold your funds. Per Hyperliquid's developer docs, "agent wallets are permissioned signers that do not hold funds but can execute Hyperliquid actions for a master account." Your capital stays under the master account you control; withdrawals stay with you.

Contrast that with the Base MCP setup, where the agent holds a real self-custody wallet whose private key controls the coins directly — lose that key and the wallet is drained with no recourse. On Hyperliquid, the worst a compromised agent key can do is trade badly; it can't sign a withdrawal to an attacker's address. That's a meaningfully smaller blast radius, and it's the single best reason to start your onchain agent journey here rather than with a fund-holding hot wallet.

A few properties to internalize. You approve the agent through an ApproveAgent action, and it's revoked automatically when it expires, when you register a new agent with the same name, or when the account runs out of funds. Generate a fresh agent wallet each time rather than reusing an old one — the docs warn that a deregistered agent's nonce state can be pruned, which risks replayed transactions. Revocation is your second kill switch, and it's independent of the platform.

What Can Your Agent Actually Do — and What Should It Not?

Through a Hyperliquid MCP, an agent can read the full market (prices, funding, order books, open positions, PnL) and act on it: place market and limit orders, set leverage, and close positions across 200-plus perps. That's a lot of rope. The read side is close to free and risk-free; the trade side, on a leveraged venue, is where a careless agent turns a bad idea into a liquidation. Respect the gradient.

• Read and analyze. Scan markets, check funding regimes, discover which traders are positioned where, and write a brief. Start — and stay a while — here.
• Low-leverage spot-like perps. A 1x or 2x position on a blue-chip perp behaves closer to spot and is the right first live action.
• High leverage. Hyperliquid allows large multiples. This is the sharpest tool in the box, and the fastest way for an agent to be liquidated by a wick a human would have ignored. Keep it capped low or banned outright while you're learning the agent's behavior.

Onchain, there's no circuit breaker to pause a cascade and no exchange that will reverse a bad fill. The safety skill in the next section exists to keep your agent on the left end of that gradient until you've decided, with evidence, to let it move right.

The Setup, Step by Step

Step One: Sign Up for OpenClaw Direct and Provision Your Instance

Go to openclaw.direct/users/sign_up and create an account. The Advanced plan ($29/month, "Most Popular") is the right starting point for trading workloads — 4 GB of dedicated RAM and unlimited AI models, so you're not rationing calls while your agent watches an around-the-clock market. Every subscription includes free trial credits, enough to wire the whole thing up and watch a few actions before you commit. Create a new Instance, name it something like "HL Agent," and click "Start Provisioning." While it builds, move to Step Two.

Step Two: Fund a Master Account and Approve an Agent Wallet

Fund the Hyperliquid account you'll trade from — this is your master account, and it's the money at risk. Treat the balance as your real circuit breaker: on a venue with no daily loss limit you can rely on, the only hard cap that always holds is the size of the account the agent can reach. Then, from Hyperliquid's API page, approve a new agent wallet. You'll get a signing key that goes into the OpenClaw Direct credential vault, scoped to your Instance and never written to a personal disk. Because that key can trade but not withdraw, funding this account is not the same all-or-nothing decision as loading a self-custody hot wallet — but size it like a stake you'd be annoyed to lose, not one you'd need to rearrange your month over.

Step Three: Wire a Hyperliquid MCP Into Your Instance

With your Instance provisioned, add your chosen Hyperliquid MCP to its server list — Senpi's toolkit, HyperLiquid-Claw, or edkdev's server. Point the agent at the MCP and supply the agent-wallet key from Step Two, or run in read-only mode first with just your public address (both HyperLiquid-Claw and most servers support this). The MCP is model-agnostic, so you're not locked to one provider — use whichever model you already trust. Once connected, your agent can see the Hyperliquid tools it's allowed to call. It just shouldn't call the trading ones yet.

Step Four: Attach a Safety Skill (Don't Skip This)

Wiring the MCP gives your agent the capability to trade. It does not give it the judgment to trade well. Before it signs a single order, attach a small persistent safety skill to your Instance from the Skills card. A sensible Hyperliquid starting set:

• A hard leverage ceiling — start at 1x–2x, and never let the agent set leverage above it.
• A per-trade notional cap and a rolling daily volume cap.
• A coin whitelist — only the markets you actually want traded (e.g. BTC, ETH, SOL), nothing the agent found trending.
• A ban on opening new positions during extreme funding or thin liquidity, plus a minimum-liquidity floor so it won't trade into a market it can't exit.
• A rule to read account balance, open positions, and current leverage before every action, to avoid stacking or over-leveraging.

This lives in a skill, not a chat instruction, because chat instructions vanish when the agent's memory is compacted — persistent rules belong in persistent files. It's the same pattern we cover in how to structure your AGENTS.md: a skill survives every conversation, restart, and model swap. On a leveraged market that never closes, a bad rule left unattended has all night to compound.

Step Five: Start Read-Only, Then Add Approvals

Give your agent a bounded first task that moves nothing. From the OpenClaw Direct dashboard, ask it to read your balances and open positions, pull current Hyperliquid market context and funding, and write a short brief on what it would trade if it were trading. This costs nothing, exercises the MCP end to end, and shows you how the agent reasons before it can act. Run that loop a few times. Sensible briefs are evidence the tools work; nonsense briefs catch a problem before any money moves.

When you graduate to live orders, keep a human in the loop. Wire a Telegram approval on every trade so you get a preview — market, side, size, leverage, estimated entry — with confirm and reject buttons before anything signs. This is the exact interaction Senpi made its headline feature, and it works for the same reason: chatting with your agent is a natural place to catch a bad trade before it fills. Keep the first real order tiny — a small, low-leverage position on a blue-chip perp — then expand into scheduled strategies (see scheduling agent cron jobs) only once the plumbing has earned your trust.

Judge It on Live PnL, Not Backtests

Here's the honest part the waitlist hype skips. The quant crowd on Reddit has a standing complaint that applies directly to every AI trading agent: as u/flybyskyhi put it (276 upvotes), "this subreddit has 50,000 posts of people bragging about their backtests outperforming the medallion fund for every one post displaying live PnL." An impressive simulated result is not evidence your agent will make money on a live, adversarial, leveraged venue. Demand the live log.

So graduate slowly and size down. The most-upvoted advice in that same thread was u/Qorsair's (84 upvotes): "keep your live allocation to 10% of what you're thinking right now." That's the right instinct for a Hyperliquid agent too. Run it read-only until its briefs are consistently sane, then live at a fraction of the size you're tempted by, and let the audit trail — which OpenClaw Direct keeps for every action — be your proof rather than a screenshot of a backtest. For the fuller reckoning of where models actually fall short with money on the line, we wrote what AI still can't do in markets.

What Happens When Something Goes Wrong

Every serious agentic setup has to answer one question: when your agent does something you don't want, how fast can you stop it? On Hyperliquid you have two independent kill switches, which is one more than most setups.

Your fastest is the OpenClaw Direct dashboard: suspend or terminate the Instance from any browser, on any device. Because the agent-wallet key lives in the platform vault rather than on your laptop, killing the Instance means no process can sign a new order. Your second, independent of the platform, is revoking the agent wallet on Hyperliquid itself — deregister it and its signing rights end, no matter what any process tries. And because that agent wallet never held your funds in the first place, even a fully compromised key can't withdraw your balance to an attacker. That layered stop is the structural advantage of trading here.

The harder truth is what a kill switch can't undo. A leveraged position that already opened can still be liquidated in a flash crash before you hit the button, and Hyperliquid has no circuit breaker to buy you time. This is why the leverage ceiling and position caps in your safety skill do the heavy lifting, and why the master-account balance — not the kill switch — is your real limit on the downside. The rule that matters most stays simple: don't fund the account with more than you can lose without rearranging your life.

Where to Go From Here

The plumbing is finally there. The most active perps venue in crypto has multiple ways to let an OpenClaw agent read the market, place trades through a permissioned signer that can't drain you, and check in with you on Telegram before it acts — and it works with whichever model you already trust. Senpi proved traders want this shape of product; the parts are open enough that you can run it yourself on hosting you control, at a fraction of the ceremony. The remaining work — which markets, how much leverage, how to grow trust over time — is the same work any perps trader does, and the right way to build those instincts is small stakes over a few weeks with read-only briefs and Telegram approvals.

All of it depends on an agent that's actually online when the market is — which, onchain, is always — and that keeps its signing key somewhere safer than your laptop. That's why we built OpenClaw Direct: a dedicated Instance for every user, encrypted credential storage, 99.9% uptime, a full audit trail, a dashboard kill switch reachable from any browser, and automatic platform updates so the infrastructure under your agent stays current without you maintaining it. Free trial credits come with every subscription — enough to wire up Hyperliquid end to end and watch your first few reads and orders fire.

---

Sources: The Defiant — Senpi Launches the First Personal Trading Agents for Hyperliquid, Senpi — AI Trading Agents for Hyperliquid (Quickstart), GitHub — Senpi-ai/senpi-skills, HyperLiquid-Claw — MCP trading skill for OpenClaw, GitHub — edkdev/hyperliquid-mcp, Hyperliquid Docs — Nonces and API Wallets, Hyperliquid Docs — Builder Codes, and r/algotrading — live PnL vs backtests thread.