# Bithumb Open API vs Upbit Open API (slim)

> Upbit Open scores 54.7 (C) to Bithumb Open's 50.6 (D) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bithumb-vs-upbit.md (~3,700 tokens) · this version ~1,530 tokens · JSON https://www.anchorterminal.com/compare/bithumb-vs-upbit.json · canonical https://www.anchorterminal.com/compare/bithumb-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 Bithumb Open API's 50.6 (D), and leads in 5 of 7 scored categories. Both do exchange market data.

- Bithumb Open API: D 50.6, rank #999 of 1349 · https://www.anchorterminal.com/tools/bithumb.min.md
- Upbit Open API: C 54.7, rank #860 of 1349 · https://www.anchorterminal.com/tools/upbit.min.md
- Bithumb Open API, good for KRW-market trading for agents acting for a verified Korean account, with a vendor-built MCP server, CLI and skills. Also Runs on your own machine.
- 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 Reliability, 42 against 34; Maintenance & community, 83 against 69; Transparency & trust, 54 against 47.

| Category | Bithumb Open API | Upbit Open API |
| --- | --- | --- |
| Reliability (16%) | 34 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 66 |
| Agent ergonomics (13%) | 67 | 70 |
| Security & auth (14%) | 60 | 59 |
| Payments & pricing (10%) | 15 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 69 | 83 |
| Transparency & trust (7%) | 47 | 54 |

| Fact (where they differ) | Bithumb Open API | Upbit Open API |
| --- | --- | --- |
| Vendor | Bithumb Co., Ltd. | Dunamu Inc. |
| Transports | stdio |  |
| Tools exposed | 41 | 0 |
| Read-only variant documented | yes | no |
| Last release | 2026-10-13 | 2026-10-20 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | couldn't be read | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
| Popularity | 6 stars | 91 stars |

Why the edge:
- Maintenance & community, Upbit Open API +14: 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.); 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.)
- Reliability, Upbit Open API +8: Bithumb Open API 34 (Read with the hosted lines. No status page found on apidocs.bithumb.com or in llms.txt; wallet-status and notices endpoints stand in (0). No readable incident history, though two notices record a public WebSocket interruption and a brief service break (5). Rate limits documented per category with numbers, updated 27 October 2026 (15). A breach is described only as a temporary restriction, with no status code, header or Retry-After, and no client order id or idempotency key is documented; 422 order_not_ready and 500 server_error say to retry later (4 of 15). No SLA found (0). The API is generally available; the MCP server and CLI are at 0.8.5 (10). 0 + 5 + 15 + 4 + 0 + 10 = 34.); Upbit Open API 42 (Read with the hosted lines. No status page found on docs.upbit.com or in llms.txt; a wallet-status endpoint and an announcements stream stand in (0). No readable incident history (5). Rate limits documented with numbers per group, per IP and per pocket, updated 7 October 2026 (15). 429 then 418 with a stated block length and a Remaining-Req header, an order-test endpoint and a self-match-prevention default; an order identifier for safe retries was not checked (12 of 15). No SLA found (0). Generally available (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.)
- Transparency & trust, Upbit Open API +7: 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.); 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.)