{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/gemini-exchange.json", "name": "Gemini Exchange API", "score": 74.6, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "gemini-exchange" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/kraken.json", "name": "Kraken API", "score": 71, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "kraken" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/dydx.json", "name": "dYdX", "score": 69.5, "shared": [ "exchange.derivatives", "exchange.market-data", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto", "wallet.onchain" ], "slug": "dydx" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/okx.json", "name": "OKX API", "score": 64.3, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "okx" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/binance.json", "name": "Binance API", "score": 63.2, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "binance" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/bitfinex.json", "name": "Bitfinex API", "score": 58.4, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "bitfinex" } ], "tool": { "slug": "hyperliquid", "name": "Hyperliquid", "vendor": "Hyperliquid Labs", "vendorUrl": "https://hyperliquid.xyz", "kind": "http-api", "category": "crypto-exchanges", "summary": "Hyperliquid is a perpetuals and spot exchange whose order book runs on its own chain. Agents trade through the REST info and exchange endpoints and WebSocket at api.hyperliquid.xyz, signing with a wallet key or an approved API wallet.", "url": "https://www.anchorterminal.com/tools/hyperliquid", "markdownUrl": "https://www.anchorterminal.com/tools/hyperliquid.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hyperliquid.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hyperliquid.json", "dns": "hyperliquid.grade.anchorterminal.com", "repo": "https://github.com/hyperliquid-dex/hyperliquid-python-sdk", "license": "The exchange runs on the Hyperliquid chain (HyperCore), whose node is distributed as a binary under an Apache-2.0 repository; the Python and Rust SDKs are MIT. The API servers and front end are closed", "transports": [], "packages": [ { "registry": "pypi", "name": "hyperliquid-python-sdk" } ], "auth": "mixed", "authNotes": "No API keys. Every exchange action is a signed message from an EVM wallet; info requests need no signature. A master account approves API wallets (agent wallets) with `approveAgent`, optionally named and with an expiry, which can only sign on its behalf and cannot query data. L1 actions (orders, cancels, margin settings) and user-signed actions (USDC and spot sends, withdrawals, approvals) use two different EIP-712 schemes, and the docs recommend an SDK for signing. Nonces are per signer, must sit within two days behind and one day ahead of block time, and sub-accounts signed by one API wallet share its nonce set (https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/nonces-and-api-wallets.md, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API has no charge. Base-tier fees are 0.045% taker and 0.015% maker on perpetuals and 0.070% taker and 0.040% maker on spot, assessed on rolling 14-day volume, falling to 0.024% taker and 0% maker above $7 billion, with maker rebates to -0.003% for large maker share and staking discounts of 5% to 40%. Withdrawals to the bridge cost $1; an activation gas fee applies to a first order. `reserveRequestWeight` buys extra rate limit at 0.0005 USDC a request (https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees.md, checked 2026-11-03).", "priceSummary": "0.04% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs (checked 2026-11-03). Accounts are funded by depositing USDC on Arbitrum or other bridged chains; several third-party MCP servers in the registry sell Hyperliquid data by x402, none of them Hyperliquid's.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 1873, "npmWeekly": null, "pypiWeekly": 167497, "asOf": "2026-11-03" }, "docsUrl": "https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api", "llmsTxt": "https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt", "capabilities": [ "exchange.derivatives", "exchange.spot-trading", "exchange.market-data", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto", "wallet.onchain" ], "tags": [ "official", "hosted", "closed-source", "llms-txt", "python", "rust", "sandbox", "usage-priced", "no-key", "no-status-page", "bug-bounty", "rest" ], "lastRelease": "2026-06-04", "graded": true, "anchor": { "graded": true, "score": 50, "grade": "D", "agentReady": false, "rank": 1018, "ranked": true, "rankOf": 1349, "categoryRank": 19, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 39, "payments": 55, "reliability": 40, "schema": 42, "security": 64, "transparency": 26 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 40, "points": 8, "reason": "Read with the hosted lines on the REST API at api.hyperliquid.xyz, the surface an agent calls; the chain behind it is noted under details. No status page found in the docs, on hyperliquid.xyz or at status.hyperliquid.xyz, which did not resolve (0). No readable history (5). Rate limits documented with numbers per IP, per address and per WebSocket connection (15). When limited, an address gets one request every 10 seconds; no 429 shape or Retry-After is documented, but `cloid`, per-signer nonces, `expiresAfter` and `noop` make retries safe (10 of 15). No SLA (0). Mainnet is generally available (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.", "checked": "2026-11-03" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 42, "points": 6.83, "reason": "No OpenAPI or other machine-readable contract; request and response shapes are tables and JSON examples in the docs (0 of 25). llms.txt and a Markdown twin of every page by appending .md (10). Each info type and exchange action has a short description of what it does, and the signing page lists common mistakes, but little says when to use one call over another (12 of 20). Fields are one-letter keys (`a`, `b`, `p`, `s`, `r`, `t`, `c`) with numbers as strings, enums such as `tif` Alo, Ioc or Gtc, and required fields marked in tables (9 of 15). An example for every call and a list of order and cancel error strings, with no HTTP error table (11 of 15). No API version, no changelog and no dated release notes; deprecated actions such as `userDexAbstraction` are marked in place (0 of 15). Total 42.", "checked": "2026-11-03" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 70, "points": 11.38, "reason": "An API, read for response sizing. Time-range calls return at most 500 blocks of data, fills and historical orders cap at 2,000 items, candles at 5,000, l2Book at 20 levels a side (18 of 25). Cursor-by-timestamp pagination on fills and funding, filtering by coin or dex, no field selection (14 of 20). Order errors are documented strings per order, one batch-level error rejects a batch, and `orderStatus` answers `unknownOid`; no codes and no rate-limit error shape (12 of 20). `cloid`, per-signer nonces within a time window, `expiresAfter`, `noop` to burn a nonce and `scheduleCancel` as a dead man's switch (18 of 20). Few required fields, but signing needs msgpack field order, two EIP-712 schemes and lowercase addresses, and the official SDKs are Python (Alpha) and Rust only (8 of 15). Total 70.", "checked": "2026-11-03" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 64, "points": 11.2, "reason": "No shared secrets. Actions are signed by the wallet key or by an API wallet the master approves with a name and optional expiry; API wallets can only sign, withdrawals and external sends are user-signed, and approving a new wallet deregisters the old. No IP allow-list or address allow-list (24 of 30). An API wallet is a trading-only credential and info needs no key, but nothing limits order size or marks an action as needing approval (10 of 20). The API returns no untrusted content (10). Fills, historical orders, `userRole` and nonces are queryable per account; no per-wallet action log (8 of 15). A bug bounty run by the Hyper Foundation with rewards up to under 1 million USDC, a Zellic audit of the bridge contract, a SECURITY.md on the SDK; no security.txt (403), no SOC 2 (12 of 20). Total 64.", "checked": "2026-11-03" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 55, "points": 6.88, "reason": "No machine payment protocol (0). Fees published per tier without login (20). No card anywhere; public info endpoints are free and the testnet faucet gives 1,000 mock USDC, though only to an address that has deposited on mainnet (15 of 20). No signup; an agent with a funded EVM wallet deposits USDC on a bridged chain and trades, subject to the unread terms (20). Total 55.", "checked": "2026-11-03" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 39, "points": 3.41, "reason": "Read as a closed hosted service with open SDKs. The API has no dated changelog, so the last dated change is the Python SDK's 0.24.0 on 4 June 2026, 152 days before this check; the node repository was pushed on 10 August 2026 and the docs describe newer actions (HIP-4 outcome markets, borrow and lend) without dates. Judgement call (10 of 30). No three dated releases in 90 days (0). Support through Discord and the docs' FAQ, 112 open issues on the SDK whose replies couldn't be read (8 of 25). Official Python and Rust SDKs, the Rust one last pushed 21 October 2025; no MCP registry entry (15). CI on Python 3.9 and 3.13 with Poetry, Dependabot badge, a lock file (6 of 10). Total 39.", "checked": "2026-11-03" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 26, "points": 2.28, "note": "editorial 20, provenance 32", "reason": "The editorial half. The SDKs are MIT and the node repository Apache-2.0 with a Dockerfile around a binary; the API servers and front end are closed and the terms were unreadable (12 of 30). No privacy policy read and nothing in the docs on data handling (0 of 30). Deprecated actions are marked in the docs without dates or a policy (8 of 20). No subprocessors or data locations (0 of 20). Total 20.", "checked": "2026-11-03" } ], "assessment": { "date": "2026-11-03", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "An API, read for response sizing. Time-range calls return at most 500 blocks of data, fills and historical orders cap at 2,000 items, candles at 5,000, l2Book at 20 levels a side (18 of 25). Cursor-by-timestamp pagination on fills and funding, filtering by coin or dex, no field selection (14 of 20). Order errors are documented strings per order, one batch-level error rejects a batch, and `orderStatus` answers `unknownOid`; no codes and no rate-limit error shape (12 of 20). `cloid`, per-signer nonces within a time window, `expiresAfter`, `noop` to burn a nonce and `scheduleCancel` as a dead man's switch (18 of 20). Few required fields, but signing needs msgpack field order, two EIP-712 schemes and lowercase addresses, and the official SDKs are Python (Alpha) and Rust only (8 of 15). Total 70.", "maintenance": "Read as a closed hosted service with open SDKs. The API has no dated changelog, so the last dated change is the Python SDK's 0.24.0 on 4 June 2026, 152 days before this check; the node repository was pushed on 10 August 2026 and the docs describe newer actions (HIP-4 outcome markets, borrow and lend) without dates. Judgement call (10 of 30). No three dated releases in 90 days (0). Support through Discord and the docs' FAQ, 112 open issues on the SDK whose replies couldn't be read (8 of 25). Official Python and Rust SDKs, the Rust one last pushed 21 October 2025; no MCP registry entry (15). CI on Python 3.9 and 3.13 with Poetry, Dependabot badge, a lock file (6 of 10). Total 39.", "payments": "No machine payment protocol (0). Fees published per tier without login (20). No card anywhere; public info endpoints are free and the testnet faucet gives 1,000 mock USDC, though only to an address that has deposited on mainnet (15 of 20). No signup; an agent with a funded EVM wallet deposits USDC on a bridged chain and trades, subject to the unread terms (20). Total 55.", "reliability": "Read with the hosted lines on the REST API at api.hyperliquid.xyz, the surface an agent calls; the chain behind it is noted under details. No status page found in the docs, on hyperliquid.xyz or at status.hyperliquid.xyz, which did not resolve (0). No readable history (5). Rate limits documented with numbers per IP, per address and per WebSocket connection (15). When limited, an address gets one request every 10 seconds; no 429 shape or Retry-After is documented, but `cloid`, per-signer nonces, `expiresAfter` and `noop` make retries safe (10 of 15). No SLA (0). Mainnet is generally available (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.", "schema": "No OpenAPI or other machine-readable contract; request and response shapes are tables and JSON examples in the docs (0 of 25). llms.txt and a Markdown twin of every page by appending .md (10). Each info type and exchange action has a short description of what it does, and the signing page lists common mistakes, but little says when to use one call over another (12 of 20). Fields are one-letter keys (`a`, `b`, `p`, `s`, `r`, `t`, `c`) with numbers as strings, enums such as `tif` Alo, Ioc or Gtc, and required fields marked in tables (9 of 15). An example for every call and a list of order and cancel error strings, with no HTTP error table (11 of 15). No API version, no changelog and no dated release notes; deprecated actions such as `userDexAbstraction` are marked in place (0 of 15). Total 42.", "security": "No shared secrets. Actions are signed by the wallet key or by an API wallet the master approves with a name and optional expiry; API wallets can only sign, withdrawals and external sends are user-signed, and approving a new wallet deregisters the old. No IP allow-list or address allow-list (24 of 30). An API wallet is a trading-only credential and info needs no key, but nothing limits order size or marks an action as needing approval (10 of 20). The API returns no untrusted content (10). Fills, historical orders, `userRole` and nonces are queryable per account; no per-wallet action log (8 of 15). A bug bounty run by the Hyper Foundation with rewards up to under 1 million USDC, a Zellic audit of the bridge contract, a SECURITY.md on the SDK; no security.txt (403), no SOC 2 (12 of 20). Total 64.", "transparency": "The editorial half. The SDKs are MIT and the node repository Apache-2.0 with a Dockerfile around a binary; the API servers and front end are closed and the terms were unreadable (12 of 30). No privacy policy read and nothing in the docs on data handling (0 of 30). Deprecated actions are marked in the docs without dates or a policy (8 of 20). No subprocessors or data locations (0 of 20). Total 20." }, "sources": [ { "what": "docs robots.txt", "url": "https://hyperliquid.gitbook.io/robots.txt", "seen": "2026-11-03" }, { "what": "docs llms.txt index", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt", "seen": "2026-11-03" }, { "what": "API overview (base URLs, SDKs)", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api", "seen": "2026-11-03" }, { "what": "info endpoint", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint.md", "seen": "2026-11-03" }, { "what": "exchange endpoint (actions, agent-signable variants, dead man's switch)", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/exchange-endpoint.md", "seen": "2026-11-03" }, { "what": "nonces and API wallets", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/nonces-and-api-wallets.md", "seen": "2026-11-03" }, { "what": "signing", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/signing.md", "seen": "2026-11-03" }, { "what": "rate limits and user limits", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/rate-limits-and-user-limits.md", "seen": "2026-11-03" }, { "what": "error responses", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/error-responses.md", "seen": "2026-11-03" }, { "what": "fees", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees.md", "seen": "2026-11-03" }, { "what": "testnet faucet", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/onboarding/testnet-faucet.md", "seen": "2026-11-03" }, { "what": "HyperCore overview", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/overview.md", "seen": "2026-11-03" }, { "what": "API servers", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/api-servers.md", "seen": "2026-11-03" }, { "what": "core contributors", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors.md", "seen": "2026-11-03" }, { "what": "bug bounty programme", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/bug-bounty-program.md", "seen": "2026-11-03" }, { "what": "audits", "url": "https://hyperliquid.gitbook.io/hyperliquid-docs/audits.md", "seen": "2026-11-03" }, { "what": "official MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=hyperliquid", "seen": "2026-11-03" }, { "what": "hyperliquid-dex repositories", "url": "https://api.github.com/orgs/hyperliquid-dex/repos?per_page=100\u0026sort=pushed", "seen": "2026-11-03" }, { "what": "Python SDK repository (stars, issues) and shallow clone", "url": "https://api.github.com/repos/hyperliquid-dex/hyperliquid-python-sdk", "seen": "2026-11-03" }, { "what": "PyPI release feed", "url": "https://pypi.org/rss/project/hyperliquid-python-sdk/releases.xml", "seen": "2026-11-03" }, { "what": "PyPI downloads (pypistats, third-party aggregate)", "url": "https://pypistats.org/api/packages/hyperliquid-python-sdk/recent", "seen": "2026-11-03" }, { "what": "terms (script-drawn, title only)", "url": "https://app.hyperliquid.xyz/terms", "seen": "2026-11-03" }, { "what": "terms on the apex domain (403)", "url": "https://hyperliquid.xyz/terms", "seen": "2026-11-03" }, { "what": "security.txt (403)", "url": "https://hyperliquid.xyz/.well-known/security.txt", "seen": "2026-11-03" }, { "what": "RDAP for hyperliquid.xyz", "url": "https://rdap.centralnic.com/xyz/domain/hyperliquid.xyz", "seen": "2026-11-03" } ], "openQuestions": [ "unchecked: the terms of use and privacy policy (app.hyperliquid.xyz draws by script, hyperliquid.xyz/terms answered 403), so the restricted jurisdictions, the legal entity and what the terms say about bots come from nothing first-hand. Third-party pages describe US and Ontario users as restricted persons at the front end.", "unchecked: a status page and any incident record. Press reports describe a 37-minute API outage in July 2025 (outside the 12-month window) and a HyperEVM disruption on 2 April 2026; neither was read on a Hyperliquid page, so no deduction and nothing in reliability.", "unchecked: the last 23,750 characters of the exchange endpoint page beyond the trailing stop section were read only in part; subAccountTransfer and vault actions are listed from the first part.", "unchecked: Hyper Foundation's site (script-drawn) and whether an entity other than Hyperliquid Labs operates the API servers; the docs don't say who runs api.hyperliquid.xyz.", "firstReleased is 30 March 2023, the creation date of the hyperliquid-python-sdk repository, the earliest first-hand date found; the oldest PyPI release in the feed is 0.1.12 on 20 September 2023. The mainnet launch date was not read first-hand.", "lastRelease is 4 June 2026, the Python SDK's 0.24.0. The API gains actions without dated notes, so the service may be more current than that date shows.", "Judgement call on kind. Listed as http-api on the hosted REST API, the surface an agent calls; the order book and clearinghouse run on the Hyperliquid chain, recorded under details. pypiWeekly comes from pypistats.org, a third-party aggregate; no score rests on it.", "Our own products. It doesn't do LocalGhost's or letme's job. Graded the normal way." ] }, "negative": 0, "verdict": "Hyperliquid's API needs no signup or key, an approved API wallet can trade but not withdraw, fees and rate limits are published with numbers, and a testnet mirrors mainnet. There is no official MCP server, OpenAPI file, status page, changelog or readable terms, and signing uses two schemes the docs say to leave to an SDK.", "bestFor": "An agent trading perpetuals or spot on chain from its own wallet with no account, or acting for a master account through an approved API wallet.", "strengths": [ "API wallets approved by the master account can only sign trading actions; withdrawals and external transfers need the user's own key", "Numeric rate limits per IP and per address, with weights per request type and a paid `reserveRequestWeight` top-up", "Fees published per tier from 0.045% taker and 0.015% maker on perpetuals, with maker rebates and staking discounts", "A testnet at api.hyperliquid-testnet.xyz with the same API and a faucet of 1,000 mock USDC for addresses that have deposited on mainnet", "Client order IDs (`cloid`), `expiresAfter`, `noop` and a `scheduleCancel` dead man's switch for safe retries" ], "weaknesses": [ "No official MCP server; the 23 registry entries are all third parties, several selling data by x402", "No OpenAPI file, no changelog, no API versioning and no status page found", "The terms of use and privacy policy at app.hyperliquid.xyz draw by script and hyperliquid.xyz/terms answered 403, so the restricted jurisdictions are unchecked", "Order errors are message strings without codes, and the docs give no 429 or Retry-After guidance beyond one request every 10 seconds when limited", "The official Python SDK is marked Alpha, last released 4 June 2026, with 112 open issues" ], "agentNotes": [ "Generate a fresh API wallet, approve it with `approveAgent` with a name and expiry, sign with it, and query with the master address, never the agent address", "Use the Python SDK's `sign_l1_action` and `sign_user_signed_action`; mixing the two, field order in msgpack or an uppercase address gives \"User or API Wallet ... does not exist\"", "Set a `cloid` on every order and read the per-order `statuses` array; one batch-level error rejects the whole batch", "Budget address limits by volume (one action per 1 USDC traded after 10,000); batch orders to lower IP weight, and use WebSocket for data", "Arm `scheduleCancel` before unattended trading so open orders are cancelled if the agent stops" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50 } ], "editorialScores": { "ergonomics": 70, "maintenance": 39, "payments": 55, "reliability": 40, "schema": 42, "security": 64, "transparency": 20 }, "provenanceScore": 32, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 }, "scoreHistory": [ { "date": "2026-11-03", "grade": "D", "kind": "listed", "method": "0.7", "score": 50 } ] }, "connect": { "install": "pip install hyperliquid-python-sdk", "http": "curl -X POST https://api.hyperliquid.xyz/info -H 'Content-Type: application/json' -d '{\"type\":\"l2Book\",\"coin\":\"BTC\"}'" }, "letme": { "capability": "https://letme.dev/exchange.derivatives", "tool": "https://letme.dev/hyperliquid" }, "notable": [ "No official MCP server. The official MCP registry's search for hyperliquid lists 23 entries from 12 third-party publishers (Tessera, HLWatch, Junct, Pipeworx, Ironflow, Reins and others), none from hyperliquid-dex or a hyperliquid.xyz namespace; the docs and the hyperliquid-dex GitHub organisation have none (https://registry.modelcontextprotocol.io/v0/servers?search=hyperliquid)", "What runs on chain. HyperCore holds the margin and matching engine state under HyperBFT consensus; the docs say the order book is not run off chain. API servers follow a node, keep the state locally, answer REST and WebSocket queries and forward signed transactions to a node, returning the result once the block commits (https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/api-servers.md)", "Rate limits are 1,200 weight a minute per IP (orders weigh 1 plus one per 40 batched items, most info requests 20, l2Book and clearinghouseState 2) and, per address, one action per 1 USDC traded since inception after an initial 10,000, with a rate-limited address allowed one request every 10 seconds. Open orders are capped at 1,000 plus one per 5 million USDC of volume up to 5,000 (https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/rate-limits-and-user-limits.md)", "API wallets only sign. Withdrawals (`withdraw3`), USDC and spot sends are user-signed actions; `agentSendAsset` and `cDeposit2` are the agent-signable variants, and `agentSendAsset` requires the destination to match the source address (https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/exchange-endpoint.md)", "The order response lists a status per order, `resting`, `filled` or `error` with a message string such as \"Order must have minimum value of $10.\"; `scheduleCancel` is a dead man's switch (at most 10 triggers a day) and `noop` burns a nonce to cancel in-flight actions (https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/error-responses.md)", "hyperliquid-python-sdk 0.24.0 on PyPI (4 June 2026), MIT, classifier Alpha, 42 releases since 0.1.12 on 20 September 2023, with CI on Python 3.9 and 3.13 (https://pypi.org/rss/project/hyperliquid-python-sdk/releases.xml)", "The docs say Hyperliquid Labs is self-funded and has taken no external capital, led by Jeff and iliensinc; the bug bounty is run by the Hyper Foundation with rewards in USDC up to under 1 million for critical bugs (https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors.md)" ], "area": "payments", "details": [ { "label": "Surface listed", "value": "The REST API at api.hyperliquid.xyz (POST /info and POST /exchange) and its WebSocket, with the official Python SDK, read from the GitBook docs (Markdown twins), the hyperliquid-dex repositories, PyPI and the MCP registry on 3 November 2026. No wallet was connected and no action was signed" }, { "label": "MCP server", "value": "None found. Checked the docs (no mention), the hyperliquid-dex GitHub organisation (11 repositories, none an MCP server) and the official MCP registry, whose search returns 23 entries from third parties only, among them io.github.junct-bot/hyperliquid-mcp (hosted), io.github.pipeworx-io (hosted and npm), io.github.Br0ski777 (x402-paid) and io.github.R2Rlabs/hyperliquid-reins (a stdio server that holds a private key). None is Hyperliquid's" }, { "label": "What runs on chain", "value": "HyperCore, the margin and matching engine state, runs under HyperBFT consensus with the order book on chain; the docs give a 0.2 second median end-to-end latency for co-located clients and about 200,000 orders a second. API servers are off-chain relays that follow a node, serve REST and WebSocket and forward transactions. HyperEVM shares the state for smart contracts. Fees go to HLP, the assistance fund (which buys and burns HYPE) and deployers" }, { "label": "Key permissions", "value": "No API keys. API wallets approved by `approveAgent` sign L1 actions (orders, cancels, modifies, margin settings, TWAPs, vault transfers) and the agent variants `agentSendAsset` (destination must equal source) and `cDeposit2`. Withdrawals, USDC and spot sends to other addresses, builder fee approvals and abstraction changes are user-signed by the master key. One unnamed and several named API wallets; approving a new one deregisters the old; expiry optional. No IP or address allow-list" }, { "label": "Rate limits", "value": "Per IP 1,200 weight a minute (actions 1 plus floor(batch/40), most info 20, l2Book and clearinghouseState 2, userRole 60, extra weight per 20 items on history calls). Per address one action per 1 USDC traded since inception after 10,000 free, cancels up to min(limit + 100,000, 2 times limit), then one request every 10 seconds. WebSocket 10 connections, 30 new a minute, 1,000 subscriptions, 2,000 messages a minute, 100 inflight posts. EVM JSON-RPC 100 a minute" }, { "label": "Testnet", "value": "https://api.hyperliquid-testnet.xyz with the same API. The faucet at app.hyperliquid-testnet.xyz/drip gives 1,000 mock USDC to an address that has deposited on mainnet" }, { "label": "Countries", "value": "Unchecked. The terms at app.hyperliquid.xyz/terms draw by script and hyperliquid.xyz/terms answered 403. Third-party pages found by search describe restricted persons in the United States, Ontario and sanctioned jurisdictions, applied at the front end by Hyperliquid Labs; not confirmed first-hand" }, { "label": "Fees", "value": "Perpetuals 0.045% taker and 0.015% maker at tier 0, to 0.024% and 0% above $7 billion of 14-day volume; spot 0.070% and 0.040% to 0.025% and 0%. Maker rebates -0.001% to -0.003% by maker share. Staking discounts 5% (Wood, more than 10 HYPE) to 40% (Diamond, more than 500,000). Spot volume counts double. HIP-3 deployers keep up to 50% of fees on their assets" }, { "label": "WebSocket", "value": "wss://api.hyperliquid.xyz/ws with subscriptions (trades, l2Book, user events, fills, candles) and post requests that carry info and exchange payloads, with timeouts and heartbeats documented. No FIX" }, { "label": "Terms on automated trading", "value": "Unchecked, the terms were unreadable. The API docs assume programmatic trading throughout, with market-making, self-trade prevention and builder-code pages" }, { "label": "Errors", "value": "Per-order status strings (Tick, MinTradeNtl, PerpMargin, ReduceOnly, BadAloPx, IocCancel, MarketOrderNoLiquidity, Oracle, PerpMaxPosition and others) and MissingOrder on cancel; a batch-level error rejects the whole batch. No HTTP status or 429 shape documented for rate limits" }, { "label": "SDKs", "value": "hyperliquid-python-sdk 0.24.0 (MIT, Alpha, 4 June 2026, 1,873 stars, 112 open issues) and hyperliquid-rust-sdk (MIT, last pushed 21 October 2025) from hyperliquid-dex; TypeScript SDKs by nktkas and nomeida and a Rust hypersdk are community work linked from the docs; CCXT covers it" }, { "label": "Legal entity", "value": "Not established. The docs name Hyperliquid Labs as the core contributor, self-funded, and the Hyper Foundation as owner of bug bounty submissions (bugbounty@hyperfoundation.org); hyperfoundation.org draws by script and no terms page was readable" } ], "unitPrices": [ { "item": "Perpetuals taker fee, tier 0", "unit": "pct", "usd": 0.045, "note": "0.045% of notional; maker 0.015%" }, { "item": "Spot taker fee, tier 0", "unit": "pct", "usd": 0.07, "note": "0.070% of notional; maker 0.040%" }, { "item": "Bridge withdrawal", "unit": "tx", "usd": 1, "note": "$1 per withdrawal to the bridge contract" } ], "provenance": { "legalEntity": "", "domain": "hyperliquid.xyz", "domainRegistered": "2022-10-15", "endpointOnVendorDomain": true, "terms": "https://app.hyperliquid.xyz/terms", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "No legal entity found on a readable page. The docs name Hyperliquid Labs (self-funded) and the Hyper Foundation (bug bounty); app.hyperliquid.xyz/terms and hyperfoundation.org draw by script and hyperliquid.xyz/terms answered 403.", "RDAP gives hyperliquid.xyz a registration date of 15 October 2022, registrar Squarespace Domains.", "No status page found; status.hyperliquid.xyz did not resolve and the docs link none. No changelog; the docs have no dated release notes.", "https://hyperliquid.xyz/.well-known/security.txt answered 403, so security.txt is unknown. The docs' bug bounty page gives bugbounty@hyperfoundation.org.", "hyperliquid.gitbook.io/robots.txt allows everything with Content-Signal ai-input=yes; hyperliquid.xyz/robots.txt allows everything." ], "score": 32, "checks": [ { "check": "Legal entity named", "value": "not found", "points": 0, "max": 20, "state": "no" }, { "check": "Domain age", "value": "hyperliquid.xyz, registered 2022-10-15 (4 years)", "points": 7, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": "hyperliquid.xyz", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "security.txt", "value": "could not be fetched", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "not researched yet", "points": 0, "max": 0, "state": "na" }, { "check": "Support route", "value": "help pages, a community", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://app.hyperliquid.xyz/terms", "state": "unreadable", "reason": "the page has 1 words of text without a browser, so the document is drawn by script or sits elsewhere", "readAt": "2026-11-03", "points": 7, "max": 10 }, { "kind": "privacy", "url": "", "state": "none-found", "points": 0, "max": 10 } ] }, "humans": { "slug": "hyperliquid", "checked": "2026-11-03", "company": "Hyperliquid Labs", "peopleNote": "The docs' core contributors page says Hyperliquid Labs is led by Jeff and iliensinc, classmates from Harvard, linking an X account for Jeff (chameleon_jeff) and giving no surname for either, so nobody is listed; a surname is never guessed. No other Hyperliquid page read names a person with a role, and the Hyper Foundation's site draws by script. Ownership is private from the same page, which says Hyperliquid Labs is self-funded and has not taken any external capital, so no investors are listed; the search for funding stopped there.", "companySocial": { "github": "https://github.com/hyperliquid-dex" }, "support": { "urls": [ "https://hyperliquid.gitbook.io/hyperliquid-docs/support/read-me-support-guide" ], "community": [ { "label": "Discord", "url": "https://discord.gg/tPw7CXqYAe", "kind": "discord" } ], "contactEmails": [ "bugbounty@hyperfoundation.org" ] }, "sources": [ "https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors.md", "https://hyperliquid.gitbook.io/hyperliquid-docs/bug-bounty-program.md", "https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt", "https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/master/SECURITY.md", "https://api.github.com/orgs/hyperliquid-dex/repos?per_page=100\u0026sort=pushed" ], "ownership": { "status": "private", "checked": "2026-11-03", "sources": [ "https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors.md" ] } }, "pageJsonUrl": "https://www.anchorterminal.com/tools/hyperliquid.json", "live": { "slug": "hyperliquid", "securityTxt": { "url": "https://hyperliquid.xyz/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-04T15:54:05.956872316Z" }, "updatedAt": "2026-11-04T15:54:05.956872316Z" } }, "verify": { "accepts": "a page on hyperliquid.xyz or one of its subdomains, or the README at the root of github.com/hyperliquid-dex/hyperliquid-python-sdk", "badgeUrl": "https://www.anchorterminal.com/badges/hyperliquid.svg", "body": { "slug": "hyperliquid", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/hyperliquid", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/hyperliquid\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/hyperliquid.svg\" alt=\"Hyperliquid on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Hyperliquid on Anchor Terminal](https://www.anchorterminal.com/badges/hyperliquid.svg)](https://www.anchorterminal.com/tools/hyperliquid)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/hyperliquid\"\u003eHyperliquid on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/hyperliquid", "json": "https://www.anchorterminal.com/tools/hyperliquid.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/hyperliquid.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/hyperliquid#pricing", "reviews": "https://www.anchorterminal.com/tools/hyperliquid#reviews", "slim": "https://www.anchorterminal.com/tools/hyperliquid.min.md" }, "markdown": "## Overview\n\n**Grade D · 50/100 · rank #1018 of 1349 · #19 in Crypto exchanges · not agent-ready · confidence medium**\n\n\n## Assessment\n\nHyperliquid's API needs no signup or key, an approved API wallet can trade but not withdraw, fees and rate limits are published with numbers, and a testnet mirrors mainnet. There is no official MCP server, OpenAPI file, status page, changelog or readable terms, and signing uses two schemes the docs say to leave to an SDK.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Hyperliquid Labs (https://hyperliquid.xyz) |\n| Kind | HTTP API |\n| Category | Crypto exchanges (https://www.anchorterminal.com/categories/crypto-exchanges) |\n| Auth | OAuth or key · No API keys. Every exchange action is a signed message from an EVM wallet; info requests need no signature. A master account approves API wallets (agent wallets) with `approveAgent`, optionally named and with an expiry, which can only sign on its behalf and cannot query data. L1 actions (orders, cancels, margin settings) and user-signed actions (USDC and spot sends, withdrawals, approvals) use two different EIP-712 schemes, and the docs recommend an SDK for signing. Nonces are per signer, must sit within two days behind and one day ahead of block time, and sub-accounts signed by one API wallet share its nonce set (https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/nonces-and-api-wallets.md, checked 2026-11-03). |\n| Pricing | Pay per use (0.04% fee) · The API has no charge. Base-tier fees are 0.045% taker and 0.015% maker on perpetuals and 0.070% taker and 0.040% maker on spot, assessed on rolling 14-day volume, falling to 0.024% taker and 0% maker above $7 billion, with maker rebates to -0.003% for large maker share and staking discounts of 5% to 40%. Withdrawals to the bridge cost $1; an activation gas fee applies to a first order. `reserveRequestWeight` buys extra rate limit at 0.0005 USDC a request (https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees.md, checked 2026-11-03). |\n| x402 | No · No x402, MPP or L402 in the API docs (checked 2026-11-03). Accounts are funded by depositing USDC on Arbitrum or other bridged chains; several third-party MCP servers in the registry sell Hyperliquid data by x402, none of them Hyperliquid's. |\n| Licence | The exchange runs on the Hyperliquid chain (HyperCore), whose node is distributed as a binary under an Apache-2.0 repository; the Python and Rust SDKs are MIT. The API servers and front end are closed |\n| Tools exposed | 0 |\n| Packages | pypi: `hyperliquid-python-sdk` |\n| Source | https://github.com/hyperliquid-dex/hyperliquid-python-sdk |\n| Docs | https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api |\n| llms.txt | https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt |\n| Last release | 2026-06-04 |\n| GitHub stars | 1,873 (as of 2026-11-03) |\n| PyPI downloads / week | 167,497 |\n| Surface listed | The REST API at api.hyperliquid.xyz (POST /info and POST /exchange) and its WebSocket, with the official Python SDK, read from the GitBook docs (Markdown twins), the hyperliquid-dex repositories, PyPI and the MCP registry on 3 November 2026. No wallet was connected and no action was signed |\n| MCP server | None found. Checked the docs (no mention), the hyperliquid-dex GitHub organisation (11 repositories, none an MCP server) and the official MCP registry, whose search returns 23 entries from third parties only, among them io.github.junct-bot/hyperliquid-mcp (hosted), io.github.pipeworx-io (hosted and npm), io.github.Br0ski777 (x402-paid) and io.github.R2Rlabs/hyperliquid-reins (a stdio server that holds a private key). None is Hyperliquid's |\n| What runs on chain | HyperCore, the margin and matching engine state, runs under HyperBFT consensus with the order book on chain; the docs give a 0.2 second median end-to-end latency for co-located clients and about 200,000 orders a second. API servers are off-chain relays that follow a node, serve REST and WebSocket and forward transactions. HyperEVM shares the state for smart contracts. Fees go to HLP, the assistance fund (which buys and burns HYPE) and deployers |\n| Key permissions | No API keys. API wallets approved by `approveAgent` sign L1 actions (orders, cancels, modifies, margin settings, TWAPs, vault transfers) and the agent variants `agentSendAsset` (destination must equal source) and `cDeposit2`. Withdrawals, USDC and spot sends to other addresses, builder fee approvals and abstraction changes are user-signed by the master key. One unnamed and several named API wallets; approving a new one deregisters the old; expiry optional. No IP or address allow-list |\n| Rate limits | Per IP 1,200 weight a minute (actions 1 plus floor(batch/40), most info 20, l2Book and clearinghouseState 2, userRole 60, extra weight per 20 items on history calls). Per address one action per 1 USDC traded since inception after 10,000 free, cancels up to min(limit + 100,000, 2 times limit), then one request every 10 seconds. WebSocket 10 connections, 30 new a minute, 1,000 subscriptions, 2,000 messages a minute, 100 inflight posts. EVM JSON-RPC 100 a minute |\n| Testnet | https://api.hyperliquid-testnet.xyz with the same API. The faucet at app.hyperliquid-testnet.xyz/drip gives 1,000 mock USDC to an address that has deposited on mainnet |\n| Countries | Unchecked. The terms at app.hyperliquid.xyz/terms draw by script and hyperliquid.xyz/terms answered 403. Third-party pages found by search describe restricted persons in the United States, Ontario and sanctioned jurisdictions, applied at the front end by Hyperliquid Labs; not confirmed first-hand |\n| Fees | Perpetuals 0.045% taker and 0.015% maker at tier 0, to 0.024% and 0% above $7 billion of 14-day volume; spot 0.070% and 0.040% to 0.025% and 0%. Maker rebates -0.001% to -0.003% by maker share. Staking discounts 5% (Wood, more than 10 HYPE) to 40% (Diamond, more than 500,000). Spot volume counts double. HIP-3 deployers keep up to 50% of fees on their assets |\n| WebSocket | wss://api.hyperliquid.xyz/ws with subscriptions (trades, l2Book, user events, fills, candles) and post requests that carry info and exchange payloads, with timeouts and heartbeats documented. No FIX |\n| Terms on automated trading | Unchecked, the terms were unreadable. The API docs assume programmatic trading throughout, with market-making, self-trade prevention and builder-code pages |\n| Errors | Per-order status strings (Tick, MinTradeNtl, PerpMargin, ReduceOnly, BadAloPx, IocCancel, MarketOrderNoLiquidity, Oracle, PerpMaxPosition and others) and MissingOrder on cancel; a batch-level error rejects the whole batch. No HTTP status or 429 shape documented for rate limits |\n| SDKs | hyperliquid-python-sdk 0.24.0 (MIT, Alpha, 4 June 2026, 1,873 stars, 112 open issues) and hyperliquid-rust-sdk (MIT, last pushed 21 October 2025) from hyperliquid-dex; TypeScript SDKs by nktkas and nomeida and a Rust hypersdk are community work linked from the docs; CCXT covers it |\n| Legal entity | Not established. The docs name Hyperliquid Labs as the core contributor, self-funded, and the Hyper Foundation as owner of bug bounty submissions (bugbounty@hyperfoundation.org); hyperfoundation.org draws by script and no terms page was readable |\n| Capabilities | exchange.derivatives, exchange.spot-trading, exchange.market-data, exchange.balances, exchange.transfers, exchange.staking, market.crypto, wallet.onchain |\n| Tags | official, hosted, closed-source, llms-txt, python, rust, sandbox, usage-priced, no-key, no-status-page, bug-bounty, rest |\n| JSON | https://www.anchorterminal.com/api/v1/tools/hyperliquid.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 40 | 8.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 42 | 6.8 |\n| Agent ergonomics | 13% | 16.2 | 70 | 11.4 |\n| Security \u0026 auth | 14% | 17.5 | 64 | 11.2 |\n| Payments \u0026 pricing | 10% | 12.5 | 55 | 6.9 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 39 | 3.4 |\n| Transparency \u0026 trust (editorial 20, provenance 32) | 7% | 8.8 | 26 | 2.3 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **50 → D** |\n\n### Why each score\n\n- Reliability 40 (checked 2026-11-03): Read with the hosted lines on the REST API at api.hyperliquid.xyz, the surface an agent calls; the chain behind it is noted under details. No status page found in the docs, on hyperliquid.xyz or at status.hyperliquid.xyz, which did not resolve (0). No readable history (5). Rate limits documented with numbers per IP, per address and per WebSocket connection (15). When limited, an address gets one request every 10 seconds; no 429 shape or Retry-After is documented, but `cloid`, per-signer nonces, `expiresAfter` and `noop` make retries safe (10 of 15). No SLA (0). Mainnet is generally available (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 42 (checked 2026-11-03): No OpenAPI or other machine-readable contract; request and response shapes are tables and JSON examples in the docs (0 of 25). llms.txt and a Markdown twin of every page by appending .md (10). Each info type and exchange action has a short description of what it does, and the signing page lists common mistakes, but little says when to use one call over another (12 of 20). Fields are one-letter keys (`a`, `b`, `p`, `s`, `r`, `t`, `c`) with numbers as strings, enums such as `tif` Alo, Ioc or Gtc, and required fields marked in tables (9 of 15). An example for every call and a list of order and cancel error strings, with no HTTP error table (11 of 15). No API version, no changelog and no dated release notes; deprecated actions such as `userDexAbstraction` are marked in place (0 of 15). Total 42.\n- Agent ergonomics 70 (checked 2026-11-03): An API, read for response sizing. Time-range calls return at most 500 blocks of data, fills and historical orders cap at 2,000 items, candles at 5,000, l2Book at 20 levels a side (18 of 25). Cursor-by-timestamp pagination on fills and funding, filtering by coin or dex, no field selection (14 of 20). Order errors are documented strings per order, one batch-level error rejects a batch, and `orderStatus` answers `unknownOid`; no codes and no rate-limit error shape (12 of 20). `cloid`, per-signer nonces within a time window, `expiresAfter`, `noop` to burn a nonce and `scheduleCancel` as a dead man's switch (18 of 20). Few required fields, but signing needs msgpack field order, two EIP-712 schemes and lowercase addresses, and the official SDKs are Python (Alpha) and Rust only (8 of 15). Total 70.\n- Security \u0026 auth 64 (checked 2026-11-03): No shared secrets. Actions are signed by the wallet key or by an API wallet the master approves with a name and optional expiry; API wallets can only sign, withdrawals and external sends are user-signed, and approving a new wallet deregisters the old. No IP allow-list or address allow-list (24 of 30). An API wallet is a trading-only credential and info needs no key, but nothing limits order size or marks an action as needing approval (10 of 20). The API returns no untrusted content (10). Fills, historical orders, `userRole` and nonces are queryable per account; no per-wallet action log (8 of 15). A bug bounty run by the Hyper Foundation with rewards up to under 1 million USDC, a Zellic audit of the bridge contract, a SECURITY.md on the SDK; no security.txt (403), no SOC 2 (12 of 20). Total 64.\n- Payments \u0026 pricing 55 (checked 2026-11-03): No machine payment protocol (0). Fees published per tier without login (20). No card anywhere; public info endpoints are free and the testnet faucet gives 1,000 mock USDC, though only to an address that has deposited on mainnet (15 of 20). No signup; an agent with a funded EVM wallet deposits USDC on a bridged chain and trades, subject to the unread terms (20). Total 55.\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 39 (checked 2026-11-03): Read as a closed hosted service with open SDKs. The API has no dated changelog, so the last dated change is the Python SDK's 0.24.0 on 4 June 2026, 152 days before this check; the node repository was pushed on 10 August 2026 and the docs describe newer actions (HIP-4 outcome markets, borrow and lend) without dates. Judgement call (10 of 30). No three dated releases in 90 days (0). Support through Discord and the docs' FAQ, 112 open issues on the SDK whose replies couldn't be read (8 of 25). Official Python and Rust SDKs, the Rust one last pushed 21 October 2025; no MCP registry entry (15). CI on Python 3.9 and 3.13 with Poetry, Dependabot badge, a lock file (6 of 10). Total 39.\n- Transparency \u0026 trust 26 (checked 2026-11-03): The editorial half. The SDKs are MIT and the node repository Apache-2.0 with a Dockerfile around a binary; the API servers and front end are closed and the terms were unreadable (12 of 30). No privacy policy read and nothing in the docs on data handling (0 of 30). Deprecated actions are marked in the docs without dates or a policy (8 of 20). No subprocessors or data locations (0 of 20). Total 20.\n\nFix list, everything this grade says the listing lacks, the biggest gain first (22 items). What it covers is at https://www.anchorterminal.com/fixes/hyperliquid.md (JSON https://www.anchorterminal.com/fixes/hyperliquid.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"hyperliquid\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- unchecked: the terms of use and privacy policy (app.hyperliquid.xyz draws by script, hyperliquid.xyz/terms answered 403), so the restricted jurisdictions, the legal entity and what the terms say about bots come from nothing first-hand. Third-party pages describe US and Ontario users as restricted persons at the front end.\n- unchecked: a status page and any incident record. Press reports describe a 37-minute API outage in July 2025 (outside the 12-month window) and a HyperEVM disruption on 2 April 2026; neither was read on a Hyperliquid page, so no deduction and nothing in reliability.\n- unchecked: the last 23,750 characters of the exchange endpoint page beyond the trailing stop section were read only in part; subAccountTransfer and vault actions are listed from the first part.\n- unchecked: Hyper Foundation's site (script-drawn) and whether an entity other than Hyperliquid Labs operates the API servers; the docs don't say who runs api.hyperliquid.xyz.\n- firstReleased is 30 March 2023, the creation date of the hyperliquid-python-sdk repository, the earliest first-hand date found; the oldest PyPI release in the feed is 0.1.12 on 20 September 2023. The mainnet launch date was not read first-hand.\n- lastRelease is 4 June 2026, the Python SDK's 0.24.0. The API gains actions without dated notes, so the service may be more current than that date shows.\n- Judgement call on kind. Listed as http-api on the hosted REST API, the surface an agent calls; the order book and clearinghouse run on the Hyperliquid chain, recorded under details. pypiWeekly comes from pypistats.org, a third-party aggregate; no score rests on it.\n- Our own products. It doesn't do LocalGhost's or letme's job. Graded the normal way.\n\n### Sources\n\n- docs robots.txt: \u003chttps://hyperliquid.gitbook.io/robots.txt\u003e (seen 2026-11-03)\n- docs llms.txt index: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt\u003e (seen 2026-11-03)\n- API overview (base URLs, SDKs): \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api\u003e (seen 2026-11-03)\n- info endpoint: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint.md\u003e (seen 2026-11-03)\n- exchange endpoint (actions, agent-signable variants, dead man's switch): \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/exchange-endpoint.md\u003e (seen 2026-11-03)\n- nonces and API wallets: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/nonces-and-api-wallets.md\u003e (seen 2026-11-03)\n- signing: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/signing.md\u003e (seen 2026-11-03)\n- rate limits and user limits: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/rate-limits-and-user-limits.md\u003e (seen 2026-11-03)\n- error responses: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/error-responses.md\u003e (seen 2026-11-03)\n- fees: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees.md\u003e (seen 2026-11-03)\n- testnet faucet: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/onboarding/testnet-faucet.md\u003e (seen 2026-11-03)\n- HyperCore overview: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/overview.md\u003e (seen 2026-11-03)\n- API servers: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/api-servers.md\u003e (seen 2026-11-03)\n- core contributors: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors.md\u003e (seen 2026-11-03)\n- bug bounty programme: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/bug-bounty-program.md\u003e (seen 2026-11-03)\n- audits: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/audits.md\u003e (seen 2026-11-03)\n- official MCP registry search: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=hyperliquid\u003e (seen 2026-11-03)\n- hyperliquid-dex repositories: \u003chttps://api.github.com/orgs/hyperliquid-dex/repos?per_page=100\u0026sort=pushed\u003e (seen 2026-11-03)\n- Python SDK repository (stars, issues) and shallow clone: \u003chttps://api.github.com/repos/hyperliquid-dex/hyperliquid-python-sdk\u003e (seen 2026-11-03)\n- PyPI release feed: \u003chttps://pypi.org/rss/project/hyperliquid-python-sdk/releases.xml\u003e (seen 2026-11-03)\n- PyPI downloads (pypistats, third-party aggregate): \u003chttps://pypistats.org/api/packages/hyperliquid-python-sdk/recent\u003e (seen 2026-11-03)\n- terms (script-drawn, title only): \u003chttps://app.hyperliquid.xyz/terms\u003e (seen 2026-11-03)\n- terms on the apex domain (403): \u003chttps://hyperliquid.xyz/terms\u003e (seen 2026-11-03)\n- security.txt (403): \u003chttps://hyperliquid.xyz/.well-known/security.txt\u003e (seen 2026-11-03)\n- RDAP for hyperliquid.xyz: \u003chttps://rdap.centralnic.com/xyz/domain/hyperliquid.xyz\u003e (seen 2026-11-03)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/hyperliquid/history.json\n\n- 2026-11-03: graded 50 D (methodology 0.7)\n\n## Who's behind it (provenance 32/100, checked 2026-11-03)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | not found | 0/20 |\n| Domain age | hyperliquid.xyz, registered 2022-10-15 (4 years) | 7/15 |\n| Endpoint on the vendor's domain | hyperliquid.xyz | 15/15 |\n| Terms of service | published, but our reader couldn't read it | 7/10 |\n| Privacy policy | not found | 0/10 |\n| Status page | not found | 0/10 |\n| Changelog | not found | 0/10 |\n| security.txt | could not be fetched | 0/10 |\n| People named | not researched yet | n/a |\n| Support route | help pages, a community | 5/5 |\n\nNo legal entity found on a readable page. The docs name Hyperliquid Labs (self-funded) and the Hyper Foundation (bug bounty); app.hyperliquid.xyz/terms and hyperfoundation.org draw by script and hyperliquid.xyz/terms answered 403.\n\nRDAP gives hyperliquid.xyz a registration date of 15 October 2022, registrar Squarespace Domains.\n\nNo status page found; status.hyperliquid.xyz did not resolve and the docs link none. No changelog; the docs have no dated release notes.\n\nhttps://hyperliquid.xyz/.well-known/security.txt answered 403, so security.txt is unknown. The docs' bug bounty page gives bugbounty@hyperfoundation.org.\n\nhyperliquid.gitbook.io/robots.txt allows everything with Content-Signal ai-input=yes; hyperliquid.xyz/robots.txt allows everything.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://app.hyperliquid.xyz/terms), read 2026-11-03. Our reader couldn't read it (the page has 1 words of text without a browser, so the document is drawn by script or sits elsewhere).\n\n\n**Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0.\n\n\n## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)\n\n### Key people\n\n- No people named yet.\n- Note: The docs' core contributors page says Hyperliquid Labs is led by Jeff and iliensinc, classmates from Harvard, linking an X account for Jeff (chameleon_jeff) and giving no surname for either, so nobody is listed; a surname is never guessed. No other Hyperliquid page read names a person with a role, and the Hyper Foundation's site draws by script. Ownership is private from the same page, which says Hyperliquid Labs is self-funded and has not taken any external capital, so no investors are listed; the search for funding stopped there.\n- Hyperliquid Labs: GitHub https://github.com/hyperliquid-dex\n\n### Getting support\n\n- Discord: https://discord.gg/tPw7CXqYAe\n- Help: https://hyperliquid.gitbook.io/hyperliquid-docs/support/read-me-support-guide\n- General contact: bugbounty@hyperfoundation.org\n- Sources: https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors.md, https://hyperliquid.gitbook.io/hyperliquid-docs/bug-bounty-program.md, https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt, https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/master/SECURITY.md, https://api.github.com/orgs/hyperliquid-dex/repos?per_page=100\u0026sort=pushed\n\n## Live (updated 2026-11-04 15:54 UTC)\n\n- security.txt: unknown\n- Always current: https://www.anchorterminal.com/api/v1/live/hyperliquid.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Perpetuals taker fee, tier 0 | 0.04% | percentage fee | 0.045% of notional; maker 0.015% |\n| Spot taker fee, tier 0 | 0.07% | percentage fee | 0.070% of notional; maker 0.040% |\n| Bridge withdrawal | $1 | per transaction | $1 per withdrawal to the bridge contract |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- API wallets approved by the master account can only sign trading actions; withdrawals and external transfers need the user's own key\n- Numeric rate limits per IP and per address, with weights per request type and a paid `reserveRequestWeight` top-up\n- Fees published per tier from 0.045% taker and 0.015% maker on perpetuals, with maker rebates and staking discounts\n- A testnet at api.hyperliquid-testnet.xyz with the same API and a faucet of 1,000 mock USDC for addresses that have deposited on mainnet\n- Client order IDs (`cloid`), `expiresAfter`, `noop` and a `scheduleCancel` dead man's switch for safe retries\n\n## Weaknesses\n\n- No official MCP server; the 23 registry entries are all third parties, several selling data by x402\n- No OpenAPI file, no changelog, no API versioning and no status page found\n- The terms of use and privacy policy at app.hyperliquid.xyz draw by script and hyperliquid.xyz/terms answered 403, so the restricted jurisdictions are unchecked\n- Order errors are message strings without codes, and the docs give no 429 or Retry-After guidance beyond one request every 10 seconds when limited\n- The official Python SDK is marked Alpha, last released 4 June 2026, with 112 open issues\n\n\n\n## Before you call it (notes for agents)\n\n1. Generate a fresh API wallet, approve it with `approveAgent` with a name and expiry, sign with it, and query with the master address, never the agent address\n2. Use the Python SDK's `sign_l1_action` and `sign_user_signed_action`; mixing the two, field order in msgpack or an uppercase address gives \"User or API Wallet ... does not exist\"\n3. Set a `cloid` on every order and read the per-order `statuses` array; one batch-level error rejects the whole batch\n4. Budget address limits by volume (one action per 1 USDC traded after 10,000); batch orders to lower IP weight, and use WebSocket for data\n5. Arm `scheduleCancel` before unattended trading so open orders are cancelled if the agent stops\n\n## Connect\n\nInstall:\n\n```bash\npip install hyperliquid-python-sdk\n```\n\nFirst request:\n\n```bash\ncurl -X POST https://api.hyperliquid.xyz/info -H 'Content-Type: application/json' -d '{\"type\":\"l2Book\",\"coin\":\"BTC\"}'\n```\n\nThrough letme: https://letme.dev/hyperliquid. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Gemini Exchange API | BB | 74.6 | 70 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/gemini-exchange.md |\n| Kraken API | BB | 71 | 159 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/kraken.md |\n| dYdX | B | 69.5 | 221 | exchange.derivatives, exchange.market-data, exchange.balances, exchange.transfers, exchange.staking, market.crypto, wallet.onchain | no | https://www.anchorterminal.com/tools/dydx.md |\n| OKX API | B | 64.3 | 413 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/okx.md |\n| Binance API | B | 63.2 | 448 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/binance.md |\n| Bitfinex API | C | 58.4 | 687 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/bitfinex.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- No official MCP server. The official MCP registry's search for hyperliquid lists 23 entries from 12 third-party publishers (Tessera, HLWatch, Junct, Pipeworx, Ironflow, Reins and others), none from hyperliquid-dex or a hyperliquid.xyz namespace; the docs and the hyperliquid-dex GitHub organisation have none (source: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=hyperliquid\u003e)\n- What runs on chain. HyperCore holds the margin and matching engine state under HyperBFT consensus; the docs say the order book is not run off chain. API servers follow a node, keep the state locally, answer REST and WebSocket queries and forward signed transactions to a node, returning the result once the block commits (source: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/api-servers.md\u003e)\n- Rate limits are 1,200 weight a minute per IP (orders weigh 1 plus one per 40 batched items, most info requests 20, l2Book and clearinghouseState 2) and, per address, one action per 1 USDC traded since inception after an initial 10,000, with a rate-limited address allowed one request every 10 seconds. Open orders are capped at 1,000 plus one per 5 million USDC of volume up to 5,000 (source: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/rate-limits-and-user-limits.md\u003e)\n- API wallets only sign. Withdrawals (`withdraw3`), USDC and spot sends are user-signed actions; `agentSendAsset` and `cDeposit2` are the agent-signable variants, and `agentSendAsset` requires the destination to match the source address (source: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/exchange-endpoint.md\u003e)\n- The order response lists a status per order, `resting`, `filled` or `error` with a message string such as \"Order must have minimum value of $10.\"; `scheduleCancel` is a dead man's switch (at most 10 triggers a day) and `noop` burns a nonce to cancel in-flight actions (source: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/error-responses.md\u003e)\n- hyperliquid-python-sdk 0.24.0 on PyPI (4 June 2026), MIT, classifier Alpha, 42 releases since 0.1.12 on 20 September 2023, with CI on Python 3.9 and 3.13 (source: \u003chttps://pypi.org/rss/project/hyperliquid-python-sdk/releases.xml\u003e)\n- The docs say Hyperliquid Labs is self-funded and has taken no external capital, led by Jeff and iliensinc; the bug bounty is run by the Hyper Foundation with rewards in USDC up to under 1 million for critical bugs (source: \u003chttps://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors.md\u003e)\n\n- #19 of 21 in Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Compare\n\n- [Bitfinex API vs Hyperliquid](https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.md): C 58.4 vs D 50\n- [Bitget vs Hyperliquid](https://www.anchorterminal.com/compare/bitget-vs-hyperliquid.md): D 53.9 vs D 50\n- [Bithumb Open API vs Hyperliquid](https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.md): D 50.6 vs D 50\n- [Bitstamp API vs Hyperliquid](https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.md): D 50.4 vs D 50\n- [Bybit vs Hyperliquid](https://www.anchorterminal.com/compare/bybit-vs-hyperliquid.md): C 57.3 vs D 50\n- [Crypto.com Exchange API vs Hyperliquid](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid.md): D 46.8 vs D 50\n- [Gate vs Hyperliquid](https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid.md): C 56.4 vs D 50\n- [Gemini Exchange API vs Hyperliquid](https://www.anchorterminal.com/compare/gemini-exchange-vs-hyperliquid.md): BB 74.6 vs D 50\n- [HTX trading API vs Hyperliquid](https://www.anchorterminal.com/compare/htx-vs-hyperliquid.md): E 43.3 vs D 50\n- [Hyperliquid vs Upbit Open API](https://www.anchorterminal.com/compare/hyperliquid-vs-upbit.md): D 50 vs C 54.7\n- [Binance API vs Hyperliquid](https://www.anchorterminal.com/compare/binance-vs-hyperliquid.md): B 63.2 vs D 50\n- [Coinbase Advanced Trade API vs Hyperliquid](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid.md): C 61.7 vs D 50\n- [Coinbase MCP server (Coinbase for Agents) vs Hyperliquid](https://www.anchorterminal.com/compare/coinbase-mcp-vs-hyperliquid.md): C 60 vs D 50\n- [Hyperliquid vs Uniswap Trading API](https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.md): D 50 vs B 63.3\n- [Deribit vs Hyperliquid](https://www.anchorterminal.com/compare/deribit-vs-hyperliquid.md): C 59 vs D 50\n- [dYdX vs Hyperliquid](https://www.anchorterminal.com/compare/dydx-vs-hyperliquid.md): B 69.5 vs D 50\n- [Hyperliquid vs Kraken API](https://www.anchorterminal.com/compare/hyperliquid-vs-kraken.md): D 50 vs BB 71\n- [Hyperliquid vs KuCoin](https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin.md): D 50 vs D 53.9\n- [Hyperliquid vs MEXC API](https://www.anchorterminal.com/compare/hyperliquid-vs-mexc.md): D 50 vs C 56.3\n- [Hyperliquid vs OKX API](https://www.anchorterminal.com/compare/hyperliquid-vs-okx.md): D 50 vs B 64.3\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on hyperliquid.xyz or one of its subdomains, or the README at the root of github.com/hyperliquid-dex/hyperliquid-python-sdk. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"hyperliquid\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/hyperliquid\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/hyperliquid.svg\" alt=\"Hyperliquid on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Hyperliquid on Anchor Terminal](https://www.anchorterminal.com/badges/hyperliquid.svg)](https://www.anchorterminal.com/tools/hyperliquid)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/hyperliquid\"\u003eHyperliquid on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Hyperliquid is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/hyperliquid-dark.png\n- Light: https://www.anchorterminal.com/assets/share/hyperliquid-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Crypto exchanges", "url": "https://www.anchorterminal.com/categories/crypto-exchanges" }, { "name": "Hyperliquid", "url": "" } ], "description": "Hyperliquid is a perpetuals and spot exchange whose order book runs on its own chain. Agents trade through the REST info and exchange endpoints and WebSocket at api.hyperliquid.xyz, signing with a wallet key or an approved API wallet.", "facts": [ "rank #1018 of 1349", "OAuth or key auth", "0 desk reviews" ], "h1": "Hyperliquid", "image": "https://www.anchorterminal.com/assets/og/tools-hyperliquid.png", "path": "/tools/hyperliquid", "published": "2026-10-01", "section": "tools", "title": "Hyperliquid review (2026): pricing, alternatives and grade D", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/tools/hyperliquid" }, "tokens": { "markdown": 8800, "slim": 2480 }, "version": 1 }