{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/gemini-exchange.json", "name": "Gemini Exchange API", "score": 74.6, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "slug": "gemini-exchange" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/kraken.json", "name": "Kraken API", "score": 71, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "slug": "kraken" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/okx.json", "name": "OKX API", "score": 64.3, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "slug": "okx" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/binance.json", "name": "Binance API", "score": 63.2, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "slug": "binance" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/coinbase-advanced-trade.json", "name": "Coinbase Advanced Trade API", "score": 61.7, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "slug": "coinbase-advanced-trade" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/deribit.json", "name": "Deribit", "score": 59, "shared": [ "exchange.derivatives", "exchange.market-data", "exchange.spot-trading", "exchange.balances", "exchange.transfers", "market.crypto" ], "slug": "deribit" } ], "tool": { "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 38, "points": 7.6, "reason": "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.", "checked": "2026-11-03" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 40, "points": 6.5, "reason": "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.", "checked": "2026-11-03" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 69, "points": 11.21, "reason": "Graded on the REST API. Responses can be sized with depth types, size and limit parameters on books, candles and history (15 of 25). Paging by from, size and direct on orders and history (14 of 20). Errors return err-code strings with messages, listed in tables (13 of 20). A client-order-id unique within 8 hours and idempotent withdrawal ids make retries safe, with no idempotency header on other writes (14 of 20). Few required parameters and official SDKs in five languages (13 of 15). 15 + 14 + 13 + 14 + 13 = 69.", "checked": "2026-11-03" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 51, "points": 8.93, "reason": "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.", "checked": "2026-11-03" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 15, "points": 1.88, "reason": "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.", "checked": "2026-11-03" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 57, "points": 4.99, "reason": "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.", "checked": "2026-11-03" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 25, "points": 2.19, "note": "editorial 15, provenance 34", "reason": "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.", "checked": "2026-11-03" } ], "assessment": { "date": "2026-11-03", "basis": "public evidence", "confidence": "low", "notes": { "ergonomics": "Graded on the REST API. Responses can be sized with depth types, size and limit parameters on books, candles and history (15 of 25). Paging by from, size and direct on orders and history (14 of 20). Errors return err-code strings with messages, listed in tables (13 of 20). A client-order-id unique within 8 hours and idempotent withdrawal ids make retries safe, with no idempotency header on other writes (14 of 20). Few required parameters and official SDKs in five languages (13 of 15). 15 + 14 + 13 + 14 + 13 = 69.", "maintenance": "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.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "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.", "transparency": "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." }, "sources": [ { "what": "robots.txt (www.htx.com allows /; www.huobi.com disallows all; huobiapi.github.io none)", "url": "https://www.htx.com/robots.txt", "seen": "2026-11-03" }, { "what": "spot API reference (auth, permissions, IP binding, testnet shutdown, rate limits, client-order-id, errors, SDKs, changelog)", "url": "https://huobiapi.github.io/docs/spot/v1/en/", "seen": "2026-11-03" }, { "what": "USDT-margined swap API reference (changelog to 10 November 2022, Huobi branding)", "url": "https://huobiapi.github.io/docs/usdt_swap/v1/en/", "seen": "2026-11-03" }, { "what": "huobiapi GitHub account (User, created 21 November 2014, 21 repositories, huobi_fix among them)", "url": "https://api.github.com/users/huobiapi", "seen": "2026-11-03" }, { "what": "HuobiRDCenter SDK repositories and push dates", "url": "https://api.github.com/orgs/HuobiRDCenter/repos", "seen": "2026-11-03" }, { "what": "huobi_fix README (404)", "url": "https://raw.githubusercontent.com/huobiapi/huobi_fix/master/README.md", "seen": "2026-11-03" }, { "what": "official MCP registry search for htx (one third-party entry) and huobi (none)", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=htx", "seen": "2026-11-03" }, { "what": "fee page (script-drawn, no text)", "url": "https://www.htx.com/fee/", "seen": "2026-11-03" }, { "what": "HTX Platform User Agreement (script-drawn, no text)", "url": "https://www.htx.com/en-in/support/360000298561/", "seen": "2026-11-03" }, { "what": "about page and home page (no text)", "url": "https://www.htx.com/en-us/about/", "seen": "2026-11-03" }, { "what": "security.txt (no text)", "url": "https://www.htx.com/.well-known/security.txt", "seen": "2026-11-03" }, { "what": "RDAP for htx.com", "url": "https://rdap.verisign.com/com/v1/domain/htx.com", "seen": "2026-11-03" } ], "openQuestions": [ "unchecked: the user agreement (legal entity, restricted jurisdictions, clauses on API and automated use), the privacy policy, the fee schedule, the about page and HTX's newer API docs on htx.com. Every page on www.htx.com is drawn by script and answered no text; the support-article URL was found by search and also answered no text. Transparency and payments are scored absent for that reason, with low confidence.", "unchecked: FIX access. huobiapi/huobi_fix exists (pushed 3 March 2025) but its README answered 404.", "unchecked: WebSocket connection and subscription limits, and the last 64,000 characters of the spot reference (three of four pages read).", "firstReleased is 21 November 2014, the creation date of the huobiapi GitHub account, the earliest first-hand date found for the API programme; the API itself is older. lastRelease is 21 October 2026, the last push to the HuobiRDCenter contract SDKs, since the readable changelog ends in June 2022.", "Kind http-api: the REST and WebSocket API is the only surface. No MCP server found after reading the docs, both GitHub accounts and the registry.", "The docs state two expiry rules for keys without IP binding (expires after 90 days; deactivated after 90 days without use for trade and withdraw keys). Recorded, not deducted.", "Humans: no first-hand page naming a person with a role was readable. Press releases name Justin Sun as Global Advisor of HTX; not recorded.", "Our own products. It doesn't do LocalGhost's or letme's job." ] }, "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 }, "scoreHistory": [ { "date": "2026-11-03", "grade": "E", "kind": "listed", "method": "0.7", "score": 43.3 } ] }, "connect": { "http": "curl https://api.huobi.pro/market/tickers" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/htx" }, "notable": [ "MCP server, none found. The API docs, the huobiapi GitHub account (21 repositories) and the HuobiRDCenter organisation (14 SDK repositories) mention no MCP server, and the official MCP registry lists only a third party's io.github.mrfentmen/htx-mcp (market tickers and depth, stdio, version 1.0.0 of 21 September 2026), which is not HTX's (https://registry.modelcontextprotocol.io/v0/servers?search=htx)", "The public API reference at huobiapi.github.io is still branded Huobi, with huobi.pro hosts, and its last dated changelog entry is 24 June 2022. HTX's newer docs at htx.com/en-us/opend/newApiPages/ are drawn by script and answered our reader with no text (https://huobiapi.github.io/docs/spot/v1/en/)", "The testnet is closed. The docs say \"we decide to shutdown the testnet environment\" and point to the live environment (https://huobiapi.github.io/docs/spot/v1/en/)", "Rate limits are per UID and per endpoint, with numbers, 100 requests per 2 seconds to place or cancel an order, 50 per 2 seconds for batch orders and batch cancels, 100 per 2 seconds for account reads. Responses carry X-HB-RateLimit-Requests-Remain and X-HB-RateLimit-Requests-Expire. No 429 or Retry-After behaviour is documented (https://huobiapi.github.io/docs/spot/v1/en/)", "A client-order-id of up to 64 characters must be unique within 8 hours, and a repeat answers invalid.client.order.id; a withdrawal's client-order-id is checked for idempotence and a repeat returns the earlier withdrawal id (https://huobiapi.github.io/docs/spot/v1/en/)", "Official SDKs for Python, Java, C++, C# and Go under HuobiRDCenter, the spot ones last pushed between April and July 2026 and the contract ones on 21 October 2026, all still named huobi_* (https://api.github.com/orgs/HuobiRDCenter/repos)", "A huobiapi/huobi_fix repository exists (last pushed 3 March 2025) but its README answered 404, so what FIX access HTX gives is unchecked (https://github.com/huobiapi/huobi_fix)", "The HTX Platform User Agreement lives at htx.com/en-in/support/360000298561/ and answered our reader with no text, so the legal entity, the restricted jurisdictions and the clauses on API and automated use are unread. Press reports of October 2026 say Russia was added to the restricted list; that is a lead, not a source (https://www.htx.com/en-in/support/360000298561/)", "No status page found; status.htx.com does not resolve and no status link was readable on htx.com (checked 2026-11-03)" ], "area": "payments", "details": [ { "label": "Surface listed", "value": "The spot and USDT-margined swap REST and WebSocket APIs at api.huobi.pro, read from huobiapi.github.io, the huobiapi and HuobiRDCenter GitHub accounts and the MCP registry on 3 November 2026. No account was made and no private endpoint was called" }, { "label": "MCP server", "value": "None found. Looked in the API docs, the huobiapi GitHub account, the HuobiRDCenter organisation and the official MCP registry, where the only entry is a third party's io.github.mrfentmen/htx-mcp (stdio, npm htx-mcp, version 1.0.0 of 21 September 2026), not HTX's" }, { "label": "Key permissions", "value": "Read, Trade and Withdraw on a main account key; Read and Trade on a sub-user key. Up to 20 bound IP addresses per key; a key without IP binding expires after 90 days per the docs (the 14 June 2022 changelog says trade and withdraw keys are deactivated after 90 days without use). Withdrawal address allow-lists unchecked" }, { "label": "Rate limits", "value": "Per UID and per endpoint. Place order 100 per 2 seconds, batch orders 50 per 2 seconds, cancel 100 per 2 seconds, batch cancel 50 per 2 seconds, conditional orders 20 per 2 seconds, account reads 100 per 2 seconds, deposit and withdrawal calls 20 per 2 seconds, spot and futures transfer 10 per minute. Headers X-HB-RateLimit-Requests-Remain and X-HB-RateLimit-Requests-Expire. No 429 or Retry-After documented" }, { "label": "Testnet", "value": "Closed. The docs say the testnet environment was shut down and point to the live environment" }, { "label": "Countries", "value": "Unchecked. The user agreement's restricted-jurisdictions list is on a script-drawn page that answered no text. Press reports of October 2026 say Russia was added; third-party guides also name the United States, the United Kingdom and others, none confirmed first-hand" }, { "label": "Fees", "value": "Unchecked. htx.com/fee answered no text. Third-party guides give 0.2 per cent maker and taker at the base tier" }, { "label": "FIX and WebSocket", "value": "WebSocket at wss://api.huobi.pro/ws (market), /feed (incremental book) and /ws/v2 (account and orders), with api-aws.huobi.pro twins. A huobiapi/huobi_fix repository exists but its README answered 404, so FIX access is unchecked" }, { "label": "Terms on automation", "value": "Unchecked. The HTX Platform User Agreement (htx.com/en-in/support/360000298561/) answered no text" }, { "label": "SDKs", "value": "huobi_Python (684 stars), huobi_Java, huobi_Cpp, huobi_CSharp and huobi_Golang for spot, and python, java, csharp and golang contract SDKs, under HuobiRDCenter" }, { "label": "Legal entity", "value": "Unknown. The user agreement couldn't be read. HTX has said in press coverage that Huobi Global S.A. is distinct from the exchange, which is a lead and not a source" } ], "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, "checks": [ { "check": "Legal entity named", "value": "not found", "points": 0, "max": 20, "state": "no" }, { "check": "Domain age", "value": "htx.com, registered 1995-12-13 (30 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": " is not on htx.com", "points": 0, "max": 15, "state": "no" }, { "check": "Terms of service", "value": "read, states 4 of the 7 things a reader expects, and has 1 clause that costs points", "points": 5.4, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "not researched yet", "points": 0, "max": 0, "state": "na" }, { "check": "Support route", "value": "help pages, a community", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.htx.com/en-in/support/360000298561/", "state": "read", "readAt": "2026-11-03", "words": 24067, "points": 5.4, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": false }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "Governing Law: This Agreement and any dispute or claim arising out of or in connection with it shall be governed by and construed in accordance with the laws of Pakistan, excluding its conflict of laws rules.", "says": "The law of Pakistan" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "…under applicable laws, our total aggregate liability to you in connection with the Services shall not exceed the total fees paid by you to HTX in connection with the Services from the period starting 3 months prior to the event giving rise to the liability and ending at the time of the relevant event.", "says": "Capped at the fees paid in the 3 months before the claim" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "…the right to refuse your registration for an Account and if you have already created an Account, we shall have the right to suspend, terminate and/or close your Account without any advance notice to you and hold you accountable for any adverse consequences arising therefrom." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "Unless you have an Account (as defined herein) with the Platform, you shall not use the Services intended to be provided to Users with an Account." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "toKnow": [ { "key": "terms.nonotice", "label": "Says the terms or the service can change without notice", "found": true, "quote": "(ii) to modify, suspend or terminate any or all of the Services offered at any time without prior notice to you.", "costsPoints": true }, { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "…your registration for an Account and if you have already created an Account, we shall have the right to suspend, terminate and/or close your Account without any advance notice to you and hold you accountable for any adverse consequences arising therefrom." }, { "key": "terms.arbitration", "label": "Requires arbitration or waives class actions", "found": true, "quote": "…(collectively referred to as the \"Dispute\"), the Dispute shall be referred to and finally resolved by binding arbitration administered by the Hong Kong International Arbitration Centre (“HKIAC”) in accordance with the Arbitration Rules of the Hong Kong International Arbitration Centre (“HKIAC Rules”) for the time bein…" } ], "notes": [ { "date": "2026-11-03", "text": "Total liability is capped at the fees the customer paid to HTX in the 3 months before the event giving rise to the claim.", "quote": "our total aggregate liability to you in connection with the Services shall not exceed the total fees paid by you to HTX in connection with the Services from the period starting 3 months prior to the event giving rise to the liability and ending at the time of the relevant event." }, { "date": "2026-11-03", "text": "Accepting the agreement assigns to HTX, exclusively and free of charge, all copyright in any information the customer publishes on the website.", "quote": "Upon acceptance of this Agreement, it shall be deemed that you have transferred and assigned exclusively and free of charge to us all copyright of any form of information that you publish on this Website" }, { "date": "2026-11-03", "text": "Users from the United States, the United Kingdom, Singapore, Hong Kong and all EU member states, among others, are prohibited from using all services.", "quote": "USERS FROM THE FOLLOWING JURISDICTIONS ARE PROHIBITED FROM USING ALL SERVICES: MAINLAND CHINA, THE UNITED STATES OF AMERICA, CUBA, IRAN, NORTH KOREA, SUDAN, SYRIA, VENEZUELA, HONG KONG CHINA, THE UNITED KINGDOM, SINGAPORE, MYANMAR, CRIMEA, DONETSK, LUHANSK, KHERSON, ZAPORIZHZHIA, SEVASTOPOL" } ] }, { "kind": "privacy", "url": "", "state": "none-found", "points": 0, "max": 10 } ] }, "humans": { "slug": "htx", "checked": "2026-11-03", "company": "HTX", "peopleNote": "No first-hand page naming a person with a role could be read. HTX's about page, home page and support articles on www.htx.com are drawn by script and answered our reader with no text on 3 November 2026, and the user agreement that would name the legal entity answered the same. Press releases distributed through PR Newswire and Chainwire in 2023 to 2025 call Justin Sun the Global Advisor of HTX and a member of its Global Advisory Board; none is an HTX page, so nobody is listed. Ownership is unknown for the same reason: press reports say About Capital bought Huobi in October 2022 and that HTX calls Huobi Global S.A. a distinct entity, but no HTX page, filing or buyer's announcement was read. No investors were looked for, since the company behind the exchange couldn't be named from a first-hand page.", "companySocial": { "github": "https://github.com/HuobiRDCenter" }, "support": { "urls": [ "https://huobiapi.github.io/docs/spot/v1/en/" ], "community": [ { "label": "HTX API Telegram group", "url": "https://t.me/htx_api", "kind": "telegram" } ] }, "sources": [ "https://huobiapi.github.io/docs/spot/v1/en/", "https://api.github.com/users/huobiapi", "https://api.github.com/orgs/HuobiRDCenter/repos", "https://www.htx.com/en-us/about/", "https://www.htx.com/en-in/support/360000298561/" ], "ownership": { "status": "unknown", "checked": "2026-11-03", "sources": [ "https://www.htx.com/en-in/support/360000298561/" ] } }, "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" } }, "verify": { "accepts": "a page on htx.com or one of its subdomains", "badgeUrl": "https://www.anchorterminal.com/badges/htx.svg", "body": { "slug": "htx", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/htx", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/htx\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/htx.svg\" alt=\"HTX trading API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![HTX trading API on Anchor Terminal](https://www.anchorterminal.com/badges/htx.svg)](https://www.anchorterminal.com/tools/htx)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/htx\"\u003eHTX trading API on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/htx", "json": "https://www.anchorterminal.com/tools/htx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/htx.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/htx#pricing", "reviews": "https://www.anchorterminal.com/tools/htx#reviews", "slim": "https://www.anchorterminal.com/tools/htx.min.md" }, "markdown": "## Overview\n\n**Grade E · 43.3/100 · rank #1166 of 1349 · #21 in Crypto exchanges · not agent-ready · confidence low**\n\n\n## Assessment\n\nHTX'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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | HTX (https://www.htx.com) |\n| Kind | HTTP API |\n| Category | Crypto exchanges (https://www.anchorterminal.com/categories/crypto-exchanges) |\n| Auth | API key · 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). |\n| Pricing | Pay per use (Pay per use) · 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). |\n| x402 | No · 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. |\n| Licence | unknown |\n| Tools exposed | 0 |\n| Source | https://github.com/HuobiRDCenter |\n| Docs | https://huobiapi.github.io/docs/spot/v1/en/ |\n| llms.txt | not found |\n| Last release | 2026-10-21 |\n| GitHub stars | 684 (as of 2026-11-03) |\n| Surface listed | The spot and USDT-margined swap REST and WebSocket APIs at api.huobi.pro, read from huobiapi.github.io, the huobiapi and HuobiRDCenter GitHub accounts and the MCP registry on 3 November 2026. No account was made and no private endpoint was called |\n| MCP server | None found. Looked in the API docs, the huobiapi GitHub account, the HuobiRDCenter organisation and the official MCP registry, where the only entry is a third party's io.github.mrfentmen/htx-mcp (stdio, npm htx-mcp, version 1.0.0 of 21 September 2026), not HTX's |\n| Key permissions | Read, Trade and Withdraw on a main account key; Read and Trade on a sub-user key. Up to 20 bound IP addresses per key; a key without IP binding expires after 90 days per the docs (the 14 June 2022 changelog says trade and withdraw keys are deactivated after 90 days without use). Withdrawal address allow-lists unchecked |\n| Rate limits | Per UID and per endpoint. Place order 100 per 2 seconds, batch orders 50 per 2 seconds, cancel 100 per 2 seconds, batch cancel 50 per 2 seconds, conditional orders 20 per 2 seconds, account reads 100 per 2 seconds, deposit and withdrawal calls 20 per 2 seconds, spot and futures transfer 10 per minute. Headers X-HB-RateLimit-Requests-Remain and X-HB-RateLimit-Requests-Expire. No 429 or Retry-After documented |\n| Testnet | Closed. The docs say the testnet environment was shut down and point to the live environment |\n| Countries | Unchecked. The user agreement's restricted-jurisdictions list is on a script-drawn page that answered no text. Press reports of October 2026 say Russia was added; third-party guides also name the United States, the United Kingdom and others, none confirmed first-hand |\n| Fees | Unchecked. htx.com/fee answered no text. Third-party guides give 0.2 per cent maker and taker at the base tier |\n| FIX and WebSocket | WebSocket at wss://api.huobi.pro/ws (market), /feed (incremental book) and /ws/v2 (account and orders), with api-aws.huobi.pro twins. A huobiapi/huobi_fix repository exists but its README answered 404, so FIX access is unchecked |\n| Terms on automation | Unchecked. The HTX Platform User Agreement (htx.com/en-in/support/360000298561/) answered no text |\n| SDKs | huobi_Python (684 stars), huobi_Java, huobi_Cpp, huobi_CSharp and huobi_Golang for spot, and python, java, csharp and golang contract SDKs, under HuobiRDCenter |\n| Legal entity | Unknown. The user agreement couldn't be read. HTX has said in press coverage that Huobi Global S.A. is distinct from the exchange, which is a lead and not a source |\n| Capabilities | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, market.crypto |\n| Tags | hosted, api-key, closed-source, usage-priced, python, java, go, no-status-page |\n| JSON | https://www.anchorterminal.com/api/v1/tools/htx.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 38 | 7.6 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 40 | 6.5 |\n| Agent ergonomics | 13% | 16.2 | 69 | 11.2 |\n| Security \u0026 auth | 14% | 17.5 | 51 | 8.9 |\n| Payments \u0026 pricing | 10% | 12.5 | 15 | 1.9 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 57 | 5.0 |\n| Transparency \u0026 trust (editorial 15, provenance 34) | 7% | 8.8 | 25 | 2.2 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **43.3 → E** |\n\n### Why each score\n\n- Reliability 38 (checked 2026-11-03): 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- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 40 (checked 2026-11-03): 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- Agent ergonomics 69 (checked 2026-11-03): Graded on the REST API. Responses can be sized with depth types, size and limit parameters on books, candles and history (15 of 25). Paging by from, size and direct on orders and history (14 of 20). Errors return err-code strings with messages, listed in tables (13 of 20). A client-order-id unique within 8 hours and idempotent withdrawal ids make retries safe, with no idempotency header on other writes (14 of 20). Few required parameters and official SDKs in five languages (13 of 15). 15 + 14 + 13 + 14 + 13 = 69.\n- Security \u0026 auth 51 (checked 2026-11-03): 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- Payments \u0026 pricing 15 (checked 2026-11-03): 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- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 57 (checked 2026-11-03): 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- Transparency \u0026 trust 25 (checked 2026-11-03): 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\nFix list, everything this grade says the listing lacks, the biggest gain first (21 items). What it covers is at https://www.anchorterminal.com/fixes/htx.md (JSON https://www.anchorterminal.com/fixes/htx.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"htx\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- unchecked: the user agreement (legal entity, restricted jurisdictions, clauses on API and automated use), the privacy policy, the fee schedule, the about page and HTX's newer API docs on htx.com. Every page on www.htx.com is drawn by script and answered no text; the support-article URL was found by search and also answered no text. Transparency and payments are scored absent for that reason, with low confidence.\n- unchecked: FIX access. huobiapi/huobi_fix exists (pushed 3 March 2025) but its README answered 404.\n- unchecked: WebSocket connection and subscription limits, and the last 64,000 characters of the spot reference (three of four pages read).\n- firstReleased is 21 November 2014, the creation date of the huobiapi GitHub account, the earliest first-hand date found for the API programme; the API itself is older. lastRelease is 21 October 2026, the last push to the HuobiRDCenter contract SDKs, since the readable changelog ends in June 2022.\n- Kind http-api: the REST and WebSocket API is the only surface. No MCP server found after reading the docs, both GitHub accounts and the registry.\n- The docs state two expiry rules for keys without IP binding (expires after 90 days; deactivated after 90 days without use for trade and withdraw keys). Recorded, not deducted.\n- Humans: no first-hand page naming a person with a role was readable. Press releases name Justin Sun as Global Advisor of HTX; not recorded.\n- Our own products. It doesn't do LocalGhost's or letme's job.\n\n### Sources\n\n- robots.txt (www.htx.com allows /; www.huobi.com disallows all; huobiapi.github.io none): \u003chttps://www.htx.com/robots.txt\u003e (seen 2026-11-03)\n- spot API reference (auth, permissions, IP binding, testnet shutdown, rate limits, client-order-id, errors, SDKs, changelog): \u003chttps://huobiapi.github.io/docs/spot/v1/en/\u003e (seen 2026-11-03)\n- USDT-margined swap API reference (changelog to 10 November 2022, Huobi branding): \u003chttps://huobiapi.github.io/docs/usdt_swap/v1/en/\u003e (seen 2026-11-03)\n- huobiapi GitHub account (User, created 21 November 2014, 21 repositories, huobi_fix among them): \u003chttps://api.github.com/users/huobiapi\u003e (seen 2026-11-03)\n- HuobiRDCenter SDK repositories and push dates: \u003chttps://api.github.com/orgs/HuobiRDCenter/repos\u003e (seen 2026-11-03)\n- huobi_fix README (404): \u003chttps://raw.githubusercontent.com/huobiapi/huobi_fix/master/README.md\u003e (seen 2026-11-03)\n- official MCP registry search for htx (one third-party entry) and huobi (none): \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=htx\u003e (seen 2026-11-03)\n- fee page (script-drawn, no text): \u003chttps://www.htx.com/fee/\u003e (seen 2026-11-03)\n- HTX Platform User Agreement (script-drawn, no text): \u003chttps://www.htx.com/en-in/support/360000298561/\u003e (seen 2026-11-03)\n- about page and home page (no text): \u003chttps://www.htx.com/en-us/about/\u003e (seen 2026-11-03)\n- security.txt (no text): \u003chttps://www.htx.com/.well-known/security.txt\u003e (seen 2026-11-03)\n- RDAP for htx.com: \u003chttps://rdap.verisign.com/com/v1/domain/htx.com\u003e (seen 2026-11-03)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/htx/history.json\n\n- 2026-11-03: graded 43.3 E (methodology 0.7)\n\n## Who's behind it (provenance 34/100, checked 2026-11-03)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | not found | 0/20 |\n| Domain age | htx.com, registered 1995-12-13 (30 years) | 15/15 |\n| Endpoint on the vendor's domain | is not on htx.com | 0/15 |\n| Terms of service | read, states 4 of the 7 things a reader expects, and has 1 clause that costs points | 5.4/10 |\n| Privacy policy | not found | 0/10 |\n| Status page | not found | 0/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n| People named | not researched yet | n/a |\n| Support route | help pages, a community | 5/5 |\n\nThe 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.\n\nRDAP 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.\n\nThe API endpoint api.huobi.pro is on the old huobi.pro domain, not htx.com.\n\nwww.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.\n\nhttps://www.htx.com/.well-known/security.txt answered no text; recorded as none. status.htx.com does not resolve.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.htx.com/en-in/support/360000298561/), read 2026-11-03, gives no date, states 4 of the 7 things a reader expects.\n\n- To know. Says the terms or the service can change without notice (costs points). \"(ii) to modify, suspend or terminate any or all of the Services offered at any time without prior notice to you.\"\n- To know. Says access can be ended without notice or for any reason. \"…your registration for an Account and if you have already created an Account, we shall have the right to suspend, terminate and/or close your Account without any advance notice to you and hold you accountable for any adverse consequences arising therefrom.\"\n- To know. Requires arbitration or waives class actions. \"…(collectively referred to as the \"Dispute\"), the Dispute shall be referred to and finally resolved by binding arbitration administered by the Hong Kong International Arbitration Centre (“HKIAC”) in accordance with the Arbitration Rules of the Hong Kong International Arbitration Centre (“HKIAC Rules”) for the time bein…\"\n- Not found in the text. Gives the date it was last updated.\n- Names the governing law or courts. The law of Pakistan.\n- States a limit on its liability. Capped at the fees paid in the 3 months before the claim.\n- Not found in the text. Says how changes to the terms are announced.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-11-03). Total liability is capped at the fees the customer paid to HTX in the 3 months before the event giving rise to the claim. \"our total aggregate liability to you in connection with the Services shall not exceed the total fees paid by you to HTX in connection with the Services from the period starting 3 months prior to the event giving rise to the liability and ending at the time of the relevant event.\"\n- Also in the text (2026-11-03). Accepting the agreement assigns to HTX, exclusively and free of charge, all copyright in any information the customer publishes on the website. \"Upon acceptance of this Agreement, it shall be deemed that you have transferred and assigned exclusively and free of charge to us all copyright of any form of information that you publish on this Website\"\n- Also in the text (2026-11-03). Users from the United States, the United Kingdom, Singapore, Hong Kong and all EU member states, among others, are prohibited from using all services. \"USERS FROM THE FOLLOWING JURISDICTIONS ARE PROHIBITED FROM USING ALL SERVICES: MAINLAND CHINA, THE UNITED STATES OF AMERICA, CUBA, IRAN, NORTH KOREA, SUDAN, SYRIA, VENEZUELA, HONG KONG CHINA, THE UNITED KINGDOM, SINGAPORE, MYANMAR, CRIMEA, DONETSK, LUHANSK, KHERSON, ZAPORIZHZHIA, SEVASTOPOL\"\n\n**Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0.\n\n\n## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)\n\n### Key people\n\n- No people named yet.\n- Note: No first-hand page naming a person with a role could be read. HTX's about page, home page and support articles on www.htx.com are drawn by script and answered our reader with no text on 3 November 2026, and the user agreement that would name the legal entity answered the same. Press releases distributed through PR Newswire and Chainwire in 2023 to 2025 call Justin Sun the Global Advisor of HTX and a member of its Global Advisory Board; none is an HTX page, so nobody is listed. Ownership is unknown for the same reason: press reports say About Capital bought Huobi in October 2022 and that HTX calls Huobi Global S.A. a distinct entity, but no HTX page, filing or buyer's announcement was read. No investors were looked for, since the company behind the exchange couldn't be named from a first-hand page.\n- HTX: GitHub https://github.com/HuobiRDCenter\n\n### Getting support\n\n- Help: https://huobiapi.github.io/docs/spot/v1/en/\n- Community (HTX API Telegram group): https://t.me/htx_api\n- Sources: https://huobiapi.github.io/docs/spot/v1/en/, https://api.github.com/users/huobiapi, https://api.github.com/orgs/HuobiRDCenter/repos, https://www.htx.com/en-us/about/, https://www.htx.com/en-in/support/360000298561/\n\n## Live (updated 2026-11-04 15:54 UTC)\n\n- security.txt: none\n- Always current: https://www.anchorterminal.com/api/v1/live/htx.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Strengths\n\n- Key permissions split into Read, Trade and Withdraw, sub-user keys without Withdraw, and up to 20 bound IP addresses per key\n- Rate limits published per endpoint with numbers, and remaining-quota headers on every response\n- A client-order-id unique within 8 hours on orders and idempotent on withdrawals, so a retry doesn't double an order\n- Official SDKs in Python, Java, C++, C# and Go, the contract ones pushed on 21 October 2026\n\n## Weaknesses\n\n- No official MCP server; the only one in the MCP registry is a third party's read-only ticker server\n- The testnet is shut down, so order logic can only be tried with real funds\n- 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\n- No status page, no SLA and no documented 429 or Retry-After behaviour\n- The fee schedule, user agreement, privacy policy and restricted-country list couldn't be read, so none is recorded first-hand\n\n\n\n## Before you call it (notes for agents)\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## Connect\n\nFirst request:\n\n```bash\ncurl https://api.huobi.pro/market/tickers\n```\n\nThrough letme: https://letme.dev/htx. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Gemini Exchange API | BB | 74.6 | 70 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/gemini-exchange.md |\n| Kraken API | BB | 71 | 159 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/kraken.md |\n| OKX API | B | 64.3 | 413 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/okx.md |\n| Binance API | B | 63.2 | 448 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/binance.md |\n| Coinbase Advanced Trade API | C | 61.7 | 493 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/coinbase-advanced-trade.md |\n| Deribit | C | 59 | 650 | exchange.derivatives, exchange.market-data, exchange.spot-trading, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/deribit.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- MCP server, none found. The API docs, the huobiapi GitHub account (21 repositories) and the HuobiRDCenter organisation (14 SDK repositories) mention no MCP server, and the official MCP registry lists only a third party's io.github.mrfentmen/htx-mcp (market tickers and depth, stdio, version 1.0.0 of 21 September 2026), which is not HTX's (source: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=htx\u003e)\n- The public API reference at huobiapi.github.io is still branded Huobi, with huobi.pro hosts, and its last dated changelog entry is 24 June 2022. HTX's newer docs at htx.com/en-us/opend/newApiPages/ are drawn by script and answered our reader with no text (source: \u003chttps://huobiapi.github.io/docs/spot/v1/en/\u003e)\n- The testnet is closed. The docs say \"we decide to shutdown the testnet environment\" and point to the live environment (source: \u003chttps://huobiapi.github.io/docs/spot/v1/en/\u003e)\n- Rate limits are per UID and per endpoint, with numbers, 100 requests per 2 seconds to place or cancel an order, 50 per 2 seconds for batch orders and batch cancels, 100 per 2 seconds for account reads. Responses carry X-HB-RateLimit-Requests-Remain and X-HB-RateLimit-Requests-Expire. No 429 or Retry-After behaviour is documented (source: \u003chttps://huobiapi.github.io/docs/spot/v1/en/\u003e)\n- A client-order-id of up to 64 characters must be unique within 8 hours, and a repeat answers invalid.client.order.id; a withdrawal's client-order-id is checked for idempotence and a repeat returns the earlier withdrawal id (source: \u003chttps://huobiapi.github.io/docs/spot/v1/en/\u003e)\n- Official SDKs for Python, Java, C++, C# and Go under HuobiRDCenter, the spot ones last pushed between April and July 2026 and the contract ones on 21 October 2026, all still named huobi_* (source: \u003chttps://api.github.com/orgs/HuobiRDCenter/repos\u003e)\n- A huobiapi/huobi_fix repository exists (last pushed 3 March 2025) but its README answered 404, so what FIX access HTX gives is unchecked (source: \u003chttps://github.com/huobiapi/huobi_fix\u003e)\n- The HTX Platform User Agreement lives at htx.com/en-in/support/360000298561/ and answered our reader with no text, so the legal entity, the restricted jurisdictions and the clauses on API and automated use are unread. Press reports of October 2026 say Russia was added to the restricted list; that is a lead, not a source (source: \u003chttps://www.htx.com/en-in/support/360000298561/\u003e)\n- No status page found; status.htx.com does not resolve and no status link was readable on htx.com (checked 2026-11-03)\n\n- #21 of 21 in Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Compare\n\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md): C 58.4 vs E 43.3\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md): D 53.9 vs E 43.3\n- [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.md): D 50.6 vs E 43.3\n- [Bitstamp API vs HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md): D 50.4 vs E 43.3\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md): C 57.3 vs E 43.3\n- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md): D 46.8 vs E 43.3\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md): C 56.4 vs E 43.3\n- [Gemini Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.md): BB 74.6 vs E 43.3\n- [HTX trading API vs Hyperliquid](https://www.anchorterminal.com/compare/htx-vs-hyperliquid.md): E 43.3 vs D 50\n- [HTX trading API vs Kraken API](https://www.anchorterminal.com/compare/htx-vs-kraken.md): E 43.3 vs BB 71\n- [HTX trading API vs KuCoin](https://www.anchorterminal.com/compare/htx-vs-kucoin.md): E 43.3 vs D 53.9\n- [HTX trading API vs MEXC API](https://www.anchorterminal.com/compare/htx-vs-mexc.md): E 43.3 vs C 56.3\n- [HTX trading API vs OKX API](https://www.anchorterminal.com/compare/htx-vs-okx.md): E 43.3 vs B 64.3\n- [HTX trading API vs Uniswap Trading API](https://www.anchorterminal.com/compare/htx-vs-uniswap.md): E 43.3 vs B 63.3\n- [HTX trading API vs Upbit Open API](https://www.anchorterminal.com/compare/htx-vs-upbit.md): E 43.3 vs C 54.7\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md): B 63.2 vs E 43.3\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md): C 61.7 vs E 43.3\n- [Coinbase MCP server (Coinbase for Agents) vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.md): C 60 vs E 43.3\n- [Deribit vs HTX trading API](https://www.anchorterminal.com/compare/deribit-vs-htx.md): C 59 vs E 43.3\n- [dYdX vs HTX trading API](https://www.anchorterminal.com/compare/dydx-vs-htx.md): B 69.5 vs E 43.3\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on htx.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"htx\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/htx\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/htx.svg\" alt=\"HTX trading API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![HTX trading API on Anchor Terminal](https://www.anchorterminal.com/badges/htx.svg)](https://www.anchorterminal.com/tools/htx)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/htx\"\u003eHTX trading API on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say HTX trading API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/htx-dark.png\n- Light: https://www.anchorterminal.com/assets/share/htx-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Crypto exchanges", "url": "https://www.anchorterminal.com/categories/crypto-exchanges" }, { "name": "HTX trading API", "url": "" } ], "description": "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.", "facts": [ "rank #1166 of 1349", "API key auth", "0 desk reviews" ], "h1": "HTX trading API", "image": "https://www.anchorterminal.com/assets/og/tools-htx.png", "path": "/tools/htx", "published": "2026-10-01", "section": "tools", "title": "HTX trading review (2026): pricing, alternatives and grade E", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/tools/htx" }, "tokens": { "markdown": 7900, "slim": 1780 }, "version": 1 }