{ "data": { "a": { "slug": "bithumb", "name": "Bithumb Open API", "vendor": "Bithumb Co., Ltd.", "vendorUrl": "https://apidocs.bithumb.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Bithumb, a Korean exchange, runs a REST and WebSocket Open API for KRW market data, orders, balances, deposits and withdrawals, and an official AI Trade Kit with a local MCP server, a CLI and agent skills.", "url": "https://www.anchorterminal.com/tools/bithumb", "markdownUrl": "https://www.anchorterminal.com/tools/bithumb.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bithumb.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bithumb.json", "dns": "bithumb.grade.anchorterminal.com", "repo": "https://github.com/bithumb-official/bithumb-ai-trade-kit", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@bithumb-official/bithumb-mcp" }, { "registry": "npm", "name": "@bithumb-official/bithumb-cli" } ], "auth": "api-key", "authNotes": "Access and secret keys issued under My Page \u003e API Management on bithumb.com after identity verification. The person picks permissions (asset inquiry, order inquiry, place orders, withdrawals and others) and registers the IP addresses allowed to call. Each request carries a JWT signed with the secret as a Bearer token. Keys are valid for one year from issue and can't be extended; up to 10 per account including expired ones; the secret is shown once. The MCP server and CLI read BITHUMB_ACCESS_KEY and BITHUMB_SECRET_KEY, and market tools need no key (https://apidocs.bithumb.com/docs/빠른-시작-가이드.md, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "Trading fees per fill. The fee page at bithumb.com/react/info/fee/trade timed out on every attempt, so no rate is recorded; press reports from 2024 describe a 0.04 per cent rate with a monthly coupon and 0.25 per cent without, which is a lead and not a source. Public market data needs no key and no account (https://www.bithumb.com/react/info/fee/trade, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the AI Trade Kit repository or llms.txt (checked 2026-11-03). Fees are taken from each fill.", "endpoints": [] }, "toolCount": 41, "popularity": { "githubStars": 6, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://apidocs.bithumb.com/reference/api-레퍼런스", "llmsTxt": "https://apidocs.bithumb.com/llms.txt", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "api-key", "closed-source", "usage-priced", "mcp", "cli", "agent-skills", "read-only-mode", "llms-txt", "mit", "no-status-page" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 50.6, "grade": "D", "agentReady": false, "rank": 999, "ranked": true, "rankOf": 1349, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 69, "payments": 15, "reliability": 34, "schema": 64, "security": 60, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Bithumb runs an official local MCP server with 41 tools, module selection and a read-only flag, beside a CLI with per-profile read-only gating and six agent skills, over an API with scoped one-year keys and a mandatory IP list. There is no sandbox, no status page, no documented 429 behaviour, and the fees and terms couldn't be read.", "bestFor": "KRW-market trading for agents acting for a verified Korean account, with a vendor-built MCP server, CLI and skills.", "strengths": [ "An official MCP server from Bithumb with 41 tools in seven selectable modules and a `--read-only` flag that blocks orders, deposits and withdrawals", "Keys scoped to chosen permissions, limited to registered IPs and expiring after one year, with a key-list endpoint that shows expiry", "The CLI's per-profile read-only flag, local audit log and second factor on KRW deposits and withdrawals, and skills that refuse to bypass read-only", "Rate limits published per category with numbers, and notices with effective dates for changes such as the 200-market ticker cap", "Errors return a stable error.name under an HTTP status, with retry guidance for order_not_ready and server_error" ], "weaknesses": [ "No sandbox or testnet; every order uses real funds", "A rate-limit breach is signalled only as a temporary restriction, with no status code, header or Retry-After documented", "No status page, incident history or SLA", "The MCP server is local only, not in the official MCP registry, and its source is not published (the kit repository holds skills and setup files)", "The fee schedule, terms of service and Open API terms on bithumb.com timed out or answered a title only, so none is recorded first-hand" ], "agentNotes": [ "Ask for a key with asset and order inquiry plus order placement only, never withdrawals, with your IP registered; keys expire after one year and a wrong IP answers 401 NotAllowIP", "Start the server with `--modules market,account,trade --read-only` for analysis and drop `--read-only` only when the person asks to trade; deposit and withdraw modules stay off", "Prefer the `bithumb` CLI for writes, as the skills do, and check `bithumb config show --json` for a read-only profile before any order", "Keep the ticker's markets parameter at 200 or fewer, batch orders at 30 and cancels at 30 per request, and stay under 140 private calls a second per category", "Retry 422 order_not_ready and 500 server_error after a pause; there is no sandbox, so start with the smallest order the market allows" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.6 } ], "editorialScores": { "ergonomics": 67, "maintenance": 69, "payments": 15, "reliability": 34, "schema": 64, "security": 60, "transparency": 24 }, "provenanceScore": 69, "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": "npm install -g @bithumb-official/bithumb-cli", "http": "curl 'https://api.bithumb.com/v1/market/all?isDetails=false'", "config": { "mcpServers": { "bithumb": { "args": [ "-y", "@bithumb-official/bithumb-mcp", "--modules", "market,account,trade", "--read-only" ], "command": "npx", "env": { "BITHUMB_ACCESS_KEY": "${BITHUMB_ACCESS_KEY}", "BITHUMB_SECRET_KEY": "${BITHUMB_SECRET_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/bithumb" }, "area": "payments", "provenance": { "legalEntity": "Bithumb Co., Ltd.", "domain": "bithumb.com", "domainRegistered": "2015-06-16", "endpointOnVendorDomain": true, "terms": "https://www.bithumb.com/react/terms/info-terms", "privacy": "", "statusPage": "", "changelog": "https://apidocs.bithumb.com/changelog", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "Bithumb Co., Ltd. is named in the AI Trade Kit's disclaimer (compliance review 007441, 29 May 2026 to 28 May 2027). The terms of service at bithumb.com/react/terms/info-terms answered a page title only on two attempts, and the Open API terms, company page and fee pages timed out or did the same; no privacy policy URL was found in the sitemap's first part, so it is left empty.", "www.bithumb.com/robots.txt has no active rules (comments only) and two sitemaps; apidocs.bithumb.com/robots.txt allows everything but edit, login and api-next paths and points to llms.txt.", "https://www.bithumb.com/.well-known/security.txt timed out twice; recorded as unknown.", "RDAP gives bithumb.com a registration date of 16 June 2015.", "No status page found; the API has wallet-status and notices endpoints." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bithumb.json", "live": { "slug": "bithumb", "versions": [ { "registry": "npm", "name": "@bithumb-official/bithumb-cli", "version": "0.8.5", "seenAt": "2026-11-04T20:02:56.600783413Z" }, { "registry": "npm", "name": "@bithumb-official/bithumb-mcp", "version": "0.8.5", "seenAt": "2026-11-04T20:02:55.754674786Z" } ], "githubStars": 6, "npmWeekly": 87, "securityTxt": { "url": "https://bithumb.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:26.914675257Z" }, "updatedAt": "2026-11-04T20:02:57.989976217Z" } }, "answer": "Bithumb Open API scores 50.6 (D) on agent readiness against HTX trading API's 43.3 (E), and leads in 4 of 7 scored categories.", "b": { "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" } }, "edges": [ { "by": 24, "category": "schema", "leads": "bithumb", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI found; the reference is a readme.io site with Markdown twins, and the MCP tool schemas weren't read since the server's source isn't published (5 of 25). llms.txt on apidocs.bithumb.com (10). Reference pages state purpose and the skills say when to use each module and when not to (15 of 20). Typed parameters with enums for side, order type and time in force (10 of 15). Examples in several languages and an error-code page with names, statuses and meanings (12 of 15). Versions per endpoint (v1, v2, v2.1.5) and notices with effective dates (12 of 15). 5 + 10 + 15 + 10 + 12 + 12 = 64.", "b": "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." }, "scores": { "a": 64, "b": 40 } }, { "by": 22, "category": "transparency", "leads": "bithumb", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed service whose terms couldn't be read (timeouts and a title-only page); the kit is MIT with a disclaimer naming Bithumb Co., Ltd. (10 of 30). No privacy policy read (0 of 30, unchecked). Dated retirement of WebSocket Private v1 and effective dates on breaking notices (14 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 14 + 0 = 24.", "b": "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." }, "scores": { "a": 47, "b": 25 } }, { "by": 12, "category": "maintenance", "leads": "bithumb", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. Rate limits updated 27 October 2026 and the ticker cap effective 13 October 2026 (30). Batch orders 20 August, Private v1 retired 30 September, the ticker cap 13 October and the limits page 27 October 2026 (20). A phone support line, dated notices and a GitHub repository with no open issues and one commit; replies not observed (9 of 15). The MCP server is not in the official MCP registry and there is no SDK; the CLI and MCP packages are current (5 of 15). The MCP package depends only on @modelcontextprotocol/sdk ^1.26 on Node 18, with no public source or CI (5 of 10). 30 + 20 + 9 + 5 + 5 = 69.", "b": "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." }, "scores": { "a": 69, "b": 57 } }, { "by": 9, "category": "security", "leads": "bithumb", "name": "Security \u0026 auth", "reasons": { "a": "Keys scoped to chosen permissions, mandatory registered IPs, one-year expiry, a JWT per request and a key-list endpoint with expiry (26 of 30). Read-only keys, `--read-only` on the MCP server, per-profile read_only on the CLI, a second factor on KRW deposits and withdrawals, and skills that refuse to switch profiles to bypass read-only; nothing server-side confirms an order (16 of 20). The API returns exchange data and the disclaimer warns about prompt injection through third-party plugins (11 of 15). A local audit log for CLI and MCP calls and a key-list endpoint; no server-side per-call log (7 of 15). security.txt timed out and no disclosure policy, bug bounty or certification was found (0 of 20, security.txt unchecked). 26 + 16 + 11 + 7 + 0 = 60.", "b": "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." }, "scores": { "a": 60, "b": 51 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Bithumb Co., Ltd.", "b": "HTX", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "41", "b": "0", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-13", "b": "2026-10-21", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "6 stars", "b": "684 stars", "name": "Popularity" } ], "faq": [ { "answer": "Bithumb Open API scores 50.6 (D) on agent readiness against HTX trading API's 43.3 (E), and leads in 4 of 7 scored categories.", "question": "Which is better for AI agents, Bithumb Open API or HTX trading API?" }, { "answer": "Both need an API key.", "question": "Do Bithumb Open API and HTX trading API need an API key?" }, { "answer": "Bithumb Open API runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for HTX trading API.", "question": "Can an agent call Bithumb Open API and HTX trading API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 64 against 40", "Security \u0026 auth, 60 against 51", "Maintenance \u0026 community, 69 against 57", "Transparency \u0026 trust, 47 against 25" ], "also": [ "Runs on your own machine" ], "goodFor": "KRW-market trading for agents acting for a verified Korean account, with a vendor-built MCP server, CLI and skills.", "slug": "bithumb", "watchFor": "No sandbox or testnet; every order uses real funds" }, { "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" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.json", "title": "Bitfinex API vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bithumb" }, { "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/bitget-vs-bithumb.json", "title": "Bitget vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/bitget-vs-bithumb" }, { "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/bithumb-vs-bitstamp.json", "title": "Bithumb Open API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-bybit.json", "title": "Bithumb Open API vs Bybit", "url": "https://www.anchorterminal.com/compare/bithumb-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.json", "title": "Bithumb Open API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.json", "title": "Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.json", "title": "Bithumb Open API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-deribit.json", "title": "Bithumb Open API vs Deribit", "url": "https://www.anchorterminal.com/compare/bithumb-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-dydx.json", "title": "Bithumb Open API vs dYdX", "url": "https://www.anchorterminal.com/compare/bithumb-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-gate-io.json", "title": "Bithumb Open API vs Gate", "url": "https://www.anchorterminal.com/compare/bithumb-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.json", "title": "Bithumb Open API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.json", "title": "Bithumb Open API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-kraken.json", "title": "Bithumb Open API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-kucoin.json", "title": "Bithumb Open API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bithumb-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-mexc.json", "title": "Bithumb Open API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-okx.json", "title": "Bithumb Open API vs OKX API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-uniswap.json", "title": "Bithumb Open API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-upbit.json", "title": "Bithumb Open API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-upbit" }, { "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/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/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/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/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/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-kraken.json", "title": "HTX trading API vs Kraken API", "url": "https://www.anchorterminal.com/compare/htx-vs-kraken" }, { "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-bithumb.json", "title": "Binance API vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-bithumb" }, { "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/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-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/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/dydx-vs-htx.json", "title": "dYdX vs HTX trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-htx" } ], "panel": null, "scores": [ { "bithumb": 34, "by": 4, "edge": "htx", "htx": 38, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bithumb": 64, "by": 24, "edge": "bithumb", "htx": 40, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bithumb": 67, "by": 2, "edge": "htx", "htx": 69, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bithumb": 60, "by": 9, "edge": "bithumb", "htx": 51, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bithumb": 15, "by": 0, "edge": "", "htx": 15, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bithumb": 69, "by": 12, "edge": "bithumb", "htx": 57, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bithumb": 47, "by": 22, "edge": "bithumb", "htx": 25, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Bithumb Open API scores 50.6 (D) on agent readiness against HTX trading API's 43.3 (E), and leads in 4 of 7 scored categories. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "bithumb": "Bithumb runs an official local MCP server with 41 tools, module selection and a read-only flag, beside a CLI with per-profile read-only gating and six agent skills, over an API with scoped one-year keys and a mandatory IP list. There is no sandbox, no status page, no documented 429 behaviour, and the fees and terms couldn't be read.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bithumb-vs-htx", "json": "https://www.anchorterminal.com/compare/bithumb-vs-htx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bithumb-vs-htx.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bithumb-vs-htx.min.md" }, "markdown": "Bithumb Open API scores 50.6 (D) on agent readiness against HTX trading API's 43.3 (E), and leads in 4 of 7 scored categories. Both do exchange market data.\n\n- Bithumb Open API: grade D, 50.6/100, rank #999 of 1349. Markdown https://www.anchorterminal.com/tools/bithumb.md · JSON https://www.anchorterminal.com/api/v1/tools/bithumb.json\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- 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### Bithumb Open API (D)\n\nGood for: KRW-market trading for agents acting for a verified Korean account, with a vendor-built MCP server, CLI and skills.\n\nAhead on:\n- Schema \u0026 documentation, 64 against 40\n- Security \u0026 auth, 60 against 51\n- Maintenance \u0026 community, 69 against 57\n- Transparency \u0026 trust, 47 against 25\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No sandbox or testnet; every order uses real funds\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\n## Why the edge\n\n### Schema \u0026 documentation: Bithumb Open API +24\n\n- Bithumb Open API (64): No OpenAPI found; the reference is a readme.io site with Markdown twins, and the MCP tool schemas weren't read since the server's source isn't published (5 of 25). llms.txt on apidocs.bithumb.com (10). Reference pages state purpose and the skills say when to use each module and when not to (15 of 20). Typed parameters with enums for side, order type and time in force (10 of 15). Examples in several languages and an error-code page with names, statuses and meanings (12 of 15). Versions per endpoint (v1, v2, v2.1.5) and notices with effective dates (12 of 15). 5 + 10 + 15 + 10 + 12 + 12 = 64.\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\n### Transparency \u0026 trust: Bithumb Open API +22\n\n- Bithumb Open API (47): The editorial half. A closed service whose terms couldn't be read (timeouts and a title-only page); the kit is MIT with a disclaimer naming Bithumb Co., Ltd. (10 of 30). No privacy policy read (0 of 30, unchecked). Dated retirement of WebSocket Private v1 and effective dates on breaking notices (14 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 14 + 0 = 24.\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\n### Maintenance \u0026 community: Bithumb Open API +12\n\n- Bithumb Open API (69): Read as a closed service. Rate limits updated 27 October 2026 and the ticker cap effective 13 October 2026 (30). Batch orders 20 August, Private v1 retired 30 September, the ticker cap 13 October and the limits page 27 October 2026 (20). A phone support line, dated notices and a GitHub repository with no open issues and one commit; replies not observed (9 of 15). The MCP server is not in the official MCP registry and there is no SDK; the CLI and MCP packages are current (5 of 15). The MCP package depends only on @modelcontextprotocol/sdk ^1.26 on Node 18, with no public source or CI (5 of 10). 30 + 20 + 9 + 5 + 5 = 69.\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\n### Security \u0026 auth: Bithumb Open API +9\n\n- Bithumb Open API (60): Keys scoped to chosen permissions, mandatory registered IPs, one-year expiry, a JWT per request and a key-list endpoint with expiry (26 of 30). Read-only keys, `--read-only` on the MCP server, per-profile read_only on the CLI, a second factor on KRW deposits and withdrawals, and skills that refuse to switch profiles to bypass read-only; nothing server-side confirms an order (16 of 20). The API returns exchange data and the disclaimer warns about prompt injection through third-party plugins (11 of 15). A local audit log for CLI and MCP calls and a key-list endpoint; no server-side per-call log (7 of 15). security.txt timed out and no disclosure policy, bug bounty or certification was found (0 of 20, security.txt unchecked). 26 + 16 + 11 + 7 + 0 = 60.\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\n## Score by category\n\n| Category | Weight | Bithumb Open API | HTX trading API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 34 | 38 | HTX trading API +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 40 | Bithumb Open API +24 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 69 | HTX trading API +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 51 | Bithumb Open API +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 15 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 57 | Bithumb Open API +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 47 | 25 | Bithumb Open API +22 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.6 · D** | **43.3 · E** | |\n\n## Facts side by side\n\n| Fact | Bithumb Open API | HTX trading API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bithumb Co., Ltd. | HTX |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Tools exposed | 41 | 0 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-13 | 2026-10-21 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | no document linked | no document linked |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 6 stars | 684 stars |\n\n## Verdicts\n\n**Bithumb Open API.** Bithumb runs an official local MCP server with 41 tools, module selection and a read-only flag, beside a CLI with per-profile read-only gating and six agent skills, over an API with scoped one-year keys and a mandatory IP list. There is no sandbox, no status page, no documented 429 behaviour, and the fees and terms couldn't be read.\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## Before you call either\n\n### Bithumb Open API\n\n1. Ask for a key with asset and order inquiry plus order placement only, never withdrawals, with your IP registered; keys expire after one year and a wrong IP answers 401 NotAllowIP\n2. Start the server with `--modules market,account,trade --read-only` for analysis and drop `--read-only` only when the person asks to trade; deposit and withdraw modules stay off\n3. Prefer the `bithumb` CLI for writes, as the skills do, and check `bithumb config show --json` for a read-only profile before any order\n4. Keep the ticker's markets parameter at 200 or fewer, batch orders at 30 and cancels at 30 per request, and stay under 140 private calls a second per category\n5. Retry 422 order_not_ready and 500 server_error after a pause; there is no sandbox, so start with the smallest order the market allows\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## Questions\n\n### Which is better for AI agents, Bithumb Open API or HTX trading API?\n\nBithumb Open API scores 50.6 (D) on agent readiness against HTX trading API's 43.3 (E), and leads in 4 of 7 scored categories.\n\n### Do Bithumb Open API and HTX trading API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Bithumb Open API and HTX trading API without installing anything?\n\nBithumb Open API runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for HTX trading API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bithumb-vs-htx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bithumb-vs-htx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bithumb\", \"b\": \"htx\"}`. From a terminal: `anchor compare bithumb htx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bithumb.json and https://www.anchorterminal.com/api/v1/tools/htx.json\n\n## Other comparisons with Bithumb Open API or HTX trading API\n\n- [Bitfinex API vs Bithumb Open API](https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.md)\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)\n- [Bitget vs Bithumb Open API](https://www.anchorterminal.com/compare/bitget-vs-bithumb.md)\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md)\n- [Bithumb Open API vs Bitstamp API](https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.md)\n- [Bithumb Open API vs Bybit](https://www.anchorterminal.com/compare/bithumb-vs-bybit.md)\n- [Bithumb Open API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.md)\n- [Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.md)\n- [Bithumb Open API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.md)\n- [Bithumb Open API vs Deribit](https://www.anchorterminal.com/compare/bithumb-vs-deribit.md)\n- [Bithumb Open API vs dYdX](https://www.anchorterminal.com/compare/bithumb-vs-dydx.md)\n- [Bithumb Open API vs Gate](https://www.anchorterminal.com/compare/bithumb-vs-gate-io.md)\n- [Bithumb Open API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.md)\n- [Bithumb Open API vs Hyperliquid](https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.md)\n- [Bithumb Open API vs Kraken API](https://www.anchorterminal.com/compare/bithumb-vs-kraken.md)\n- [Bithumb Open API vs KuCoin](https://www.anchorterminal.com/compare/bithumb-vs-kucoin.md)\n- [Bithumb Open API vs MEXC API](https://www.anchorterminal.com/compare/bithumb-vs-mexc.md)\n- [Bithumb Open API vs OKX API](https://www.anchorterminal.com/compare/bithumb-vs-okx.md)\n- [Bithumb Open API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bithumb-vs-uniswap.md)\n- [Bithumb Open API vs Upbit Open API](https://www.anchorterminal.com/compare/bithumb-vs-upbit.md)\n- [Bitstamp API vs HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md)\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)\n- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md)\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md)\n- [Gemini Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.md)\n- [HTX trading API vs Hyperliquid](https://www.anchorterminal.com/compare/htx-vs-hyperliquid.md)\n- [HTX trading API vs Kraken API](https://www.anchorterminal.com/compare/htx-vs-kraken.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 Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.md)\n- [Deribit vs HTX trading API](https://www.anchorterminal.com/compare/deribit-vs-htx.md)\n- [dYdX vs HTX trading API](https://www.anchorterminal.com/compare/dydx-vs-htx.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": "Bithumb Open API vs HTX trading API", "url": "" } ], "description": "Bithumb Open scores 50.6 (D) to HTX trading's 43.3 (E) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bithumb Open API D 50.6", "HTX trading API E 43.3", "scores" ], "h1": "Bithumb Open API vs HTX trading API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bithumb-vs-htx", "published": "2026-10-01", "section": "tools", "title": "Bithumb Open vs HTX trading for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/bithumb-vs-htx" }, "tokens": { "markdown": 4050, "slim": 1880 }, "version": 1 }