Use it when your goal in payments and business operations is clear and you can limit it to the data and actions it actually needs.
Hyperliquid
Hyperliquid market data, account history, trade review
What does it add to Hermes?
Hyperliquid market data, account history, trade review
Hyperliquid is a skill related to payments and business operations. It handles financial or commercial data and actions; any write operation needs stronger approval and limits than ordinary use.
This plain-language explanation is based on the publisher description. The original text remains visible for verification.
Do not add it merely to experiment when Hermes already has a simpler path, or when you cannot review its source and permissions.
Best for users who want a repeatable way of working inside Hermes.
Use a sandbox or test data and do not grant real payment or refund permissions in the first test.
Hyperliquid market data, account history, trade review
This entry was indexed from Hermes Optional Skills. Our explanation interprets the type and domain without inventing a capability not present upstream.
The source is official or editorially reviewed, but you still need to review permissions and version compatibility.
Inspect, install, then test.
- 01Open the source
Match the publisher, license, and description to your need. Check the real update history.
- 02Review permissions and secrets
Never paste a secret value into this site. Use environment-variable names and grant the smallest scope.
- 03Copy setup only after review
The controls below copy text. They do not execute commands on your device.
- 04Test with a non-sensitive task
Inspect the visible tools, then exclude write or delete tools you do not need.
Review the command, then copy it.
hermes skills install hyperliquidHermes Belarabi does not execute this command. Installation happens on your device and remains subject to Hermes scanning and your review.
Exactly what Hermes loads when this skill runs.
Reproduced from the official documentation. Read it before enabling the skill: this text becomes the agent's instructions.
Hyperliquid market data, account history, trade review.
Skill metadata
A lookup table. Do not read it all; find the row that applies to you.
| Source | Optional — install with hermes skills install official/blockchain/hyperliquid |
| Path | optional-skills/blockchain/hyperliquid |
| Version | 0.1.0 |
| Author | Hugo Sequier (Hugo-SEQUIER), Hermes Agent |
| License | MIT |
| Platforms | linux, macos, windows |
| Tags | Hyperliquid, Blockchain, Crypto, Trading, Perpetuals, Spot, DeFi |
Reference: full SKILL.md
Explains the idea itself. Read it slowly; the later sections build on it.
Query Hyperliquid market and account data through the public /info endpoint.
Read-only — no API key, no signing, no order placement.
12 commands: dexs, markets, spots, candles, funding, l2, state,
spot-balances, fills, orders, review, export. Stdlib only
(urllib, json, argparse).
---
When to Use
Explains the idea itself. Read it slowly; the later sections build on it.
- User asks for Hyperliquid perp or spot market data, candles, funding, or L2 book
- User wants to inspect a wallet's perp positions, spot balances, fills, or orders
- User wants a post-trade review combining recent fills with market context
- User wants to inspect builder-deployed perp dexs or HIP-3 markets
- User wants a normalized JSON export of candles + funding for backtesting prep
---
Prerequisites
Settings you configure once. Change one at a time so you can see what each does. Set HYPERLIQUID_API_URL, HYPERLIQUID_USER_ADDRESS in your environment, not in the chat.
Stdlib only — no external packages, no API key.
The script reads ${HERMES_HOME:-~/.hermes}/.env for two optional defaults:
HYPERLIQUID_API_URL— defaults tohttps://api.hyperliquid.xyz. Set tohttps://api.hyperliquid-testnet.xyzfor testnet.HYPERLIQUID_USER_ADDRESS— default address forstate,spot-balances,fills,orders, andreview. If unset, pass the address as the first positional argument.
A project .env in the current working directory is honored as a dev fallback.
Helper script: ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py
---
How to Run
Explains the idea itself. Read it slowly; the later sections build on it.
Invoke through the terminal tool:
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py <command> [args]Add --json to any command for machine-readable output.
---
Quick Reference
Settings you configure once. Change one at a time so you can see what each does. Set HYPERLIQUID_USER_ADDRESS in your environment, not in the chat.
hyperliquid_client.py dexs
hyperliquid_client.py markets [--dex DEX] [--limit N] [--sort volume|oi|funding_abs|change_abs|name]
hyperliquid_client.py spots [--limit N]
hyperliquid_client.py candles <coin> [--interval 1h] [--hours 24] [--limit N]
hyperliquid_client.py funding <coin> [--hours 72] [--limit N]
hyperliquid_client.py l2 <coin> [--levels N]
hyperliquid_client.py state [address] [--dex DEX]
hyperliquid_client.py spot-balances [address] [--limit N]
hyperliquid_client.py fills [address] [--hours N] [--limit N] [--aggregate-by-time]
hyperliquid_client.py orders [address] [--limit N]
hyperliquid_client.py review [address] [--coin COIN] [--hours N] [--fills N]
hyperliquid_client.py export <coin> [--interval 1h] [--hours N] [--output PATH]For state, spot-balances, fills, orders, and review, the address is
optional when HYPERLIQUID_USER_ADDRESS is set in ${HERMES_HOME:-~/.hermes}/.env.
---
Procedure
Explains the idea itself. Read it slowly; the later sections build on it.
1. Discover DEXs and Markets
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py dexs
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
markets --limit 15 --sort volume
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
spots --limit 15--dexonly applies to perp endpoints; omit for the first perp dex.- Spot pairs may show as
PURR/USDCor aliases like@107. - HIP-3 markets prefix the coin with the dex, e.g.
mydex:BTC.
2. Pull Historical Market Data
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
candles BTC --interval 1h --hours 72 --limit 48
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
funding BTC --hours 168 --limit 30Time-range endpoints paginate. For larger windows, repeat with a later
startTime or use export (below).
3. Inspect Live Order Book
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
l2 BTC --levels 10Use when asked about book depth, near-term liquidity, or potential market impact of a large order.
4. Review an Account
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
state 0xabc...
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
spot-balancesstate returns perp positions; spot-balances returns spot inventory.
Use these for "how are my positions?", "what am I holding?", "how much is
withdrawable?".
5. Review Fills and Orders
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
fills 0xabc... --hours 72 --limit 25
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
orders --limit 256. Generate a Trade Review
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
review 0xabc... --hours 72 --fills 50
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
review --coin BTC --hours 168Reports realized PnL, fees, win/loss counts, coin breakdowns, market trend and average funding for each traded perp, plus heuristics (fee drag, concentration, counter-trend losses).
For deeper post-trade analysis: start with review to find problem coins
or windows → pull fills and orders for that period → pull candles
and funding for each traded coin → judge decision quality separately
from outcome quality.
7. Export a Reusable Dataset
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
export BTC --interval 1h --hours 168 --output ./btc-1h-7d.json
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
export BTC --interval 15m --hours 72 --end-time-ms 1760000000000Output JSON contains: schema version, source metadata, exact time window,
normalized candle rows, normalized funding rows, summary stats. Use
--end-time-ms for reproducible windows.
---
Pitfalls
Explains the idea itself. Read it slowly; the later sections build on it.
- Public info endpoints are rate-limited. Large historical queries may return capped windows; iterate with later
startTimevalues. fills --hours ...usesuserFillsByTime, which only exposes a recent rolling window — not full archive history.historicalOrdersreturns recent orders only; not a full export.- The
reviewcommand is heuristic. It cannot reconstruct intent, order placement quality, or true slippage from fills alone. - The
exportcommand writes a normalized dataset, not a backtest engine. You still need your own slippage/fill model. - Spot aliases like
@107are valid identifiers even when the UI shows a friendlier name. l2is a point-in-time snapshot, not a time series.
---
Verification
Explains the idea itself. Read it slowly; the later sections build on it.
python3 ~/.hermes/skills/blockchain/hyperliquid/scripts/hyperliquid_client.py \
markets --limit 5Should print the top Hyperliquid perp markets by 24h notional volume.