Is Hyperliquid good for bots?

What the question comes down to

Hyperliquid has the pieces an automated trader needs: a fully onchain order book, one documented public API, keys that trade without being able to withdraw, and a published fee schedule. It also has rules that do not bend for a program: rate limits earned by trading, liquidation on equity, and funding exchanged every hour.

No verdict follows from that, and this page gives none. Whether it suits your program depends on how often it trades, how much it reads, how large its orders are, and what it does when a read fails.

What makes it workable

• An onchain order book. HyperCore includes fully onchain perpetual futures and spot order books, and every order, cancel, trade and liquidation happens transparently with one-block finality inherited from HyperBFT.
• One API for everything. The same info and exchange endpoints the web interface uses, plus a websocket, with an official Python SDK and community SDKs in Rust and TypeScript.
• Keys that trade and nothing more. Measured on mainnet on 28 September 2026, an approved agent key was refused withdraw3, usdSend, spotSend, sendAsset and usdClassTransfer, and refused to approve a second agent.
• Costs you can price in advance. Perps start at 0.045% taker and 0.015% maker at the base tier, falling with volume and with HYPE staked. Funding is purely peer-to-peer and no fees are collected on it.
• A test venue on the same paths. api.hyperliquid-testnet.xyz, where a program belongs until it stops surprising you.

What to watch

• Rate limits in two currencies. Per IP, REST requests share an aggregated weight of 1200 a minute. Per address, 1 request per 1 USDC traded cumulatively, after an initial buffer of 10000. A program that polls where it could subscribe pays in both.
• Liquidation on equity, not on an opinion. A position is liquidated when the account's equity falls below the maintenance margin, half the initial margin at max leverage: 1.25% to 16.7% by asset. Below two thirds of that without a fill through the book, it goes to the liquidator vault.
• Funding every hour, not every eight. The rate is computed as an 8-hour figure and one eighth of it is exchanged each hour, capped at 4% an hour. A backtest that ignores it measures something else.
• Leverage and order size are bounded per asset. Max leverage varies from 3x to 40x and is an integer. A single market order is capped at 30,000,000 dollars where max leverage is 25 or more, and at 500,000 at the low end.
• Not every market takes cross margin. Some perps take isolated margin only, and a program that always sets its leverage as cross has it refused there: the order never leaves.

What it costs to run one

Both legs pay the venue. At the base tier a perp taker pays 0.045% of the notional and a maker 0.015%. The tiers fall with 14-day volume, from above 5M dollars to above 7B, and staking HYPE cuts the rate again, up to 40% off.

A builder can add at most 0.1% on perps, and only once the user has approved a maximum for that builder address, signed by the user's main wallet and never by an agent wallet.

Funding is the cost a program forgets, because it never appears in a fill: the position size times the oracle price times the rate. At the interest term alone, 0.00125% an hour, 72 hours of it is 0.09% of the notional, as much as two taker legs at the base rate.

Where our own tool sits

Locker Protocol Agentic answers the key question rather than the strategy question. The account's key stays in your wallet, offline in Locker Vault when you choose the safest way; the computer holds only an agent key, sealed under a password and expiring on its own; a local policy is checked twice before an order is signed, under a mandate your wallet signs.