{ "data": { "a": { "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": 966, "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" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "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 } }, "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" }, "area": "payments", "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 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/hyperliquid.json", "live": { "slug": "hyperliquid", "versions": [ { "registry": "github", "name": "hyperliquid-dex/hyperliquid-python-sdk", "version": "0.24.0", "released": "2026-06-04", "seenAt": "2026-11-04T20:25:22.19916859Z" }, { "registry": "pypi", "name": "hyperliquid-python-sdk", "version": "0.24.0", "released": "2026-06-04", "seenAt": "2026-11-04T20:25:21.979453168Z" } ], "githubStars": 1876, "pypiWeekly": 167497, "securityTxt": { "url": "https://hyperliquid.xyz/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-04T15:54:05.956872316Z" }, "updatedAt": "2026-11-04T20:25:22.19916859Z" } }, "answer": "KuCoin scores 53.9 (D) on agent readiness against Hyperliquid's 50 (D), and leads in 4 of 7 scored categories. Hyperliquid leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing.", "b": { "slug": "kucoin", "name": "KuCoin", "vendor": "KuCoin", "vendorUrl": "https://www.kucoin.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "KuCoin is a centralised crypto exchange for spot, margin and futures trading and earn products, reached through its REST and WebSocket API with a unified trading account, an official multi-language SDK and read-only agent skills. It runs no MCP server.", "url": "https://www.anchorterminal.com/tools/kucoin", "markdownUrl": "https://www.anchorterminal.com/tools/kucoin.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kucoin.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kucoin.json", "dns": "kucoin.grade.anchorterminal.com", "repo": "https://github.com/Kucoin/kucoin-universal-sdk", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API key, secret and user-set passphrase minted under API Management after a browser sign-up and identity verification, with KC-API-KEY, KC-API-SIGN (HMAC-SHA256 over timestamp, method, path and body, Base64), KC-API-TIMESTAMP, KC-API-PASSPHRASE (the passphrase signed with the secret) and KC-API-KEY-VERSION headers. Permissions are General (read-only), Spot, Margin, Futures, Earn, Withdrawal, FlexTransfers, LeadtradeFutures and Unified; Withdrawal and FlexTransfers need an IP allow-list, and a key with trading permissions and no IP bound has trading disabled or is deleted after 30 days of inactivity. General-only keys do not expire (https://www.kucoin.com/docs-new/authentication, https://www.kucoin.com/docs-new/ and https://www.kucoin.com/support/360015102174, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing; trades carry KuCoin's fees. Spot fee levels are set against a base of 0.1 per cent maker and 0.1 per cent taker at LV0, with some pairs priced differently and a 20 per cent discount when fees are paid in KCS. The futures LV0 rate (0.02 per cent maker and 0.06 per cent taker per a KuCoin blog post) sits in an image on the support page and was not read first-hand. The fee page itself loads its table by script (https://www.kucoin.com/support/360015188494 and https://www.kucoin.com/en-eu/support/360015207133, checked 2026-11-03).", "priceSummary": "0.1% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the skills hub or the fee pages (checked 2026-11-03).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 55, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.kucoin.com/docs-new/", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "closed-source", "api-key", "usage-priced", "no-status-page", "agent-skills", "python", "typescript", "go", "java", "php" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 53.9, "grade": "D", "agentReady": false, "rank": 825, "ranked": true, "rankOf": 1349, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 62, "maintenance": 73, "payments": 35, "reliability": 45, "schema": 60, "security": 55, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "KuCoin publishes pooled rate limits with remaining and reset headers, scoped keys where withdrawals and transfers need an IP allow-list, an official SDK in five languages and read-only agent skills. It runs no MCP server, has no sandbox, status page or OpenAPI file, and its terms name no legal entity.", "bestFor": "An agent trading spot, margin and futures in a person's KuCoin account outside the restricted list, with no sandbox and no MCP server, so through the SDK or raw REST.", "strengths": [ "Rate limits published per VIP level with per-endpoint weights and gw-ratelimit-limit, gw-ratelimit-remaining and gw-ratelimit-reset headers, 429000 on breach", "API key permissions split into General, Spot, Margin, Futures, Earn, Withdrawal, FlexTransfers and Unified, with Withdrawal and FlexTransfers requiring an IP allow-list", "Official kucoin-universal-sdk for Go, Python, Node.js, PHP and Java, MIT, pushed September 2026", "Unified Trading Account API V2 with a dated changelog and unified six-digit error codes", "Seven read-only agent skills in a KuCoin-published repository, installable with the skills CLI" ], "weaknesses": [ "No official MCP server; the registry's `kucoin` entry is a third party's keyless market-data package", "No sandbox or testnet; the legacy sandbox is offline and the docs point to mocking", "No status page, incident history or SLA found", "No OpenAPI file or llms.txt; the SDK page links a Postman workspace instead", "Terms name no company and fix the Turks and Caicos Islands as the deemed place of every transaction; the privacy policy names only KuCoin" ], "agentNotes": [ "Mint a key with General only for research; add Spot or Futures only with an IP allow-list, since unbound trading keys are disabled after 30 days of inactivity", "Send a UUID clientOid on every order and keep it for the retry, and read the order back by clientOid before placing again", "Budget requests by weight against gw-ratelimit-remaining and sleep for gw-ratelimit-reset milliseconds on 429000; sub-accounts share the pool", "There is no sandbox, so rehearse with the smallest order size on a dedicated sub-account", "Use the UTA V2 endpoints and hosts; the Classic API loses endpoints without notice, as the margin credit endpoints did on 21 October 2026" ], "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": 53.9 } ], "editorialScores": { "ergonomics": 62, "maintenance": 73, "payments": 35, "reliability": 45, "schema": 60, "security": 55, "transparency": 52 }, "provenanceScore": 55, "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 } }, "connect": { "http": "curl https://api.kucoin.com/api/v1/market/orderbook/level1?symbol=BTC-USDT" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/kucoin" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, LV0 maker or taker", "unit": "pct", "usd": 0.1, "note": "base rate; some pairs differ, 20 per cent off in KCS" } ], "provenance": { "legalEntity": "", "domain": "kucoin.com", "domainRegistered": "2013-11-13", "endpointOnVendorDomain": true, "terms": "https://www.kucoin.com/support/47185419968079", "privacy": "https://www.kucoin.com/legal/privacy-policy", "statusPage": "", "changelog": "https://www.kucoin.com/docs-new/change-log", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms (last updated 29 October 2026) name no company; they deem all activity to occur in the Turks and Caicos Islands under its law with SIAC arbitration. /legal/terms-of-use is a shell page that links the support article recorded here. The privacy policy (dated 10/05/2026 in an ambiguous format) names KuCoin as controller with no company name.", "www.kucoin.com/robots.txt disallows assets, order and account paths only; docs-new and support pages are allowed.", "RDAP gives kucoin.com a registration date of 13 November 2013 (Amazon Registrar).", "https://www.kucoin.com/.well-known/security.txt answers 404. No status page found; status.kucoin.com does not resolve and the docs link none.", "The docs changelog is dated by day; its newest entry is dated 6 November 2026, three days ahead of the check, and the newest past entry 2 November 2026." ], "score": 55 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kucoin.json", "live": { "slug": "kucoin", "versions": [ { "registry": "github", "name": "Kucoin/kucoin-universal-sdk", "version": "v1.3.1", "released": "2026-05-29", "seenAt": "2026-11-04T20:29:03.487838607Z" } ], "githubStars": 55, "securityTxt": { "url": "https://kucoin.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:04.738329571Z" }, "updatedAt": "2026-11-04T20:29:03.487838607Z" } }, "edges": [ { "by": 34, "category": "maintenance", "leads": "kucoin", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed hosted service. The changelog's newest past entry is 2 November 2026 and the universal SDK was pushed 15 September (30). Nine dated changelog entries since 5 August 2026 (20). A Telegram API group (t.me/KuCoin_API) and api@kucoin.com for limit requests, no public issue tracker for the API; the SDK repository's issues were not checked (10 of 25). Official SDKs current in five languages, no MCP registry presence (13 of 15). No package health signal checked (0 of 10). 73." }, "scores": { "a": 39, "b": 73 } }, { "by": 28, "category": "transparency", "leads": "kucoin", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The editorial half. A closed hosted service with terms that are clear on use, liability and law but name no company (12 of 30). The privacy policy gives retention periods by purpose and provider (2 years after closure, 14 months for Firebase, 3 years for Jumio, 5 years for Sumsub) and names 41 services, with no data centre locations (22 of 30). Endpoints are removed and fields deprecated in dated changelog entries with no notice period or policy (8 of 20). Third parties named by service, locations not stated beyond transfers around the globe (10 of 20). 52." }, "scores": { "a": 26, "b": 54 } }, { "by": 20, "category": "payments", "leads": "hyperliquid", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No machine payment protocol (0). The spot base fee is stated in support articles without login, the futures base rate and the full tier table sit in images or behind script (15 of 20). Market data needs no key, no card is asked for at sign-up (20). A person registers, verifies identity and mints the key in a browser (0). 35." }, "scores": { "a": 55, "b": 35 } }, { "by": 18, "category": "schema", "leads": "kucoin", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "No OpenAPI or other machine-readable contract was found; the docs link a Postman workspace and the universal SDK is generated from an internal spec (8 of 25). No llms.txt; the skills hub ships Markdown SKILL.md files with endpoint tables for seven product areas, read-only (6 of 10). One docs page per endpoint with a description, permission and weight, but no when-to-use guidance (12 of 20). Typed parameter tables with enums for type and side and required flags (11 of 15). Request and response examples per endpoint and a unified six-digit error code scheme introduced with V2 (10 of 15). Dated changelog with V1 to V2 versioning (13 of 15). 60." }, "scores": { "a": 42, "b": 60 } }, { "by": 9, "category": "security", "leads": "hyperliquid", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "API key with a user-set passphrase, HMAC-SHA256 signing, nine permission groups, IP allow-lists required for Withdrawal and FlexTransfers, trading keys without an IP disabled after 30 days of inactivity, revocation on the management page; no OAuth and no expiry on General keys (24 of 30). A General-only key is a true read-only mode and withdrawals are a separate permission; no confirmation step for writes beyond the key scope (12 of 20). Tools return the exchange's own data (10). The API key info endpoint shows permissions and IP lists; no per-call audit log was found (5 of 15). No security.txt, no disclosure policy or bounty on a page we could read, a whistleblower notice on the legal page (4 of 20). 55." }, "scores": { "a": 64, "b": 55 } }, { "by": 8, "category": "ergonomics", "leads": "hyperliquid", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Read for the API alone, since there is no MCP server. Responses take limit and cursor parameters on list endpoints and the order book depth is a parameter (14 of 25). Pagination and symbol filters on orders, fills and ledgers (15 of 20). Codes and messages per response, with the V2 scheme claimed to be clearer; the rate-limit page's own examples contradict its table, which costs an agent a turn (12 of 20). clientOid on orders makes retries safe; no MCP annotations to read (10 of 20). Three required fields on a spot order, official SDKs in five languages (11 of 15). 62." }, "scores": { "a": 70, "b": 62 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Hyperliquid Labs", "b": "KuCoin", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "none", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-06-04", "b": "2026-11-02", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "1.9k stars, 167k PyPI/wk", "b": "55 stars", "name": "Popularity" } ], "faq": [ { "answer": "KuCoin scores 53.9 (D) on agent readiness against Hyperliquid's 50 (D), and leads in 4 of 7 scored categories. Hyperliquid leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Hyperliquid or KuCoin?" }, { "answer": "Hyperliquid takes an API key or an OAuth sign-in. KuCoin needs an API key.", "question": "Do Hyperliquid and KuCoin need an API key?" }, { "answer": "No hosted endpoint is listed for Hyperliquid. No hosted endpoint is listed for KuCoin.", "question": "Can an agent call Hyperliquid and KuCoin without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 70 against 62", "Security \u0026 auth, 64 against 55", "Payments \u0026 pricing, 55 against 35" ], "also": null, "goodFor": "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.", "slug": "hyperliquid", "watchFor": "No official MCP server; the 23 registry entries are all third parties, several selling data by x402" }, { "aheadOn": [ "Reliability, 45 against 40", "Schema \u0026 documentation, 60 against 42", "Maintenance \u0026 community, 73 against 39", "Transparency \u0026 trust, 54 against 26" ], "also": null, "goodFor": "An agent trading spot, margin and futures in a person's KuCoin account outside the restricted list, with no sandbox and no MCP server, so through the SDK or raw REST.", "slug": "kucoin", "watchFor": "No official MCP server; the registry's `kucoin` entry is a third party's keyless market-data package" } ], "history": null, "job": { "capability": "exchange.derivatives", "name": "Exchange derivatives" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.json", "title": "Bitfinex API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.json", "title": "Bitfinex API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-hyperliquid.json", "title": "Bitget vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bitget-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-kucoin.json", "title": "Bitget vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitget-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.json", "title": "Bithumb Open API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-kucoin.json", "title": "Bithumb Open API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bithumb-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.json", "title": "Bitstamp API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.json", "title": "Bitstamp API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-hyperliquid.json", "title": "Bybit vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bybit-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-kucoin.json", "title": "Bybit vs KuCoin", "url": "https://www.anchorterminal.com/compare/bybit-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid.json", "title": "Crypto.com Exchange API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.json", "title": "Crypto.com Exchange API vs KuCoin", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid.json", "title": "Gate vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-kucoin.json", "title": "Gate vs KuCoin", "url": "https://www.anchorterminal.com/compare/gate-io-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-hyperliquid.json", "title": "Gemini Exchange API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin.json", "title": "Gemini Exchange API vs KuCoin", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-hyperliquid.json", "title": "HTX trading API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/htx-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-kucoin.json", "title": "HTX trading API vs KuCoin", "url": "https://www.anchorterminal.com/compare/htx-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-upbit.json", "title": "Hyperliquid vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-mexc.json", "title": "KuCoin vs MEXC API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-okx.json", "title": "KuCoin vs OKX API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-uniswap.json", "title": "KuCoin vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-upbit.json", "title": "KuCoin vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-hyperliquid.json", "title": "Binance API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/binance-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-kucoin.json", "title": "Binance API vs KuCoin", "url": "https://www.anchorterminal.com/compare/binance-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid.json", "title": "Coinbase Advanced Trade API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin.json", "title": "Coinbase Advanced Trade API vs KuCoin", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-hyperliquid.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin.json", "title": "Coinbase MCP server (Coinbase for Agents) vs KuCoin", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.json", "title": "Hyperliquid vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-kucoin.json", "title": "Kraken API vs KuCoin", "url": "https://www.anchorterminal.com/compare/kraken-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-hyperliquid.json", "title": "Deribit vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/deribit-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-kucoin.json", "title": "Deribit vs KuCoin", "url": "https://www.anchorterminal.com/compare/deribit-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-hyperliquid.json", "title": "dYdX vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/dydx-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-kucoin.json", "title": "dYdX vs KuCoin", "url": "https://www.anchorterminal.com/compare/dydx-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-kraken.json", "title": "Hyperliquid vs Kraken API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-mexc.json", "title": "Hyperliquid vs MEXC API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-okx.json", "title": "Hyperliquid vs OKX API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-okx" } ], "panel": null, "scores": [ { "by": 5, "edge": "kucoin", "hyperliquid": 40, "key": "reliability", "kucoin": 45, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "edge": "kucoin", "hyperliquid": 42, "key": "schema", "kucoin": 60, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 8, "edge": "hyperliquid", "hyperliquid": 70, "key": "ergonomics", "kucoin": 62, "name": "Agent ergonomics", "weight": 13 }, { "by": 9, "edge": "hyperliquid", "hyperliquid": 64, "key": "security", "kucoin": 55, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "hyperliquid", "hyperliquid": 55, "key": "payments", "kucoin": 35, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 34, "edge": "kucoin", "hyperliquid": 39, "key": "maintenance", "kucoin": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 28, "edge": "kucoin", "hyperliquid": 26, "key": "transparency", "kucoin": 54, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "KuCoin scores 53.9 (D) on agent readiness against Hyperliquid's 50 (D), and leads in 4 of 7 scored categories. Hyperliquid leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing. Both do exchange derivatives.", "tasks": null, "tutorials": [], "verdicts": { "hyperliquid": "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.", "kucoin": "KuCoin publishes pooled rate limits with remaining and reset headers, scoped keys where withdrawals and transfers need an IP allow-list, an official SDK in five languages and read-only agent skills. It runs no MCP server, has no sandbox, status page or OpenAPI file, and its terms name no legal entity." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin", "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin.min.md" }, "markdown": "KuCoin scores 53.9 (D) on agent readiness against Hyperliquid's 50 (D), and leads in 4 of 7 scored categories. Hyperliquid leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing. Both do exchange derivatives.\n\n- Hyperliquid: grade D, 50/100, rank #966 of 1349. Markdown https://www.anchorterminal.com/tools/hyperliquid.md · JSON https://www.anchorterminal.com/api/v1/tools/hyperliquid.json\n- KuCoin: grade D, 53.9/100, rank #825 of 1349. Markdown https://www.anchorterminal.com/tools/kucoin.md · JSON https://www.anchorterminal.com/api/v1/tools/kucoin.json\n- 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## Which one, for what\n\n### Hyperliquid (D)\n\nGood for: 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.\n\nAhead on:\n- Agent ergonomics, 70 against 62\n- Security \u0026 auth, 64 against 55\n- Payments \u0026 pricing, 55 against 35\n\nWatch for: No official MCP server; the 23 registry entries are all third parties, several selling data by x402\n\n### KuCoin (D)\n\nGood for: An agent trading spot, margin and futures in a person's KuCoin account outside the restricted list, with no sandbox and no MCP server, so through the SDK or raw REST.\n\nAhead on:\n- Reliability, 45 against 40\n- Schema \u0026 documentation, 60 against 42\n- Maintenance \u0026 community, 73 against 39\n- Transparency \u0026 trust, 54 against 26\n\nWatch for: No official MCP server; the registry's `kucoin` entry is a third party's keyless market-data package\n\n\n## Why the edge\n\n### Maintenance \u0026 community: KuCoin +34\n\n- Hyperliquid (39): 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- KuCoin (73): Read as a closed hosted service. The changelog's newest past entry is 2 November 2026 and the universal SDK was pushed 15 September (30). Nine dated changelog entries since 5 August 2026 (20). A Telegram API group (t.me/KuCoin_API) and api@kucoin.com for limit requests, no public issue tracker for the API; the SDK repository's issues were not checked (10 of 25). Official SDKs current in five languages, no MCP registry presence (13 of 15). No package health signal checked (0 of 10). 73.\n\n### Transparency \u0026 trust: KuCoin +28\n\n- Hyperliquid (26): 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- KuCoin (54): The editorial half. A closed hosted service with terms that are clear on use, liability and law but name no company (12 of 30). The privacy policy gives retention periods by purpose and provider (2 years after closure, 14 months for Firebase, 3 years for Jumio, 5 years for Sumsub) and names 41 services, with no data centre locations (22 of 30). Endpoints are removed and fields deprecated in dated changelog entries with no notice period or policy (8 of 20). Third parties named by service, locations not stated beyond transfers around the globe (10 of 20). 52.\n\n### Payments \u0026 pricing: Hyperliquid +20\n\n- Hyperliquid (55): 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- KuCoin (35): No machine payment protocol (0). The spot base fee is stated in support articles without login, the futures base rate and the full tier table sit in images or behind script (15 of 20). Market data needs no key, no card is asked for at sign-up (20). A person registers, verifies identity and mints the key in a browser (0). 35.\n\n### Schema \u0026 documentation: KuCoin +18\n\n- Hyperliquid (42): 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- KuCoin (60): No OpenAPI or other machine-readable contract was found; the docs link a Postman workspace and the universal SDK is generated from an internal spec (8 of 25). No llms.txt; the skills hub ships Markdown SKILL.md files with endpoint tables for seven product areas, read-only (6 of 10). One docs page per endpoint with a description, permission and weight, but no when-to-use guidance (12 of 20). Typed parameter tables with enums for type and side and required flags (11 of 15). Request and response examples per endpoint and a unified six-digit error code scheme introduced with V2 (10 of 15). Dated changelog with V1 to V2 versioning (13 of 15). 60.\n\n### Security \u0026 auth: Hyperliquid +9\n\n- Hyperliquid (64): 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- KuCoin (55): API key with a user-set passphrase, HMAC-SHA256 signing, nine permission groups, IP allow-lists required for Withdrawal and FlexTransfers, trading keys without an IP disabled after 30 days of inactivity, revocation on the management page; no OAuth and no expiry on General keys (24 of 30). A General-only key is a true read-only mode and withdrawals are a separate permission; no confirmation step for writes beyond the key scope (12 of 20). Tools return the exchange's own data (10). The API key info endpoint shows permissions and IP lists; no per-call audit log was found (5 of 15). No security.txt, no disclosure policy or bounty on a page we could read, a whistleblower notice on the legal page (4 of 20). 55.\n\n### Agent ergonomics: Hyperliquid +8\n\n- Hyperliquid (70): 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- KuCoin (62): Read for the API alone, since there is no MCP server. Responses take limit and cursor parameters on list endpoints and the order book depth is a parameter (14 of 25). Pagination and symbol filters on orders, fills and ledgers (15 of 20). Codes and messages per response, with the V2 scheme claimed to be clearer; the rate-limit page's own examples contradict its table, which costs an agent a turn (12 of 20). clientOid on orders makes retries safe; no MCP annotations to read (10 of 20). Three required fields on a spot order, official SDKs in five languages (11 of 15). 62.\n\n## Score by category\n\n| Category | Weight | Hyperliquid | KuCoin | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 45 | KuCoin +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 42 | 60 | KuCoin +18 |\n| Agent ergonomics | 13% (16.2 this run) | 70 | 62 | Hyperliquid +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 55 | Hyperliquid +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 35 | Hyperliquid +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 39 | 73 | KuCoin +34 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 26 | 54 | KuCoin +28 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50 · D** | **53.9 · D** | |\n\n## Facts side by side\n\n| Fact | Hyperliquid | KuCoin |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Hyperliquid Labs | KuCoin |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\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 | none |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | 2026-06-04 | 2026-11-02 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 1.9k stars, 167k PyPI/wk | 55 stars |\n\n## Verdicts\n\n**Hyperliquid.** 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.\n\n**KuCoin.** KuCoin publishes pooled rate limits with remaining and reset headers, scoped keys where withdrawals and transfers need an IP allow-list, an official SDK in five languages and read-only agent skills. It runs no MCP server, has no sandbox, status page or OpenAPI file, and its terms name no legal entity.\n\n## Before you call either\n\n### Hyperliquid\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### KuCoin\n\n1. Mint a key with General only for research; add Spot or Futures only with an IP allow-list, since unbound trading keys are disabled after 30 days of inactivity\n2. Send a UUID clientOid on every order and keep it for the retry, and read the order back by clientOid before placing again\n3. Budget requests by weight against gw-ratelimit-remaining and sleep for gw-ratelimit-reset milliseconds on 429000; sub-accounts share the pool\n4. There is no sandbox, so rehearse with the smallest order size on a dedicated sub-account\n5. Use the UTA V2 endpoints and hosts; the Classic API loses endpoints without notice, as the margin credit endpoints did on 21 October 2026\n\n## Questions\n\n### Which is better for AI agents, Hyperliquid or KuCoin?\n\nKuCoin scores 53.9 (D) on agent readiness against Hyperliquid's 50 (D), and leads in 4 of 7 scored categories. Hyperliquid leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing.\n\n### Do Hyperliquid and KuCoin need an API key?\n\nHyperliquid takes an API key or an OAuth sign-in. KuCoin needs an API key.\n\n### Can an agent call Hyperliquid and KuCoin without installing anything?\n\nNo hosted endpoint is listed for Hyperliquid. No hosted endpoint is listed for KuCoin.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hyperliquid\", \"b\": \"kucoin\"}`. From a terminal: `anchor compare hyperliquid kucoin`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hyperliquid.json and https://www.anchorterminal.com/api/v1/tools/kucoin.json\n\n## Other comparisons with Hyperliquid or KuCoin\n\n- [Bitfinex API vs Hyperliquid](https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.md)\n- [Bitfinex API vs KuCoin](https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.md)\n- [Bitget vs Hyperliquid](https://www.anchorterminal.com/compare/bitget-vs-hyperliquid.md)\n- [Bitget vs KuCoin](https://www.anchorterminal.com/compare/bitget-vs-kucoin.md)\n- [Bithumb Open API vs Hyperliquid](https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.md)\n- [Bithumb Open API vs KuCoin](https://www.anchorterminal.com/compare/bithumb-vs-kucoin.md)\n- [Bitstamp API vs Hyperliquid](https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.md)\n- [Bitstamp API vs KuCoin](https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.md)\n- [Bybit vs Hyperliquid](https://www.anchorterminal.com/compare/bybit-vs-hyperliquid.md)\n- [Bybit vs KuCoin](https://www.anchorterminal.com/compare/bybit-vs-kucoin.md)\n- [Crypto.com Exchange API vs Hyperliquid](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid.md)\n- [Crypto.com Exchange API vs KuCoin](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.md)\n- [Gate vs Hyperliquid](https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid.md)\n- [Gate vs KuCoin](https://www.anchorterminal.com/compare/gate-io-vs-kucoin.md)\n- [Gemini Exchange API vs Hyperliquid](https://www.anchorterminal.com/compare/gemini-exchange-vs-hyperliquid.md)\n- [Gemini Exchange API vs KuCoin](https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin.md)\n- [HTX trading API vs Hyperliquid](https://www.anchorterminal.com/compare/htx-vs-hyperliquid.md)\n- [HTX trading API vs KuCoin](https://www.anchorterminal.com/compare/htx-vs-kucoin.md)\n- [Hyperliquid vs Upbit Open API](https://www.anchorterminal.com/compare/hyperliquid-vs-upbit.md)\n- [KuCoin vs MEXC API](https://www.anchorterminal.com/compare/kucoin-vs-mexc.md)\n- [KuCoin vs OKX API](https://www.anchorterminal.com/compare/kucoin-vs-okx.md)\n- [KuCoin vs Uniswap Trading API](https://www.anchorterminal.com/compare/kucoin-vs-uniswap.md)\n- [KuCoin vs Upbit Open API](https://www.anchorterminal.com/compare/kucoin-vs-upbit.md)\n- [Binance API vs Hyperliquid](https://www.anchorterminal.com/compare/binance-vs-hyperliquid.md)\n- [Binance API vs KuCoin](https://www.anchorterminal.com/compare/binance-vs-kucoin.md)\n- [Coinbase Advanced Trade API vs Hyperliquid](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid.md)\n- [Coinbase Advanced Trade API vs KuCoin](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Hyperliquid](https://www.anchorterminal.com/compare/coinbase-mcp-vs-hyperliquid.md)\n- [Coinbase MCP server (Coinbase for Agents) vs KuCoin](https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin.md)\n- [Hyperliquid vs Uniswap Trading API](https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.md)\n- [Kraken API vs KuCoin](https://www.anchorterminal.com/compare/kraken-vs-kucoin.md)\n- [Deribit vs Hyperliquid](https://www.anchorterminal.com/compare/deribit-vs-hyperliquid.md)\n- [Deribit vs KuCoin](https://www.anchorterminal.com/compare/deribit-vs-kucoin.md)\n- [dYdX vs Hyperliquid](https://www.anchorterminal.com/compare/dydx-vs-hyperliquid.md)\n- [dYdX vs KuCoin](https://www.anchorterminal.com/compare/dydx-vs-kucoin.md)\n- [Hyperliquid vs Kraken API](https://www.anchorterminal.com/compare/hyperliquid-vs-kraken.md)\n- [Hyperliquid vs MEXC API](https://www.anchorterminal.com/compare/hyperliquid-vs-mexc.md)\n- [Hyperliquid vs OKX API](https://www.anchorterminal.com/compare/hyperliquid-vs-okx.md)\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": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Hyperliquid vs KuCoin", "url": "" } ], "description": "KuCoin scores 53.9 (D) to Hyperliquid's 50 (D) for exchange derivatives. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Hyperliquid D 50", "KuCoin D 53.9", "scores" ], "h1": "Hyperliquid vs KuCoin", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/hyperliquid-vs-kucoin", "published": "2026-10-01", "section": "tools", "title": "Hyperliquid vs KuCoin for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin" }, "tokens": { "markdown": 4750, "slim": 2630 }, "version": 1 }