{ "data": { "a": { "slug": "htx", "name": "HTX trading API", "vendor": "HTX", "vendorUrl": "https://www.htx.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "HTX, the exchange formerly Huobi, runs REST and WebSocket APIs for spot and derivatives trading, balances, transfers and withdrawals, authenticated with HMAC-signed API keys that carry read, trade and withdraw permissions.", "url": "https://www.anchorterminal.com/tools/htx", "markdownUrl": "https://www.anchorterminal.com/tools/htx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/htx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/htx.json", "dns": "htx.grade.anchorterminal.com", "repo": "https://github.com/HuobiRDCenter", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API keys made in the account's API Management page after a browser sign-up and identity check. Requests are signed with HMAC SHA256 (SignatureVersion 2) over the query string, with AccessKeyId, Timestamp and the Signature sent as query parameters; the secret never travels. A main account key carries Read, Trade and Withdraw permissions, a sub-user key Read and Trade only. A key can be bound to up to 20 IP addresses, and the docs say a key without IP binding expires after 90 days (https://huobiapi.github.io/docs/spot/v1/en/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "Trading fees per order. The fee schedule at htx.com/fee is drawn by script and answered our reader with no text, so no rate is recorded; third-party guides give 0.2 per cent maker and taker at the base tier, which is a lead and not a source. Public market data needs no key and no account (https://www.htx.com/fee/, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs or on the pages that loaded (checked 2026-11-03). Trading fees are taken from each fill.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 684, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://huobiapi.github.io/docs/spot/v1/en/", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "api-key", "closed-source", "usage-priced", "python", "java", "go", "no-status-page" ], "lastRelease": "2026-10-21", "graded": true, "anchor": { "graded": true, "score": 43.3, "grade": "E", "agentReady": false, "rank": 1166, "ranked": true, "rankOf": 1349, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 57, "payments": 15, "reliability": 38, "schema": 40, "security": 51, "transparency": 25 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.", "bestFor": "Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.", "strengths": [ "Key permissions split into Read, Trade and Withdraw, sub-user keys without Withdraw, and up to 20 bound IP addresses per key", "Rate limits published per endpoint with numbers, and remaining-quota headers on every response", "A client-order-id unique within 8 hours on orders and idempotent on withdrawals, so a retry doesn't double an order", "Official SDKs in Python, Java, C++, C# and Go, the contract ones pushed on 21 October 2026" ], "weaknesses": [ "No official MCP server; the only one in the MCP registry is a third party's read-only ticker server", "The testnet is shut down, so order logic can only be tried with real funds", "The public API reference is still branded Huobi with a last changelog entry of June 2022, and HTX's newer docs are drawn by script", "No status page, no SLA and no documented 429 or Retry-After behaviour", "The fee schedule, user agreement, privacy policy and restricted-country list couldn't be read, so none is recorded first-hand" ], "agentNotes": [ "Ask the operator for a key with Read and Trade only and bound to your IP addresses; a key without IP binding expires after 90 days", "Send a fresh client-order-id of up to 64 characters with every order and reuse it only on retry; a repeat within 8 hours answers invalid.client.order.id", "Watch X-HB-RateLimit-Requests-Remain and pace at under 100 order calls per 2 seconds per UID; limits are shared by every key on the account", "There is no testnet; try order logic with the smallest size the market allows", "Confirm the person's country is served before trading; the restricted list in the user agreement couldn't be read here" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 57, "payments": 15, "reliability": 38, "schema": 40, "security": 51, "transparency": 15 }, "provenanceScore": 34, "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.huobi.pro/market/tickers" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/htx" }, "area": "payments", "provenance": { "legalEntity": "", "domain": "htx.com", "domainRegistered": "1995-12-13", "endpointOnVendorDomain": false, "terms": "https://www.htx.com/en-in/support/360000298561/", "privacy": "", "statusPage": "", "changelog": "https://huobiapi.github.io/docs/spot/v1/en/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The legal entity is unread. The HTX Platform User Agreement and every other page on www.htx.com answered our reader with no text on 3 November 2026 (the pages are drawn by script), so the terms, privacy policy, fee schedule and about page were not read. Terms URL recorded from a search result's title.", "RDAP gives htx.com a registration date of 13 December 1995, long before the exchange took the name in 2023; the domain was acquired, not registered, by the exchange.", "The API endpoint api.huobi.pro is on the old huobi.pro domain, not htx.com.", "www.htx.com/robots.txt allows / and disallows account paths (finance/account, user-center/security and the like). www.huobi.com/robots.txt disallows everything and was not read further. huobiapi.github.io has no robots.txt.", "https://www.htx.com/.well-known/security.txt answered no text; recorded as none. status.htx.com does not resolve." ], "score": 34 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/htx.json", "live": { "slug": "htx", "securityTxt": { "url": "https://htx.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:20.226147452Z" }, "updatedAt": "2026-11-04T15:54:20.226147452Z" } }, "answer": "Kraken API scores 71 (BB) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.", "b": { "slug": "kraken", "name": "Kraken API", "vendor": "Payward, Inc.", "vendorUrl": "https://docs.kraken.com/api/", "kind": "http-api", "category": "crypto-exchanges", "summary": "Kraken's exchange APIs cover spot, tokenised US stocks, forex and futures over REST, WebSocket and FIX, with rate limits by client tier, a self-service futures demo and kraken-cli, an open-source CLI whose kraken-mcp binary is a local MCP server.", "url": "https://www.anchorterminal.com/tools/kraken", "markdownUrl": "https://www.anchorterminal.com/tools/kraken.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kraken.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kraken.json", "dns": "kraken.grade.anchorterminal.com", "repo": "https://github.com/krakenfx/kraken-cli", "license": "Proprietary hosted service under Kraken's Global Terms of Service (30 October 2026). kraken-cli, which carries the kraken-mcp server, is MIT", "transports": [ "stdio" ], "packages": [], "auth": "mixed", "authNotes": "Spot API key and private key, signed with HMAC-SHA512 over the path, nonce and POST data, sent as API-Key and API-Sign. Permissions per key are Query Funds, Deposit Funds, Withdraw Funds, Query Open Orders \u0026 Trades, Query Closed Orders \u0026 Trades, Modify Orders, Cancel/Close Orders, Query Ledger Entries and Export Data, with optional Key Expiration, IP Address Restriction, a custom nonce window and a WebSocket interface setting. Futures keys are separate. kraken auth login signs in with OAuth (authorisation code with PKCE) in a browser and saves a restricted spot key with no withdrawal rights that expires after at most 90 days, or a read-only one with --read-only (https://support.kraken.com/hc/en-us/articles/360000919966, https://github.com/krakenfx/kraken-cli, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Kraken Pro spot fees at the lowest 30-day volume tier are 0.40 per cent maker and 0.80 per cent taker, stablecoin, pegged token and FX pairs 0.20 per cent each way, and futures 0.02 per cent maker and 0.05 per cent taker. Public market data, paper trading in kraken-cli and the futures demo need no account.", "priceSummary": "0.4% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the CLI or the MCP docs (checked 2026-11-03).", "endpoints": [] }, "toolCount": 152, "popularity": { "githubStars": 795, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.kraken.com/api/", "llmsTxt": "https://raw.githubusercontent.com/krakenfx/kraken-cli/main/llms.txt", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "official", "closed-source", "api-key", "oauth", "mcp", "cli", "llms-txt", "status-page", "bug-bounty", "rust", "go", "usage-priced", "no-card", "mit" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 71, "grade": "BB", "agentReady": true, "rank": 159, "ranked": true, "rankOf": 1349, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 81, "payments": 40, "reliability": 67, "schema": 80, "security": 80, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Kraken pairs a documented REST, WebSocket and FIX API with the open-source kraken-cli, whose kraken-mcp server gates 33 dangerous tools behind approval and signs in by OAuth with a no-withdrawal key. Spot has no self-service sandbox, no OpenAPI file was found, and a 59-minute connectivity outage hit every interface on 30 October 2026.", "bestFor": "An agent that trades spot, xStocks, forex or futures on a person's Kraken account from a local machine, with paper trading to test first and an approval gate on live orders.", "strengths": [ "Official local MCP server with 152 typed tools in services, destructive_hint on dangerous tools and an elicitation approval before each unless disabled", "OAuth sign-in from the CLI mints a restricted spot key with no withdrawal rights that expires within 90 days, or a read-only key", "Rate limits published with numbers by client tier for REST and the matching engine, shared across REST, WebSocket and FIX", "Fees published without login, 0.40 per cent maker and 0.80 per cent taker at the lowest Pro tier, 0.02 and 0.05 on futures", "Dated changelog of 120 entries with deprecations announced by date, a Statuspage site with API components and a valid security.txt" ], "weaknesses": [ "No self-service spot sandbox; the spot UAT environment is on request through an account manager, and paper trading lives in the CLI", "No OpenAPI file was found for the REST API; the machine-readable contract is the CLI's tool catalogue", "Spot and derivatives clients could not connect or submit orders on any interface for 59 minutes on 30 October 2026", "The CLI's feedback tool can upload a local file it names with no approval step, so the docs say to drop it for agents reading untrusted input", "The terms bar bots, scripts and third-party applications on Kraken's content without written consent, alongside the documented API" ], "agentNotes": [ "Start kraken-mcp with -s market,paper,feedback or the default services; add trade only with a least-privilege key, and never pass --allow-dangerous on an agent that reads untrusted input", "Ask the person to run kraken auth login in their own terminal; it needs a browser and saves a no-withdrawal key that expires in 90 days at most", "Send a fresh --cl-ord-id on each order and run it with --validate first; after a network error look the order up before sending it again", "Keep the nonce strictly increasing per key and stay under the tier's counter, since EAPI:Rate limit exceeded has no Retry-After header", "Test strategies in a paper workspace, which fills at live prices with no account, before a live workspace" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71 } ], "editorialScores": { "ergonomics": 79, "maintenance": 81, "payments": 40, "reliability": 67, "schema": 80, "security": 80, "transparency": 36 }, "provenanceScore": 94, "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": "curl --proto '=https' --tlsv1.2 -LsSf https://github.com/krakenfx/kraken-cli/releases/latest/download/kraken-cli-installer.sh | sh", "http": "curl https://api.kraken.com/0/public/Ticker?pair=XBTUSD", "claudeCode": "claude mcp add --scope user kraken -- kraken-mcp -s market,paper,feedback", "config": { "mcpServers": { "kraken": { "args": [ "-s", "market,paper,feedback" ], "command": "kraken-mcp" } } } }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/kraken" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, maker, tier 1", "unit": "pct", "usd": 0.4, "note": "Kraken Pro, under $10,000 30-day volume" }, { "item": "Spot trade, taker, tier 1", "unit": "pct", "usd": 0.8, "note": "Kraken Pro, under $10,000 30-day volume" }, { "item": "Futures trade, maker, tier 1", "unit": "pct", "usd": 0.02, "note": "under $5M 30-day volume" }, { "item": "Futures trade, taker, tier 1", "unit": "pct", "usd": 0.05, "note": "under $5M 30-day volume" } ], "provenance": { "legalEntity": "Payward, Inc.", "domain": "kraken.com", "domainRegistered": "2000-04-03", "endpointOnVendorDomain": true, "terms": "https://www.kraken.com/legal/global-terms", "privacy": "https://www.kraken.com/legal/privacy", "statusPage": "https://status.kraken.com", "changelog": "https://docs.kraken.com/api/docs/change-log", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The Global Terms of Service (last updated 30 October 2026) name Payward Interactive, Inc., Payward Ltd., Bit Trade Pty Limited and Payward Trading Ltd as contracting entities by region under California law; the site footer is © 2011 to 2026 Payward, Inc. The privacy notice was linked from the legal hub and not read.", "RDAP gives kraken.com a registration date of 3 April 2000, before the exchange's 2011 founding.", "https://www.kraken.com/.well-known/security.txt names bugbounty@kraken.com and a bug bounty policy page on kraken.com, expiring 13 February 2027.", "www.kraken.com, docs.kraken.com and support.kraken.com robots.txt disallow only /u/ and /lp/ (docs allows all but /cdn-cgi/ and /_next/).", "status.kraken.com is a Statuspage site; its history page renders by script, so incidents were read from its incidents.json feed, which reached back to 4 September 2026." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kraken.json", "live": { "slug": "kraken", "vendorStatus": { "page": "https://status.kraken.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-04T20:05:18.866095768Z" }, "securityTxt": { "url": "https://kraken.com/.well-known/security.txt", "state": "valid", "expires": "2027-02-13T00:00:00.000Z", "checkedAt": "2026-11-04T15:54:35.804472383Z" }, "updatedAt": "2026-11-04T20:05:18.866095768Z" } }, "edges": [ { "by": 40, "category": "schema", "leads": "kraken", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI or other machine-readable contract found in the docs or the GitHub accounts (0). No llms.txt on htx.com, and the readable reference is a static page (0). Each endpoint states its purpose and parameters, without when-to-use guidance (12 of 20). Parameter tables carry types, required flags and enums for order types and states (10 of 15). Request and response examples throughout and error-code tables with messages (11 of 15). Versions v1 and v2 are mixed in one reference whose last changelog entry is 24 June 2022, while HTX's newer docs on htx.com couldn't be read (7 of 15). 0 + 0 + 12 + 10 + 11 + 7 = 40.", "b": "No OpenAPI file was found for the REST API in the docs read; the CLI's agents/tool-catalog.json gives JSON Schema inputs for all 188 commands and the 152 MCP tools (15 of 25). The docs serve Markdown twins such as quickstart.md and the CLI ships llms.txt, AGENTS.md and CONTEXT.md (10). Endpoint pages and guides on order lifecycle, errors and rate limits say what each call does, with less on when not to use one (15 of 20). Enums for order types, time in force and flags, and enums and required fields in the tool catalogue (12 of 15). Python, Node.js and cURL examples, an errors guide and the CLI's error-catalog.json with retry guidance (13 of 15). A changelog of 120 dated entries with deprecations dated (15). 15 + 10 + 15 + 12 + 13 + 15 = 80." }, "scores": { "a": 40, "b": 80 } }, { "by": 40, "category": "transparency", "leads": "kraken", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed service whose user agreement exists but couldn't be read (script-drawn pages), so the licence clarity is unknown rather than unclear (10 of 30). The privacy policy was not read (0 of 30, unchecked). The testnet shutdown and the 2022 changelog entries are dated, with no deprecation policy (5 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 5 + 0 = 15.", "b": "The editorial half. A closed service with clear terms naming regional Payward entities under California law; the CLI is MIT (15 of 30). The privacy notice was not read (5 of 30). The changelog dates deprecations and the terms carry a last-updated date (16 of 20). No subprocessor or data-location statement read (0 of 20). 15 + 5 + 16 + 0 = 36." }, "scores": { "a": 25, "b": 65 } }, { "by": 29, "category": "reliability", "leads": "kraken", "name": "Reliability", "reasons": { "a": "Read with the hosted lines. No status page found; status.htx.com does not resolve and nothing on htx.com was readable (0). No readable incident history (5). Rate limits documented per endpoint with numbers, 100 order calls per 2 seconds per UID and so on, with remaining-quota headers (15). No 429 or Retry-After behaviour is documented and the only limit error named is 1006 for conditional orders; a client-order-id unique within 8 hours and an idempotent withdrawal id give safe retries on writes (8 of 15). No SLA found (0). The spot and swap APIs are generally available (10). 0 + 5 + 15 + 8 + 0 + 10 = 38.", "b": "Read with the hosted lines on the spot API. status.kraken.com is a Statuspage site with REST, WebSocket and FIX components (20). The incidents feed read covers 4 September to 3 November 2026. On 30 October spot and derivatives clients could not connect or submit orders across web, mobile, REST, WebSocket and FIX for 59 minutes 39 seconds, rated minor by Kraken; on 28 October some FIX clients were rejected on reconnection for 1 hour 59 minutes while other interfaces worked; the futures engine was degraded for 3 minutes on 13 October. A whole-exchange order outage 21 seconds short of an hour is read as one major (10 of 30). Numeric limits per key by tier and per pair for the matching engine (15). EAPI:Rate limit exceeded and EService:Throttled with a retry timestamp, a client order id and a validate flag on orders, but no Retry-After header (12 of 15). No SLA (0). Generally available (10). 20 + 10 + 15 + 12 + 0 + 10 = 67." }, "scores": { "a": 38, "b": 67 } }, { "by": 29, "category": "security", "leads": "kraken", "name": "Security \u0026 auth", "reasons": { "a": "HMAC-signed keys with Read, Trade and Withdraw permissions, sub-user keys without Withdraw, up to 20 bound IPs, revocation in the account and a 90-day expiry without IP binding. The AccessKeyId and the HMAC signature travel as query parameters; the secret does not, so no deduction for a secret in the URL (24 of 30). Read-only keys and withdraw-free keys exist; no server-side confirmation for orders or withdrawals (14 of 20). The API returns the exchange's own data, no untrusted content (10). No per-call log or key-use history found for the operator (3 of 15). No security.txt, disclosure policy or certification found on the pages that loaded (0 of 20). 24 + 14 + 10 + 3 + 0 = 51.", "b": "Keys with nine named permissions, optional expiry, IP restriction and nonce window, plus an OAuth sign-in from the CLI (authorisation code with PKCE, public client) that mints a no-withdrawal key expiring within 90 days or a read-only key (30). Read-only and no-withdrawal keys, position limits and pair allowlists in account settings, and MCP approval prompts for 33 dangerous tools (18 of 20). The API returns no untrusted content; the CLI docs warn that the feedback tool uploads a local file without approval (10). Keys and their permissions are listed in settings and ledgers record activity, but no per-call log for the operator was found (6 of 15). A valid security.txt, a bug bounty policy page, SECURITY.md and a secure SDLC workflow in the CLI; certifications not read (16 of 20). 30 + 18 + 10 + 6 + 16 = 80." }, "scores": { "a": 51, "b": 80 } }, { "by": 25, "category": "payments", "leads": "kraken", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). The fee schedule at htx.com/fee is drawn by script and answered no text, so no price is recorded first-hand (0 of 20, unchecked). Public market data needs no key, card or account; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser and pass identity checks (0). 0 + 0 + 15 + 0 = 15.", "b": "No machine payment protocol (0). Maker and taker fees by tier published without login (20). Public market data, paper trading and the futures demo need no account or card (20). A person signs up, verifies and mints a key or approves the OAuth sign-in (0). 0 + 20 + 20 + 0 = 40." }, "scores": { "a": 15, "b": 40 } }, { "by": 24, "category": "maintenance", "leads": "kraken", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The readable changelog ends on 24 June 2022, but the official contract SDKs were pushed on 21 October 2026 and the spot SDKs in April and July 2026, so the API surface is still being maintained; judgement call (20 of 30). SDK pushes on 30 July, 23 August and 21 October 2026 are commits, not releases (10 of 20). A Telegram group for API support and a support centre, neither tested; GitHub issues not read (8 of 15). Official SDKs in five languages (15). No CI seen, dependencies not checked (4 of 10). 20 + 10 + 8 + 15 + 4 = 57.", "b": "Read as a closed service with an open-source client. Changelog entry of 27 October 2026 and kraken-cli v0.5.1 on 29 October (30). Fourteen changelog entries since 19 August 2026 and CLI tags on 6 and 7 August and 28 and 29 October (20). A public changelog, api@kraken.com, a status page and a CLI repository merging pull requests at the end of October; issue replies not read (11 of 15). An official Rust SDK pushed in October 2026 and a Go module from January; the MCP server is not in the official registry (12 of 15). The CLI has release and secure SDLC workflows, deny.toml and a pinned toolchain; the SDK's CI not read (8 of 10). 30 + 20 + 11 + 12 + 8 = 81." }, "scores": { "a": 57, "b": 81 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HTX", "b": "Payward, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary hosted service under Kraken's Global Terms of Service (30 October 2026). kraken-cli, which carries the kraken-mcp server, is MIT", "name": "Licence" }, { "a": "0", "b": "152", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-21", "b": "2026-10-29", "name": "Last release" }, { "a": "no date given", "b": "2026-10-30", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-10-21", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "684 stars", "b": "795 stars", "name": "Popularity" } ], "faq": [ { "answer": "Kraken API scores 71 (BB) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.", "question": "Which is better for AI agents, HTX trading API or Kraken API?" }, { "answer": "HTX trading API needs an API key. Kraken API takes an API key or an OAuth sign-in.", "question": "Do HTX trading API and Kraken API need an API key?" }, { "answer": "No hosted endpoint is listed for HTX trading API. Kraken API runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call HTX trading API and Kraken API without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.", "slug": "htx", "watchFor": "No official MCP server; the only one in the MCP registry is a third party's read-only ticker server" }, { "aheadOn": [ "Reliability, 67 against 38", "Schema \u0026 documentation, 80 against 40", "Agent ergonomics, 79 against 69", "Security \u0026 auth, 80 against 51", "Payments \u0026 pricing, 40 against 15", "Maintenance \u0026 community, 81 against 57", "Transparency \u0026 trust, 65 against 25" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine", "Free to start without a card" ], "goodFor": "An agent that trades spot, xStocks, forex or futures on a person's Kraken account from a local machine, with paper trading to test first and an approval gate on live orders.", "slug": "kraken", "watchFor": "No self-service spot sandbox; the spot UAT environment is on request through an account manager, and paper trading lives in the CLI" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-htx.json", "title": "Bitfinex API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-kraken.json", "title": "Bitfinex API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-htx.json", "title": "Bitget vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitget-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-kraken.json", "title": "Bitget vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitget-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-htx.json", "title": "Bithumb Open API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-kraken.json", "title": "Bithumb Open API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-htx.json", "title": "Bitstamp API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken.json", "title": "Bitstamp API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-htx.json", "title": "Bybit vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bybit-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-kraken.json", "title": "Bybit vs Kraken API", "url": "https://www.anchorterminal.com/compare/bybit-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.json", "title": "Crypto.com Exchange API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken.json", "title": "Crypto.com Exchange API vs Kraken API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-htx.json", "title": "Gate vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-kraken.json", "title": "Gate vs Kraken API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.json", "title": "Gemini Exchange API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken.json", "title": "Gemini Exchange API vs Kraken API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken" }, { "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/htx-vs-mexc.json", "title": "HTX trading API vs MEXC API", "url": "https://www.anchorterminal.com/compare/htx-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-okx.json", "title": "HTX trading API vs OKX API", "url": "https://www.anchorterminal.com/compare/htx-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-uniswap.json", "title": "HTX trading API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/htx-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-upbit.json", "title": "HTX trading API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/htx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-htx.json", "title": "Binance API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/binance-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-kraken.json", "title": "Binance API vs Kraken API", "url": "https://www.anchorterminal.com/compare/binance-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.json", "title": "Coinbase Advanced Trade API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken.json", "title": "Coinbase Advanced Trade API vs Kraken API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kraken.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Kraken API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kraken" }, { "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/kraken-vs-mexc.json", "title": "Kraken API vs MEXC API", "url": "https://www.anchorterminal.com/compare/kraken-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-okx.json", "title": "Kraken API vs OKX API", "url": "https://www.anchorterminal.com/compare/kraken-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-uniswap.json", "title": "Kraken API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/kraken-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-upbit.json", "title": "Kraken API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/kraken-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-htx.json", "title": "Deribit vs HTX trading API", "url": "https://www.anchorterminal.com/compare/deribit-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-kraken.json", "title": "Deribit vs Kraken API", "url": "https://www.anchorterminal.com/compare/deribit-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-htx.json", "title": "dYdX vs HTX trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-kraken.json", "title": "dYdX vs Kraken API", "url": "https://www.anchorterminal.com/compare/dydx-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-kraken.json", "title": "Hyperliquid vs Kraken API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-kraken" } ], "panel": null, "scores": [ { "by": 29, "edge": "kraken", "htx": 38, "key": "reliability", "kraken": 67, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 40, "edge": "kraken", "htx": 40, "key": "schema", "kraken": 80, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 10, "edge": "kraken", "htx": 69, "key": "ergonomics", "kraken": 79, "name": "Agent ergonomics", "weight": 13 }, { "by": 29, "edge": "kraken", "htx": 51, "key": "security", "kraken": 80, "name": "Security \u0026 auth", "weight": 14 }, { "by": 25, "edge": "kraken", "htx": 15, "key": "payments", "kraken": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 24, "edge": "kraken", "htx": 57, "key": "maintenance", "kraken": 81, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 40, "edge": "kraken", "htx": 25, "key": "transparency", "kraken": 65, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Kraken API scores 71 (BB) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "htx": "HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.", "kraken": "Kraken pairs a documented REST, WebSocket and FIX API with the open-source kraken-cli, whose kraken-mcp server gates 33 dangerous tools behind approval and signs in by OAuth with a no-withdrawal key. Spot has no self-service sandbox, no OpenAPI file was found, and a 59-minute connectivity outage hit every interface on 30 October 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/htx-vs-kraken", "json": "https://www.anchorterminal.com/compare/htx-vs-kraken.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/htx-vs-kraken.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/htx-vs-kraken.min.md" }, "markdown": "Kraken API scores 71 (BB) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category. Both do exchange market data.\n\n- HTX trading API: grade E, 43.3/100, rank #1166 of 1349. Markdown https://www.anchorterminal.com/tools/htx.md · JSON https://www.anchorterminal.com/api/v1/tools/htx.json\n- Kraken API: grade BB, 71/100, rank #159 of 1349. Markdown https://www.anchorterminal.com/tools/kraken.md · JSON https://www.anchorterminal.com/api/v1/tools/kraken.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### HTX trading API (E)\n\nGood for: Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.\n\nWatch for: No official MCP server; the only one in the MCP registry is a third party's read-only ticker server\n\n### Kraken API (BB)\n\nGood for: An agent that trades spot, xStocks, forex or futures on a person's Kraken account from a local machine, with paper trading to test first and an approval gate on live orders.\n\nAhead on:\n- Reliability, 67 against 38\n- Schema \u0026 documentation, 80 against 40\n- Agent ergonomics, 79 against 69\n- Security \u0026 auth, 80 against 51\n- Payments \u0026 pricing, 40 against 15\n- Maintenance \u0026 community, 81 against 57\n- Transparency \u0026 trust, 65 against 25\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: No self-service spot sandbox; the spot UAT environment is on request through an account manager, and paper trading lives in the CLI\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Kraken API +40\n\n- HTX trading API (40): No OpenAPI or other machine-readable contract found in the docs or the GitHub accounts (0). No llms.txt on htx.com, and the readable reference is a static page (0). Each endpoint states its purpose and parameters, without when-to-use guidance (12 of 20). Parameter tables carry types, required flags and enums for order types and states (10 of 15). Request and response examples throughout and error-code tables with messages (11 of 15). Versions v1 and v2 are mixed in one reference whose last changelog entry is 24 June 2022, while HTX's newer docs on htx.com couldn't be read (7 of 15). 0 + 0 + 12 + 10 + 11 + 7 = 40.\n- Kraken API (80): No OpenAPI file was found for the REST API in the docs read; the CLI's agents/tool-catalog.json gives JSON Schema inputs for all 188 commands and the 152 MCP tools (15 of 25). The docs serve Markdown twins such as quickstart.md and the CLI ships llms.txt, AGENTS.md and CONTEXT.md (10). Endpoint pages and guides on order lifecycle, errors and rate limits say what each call does, with less on when not to use one (15 of 20). Enums for order types, time in force and flags, and enums and required fields in the tool catalogue (12 of 15). Python, Node.js and cURL examples, an errors guide and the CLI's error-catalog.json with retry guidance (13 of 15). A changelog of 120 dated entries with deprecations dated (15). 15 + 10 + 15 + 12 + 13 + 15 = 80.\n\n### Transparency \u0026 trust: Kraken API +40\n\n- HTX trading API (25): The editorial half. A closed service whose user agreement exists but couldn't be read (script-drawn pages), so the licence clarity is unknown rather than unclear (10 of 30). The privacy policy was not read (0 of 30, unchecked). The testnet shutdown and the 2022 changelog entries are dated, with no deprecation policy (5 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 5 + 0 = 15.\n- Kraken API (65): The editorial half. A closed service with clear terms naming regional Payward entities under California law; the CLI is MIT (15 of 30). The privacy notice was not read (5 of 30). The changelog dates deprecations and the terms carry a last-updated date (16 of 20). No subprocessor or data-location statement read (0 of 20). 15 + 5 + 16 + 0 = 36.\n\n### Reliability: Kraken API +29\n\n- HTX trading API (38): Read with the hosted lines. No status page found; status.htx.com does not resolve and nothing on htx.com was readable (0). No readable incident history (5). Rate limits documented per endpoint with numbers, 100 order calls per 2 seconds per UID and so on, with remaining-quota headers (15). No 429 or Retry-After behaviour is documented and the only limit error named is 1006 for conditional orders; a client-order-id unique within 8 hours and an idempotent withdrawal id give safe retries on writes (8 of 15). No SLA found (0). The spot and swap APIs are generally available (10). 0 + 5 + 15 + 8 + 0 + 10 = 38.\n- Kraken API (67): Read with the hosted lines on the spot API. status.kraken.com is a Statuspage site with REST, WebSocket and FIX components (20). The incidents feed read covers 4 September to 3 November 2026. On 30 October spot and derivatives clients could not connect or submit orders across web, mobile, REST, WebSocket and FIX for 59 minutes 39 seconds, rated minor by Kraken; on 28 October some FIX clients were rejected on reconnection for 1 hour 59 minutes while other interfaces worked; the futures engine was degraded for 3 minutes on 13 October. A whole-exchange order outage 21 seconds short of an hour is read as one major (10 of 30). Numeric limits per key by tier and per pair for the matching engine (15). EAPI:Rate limit exceeded and EService:Throttled with a retry timestamp, a client order id and a validate flag on orders, but no Retry-After header (12 of 15). No SLA (0). Generally available (10). 20 + 10 + 15 + 12 + 0 + 10 = 67.\n\n### Security \u0026 auth: Kraken API +29\n\n- HTX trading API (51): HMAC-signed keys with Read, Trade and Withdraw permissions, sub-user keys without Withdraw, up to 20 bound IPs, revocation in the account and a 90-day expiry without IP binding. The AccessKeyId and the HMAC signature travel as query parameters; the secret does not, so no deduction for a secret in the URL (24 of 30). Read-only keys and withdraw-free keys exist; no server-side confirmation for orders or withdrawals (14 of 20). The API returns the exchange's own data, no untrusted content (10). No per-call log or key-use history found for the operator (3 of 15). No security.txt, disclosure policy or certification found on the pages that loaded (0 of 20). 24 + 14 + 10 + 3 + 0 = 51.\n- Kraken API (80): Keys with nine named permissions, optional expiry, IP restriction and nonce window, plus an OAuth sign-in from the CLI (authorisation code with PKCE, public client) that mints a no-withdrawal key expiring within 90 days or a read-only key (30). Read-only and no-withdrawal keys, position limits and pair allowlists in account settings, and MCP approval prompts for 33 dangerous tools (18 of 20). The API returns no untrusted content; the CLI docs warn that the feedback tool uploads a local file without approval (10). Keys and their permissions are listed in settings and ledgers record activity, but no per-call log for the operator was found (6 of 15). A valid security.txt, a bug bounty policy page, SECURITY.md and a secure SDLC workflow in the CLI; certifications not read (16 of 20). 30 + 18 + 10 + 6 + 16 = 80.\n\n### Payments \u0026 pricing: Kraken API +25\n\n- HTX trading API (15): No machine payment protocol (0). The fee schedule at htx.com/fee is drawn by script and answered no text, so no price is recorded first-hand (0 of 20, unchecked). Public market data needs no key, card or account; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser and pass identity checks (0). 0 + 0 + 15 + 0 = 15.\n- Kraken API (40): No machine payment protocol (0). Maker and taker fees by tier published without login (20). Public market data, paper trading and the futures demo need no account or card (20). A person signs up, verifies and mints a key or approves the OAuth sign-in (0). 0 + 20 + 20 + 0 = 40.\n\n### Maintenance \u0026 community: Kraken API +24\n\n- HTX trading API (57): Read as a closed service. The readable changelog ends on 24 June 2022, but the official contract SDKs were pushed on 21 October 2026 and the spot SDKs in April and July 2026, so the API surface is still being maintained; judgement call (20 of 30). SDK pushes on 30 July, 23 August and 21 October 2026 are commits, not releases (10 of 20). A Telegram group for API support and a support centre, neither tested; GitHub issues not read (8 of 15). Official SDKs in five languages (15). No CI seen, dependencies not checked (4 of 10). 20 + 10 + 8 + 15 + 4 = 57.\n- Kraken API (81): Read as a closed service with an open-source client. Changelog entry of 27 October 2026 and kraken-cli v0.5.1 on 29 October (30). Fourteen changelog entries since 19 August 2026 and CLI tags on 6 and 7 August and 28 and 29 October (20). A public changelog, api@kraken.com, a status page and a CLI repository merging pull requests at the end of October; issue replies not read (11 of 15). An official Rust SDK pushed in October 2026 and a Go module from January; the MCP server is not in the official registry (12 of 15). The CLI has release and secure SDLC workflows, deny.toml and a pinned toolchain; the SDK's CI not read (8 of 10). 30 + 20 + 11 + 12 + 8 = 81.\n\n## Score by category\n\n| Category | Weight | HTX trading API | Kraken API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 38 | 67 | Kraken API +29 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 80 | Kraken API +40 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 79 | Kraken API +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 80 | Kraken API +29 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 40 | Kraken API +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 57 | 81 | Kraken API +24 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 25 | 65 | Kraken API +40 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **43.3 · E** | **71 · BB** | |\n\n## Facts side by side\n\n| Fact | HTX trading API | Kraken API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HTX | Payward, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary hosted service under Kraken's Global Terms of Service (30 October 2026). kraken-cli, which carries the kraken-mcp server, is MIT |\n| Tools exposed | 0 | 152 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2026-10-21 | 2026-10-29 |\n| Terms last updated | no date given | 2026-10-30 |\n| Privacy policy last updated | no document linked | 2026-10-21 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 684 stars | 795 stars |\n\n## Verdicts\n\n**HTX trading API.** HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.\n\n**Kraken API.** Kraken pairs a documented REST, WebSocket and FIX API with the open-source kraken-cli, whose kraken-mcp server gates 33 dangerous tools behind approval and signs in by OAuth with a no-withdrawal key. Spot has no self-service sandbox, no OpenAPI file was found, and a 59-minute connectivity outage hit every interface on 30 October 2026.\n\n## Before you call either\n\n### HTX trading API\n\n1. Ask the operator for a key with Read and Trade only and bound to your IP addresses; a key without IP binding expires after 90 days\n2. Send a fresh client-order-id of up to 64 characters with every order and reuse it only on retry; a repeat within 8 hours answers invalid.client.order.id\n3. Watch X-HB-RateLimit-Requests-Remain and pace at under 100 order calls per 2 seconds per UID; limits are shared by every key on the account\n4. There is no testnet; try order logic with the smallest size the market allows\n5. Confirm the person's country is served before trading; the restricted list in the user agreement couldn't be read here\n\n### Kraken API\n\n1. Start kraken-mcp with -s market,paper,feedback or the default services; add trade only with a least-privilege key, and never pass --allow-dangerous on an agent that reads untrusted input\n2. Ask the person to run kraken auth login in their own terminal; it needs a browser and saves a no-withdrawal key that expires in 90 days at most\n3. Send a fresh --cl-ord-id on each order and run it with --validate first; after a network error look the order up before sending it again\n4. Keep the nonce strictly increasing per key and stay under the tier's counter, since EAPI:Rate limit exceeded has no Retry-After header\n5. Test strategies in a paper workspace, which fills at live prices with no account, before a live workspace\n\n## Questions\n\n### Which is better for AI agents, HTX trading API or Kraken API?\n\nKraken API scores 71 (BB) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.\n\n### Do HTX trading API and Kraken API need an API key?\n\nHTX trading API needs an API key. Kraken API takes an API key or an OAuth sign-in.\n\n### Can an agent call HTX trading API and Kraken API without installing anything?\n\nNo hosted endpoint is listed for HTX trading API. Kraken API runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/htx-vs-kraken.json, and with the fewest tokens: https://www.anchorterminal.com/compare/htx-vs-kraken.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"htx\", \"b\": \"kraken\"}`. From a terminal: `anchor compare htx kraken`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/htx.json and https://www.anchorterminal.com/api/v1/tools/kraken.json\n\n## Other comparisons with HTX trading API or Kraken API\n\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)\n- [Bitfinex API vs Kraken API](https://www.anchorterminal.com/compare/bitfinex-vs-kraken.md)\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md)\n- [Bitget vs Kraken API](https://www.anchorterminal.com/compare/bitget-vs-kraken.md)\n- [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.md)\n- [Bithumb Open API vs Kraken API](https://www.anchorterminal.com/compare/bithumb-vs-kraken.md)\n- [Bitstamp API vs HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md)\n- [Bitstamp API vs Kraken API](https://www.anchorterminal.com/compare/bitstamp-vs-kraken.md)\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)\n- [Bybit vs Kraken API](https://www.anchorterminal.com/compare/bybit-vs-kraken.md)\n- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md)\n- [Crypto.com Exchange API vs Kraken API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken.md)\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md)\n- [Gate vs Kraken API](https://www.anchorterminal.com/compare/gate-io-vs-kraken.md)\n- [Gemini Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.md)\n- [Gemini Exchange API vs Kraken API](https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken.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- [HTX trading API vs MEXC API](https://www.anchorterminal.com/compare/htx-vs-mexc.md)\n- [HTX trading API vs OKX API](https://www.anchorterminal.com/compare/htx-vs-okx.md)\n- [HTX trading API vs Uniswap Trading API](https://www.anchorterminal.com/compare/htx-vs-uniswap.md)\n- [HTX trading API vs Upbit Open API](https://www.anchorterminal.com/compare/htx-vs-upbit.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Binance API vs Kraken API](https://www.anchorterminal.com/compare/binance-vs-kraken.md)\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md)\n- [Coinbase Advanced Trade API vs Kraken API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken.md)\n- [Coinbase MCP server (Coinbase for Agents) vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Kraken API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-kraken.md)\n- [Kraken API vs KuCoin](https://www.anchorterminal.com/compare/kraken-vs-kucoin.md)\n- [Kraken API vs MEXC API](https://www.anchorterminal.com/compare/kraken-vs-mexc.md)\n- [Kraken API vs OKX API](https://www.anchorterminal.com/compare/kraken-vs-okx.md)\n- [Kraken API vs Uniswap Trading API](https://www.anchorterminal.com/compare/kraken-vs-uniswap.md)\n- [Kraken API vs Upbit Open API](https://www.anchorterminal.com/compare/kraken-vs-upbit.md)\n- [Deribit vs HTX trading API](https://www.anchorterminal.com/compare/deribit-vs-htx.md)\n- [Deribit vs Kraken API](https://www.anchorterminal.com/compare/deribit-vs-kraken.md)\n- [dYdX vs HTX trading API](https://www.anchorterminal.com/compare/dydx-vs-htx.md)\n- [dYdX vs Kraken API](https://www.anchorterminal.com/compare/dydx-vs-kraken.md)\n- [Hyperliquid vs Kraken API](https://www.anchorterminal.com/compare/hyperliquid-vs-kraken.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": "HTX trading API vs Kraken API", "url": "" } ], "description": "Kraken scores 71 (BB) to HTX trading's 43.3 (E) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "HTX trading API E 43.3", "Kraken API BB 71", "scores" ], "h1": "HTX trading API vs Kraken API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/htx-vs-kraken", "published": "2026-10-01", "section": "tools", "title": "HTX trading vs Kraken for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/htx-vs-kraken" }, "tokens": { "markdown": 4700, "slim": 2530 }, "version": 1 }