# HTX trading API vs Upbit Open API (slim)

> 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.

- Full: https://www.anchorterminal.com/compare/htx-vs-upbit.md (~4,000 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/htx-vs-upbit.json · canonical https://www.anchorterminal.com/compare/htx-vs-upbit
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-03
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- HTX trading API: E 43.3, rank #1166 of 1349 · https://www.anchorterminal.com/tools/htx.min.md
- Upbit Open API: C 54.7, rank #860 of 1349 · https://www.anchorterminal.com/tools/upbit.min.md
- HTX trading API, good for Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.
- Upbit Open API, good for KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP. Ahead on Schema & documentation, 66 against 40; Security & auth, 59 against 51; Maintenance & community, 83 against 57; Transparency & trust, 54 against 25.

| Category | HTX trading API | Upbit Open API |
| --- | --- | --- |
| Reliability (16%) | 38 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 40 | 66 |
| Agent ergonomics (13%) | 69 | 70 |
| Security & auth (14%) | 51 | 59 |
| Payments & pricing (10%) | 15 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 57 | 83 |
| Transparency & trust (7%) | 25 | 54 |

| Fact (where they differ) | HTX trading API | Upbit Open API |
| --- | --- | --- |
| Vendor | HTX | Dunamu Inc. |
| llms.txt | no | yes |
| Last release | 2026-10-21 | 2026-10-20 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 684 stars | 91 stars |

Why the edge:
- Transparency & trust, Upbit Open API +29: 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.); 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.)
- Schema & documentation, Upbit Open API +26: 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.); 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.)
- Maintenance & community, Upbit Open API +26: 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.); 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.)
- Security & auth, Upbit Open API +8: 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.); 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.)