{ "data": { "a": { "slug": "htx", "name": "HTX trading API", "vendor": "HTX", "vendorUrl": "https://www.htx.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "HTX, the exchange formerly Huobi, runs REST and WebSocket APIs for spot and derivatives trading, balances, transfers and withdrawals, authenticated with HMAC-signed API keys that carry read, trade and withdraw permissions.", "url": "https://www.anchorterminal.com/tools/htx", "markdownUrl": "https://www.anchorterminal.com/tools/htx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/htx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/htx.json", "dns": "htx.grade.anchorterminal.com", "repo": "https://github.com/HuobiRDCenter", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API keys made in the account's API Management page after a browser sign-up and identity check. Requests are signed with HMAC SHA256 (SignatureVersion 2) over the query string, with AccessKeyId, Timestamp and the Signature sent as query parameters; the secret never travels. A main account key carries Read, Trade and Withdraw permissions, a sub-user key Read and Trade only. A key can be bound to up to 20 IP addresses, and the docs say a key without IP binding expires after 90 days (https://huobiapi.github.io/docs/spot/v1/en/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "Trading fees per order. The fee schedule at htx.com/fee is drawn by script and answered our reader with no text, so no rate is recorded; third-party guides give 0.2 per cent maker and taker at the base tier, which is a lead and not a source. Public market data needs no key and no account (https://www.htx.com/fee/, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs or on the pages that loaded (checked 2026-11-03). Trading fees are taken from each fill.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 684, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://huobiapi.github.io/docs/spot/v1/en/", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "api-key", "closed-source", "usage-priced", "python", "java", "go", "no-status-page" ], "lastRelease": "2026-10-21", "graded": true, "anchor": { "graded": true, "score": 43.3, "grade": "E", "agentReady": false, "rank": 1166, "ranked": true, "rankOf": 1349, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 57, "payments": 15, "reliability": 38, "schema": 40, "security": 51, "transparency": 25 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.", "bestFor": "Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.", "strengths": [ "Key permissions split into Read, Trade and Withdraw, sub-user keys without Withdraw, and up to 20 bound IP addresses per key", "Rate limits published per endpoint with numbers, and remaining-quota headers on every response", "A client-order-id unique within 8 hours on orders and idempotent on withdrawals, so a retry doesn't double an order", "Official SDKs in Python, Java, C++, C# and Go, the contract ones pushed on 21 October 2026" ], "weaknesses": [ "No official MCP server; the only one in the MCP registry is a third party's read-only ticker server", "The testnet is shut down, so order logic can only be tried with real funds", "The public API reference is still branded Huobi with a last changelog entry of June 2022, and HTX's newer docs are drawn by script", "No status page, no SLA and no documented 429 or Retry-After behaviour", "The fee schedule, user agreement, privacy policy and restricted-country list couldn't be read, so none is recorded first-hand" ], "agentNotes": [ "Ask the operator for a key with Read and Trade only and bound to your IP addresses; a key without IP binding expires after 90 days", "Send a fresh client-order-id of up to 64 characters with every order and reuse it only on retry; a repeat within 8 hours answers invalid.client.order.id", "Watch X-HB-RateLimit-Requests-Remain and pace at under 100 order calls per 2 seconds per UID; limits are shared by every key on the account", "There is no testnet; try order logic with the smallest size the market allows", "Confirm the person's country is served before trading; the restricted list in the user agreement couldn't be read here" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 57, "payments": 15, "reliability": 38, "schema": 40, "security": 51, "transparency": 15 }, "provenanceScore": 34, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.huobi.pro/market/tickers" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/htx" }, "area": "payments", "provenance": { "legalEntity": "", "domain": "htx.com", "domainRegistered": "1995-12-13", "endpointOnVendorDomain": false, "terms": "https://www.htx.com/en-in/support/360000298561/", "privacy": "", "statusPage": "", "changelog": "https://huobiapi.github.io/docs/spot/v1/en/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The legal entity is unread. The HTX Platform User Agreement and every other page on www.htx.com answered our reader with no text on 3 November 2026 (the pages are drawn by script), so the terms, privacy policy, fee schedule and about page were not read. Terms URL recorded from a search result's title.", "RDAP gives htx.com a registration date of 13 December 1995, long before the exchange took the name in 2023; the domain was acquired, not registered, by the exchange.", "The API endpoint api.huobi.pro is on the old huobi.pro domain, not htx.com.", "www.htx.com/robots.txt allows / and disallows account paths (finance/account, user-center/security and the like). www.huobi.com/robots.txt disallows everything and was not read further. huobiapi.github.io has no robots.txt.", "https://www.htx.com/.well-known/security.txt answered no text; recorded as none. status.htx.com does not resolve." ], "score": 34 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/htx.json", "live": { "slug": "htx", "securityTxt": { "url": "https://htx.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:20.226147452Z" }, "updatedAt": "2026-11-04T15:54:20.226147452Z" } }, "answer": "Upbit Open API scores 54.7 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in 6 of 7 scored categories.", "b": { "slug": "upbit", "name": "Upbit Open API", "vendor": "Dunamu Inc.", "vendorUrl": "https://docs.upbit.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Upbit, the Korean exchange run by Dunamu, has a REST and WebSocket Open API for KRW, BTC and USDT market data, orders, balances, deposits and withdrawals, with official SDKs, a CLI and agent skills but no MCP server.", "url": "https://www.anchorterminal.com/tools/upbit", "markdownUrl": "https://www.anchorterminal.com/tools/upbit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/upbit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/upbit.json", "dns": "upbit.grade.anchorterminal.com", "repo": "https://github.com/upbit-official", "transports": [], "packages": [ { "registry": "npm", "name": "@upbit-official/upbit-cli" }, { "registry": "pypi", "name": "upbit-sdk" } ], "auth": "api-key", "authNotes": "Access and secret keys issued on the PC web site under My Page \u003e Open API Management after identity verification and two-factor authentication. At issuance the person picks the functions the key may use and must register at least one public IPv4 address, since the allow-list is mandatory. Each request carries a JWT signed with HMAC SHA512 over the access key, a fresh nonce and a SHA512 hash of the query, as a Bearer token. A key with withdrawal permission gets a withdrawal safe-lock by default that is lifted only in the mobile app. Up to 10 keys on the main pocket and 5 per sub-pocket; expired keys answer expired_access_key (https://docs.upbit.com/kr/docs/api-key.md, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "Trading fees per fill. The fee schedule is on upbit.com, whose robots.txt disallows every path for our crawler, so no rate is recorded. Public quotation endpoints need no key and no account (https://upbit.com/robots.txt, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, llms.txt, the SDK licence or the CLI docs (checked 2026-11-03). Fees are taken from each fill.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 91, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.upbit.com/kr/reference/api-overview", "llmsTxt": "https://docs.upbit.com/llms.txt", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "api-key", "closed-source", "usage-priced", "cli", "agent-skills", "llms-txt", "python", "typescript", "go", "no-status-page" ], "lastRelease": "2026-10-20", "graded": true, "anchor": { "graded": true, "score": 54.7, "grade": "C", "agentReady": false, "rank": 860, "ranked": true, "rankOf": 1349, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 83, "payments": 15, "reliability": 42, "schema": 66, "security": 59, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Upbit's Open API has a mandatory IP allow-list, scoped keys with a default withdrawal lock, per-group rate limits with 429 and 418 signalling, an order-test endpoint, official SDKs, a CLI and agent skills with a CONFIRM gate. There is no MCP server, sandbox or status page, and the fees and terms sit on a host our crawler may not read.", "bestFor": "KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.", "strengths": [ "Keys need a registered public IP, carry only the chosen functions and get a withdrawal safe-lock by default that only the mobile app lifts", "Rate limits published per group with numbers, a Remaining-Req header on every response, 429 then 418 with a stated block length", "POST /v1/orders/test checks an order and the pair's state at no cost, and the skills run it before a live order", "Official Python, TypeScript and Go SDKs at v1.1.0 (20 October 2026), a CLI with JSON output and agent skills that require a typed CONFIRM before any write", "Notices carry effective dates, such as the path-format change of 16 November 2026" ], "weaknesses": [ "No MCP server; the agent route is the CLI through skills, which need a terminal", "No sandbox or testnet beyond the order-test endpoint, and no status page or SLA", "Keys can only be issued on the PC web site after Korean identity verification and 2FA, and the exchange serves the Korean market", "The fee schedule, user terms and Open API terms are on upbit.com, which disallows every crawler path, so none is recorded first-hand", "The SDK licence page says the SDK material is not open source while the GitHub repositories carry Apache-2.0" ], "agentNotes": [ "Ask the person for a key with only the functions the task needs and your server's public IPv4 address registered; a private or unregistered IP is refused", "Sign every request with a fresh JWT (HS512, new nonce, SHA512 query hash) and branch on error.name, not error.message", "Run POST /v1/orders/test before a live order; it costs nothing and shares the 8-a-second order-test group", "Read Remaining-Req and keep orders under 12 a second per pocket; on 429 wait for the next second and on 418 wait out the stated block", "Leave the withdrawal safe-lock on unless the person lifts it in the app, and send paths with single slashes and no trailing slash before 16 November 2026" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.7 } ], "editorialScores": { "ergonomics": 70, "maintenance": 83, "payments": 15, "reliability": 42, "schema": 66, "security": 59, "transparency": 42 }, "provenanceScore": 66, "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 @upbit-official/upbit-cli", "http": "curl 'https://api.upbit.com/v1/ticker?markets=KRW-BTC'" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/upbit" }, "area": "payments", "provenance": { "legalEntity": "Dunamu Inc.", "domain": "upbit.com", "domainRegistered": "2004-01-10", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://docs.upbit.com/kr/page/privacy_policy_v1_5.md", "statusPage": "", "changelog": "https://docs.upbit.com/kr/changelog", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "Dunamu Inc. is named as the licensor in the Upbit Developer SDK License v1.0 and as the company in the developer centre's privacy policy V1.5 (from 18 May 2026).", "upbit.com/robots.txt disallows every path for User-agent * (a second group adds /terms_and_policy and others), allowing only Googlebot, MSNBot, Yeti and Daumoa; sg.upbit.com and www.dunamu.com do the same. The user terms, the Open API terms, the fee schedule and security.txt on those hosts were therefore not fetched; the terms URL is left empty.", "docs.upbit.com/robots.txt allows everything but edit, login and api-next paths and points to llms.txt, with Content-Signal ai-train=yes, search=yes, ai-input=yes.", "RDAP gives upbit.com a registration date of 10 January 2004.", "No status page found; the API has a service-status (wallet status) endpoint and an announcements WebSocket stream." ], "score": 66 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/upbit.json", "live": { "slug": "upbit", "securityTxt": { "url": "https://upbit.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:27.560288922Z" }, "updatedAt": "2026-11-04T15:53:27.560288922Z" } }, "edges": [ { "by": 29, "category": "transparency", "leads": "upbit", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed service whose user agreement exists but couldn't be read (script-drawn pages), so the licence clarity is unknown rather than unclear (10 of 30). The privacy policy was not read (0 of 30, unchecked). The testnet shutdown and the 2022 changelog entries are dated, with no deprecation policy (5 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 5 + 0 = 15.", "b": "The editorial half. A closed service whose user and Open API terms could not be fetched under upbit.com's robots.txt, and whose SDK licence page calls the SDK material not open source while the repositories carry Apache-2.0 (8 of 30). The developer centre's privacy policy names Dunamu Inc., gives retention periods and names Zendesk in Japan; the main privacy policy was not read (14 of 30). Notices with effective dates, including the path-format change and the deprecated Remaining-Req min field (12 of 20). Zendesk and Google Analytics named with a location for the developer centre only (8 of 20). 8 + 14 + 12 + 8 = 42." }, "scores": { "a": 25, "b": 54 } }, { "by": 26, "category": "schema", "leads": "upbit", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI or other machine-readable contract found in the docs or the GitHub accounts (0). No llms.txt on htx.com, and the readable reference is a static page (0). Each endpoint states its purpose and parameters, without when-to-use guidance (12 of 20). Parameter tables carry types, required flags and enums for order types and states (10 of 15). Request and response examples throughout and error-code tables with messages (11 of 15). Versions v1 and v2 are mixed in one reference whose last changelog entry is 24 June 2022, while HTX's newer docs on htx.com couldn't be read (7 of 15). 0 + 0 + 12 + 10 + 11 + 7 = 40.", "b": "No OpenAPI found; the reference is a readme.io site with a Markdown twin of every page (5 of 25). llms.txt on docs.upbit.com and a kr/llms.txt index (10). Each reference page states what the endpoint does, its group and its errors, with warnings such as market_offline after maintenance (14 of 20). Typed parameters with enums for order type, side and time in force and required flags (11 of 15). Recipes in Python, Java and Node.js and an error format of error.name and error.message with HTTP statuses (13 of 15). Feature versions in page histories (v1.6.1) and dated notices with effective dates, no single API version (13 of 15). 5 + 10 + 14 + 11 + 13 + 13 = 66." }, "scores": { "a": 40, "b": 66 } }, { "by": 26, "category": "maintenance", "leads": "upbit", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The readable changelog ends on 24 June 2022, but the official contract SDKs were pushed on 21 October 2026 and the spot SDKs in April and July 2026, so the API surface is still being maintained; judgement call (20 of 30). SDK pushes on 30 July, 23 August and 21 October 2026 are commits, not releases (10 of 20). A Telegram group for API support and a support centre, neither tested; GitHub issues not read (8 of 15). Official SDKs in five languages (15). No CI seen, dependencies not checked (4 of 10). 20 + 10 + 8 + 15 + 4 = 57.", "b": "Read as a closed service. SDK v1.1.0 on 20 October 2026 (30). The CLI 1.0.0 on 1 September, the rate-limit update of 7 October, the SDK on 20 October and the path-format notice for 16 November 2026 (20). open-api@upbit.com answers in turn on weekdays per the support notice, notices carry dates, and the six upbit-official repositories show no open issues (12 of 15). Current official SDKs in Python, TypeScript and Go (15). Apache-2.0 repositories pushed in October 2026; CI not checked (6 of 10). 30 + 20 + 12 + 15 + 6 = 83." }, "scores": { "a": 57, "b": 83 } }, { "by": 8, "category": "security", "leads": "upbit", "name": "Security \u0026 auth", "reasons": { "a": "HMAC-signed keys with Read, Trade and Withdraw permissions, sub-user keys without Withdraw, up to 20 bound IPs, revocation in the account and a 90-day expiry without IP binding. The AccessKeyId and the HMAC signature travel as query parameters; the secret does not, so no deduction for a secret in the URL (24 of 30). Read-only keys and withdraw-free keys exist; no server-side confirmation for orders or withdrawals (14 of 20). The API returns the exchange's own data, no untrusted content (10). No per-call log or key-use history found for the operator (3 of 15). No security.txt, disclosure policy or certification found on the pages that loaded (0 of 20). 24 + 14 + 10 + 3 + 0 = 51.", "b": "Keys limited to chosen functions, a mandatory public IPv4 allow-list, a JWT per request with a fresh nonce, keys listed with expiry through the API, and a withdrawal safe-lock on by default (27 of 30). Read-only keys, the default withdrawal lock lifted only in the app, and skills that require a typed CONFIRM before writes (17 of 20). The API returns exchange data and announcements, no third-party content (10 of 15). An API key list endpoint; no per-call log for the operator (5 of 15). No disclosure policy, bug bounty or certification found; security.txt on upbit.com could not be fetched under its robots.txt (0 of 20). 27 + 17 + 10 + 5 + 0 = 59." }, "scores": { "a": 51, "b": 59 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HTX", "b": "Dunamu Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "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": "0", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-21", "b": "2026-10-20", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "684 stars", "b": "91 stars", "name": "Popularity" } ], "faq": [ { "answer": "Upbit Open API scores 54.7 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, HTX trading API or Upbit Open API?" }, { "answer": "Both need an API key.", "question": "Do HTX trading API and Upbit Open API need an API key?" }, { "answer": "No hosted endpoint is listed for HTX trading API. No hosted endpoint is listed for Upbit Open API.", "question": "Can an agent call HTX trading API and Upbit Open API without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.", "slug": "htx", "watchFor": "No official MCP server; the only one in the MCP registry is a third party's read-only ticker server" }, { "aheadOn": [ "Schema \u0026 documentation, 66 against 40", "Security \u0026 auth, 59 against 51", "Maintenance \u0026 community, 83 against 57", "Transparency \u0026 trust, 54 against 25" ], "also": null, "goodFor": "KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.", "slug": "upbit", "watchFor": "No MCP server; the agent route is the CLI through skills, which need a terminal" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-htx.json", "title": "Bitfinex API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit.json", "title": "Bitfinex API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-htx.json", "title": "Bitget vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitget-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-upbit.json", "title": "Bitget vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitget-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-htx.json", "title": "Bithumb Open API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-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/bitstamp-vs-upbit.json", "title": "Bitstamp API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-htx.json", "title": "Bybit vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bybit-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-upbit.json", "title": "Bybit vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bybit-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.json", "title": "Crypto.com Exchange API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.json", "title": "Crypto.com Exchange API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-upbit.json", "title": "Deribit vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/deribit-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-upbit.json", "title": "dYdX vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/dydx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-htx.json", "title": "Gate vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-upbit.json", "title": "Gate vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.json", "title": "Gemini Exchange API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit.json", "title": "Gemini Exchange API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit" }, { "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/hyperliquid-vs-upbit.json", "title": "Hyperliquid vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-upbit.json", "title": "KuCoin vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-upbit.json", "title": "MEXC API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/mexc-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-htx.json", "title": "Binance API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/binance-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-upbit.json", "title": "Binance API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.json", "title": "Coinbase Advanced Trade API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.json", "title": "Coinbase Advanced Trade API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-upbit.json", "title": "Kraken API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/kraken-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/okx-vs-upbit.json", "title": "OKX API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/okx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/uniswap-vs-upbit.json", "title": "Uniswap Trading API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/uniswap-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-htx.json", "title": "Deribit vs HTX trading API", "url": "https://www.anchorterminal.com/compare/deribit-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-htx.json", "title": "dYdX vs HTX trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-htx" } ], "panel": null, "scores": [ { "by": 4, "edge": "upbit", "htx": 38, "key": "reliability", "name": "Reliability", "upbit": 42, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 26, "edge": "upbit", "htx": 40, "key": "schema", "name": "Schema \u0026 documentation", "upbit": 66, "weight": 13 }, { "by": 1, "edge": "upbit", "htx": 69, "key": "ergonomics", "name": "Agent ergonomics", "upbit": 70, "weight": 13 }, { "by": 8, "edge": "upbit", "htx": 51, "key": "security", "name": "Security \u0026 auth", "upbit": 59, "weight": 14 }, { "by": 0, "edge": "", "htx": 15, "key": "payments", "name": "Payments \u0026 pricing", "upbit": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 26, "edge": "upbit", "htx": 57, "key": "maintenance", "name": "Maintenance \u0026 community", "upbit": 83, "weight": 7 }, { "by": 29, "edge": "upbit", "htx": 25, "key": "transparency", "name": "Transparency \u0026 trust", "upbit": 54, "weight": 7 } ], "summary": "Upbit Open API scores 54.7 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in 6 of 7 scored categories. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "htx": "HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.", "upbit": "Upbit's Open API has a mandatory IP allow-list, scoped keys with a default withdrawal lock, per-group rate limits with 429 and 418 signalling, an order-test endpoint, official SDKs, a CLI and agent skills with a CONFIRM gate. There is no MCP server, sandbox or status page, and the fees and terms sit on a host our crawler may not read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/htx-vs-upbit", "json": "https://www.anchorterminal.com/compare/htx-vs-upbit.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/htx-vs-upbit.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/htx-vs-upbit.min.md" }, "markdown": "Upbit Open API scores 54.7 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in 6 of 7 scored categories. Both do exchange market data.\n\n- HTX trading API: grade E, 43.3/100, rank #1166 of 1349. Markdown https://www.anchorterminal.com/tools/htx.md · JSON https://www.anchorterminal.com/api/v1/tools/htx.json\n- Upbit Open API: grade C, 54.7/100, rank #860 of 1349. Markdown https://www.anchorterminal.com/tools/upbit.md · JSON https://www.anchorterminal.com/api/v1/tools/upbit.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Which one, for what\n\n### HTX trading API (E)\n\nGood for: Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.\n\nWatch for: No official MCP server; the only one in the MCP registry is a third party's read-only ticker server\n\n### Upbit Open API (C)\n\nGood for: KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.\n\nAhead on:\n- Schema \u0026 documentation, 66 against 40\n- Security \u0026 auth, 59 against 51\n- Maintenance \u0026 community, 83 against 57\n- Transparency \u0026 trust, 54 against 25\n\nWatch for: No MCP server; the agent route is the CLI through skills, which need a terminal\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Upbit Open API +29\n\n- HTX trading API (25): The editorial half. A closed service whose user agreement exists but couldn't be read (script-drawn pages), so the licence clarity is unknown rather than unclear (10 of 30). The privacy policy was not read (0 of 30, unchecked). The testnet shutdown and the 2022 changelog entries are dated, with no deprecation policy (5 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 5 + 0 = 15.\n- Upbit Open API (54): The editorial half. A closed service whose user and Open API terms could not be fetched under upbit.com's robots.txt, and whose SDK licence page calls the SDK material not open source while the repositories carry Apache-2.0 (8 of 30). The developer centre's privacy policy names Dunamu Inc., gives retention periods and names Zendesk in Japan; the main privacy policy was not read (14 of 30). Notices with effective dates, including the path-format change and the deprecated Remaining-Req min field (12 of 20). Zendesk and Google Analytics named with a location for the developer centre only (8 of 20). 8 + 14 + 12 + 8 = 42.\n\n### Schema \u0026 documentation: Upbit Open API +26\n\n- HTX trading API (40): No OpenAPI or other machine-readable contract found in the docs or the GitHub accounts (0). No llms.txt on htx.com, and the readable reference is a static page (0). Each endpoint states its purpose and parameters, without when-to-use guidance (12 of 20). Parameter tables carry types, required flags and enums for order types and states (10 of 15). Request and response examples throughout and error-code tables with messages (11 of 15). Versions v1 and v2 are mixed in one reference whose last changelog entry is 24 June 2022, while HTX's newer docs on htx.com couldn't be read (7 of 15). 0 + 0 + 12 + 10 + 11 + 7 = 40.\n- Upbit Open API (66): No OpenAPI found; the reference is a readme.io site with a Markdown twin of every page (5 of 25). llms.txt on docs.upbit.com and a kr/llms.txt index (10). Each reference page states what the endpoint does, its group and its errors, with warnings such as market_offline after maintenance (14 of 20). Typed parameters with enums for order type, side and time in force and required flags (11 of 15). Recipes in Python, Java and Node.js and an error format of error.name and error.message with HTTP statuses (13 of 15). Feature versions in page histories (v1.6.1) and dated notices with effective dates, no single API version (13 of 15). 5 + 10 + 14 + 11 + 13 + 13 = 66.\n\n### Maintenance \u0026 community: Upbit Open API +26\n\n- HTX trading API (57): Read as a closed service. The readable changelog ends on 24 June 2022, but the official contract SDKs were pushed on 21 October 2026 and the spot SDKs in April and July 2026, so the API surface is still being maintained; judgement call (20 of 30). SDK pushes on 30 July, 23 August and 21 October 2026 are commits, not releases (10 of 20). A Telegram group for API support and a support centre, neither tested; GitHub issues not read (8 of 15). Official SDKs in five languages (15). No CI seen, dependencies not checked (4 of 10). 20 + 10 + 8 + 15 + 4 = 57.\n- Upbit Open API (83): Read as a closed service. SDK v1.1.0 on 20 October 2026 (30). The CLI 1.0.0 on 1 September, the rate-limit update of 7 October, the SDK on 20 October and the path-format notice for 16 November 2026 (20). open-api@upbit.com answers in turn on weekdays per the support notice, notices carry dates, and the six upbit-official repositories show no open issues (12 of 15). Current official SDKs in Python, TypeScript and Go (15). Apache-2.0 repositories pushed in October 2026; CI not checked (6 of 10). 30 + 20 + 12 + 15 + 6 = 83.\n\n### Security \u0026 auth: Upbit Open API +8\n\n- HTX trading API (51): HMAC-signed keys with Read, Trade and Withdraw permissions, sub-user keys without Withdraw, up to 20 bound IPs, revocation in the account and a 90-day expiry without IP binding. The AccessKeyId and the HMAC signature travel as query parameters; the secret does not, so no deduction for a secret in the URL (24 of 30). Read-only keys and withdraw-free keys exist; no server-side confirmation for orders or withdrawals (14 of 20). The API returns the exchange's own data, no untrusted content (10). No per-call log or key-use history found for the operator (3 of 15). No security.txt, disclosure policy or certification found on the pages that loaded (0 of 20). 24 + 14 + 10 + 3 + 0 = 51.\n- Upbit Open API (59): Keys limited to chosen functions, a mandatory public IPv4 allow-list, a JWT per request with a fresh nonce, keys listed with expiry through the API, and a withdrawal safe-lock on by default (27 of 30). Read-only keys, the default withdrawal lock lifted only in the app, and skills that require a typed CONFIRM before writes (17 of 20). The API returns exchange data and announcements, no third-party content (10 of 15). An API key list endpoint; no per-call log for the operator (5 of 15). No disclosure policy, bug bounty or certification found; security.txt on upbit.com could not be fetched under its robots.txt (0 of 20). 27 + 17 + 10 + 5 + 0 = 59.\n\n## Score by category\n\n| Category | Weight | HTX trading API | Upbit Open API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 38 | 42 | Upbit Open API +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 66 | Upbit Open API +26 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 70 | Upbit Open API +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 59 | Upbit Open API +8 |\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) | 57 | 83 | Upbit Open API +26 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 25 | 54 | Upbit Open API +29 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **43.3 · E** | **54.7 · C** | |\n\n## Facts side by side\n\n| Fact | HTX trading API | Upbit Open API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HTX | Dunamu Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Tools exposed | 0 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-21 | 2026-10-20 |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | yes | not read yet |\n| Arbitration or class-action waiver | yes | not read yet |\n| Popularity | 684 stars | 91 stars |\n\n## Verdicts\n\n**HTX trading API.** HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.\n\n**Upbit Open API.** Upbit's Open API has a mandatory IP allow-list, scoped keys with a default withdrawal lock, per-group rate limits with 429 and 418 signalling, an order-test endpoint, official SDKs, a CLI and agent skills with a CONFIRM gate. There is no MCP server, sandbox or status page, and the fees and terms sit on a host our crawler may not read.\n\n## Before you call either\n\n### HTX trading API\n\n1. Ask the operator for a key with Read and Trade only and bound to your IP addresses; a key without IP binding expires after 90 days\n2. Send a fresh client-order-id of up to 64 characters with every order and reuse it only on retry; a repeat within 8 hours answers invalid.client.order.id\n3. Watch X-HB-RateLimit-Requests-Remain and pace at under 100 order calls per 2 seconds per UID; limits are shared by every key on the account\n4. There is no testnet; try order logic with the smallest size the market allows\n5. Confirm the person's country is served before trading; the restricted list in the user agreement couldn't be read here\n\n### Upbit Open API\n\n1. Ask the person for a key with only the functions the task needs and your server's public IPv4 address registered; a private or unregistered IP is refused\n2. Sign every request with a fresh JWT (HS512, new nonce, SHA512 query hash) and branch on error.name, not error.message\n3. Run POST /v1/orders/test before a live order; it costs nothing and shares the 8-a-second order-test group\n4. Read Remaining-Req and keep orders under 12 a second per pocket; on 429 wait for the next second and on 418 wait out the stated block\n5. Leave the withdrawal safe-lock on unless the person lifts it in the app, and send paths with single slashes and no trailing slash before 16 November 2026\n\n## Questions\n\n### Which is better for AI agents, HTX trading API or Upbit Open API?\n\nUpbit Open API scores 54.7 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in 6 of 7 scored categories.\n\n### Do HTX trading API and Upbit Open API need an API key?\n\nBoth need an API key.\n\n### Can an agent call HTX trading API and Upbit Open API without installing anything?\n\nNo hosted endpoint is listed for HTX trading API. No hosted endpoint is listed for Upbit Open API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/htx-vs-upbit.json, and with the fewest tokens: https://www.anchorterminal.com/compare/htx-vs-upbit.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"htx\", \"b\": \"upbit\"}`. From a terminal: `anchor compare htx upbit`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/htx.json and https://www.anchorterminal.com/api/v1/tools/upbit.json\n\n## Other comparisons with HTX trading API or Upbit Open API\n\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)\n- [Bitfinex API vs Upbit Open API](https://www.anchorterminal.com/compare/bitfinex-vs-upbit.md)\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md)\n- [Bitget vs Upbit Open API](https://www.anchorterminal.com/compare/bitget-vs-upbit.md)\n- [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.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- [Bitstamp API vs Upbit Open API](https://www.anchorterminal.com/compare/bitstamp-vs-upbit.md)\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)\n- [Bybit vs Upbit Open API](https://www.anchorterminal.com/compare/bybit-vs-upbit.md)\n- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md)\n- [Crypto.com Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.md)\n- [Deribit vs Upbit Open API](https://www.anchorterminal.com/compare/deribit-vs-upbit.md)\n- [dYdX vs Upbit Open API](https://www.anchorterminal.com/compare/dydx-vs-upbit.md)\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md)\n- [Gate vs Upbit Open API](https://www.anchorterminal.com/compare/gate-io-vs-upbit.md)\n- [Gemini Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.md)\n- [Gemini Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit.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- [Hyperliquid vs Upbit Open API](https://www.anchorterminal.com/compare/hyperliquid-vs-upbit.md)\n- [KuCoin vs Upbit Open API](https://www.anchorterminal.com/compare/kucoin-vs-upbit.md)\n- [MEXC API vs Upbit Open API](https://www.anchorterminal.com/compare/mexc-vs-upbit.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Binance API vs Upbit Open API](https://www.anchorterminal.com/compare/binance-vs-upbit.md)\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md)\n- [Coinbase Advanced Trade API vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.md)\n- [Coinbase MCP server (Coinbase for Agents) vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit.md)\n- [Kraken API vs Upbit Open API](https://www.anchorterminal.com/compare/kraken-vs-upbit.md)\n- [OKX API vs Upbit Open API](https://www.anchorterminal.com/compare/okx-vs-upbit.md)\n- [Uniswap Trading API vs Upbit Open API](https://www.anchorterminal.com/compare/uniswap-vs-upbit.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": "HTX trading API vs Upbit Open API", "url": "" } ], "description": "Upbit Open scores 54.7 (C) to HTX trading's 43.3 (E) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "HTX trading API E 43.3", "Upbit Open API C 54.7", "scores" ], "h1": "HTX trading API vs Upbit Open API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/htx-vs-upbit", "published": "2026-10-01", "section": "tools", "title": "HTX trading vs Upbit Open for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/htx-vs-upbit" }, "tokens": { "markdown": 4000, "slim": 1880 }, "version": 1 }