Three ways to run a Hyperliquid bot: your own Python script on the official SDK with an API wallet that can trade but not withdraw, an open-source GitHub bot such as Hummingbot or Freqtrade, or a Telegram or hosted bot that adds its own fee.
Every route trades from a funded Hyperliquid account. Join with HOLYGRAIL before the first deposit: 4% off fees on your first $25M, including what your bot trades from that main account.
API wallets cannot deposit, and bot libraries such as CCXT try to set their own referral code on an account that has none; no code can be added after $10,000 of volume. We earn a commission on referred accounts' fees; it never raises yours.
Orders and cancels cost no gas, so a bot's real limits are fees and the API rate budget (limits).
What each route costs, a working Python grid with a dead man's switch, the GitHub bots worth reading (and the fake ones to avoid), Telegram bot custody, and the rate limits every Hyperliquid bot lives under.
— Rewritten around the three ways to run a Hyperliquid trading bot: a Python quickstart with a fill-driven grid loop, open-source GitHub bots with their licences and default referral or builder settings, a warning about fake bot repositories, and Telegram bot custody. Rate limits re-checked against Hyperliquid's API docs.
Three ways to run a Hyperliquid trading bot
Route
What you use
What it costs
Who holds the key
Good for
Your own Python bot
Official SDK (0.24.0) + an API wallet
Hyperliquid fees only
You (API wallet trades, cannot withdraw)
Grids, DCA, market making, anything custom
Open-source bot from GitHub
Hummingbot, Freqtrade, passivbot on your server
Hyperliquid fees; some libraries add a small builder fee
You
Proven strategies without writing the exchange code
Telegram or hosted bot
PvP, Hypurr Fun, Dextrabot
Hyperliquid fees + the bot's own fee
The bot provider or a key vault, unless you link an API wallet
No code, phone-first trading
Hyperliquid itself listed 179 perp markets at the last site build and traded $6.15B of perps in 24 hours (as of November 3, 2026), on a fully on-chain order book where orders and cancels cost no gas. That makes it the busiest venue for bots among the perp DEXs, and the reason the cheap route (your own code) is also the most common one. For the API itself (endpoints, signing, first order) read our Hyperliquid API guide; this page is about running a bot on top of it. Comparing venues first? Perp DEX APIs for trading bots compared.
Hyperliquid trading bot in Python: setup and code
Open and fund the main account.Join Hyperliquid with HOLYGRAIL, deposit at least 5 USDC of USDC (smaller deposits can be lost), and trade once from the app. The minimum order is $10 of notional on perps. Testnet first? The testnet faucet needs a mainnet deposit from the same address, so the mainnet account comes first either way (Hyperliquid testnet guide).
Optional: a sub-account for the bot (More → Sub-Accounts). Sub-accounts unlock after $100,000 of volume (10 at first). They share your fee tier and count as separate users for rate limits, but referral discounts do not apply to them. See sub-accounts explained.
Create an API wallet (More → API). "API wallets (also known as agent wallets) can perform actions on behalf of an account without having withdrawal permissions." You get 1 unnamed and 3 named API wallets per account plus 2 named per sub-account, each valid for up to 180 days. How to store and rotate the key: API wallet security.
Install the SDK:pip install hyperliquid-python-sdk (version 0.24.0, MIT licence, Python 3.9+). Its examples/ folder has a script for each building block: basic_order.py, basic_agent.py, basic_schedule_cancel.py, basic_ws.py.
One detail trips up most first bots: the API wallet only signs. To read balances and orders you query the real account address; querying the API wallet's address returns an empty account.
A post-only grid with a dead man's switch (Python)
This places five buy and five sell ALO (add-liquidity-only, i.e. post-only) orders on ETH, 0.5% apart, in one batched action, then arms a cancel-all 60 seconds ahead. ETH sizes have 4 decimals and prices at most 5 significant figures, so near ETH's $2,442 mark on October 22, 2026, prices move in $0.1 steps and 0.01 ETH (about $24) clears the minimum.
import os, time
import eth_account
from hyperliquid.exchange import Exchange
from hyperliquid.info import Info
from hyperliquid.utils import constants
ACCOUNT = os.environ["HL_ACCOUNT_ADDRESS"] # main account address
SUB = os.environ.get("HL_SUB_ACCOUNT") # optional: the bot's sub-account
TRADER = SUB or ACCOUNT # the account the orders land in (for reads)
agent = eth_account.Account.from_key(os.environ["HL_API_WALLET_KEY"]) # cannot withdraw
info = Info(constants.MAINNET_API_URL, skip_ws=True)
ex = Exchange(agent, constants.MAINNET_API_URL, account_address=ACCOUNT, vault_address=SUB)
COIN, LEVELS, STEP, SIZE = "ETH", 5, 0.005, 0.01
mid = float(info.all_mids()[COIN])
orders = []
for i in range(1, LEVELS + 1):
for is_buy, sign in ((True, -1), (False, 1)):
px = round(mid * (1 + sign * STEP * i), 1)
orders.append(dict(coin=COIN, is_buy=is_buy, sz=SIZE, limit_px=px,
order_type=dict(limit=dict(tif="Alo")), reduce_only=False))
print(ex.bulk_orders(orders)) # one action, 10 orders
ex.schedule_cancel(int(time.time() * 1000) + 60_000) # cancel all in 60 s unless re-armed
The part that makes it a bot is the loop that reacts to fills. This one listens to your fills over the SDK's WebSocket and puts the opposite order one step away, so each filled buy becomes a sell above it and the reverse:
STATE = dict(seen=set())
def on_fills(msg):
data = msg["data"]
if data.get("isSnapshot"): # first message replays recent fills
return
for fill in data["fills"]:
if fill["coin"] != COIN or fill["tid"] in STATE["seen"]:
continue
STATE["seen"].add(fill["tid"])
px, sz = float(fill["px"]), float(fill["sz"])
bought = fill["side"] == "B"
new_px = round(px * (1 + STEP) if bought else px * (1 - STEP), 1)
ex.order(COIN, not bought, sz, new_px, dict(limit=dict(tif="Alo")))
ws_info = Info(constants.MAINNET_API_URL) # opens the WebSocket
ws_info.subscribe(dict(type="userFills", user=TRADER), on_fills)
while True: # keep the dead man's switch armed; each re-arm is one action
ex.schedule_cancel(int(time.time() * 1000) + 300_000) # cancel all in 5 min unless re-armed
time.sleep(240)
What it still lacks before real money: a maximum position, a stop bound outside the range that flattens with a reduce-only order, reconnect logic, and handling for "Post only order would have immediately matched" (re-quote one tick away). schedule_cancel must be at least 5 seconds ahead and can fire at most 10 times a day (reset at 00:00 UTC); every re-arm is an action against your address budget, which is why the loop re-arms every 4 minutes rather than every few seconds. The SDK has no TWAP or trailing-stop helper (0.24.0, checked October 22, 2026); those actions are built by hand, as in our TWAP API example. Code is an illustration, not production software.
Hyperliquid trading bots on GitHub
If you would rather run proven code than write your own, these are the open-source projects people searching "hyperliquid trading bot github" usually end up with. We read each repository and its docs on October 22, 2026; none is an endorsement, and we have run none of them with money.
Project
Licence
What it does on Hyperliquid
Watch for
Hummingbot
Apache-2.0
Market-making framework with Hyperliquid spot and perp connectors and grid controllers (grid_strike)
Its docs say the client tags orders with a builder code for attribution without a fee; its docs ask users to join through Hummingbot's own Hyperliquid referral link
Freqtrade
GPL-3.0
Strategy/backtesting bot; README lists Hyperliquid for spot and futures; uses CCXT
Inherits CCXT's defaults (below); its docs say to use the API-wallet key with the main walletAddress and warn about supply-chain attacks
CCXT
MIT
Library behind many bots (Python, JS, PHP); Hyperliquid is a listed exchange
Once it has your credentials it tries to set referral code CCXT1 and to approve and charge a 0.01% builder fee; options switch the code and the fee off
passivbot
Unlicense
Perp grid / trailing "contrarian market maker" for several venues incl. Hyperliquid
Its README links a Hyperliquid referral of its own
chainstacklabs/hyperliquid-trading-bot
Apache-2.0
Small Python grid bot on hyperliquid-python-sdk 0.24.0, testnet by default
Good to read before writing your own
OctoBot
GPL-3.0
Grid / DCA / TradingView bot
Hyperliquid spot only
Builder fees and referral codes in bot code. Open-source bots are free, but some earn from your volume the same way apps do. CCXT, the library under Freqtrade and many custom bots, acts as soon as it has your credentials (when it loads markets or sends its first order): it sends a setReferrer with the code CCXT1 (errors are ignored, so an account that already has a code keeps it) and approves a 0.01% builder fee for its own builder address, which it then adds to every order. Builder approvals must be signed by the main wallet, so with an API-wallet key the approval fails and CCXT sends orders without a builder. refSet: true skips the referral call; builderFee: false removes the fee, although CCXT still approves its builder at 0% and tags orders with it. Hummingbot's docs say its client tags orders for attribution only. A referral code is set once per account, so add HOLYGRAIL (how the referral code works) before you connect any bot.
Fake bot repos. Searching GitHub for "hyperliquid grid" on October 22, 2026 returned two repositories with keyword-stuffed descriptions that run hidden code as soon as the folder is opened in VS Code. We read them through GitHub's API and did not run them; we do not name or link them. Before you open any bot repo, check for .vscode/tasks.json with "runOn": "folderOpen", install scripts in package.json and base64 strings in config files, and never put a main wallet key in a bot you have not read.
Hyperliquid grid bot: fee math and failure modes
A grid rests buy limits below the price and sell limits above it, one per level. When a buy fills it re-quotes a sell one level higher, and the reverse; each buy-then-sell is a cycle that earns the spacing times the level's notional. It is a bet that price oscillates inside the range. Hyperliquid has no native grid UI: you run it through the API (the code above), an open-source bot or a hosted grid bot. Orders and cancels cost no gas; the costs are fees, funding on held inventory and the address rate limit.
How the two legs of a cycle fill
Cost per cycle (% of level notional)
Both legs post-only (ALO), tier 0
0.03%
Both legs ALO + referral code (4% off)
0.0288%
Both legs ALO + referral + Bronze staking (10% off)
0.0259%
One leg taker (a sloppy re-quote)
0.06%
Both legs taker (market orders)
0.09%
Grid spacing
Net per cycle after maker-maker fees
Share of gross profit kept
0.1%
0.07%
70%
0.2%
0.17%
85%
0.5%
0.47%
94%
1%
0.97%
97%
Tier-0 fees from Hyperliquid's schedule; a referral code and HYPE staking lower them, volume tiers lower them further. Every grid order should be Alo: if it would cross, it is rejected instead of paying the taker fee.
Worked example. $10,000 in a neutral ETH grid, range ±5%, 20 levels, so spacing ≈ 0.5% and $500 per level. One cycle earns $2.50 gross, pays $0.15 in maker fees and nets $2.35. Ten cycles in a day net $23.50, about 0.24% of capital before funding; zero cycles because price walked out of the range earn nothing and leave you holding inventory. Each order needs at least $10, so a small account cannot be split into a hundred levels.
Breakout and inventory. If price falls through the bottom of a neutral grid, every buy has filled and no sell will: in the example, $5,000 of ETH bought on the way down, now underwater. Set a stop bound just outside the range that cancels the ladder and flattens the position.
Leverage. Size on the fully filled side, not on the per-level margin. With 5x per level a full buy side is $25,000 of ETH against $10,000 of equity: by Hyperliquid's liquidation formula (ETH maintenance margin 2%) liquidation sits about 39% below the average entry. At 10x it is $50,000 and about 18%, a move ETH has made within a week many times.
Funding bleed. $5,000 of long inventory pays $1.50 a day at the baseline rate, comparable to a day of cycle fees, and several times that when longs are crowded.
Dead bot, live orders. Re-arm schedule_cancel on every loop so a crash cancels the ladder.
Range set by hope. Derive the range from recent realised volatility plus a buffer, not round numbers.
No code? Hosted grid bots connect through an API wallet you approve and charge a builder fee on top of Hyperliquid's: Dextrabot lists 0.01% per trade for its Hyperliquid grid bot, 2 to 36 grids (even numbers) in cross margin only. Aster's order-book perps have a native futures grid with 0% maker fees, and Lighter Standard charges 0% maker and 0% taker but has no grid, so you still need a bot (Lighter grid bot).
Hyperliquid Telegram bots and hosted bots: who holds the key
Telegram bots trade Hyperliquid from a chat. What separates them is where the trading key lives. From their own documentation, read October 22, 2026:
PvP (pvp.trade). Creates a wallet per user whose private key "is stored and encrypted by Turnkey" and can be exported; an existing Hyperliquid account can be linked with an API key instead. Its fee table starts at 0.025%–0.04% on perps at level 1, and the first deposit must be at least 10 USDC. PvP also owns the Hyperdash terminal (Hyperdash review).
Hypurr Fun. The bot creates a personal wallet with an exportable private key, or you import a key or link an API wallet. Its docs list a 1% fee on trades in its Hpump launchpad market and no fee for ordinary HyperCore trades.
Copy and grid platforms (Dextrabot, copy apps): API wallet you approve plus a builder fee; Dextrabot's copy trading is 0.055% per trade. More in Hyperliquid copy trading.
Two things to know before you use one. A wallet the bot creates is a new Hyperliquid account: it starts without your referral code and with whatever code the bot sets, and its key sits with the provider's key vault, however well protected. Linking an API wallet to an account you already hold keeps withdrawals with your own wallet. Neither bot documents which builder or referral code its orders carry; check the fee line on your fills.
The order form on Hyperliquid has three tabs, Market, Limit and Pro. The Pro menu holds TWAP, Chase, Scale, Stop Limit, Stop Market, Take Limit, Take Market and Trailing Stop. For many people who search for a "bot", these are enough:
Order type
What it automates
Good for
Via API?
TWAP
Splits a large order into suborders at intervals of 30 seconds or longer, for 5 minutes to 7 days; optional Randomize, trigger price and max/min price
Building or exiting a position without moving the book
Yes (twapOrder; trigger and max/min price are app-only; no Python SDK helper)
Scale
Lays a ladder of limit orders between a start and end price (Total Orders, Size Skew)
Laddering entries or take-profits
Build it yourself with bulk orders
Chase
A post-only (ALO) limit that re-prices one tick inside the best bid or ask, up to a Max Chase Distance
Getting maker fills without watching the screen
No: runs in your browser tab (max 5 active)
Trailing Stop
Stop that follows the best mark price by a fixed price distance or a percentage; optional activation price
Letting winners run on perps
Yes (trailingStop action; perps only; no Python SDK helper)
TP/SL
Take-profit and stop-loss triggers on the mark price, attached to an order or a whole position
Protecting every position
Yes (trigger orders, tpsl)
Docs (order types, exchange endpoint) and the app's order form, checked October 22, 2026. TP/SL triggers on the mark price. There is no native iceberg order and no native grid or DCA bot. A TWAP runs on the exchange, so it keeps working if you close the browser; Chase does not. Details: Hyperliquid TWAP orders, trailing stop tutorial, all order types.
Hyperliquid API rate limits a bot must respect
Orders cost no gas, so the ceiling on how much a bot can do is the rate limit, not the fee. There are two kinds: per IP (how fast you can talk to the API servers) and per address (how many actions your account has earned by trading).
Limit
Value
Detail
REST weight per IP
1,200 per minute
Shared by every exchange, info and explorer request from that IP
Exchange action weight
1 + floor(batch length ÷ 40)
A single order or cancel weighs 1; a batch of 79 orders weighs 2
Paginated calls (userFills, userFillsByTime, fundingHistory, twapHistory…) add weight per 20 items returned; candleSnapshot per 60
Explorer
40 per request
blockList has an extra limit of 1 per block
WebSocket per IP
10 connections, 30 new per minute, 1,000 subscriptions
At most 10 unique users across user-specific subscriptions
WebSocket messages
2,000 sent per minute, 100 in-flight posts
Across all connections from the IP
HyperEVM JSON-RPC
100 requests per minute
rpc.hyperliquid.xyz/evm only
Actions per address
1 per 1 USDC traded since the address was created, plus 10,000 at the start
Actions only, not info requests. When exhausted: 1 action every 10 seconds
Cancels per address
min(limit + 100,000, limit × 2)
So a throttled bot can still pull its orders
Open orders
1,000 + 1 per $5M of volume, max 5,000
With 1,000 or more open, new reduce-only and trigger orders are rejected
Congestion
2× your previous-day maker share of block space
Computed once per UTC day
Nonces
100 highest kept per signer
Must be unique and within (now − 2 days, now + 1 day)
Source: Hyperliquid docs "Rate limits and user limits" and "Nonces and API wallets", re-read October 22, 2026. Sub-accounts count as separate users for address-based limits. A batch of n orders is one request for the IP limit but n requests for the address limit.
The address budget. Every address starts with 10,000 actions and earns one more for each 1 USDC of volume. Check where you stand with the userRateLimit info request (info.user_rate_limit(address)): it returns cumVlm, nRequestsUsed, nRequestsCap and nRequestsSurplus. A grid bot that cancels and re-places 20 orders every minute uses 28,800 actions a day, so a new address runs dry in about 8 hours unless the bot trades enough notional to earn the difference; after that it is throttled to one action every 10 seconds. The fix is a quieter bot: modify only when price has moved a full step, widen the grid and let fills, not a timer, drive changes. An account can also buy headroom with reserveRequestWeight at 0.0005 USDC per request (10,000 actions for 5 USDC).
The IP budget. Polling clearinghouseState (weight 2) every 100 ms is 600 requests and 1,200 weight a minute: the whole budget. The same account data arrives by WebSocket at no REST cost. Batching orders in groups of up to 79 keeps each batch at weight 2 or less.
WebSocket for data, REST for actions. Subscribe to l2Book, userFills and orderUpdates; keep local order and position state.
Batch every 100 ms, with ALO (post-only) orders in separate batches from IOC and GTC, because ALO-only batches are prioritised by validators. Send cancels with the fast flag.
Modify instead of cancel-and-replace, back off with jitter after a rejection, and never drop reduce-only or flatten commands when your local token bucket is empty.
Buy a fixed amount on a schedule, for example $50 of spot HYPE or BTC every day. Spot orders must be at least 10 units of the quote token, and a $50 market buy costs $0.035 at the 0.070% spot taker fee. A limit order slightly below the price (0.040% maker) is cheaper if some days may not fill. A native TWAP is not a DCA tool: it slices one order over at most 7 days and does not repeat.
Funding carry (delta neutral)
Hyperliquid funding is paid every hour and capped at 4% an hour. Its interest component is 0.01% per 8 hours, about 11.6% a year paid by longs to shorts when the premium is zero. A carry bot holds spot and shorts the perp to collect it: BTC funding added up to 0.7305% over the 30 days to October 15, 2026. Entry and exit cost roughly $23 on $10,000 at base taker fees, so the trade needs weeks to pay, and funding can turn negative. Full method and a calculator: funding rate arbitrage guide.
Market making: maker fees, rebates and the real risks
Market making on Hyperliquid is permissionless: fund an account, create an API wallet and quote both sides with post-only orders. The docs say there is no designated market maker program, no special rebates or fees and no latency advantages; everyone gets the same schedule.
Maker rebate
Your share of all 14-day maker volume
Rate (paid to you on each fill)
Rebate tier 1
more than 0.5%
-0.001%
Rebate tier 2
more than 1.5%
-0.002%
Rebate tier 3
more than 3%
-0.003%
Why retail quoting on majors loses money. On September 25, 2026 the public book showed spreads of BTC 0.12 bp ($1), ETH 0.37 bp ($0.10), HYPE 0.11 bp, NEAR 2.43 bp, against a base maker fee of 1.5 bp per side. A quote that captures the whole BTC spread still pays more in fees than it earns. Retail makers who last quote wider on less crowded markets, keep inventory small and remember that held inventory pays hourly funding; scheduleCancel and a separate monitor are not optional. Without running a bot: HLP, the protocol vault, market-makes across Hyperliquid (APR at the last build -0.09%, 4 days lock-up after each deposit; it can lose money; see the vaults guide).
What a Hyperliquid bot pays in fees
Tier
14-day volume
Perp taker
Perp maker
Maker with referral code
0
under $5M
0.045%
0.015%
0.0144%
1
over $5M
0.040%
0.012%
—
2
over $25M
0.035%
0.008%
—
3
over $100M
0.030%
0.004%
—
4–6
over $500M
0.028%
0.000%
—
Hyperliquid fee schedule via our facts registry; spot volume counts double toward tiers. Spot base fees are 0.070% / 0.040%. HYPE staking takes 5–40% off, and the referral discount (4% on your first $25M) applies on top. No gas on orders or cancels; a USDC withdrawal costs 0.2 USDC plus a tiny HyperEVM gas fee in HYPE.
On $1M of monthly taker volume, a bot pays $450 at the base rate and $432 with the 4% referral discount; a maker-only bot on the same volume pays $150. A third-party bot adds its builder fee on top (Hyperliquid caps builder fees at 0.1% on perps and 1% on spot; revoke approvals in More → Builder Codes). Details: Hyperliquid fees.
Security and risk controls
API wallets cannot withdraw, but they can trade your balance into the ground. Use one per bot and per sub-account, and never reuse an API wallet address: once deregistered, its nonce history may be pruned and old signed actions could be replayed.
Expiry: API wallets last at most 180 days. Put the expiry date in your calendar so a bot does not silently stop.
Dead man's switch:schedule_cancel cancels all open orders at a time you set unless you push it forward. Combine it with reduce-only exits.
Hard limits in code: maximum position, maximum orders per minute, daily loss limit and a manual kill switch.
Read the code you run: fake bot repos (above) and poisoned packages exist; pin dependency versions and run bots on a machine that holds no main wallet key.
Where you live: Hyperliquid's Terms exclude the US, Ontario and sanctioned regions; a bot does not change that (restricted countries).
FAQ
Can you run a trading bot on Hyperliquid?
Yes. Hyperliquid has a public REST and WebSocket API, an official Python SDK (hyperliquid-python-sdk 0.24.0, MIT licence, released June 4, 2026 and still the latest on October 22, 2026) and community SDKs in TypeScript and Rust. A bot signs orders with an API wallet (agent wallet) that can trade for your account but cannot withdraw. There is no gas on orders or cancels; you pay trading fees on fills, 0.045% taker and 0.015% maker at the base tier.
Is there a Hyperliquid trading bot on GitHub?
Several. Hummingbot (Apache-2.0) has Hyperliquid spot and perp connectors and grid controllers; Freqtrade (GPL-3.0) lists Hyperliquid for spot and futures through CCXT; passivbot (Unlicense) runs perp grids on Hyperliquid; Chainstack publishes a small Python grid bot on the official SDK. Check the licence, the last commit and what the code does on first run: CCXT, for example, tries to set its own referral code (CCXT1) and a 0.01% builder fee unless you change its options. Never run a repo that executes code when you open the folder.
Does Hyperliquid have a built-in trading bot?
Not a grid or DCA bot. The order form has automated order types instead: TWAP (suborders at intervals of 30 seconds or longer, for 5 minutes to 7 days, $100 minimum), Scale (a ladder of limit orders), Chase (a post-only order that follows the price while your browser tab is open) and a native Trailing Stop for perps. For grids, DCA or market making you need your own code, an open-source bot or a hosted bot.
Are Hyperliquid Telegram bots safe?
They trade from a wallet the bot service creates or from your account through an API wallet you link. PvP says its keys are held in Turnkey enclaves and can be exported; Hypurr Fun creates a personal wallet whose key you can export, or lets you link an API wallet. Either way you trust the provider's infrastructure, and a wallet the bot creates is a new Hyperliquid account, without your referral code. Linking an API wallet to an account you already hold keeps withdrawals with you.
Is it safe to give a bot my Hyperliquid API key?
An API wallet can place and cancel orders but has no withdrawal permission, which limits the damage from a leak: someone could trade badly, but not send your funds away. Keep the key in an environment variable or secrets manager, give each bot its own API wallet and sub-account, and never share your main wallet's seed phrase. API wallets expire (at most 180 days) and their addresses should not be reused.
What are Hyperliquid API rate limits for bots?
Per IP: 1,200 REST weight per minute (an order action weighs 1), 10 WebSocket connections and 1,000 subscriptions. Per address: 1 action for every 1 USDC traded since the address was created, plus an initial buffer of 10,000; when you run out, one action every 10 seconds. Open orders are capped at 1,000 plus 1 per $5M of volume, up to 5,000.
Does my referral discount apply to bot trades?
It applies to orders your bot sends from your main account: the referral code gives 4% off fees on your first $25M of volume. It does not apply to sub-accounts or vaults. A builder code does not cancel it: the referral discount also applies to orders placed through apps with a builder code; the builder fee itself is charged in full. The code has to be on the account before it trades more than $10,000, and libraries such as CCXT try to set their own code on accounts that have none, so join with a code before you connect any bot.
Which automated strategy is easiest to start with?
A small, wide grid or a daily DCA buy are the simplest to code and reason about. A native TWAP needs no code at all. Funding carry and market making look safe but depend on fees, rate limits and fast cancels; a trend that runs through your grid, or a funding rate that flips, turns them into losing positions.
Where should a Hyperliquid bot run?
On a server that stays online rather than a laptop. The docs suggest batching orders every 100 ms and say that design suits a strategy running geographically near an API server; ALO (post-only) batches are prioritised by validators. Use WebSocket for market data rather than polling REST, and add reconnect logic because connections do drop.
Open the account your bot will trade from
Join Hyperliquid with code HOLYGRAIL before the first deposit: 4% off fees on your first $25M, orders from your bot's main account included. Then create the API wallet.
Want a free-to-trade venue for a slow bot? Lighter charges 0% on Standard accounts (code 718610TD); see the Lighter API guide.
Disclosure: HOLYGRAIL and 718610TD are our referral codes; we earn a share of fees paid by referred accounts. Code is an illustration, not production software or financial advice. Limits, fees, SDK details, GitHub repositories and bot documentation were checked on October 22, 2026.