# KuCoin vs Upbit Open API (slim)

> Upbit Open and KuCoin score within a point of each other for exchange market data, 54.7 and 53.9 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/kucoin-vs-upbit.md (~3,800 tokens) · this version ~1,730 tokens · JSON https://www.anchorterminal.com/compare/kucoin-vs-upbit.json · canonical https://www.anchorterminal.com/compare/kucoin-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 and KuCoin score within a point of each other on agent readiness, 54.7 (C) and 53.9 (D). KuCoin leads on payments & pricing. Both do exchange market data.

- KuCoin: D 53.9, rank #891 of 1349 · https://www.anchorterminal.com/tools/kucoin.min.md
- Upbit Open API: C 54.7, rank #860 of 1349 · https://www.anchorterminal.com/tools/upbit.min.md
- KuCoin, good for An agent trading spot, margin and futures in a person's KuCoin account outside the restricted list, with no sandbox and no MCP server, so through the SDK or raw REST. Ahead on Payments & pricing, 35 against 15.
- 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 60; Agent ergonomics, 70 against 62; Maintenance & community, 83 against 73.

| Category | KuCoin | Upbit Open API |
| --- | --- | --- |
| Reliability (16%) | 45 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 60 | 66 |
| Agent ergonomics (13%) | 62 | 70 |
| Security & auth (14%) | 55 | 59 |
| Payments & pricing (10%) | 35 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 83 |
| Transparency & trust (7%) | 54 | 54 |

| Fact (where they differ) | KuCoin | Upbit Open API |
| --- | --- | --- |
| Vendor | KuCoin | Dunamu Inc. |
| Tools exposed | none | 0 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-11-02 | 2026-10-20 |
| Terms last updated | no date given | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | 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 | 55 stars | 91 stars |

Why the edge:
- Payments & pricing, KuCoin +20: KuCoin 35 (No machine payment protocol (0). The spot base fee is stated in support articles without login, the futures base rate and the full tier table sit in images or behind script (15 of 20). Market data needs no key, no card is asked for at sign-up (20). A person registers, verifies identity and mints the key in a browser (0). 35.); Upbit Open API 15 (No machine payment protocol (0). The fee schedule is on upbit.com, which disallows every crawler path, so no price is recorded (0 of 20, unchecked). Public quotation endpoints need no key, card or account; trading needs a verified Korean account. Judgement call (15 of 20). A person must sign up, pass identity checks and issue keys on the PC web site (0). 0 + 0 + 15 + 0 = 15.)
- Maintenance & community, Upbit Open API +10: KuCoin 73 (Read as a closed hosted service. The changelog's newest past entry is 2 November 2026 and the universal SDK was pushed 15 September (30). Nine dated changelog entries since 5 August 2026 (20). A Telegram API group (t.me/KuCoin_API) and api@kucoin.com for limit requests, no public issue tracker for the API; the SDK repository's issues were not checked (10 of 25). Official SDKs current in five languages, no MCP registry presence (13 of 15). No package health signal checked (0 of 10). 73.); 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.)
- Agent ergonomics, Upbit Open API +8: KuCoin 62 (Read for the API alone, since there is no MCP server. Responses take limit and cursor parameters on list endpoints and the order book depth is a parameter (14 of 25). Pagination and symbol filters on orders, fills and ledgers (15 of 20). Codes and messages per response, with the V2 scheme claimed to be clearer; the rate-limit page's own examples contradict its table, which costs an agent a turn (12 of 20). clientOid on orders makes retries safe; no MCP annotations to read (10 of 20). Three required fields on a spot order, official SDKs in five languages (11 of 15). 62.); Upbit Open API 70 (Graded on the REST API with the CLI. Candle counts, list limits and the CLI's --max-items and --transform size responses (16 of 25). Paging and filters on orders and history (15 of 20). error.name codes to branch on, which the November 2026 notice tells clients to use, and 418 with its block length (15 of 20). An order-test endpoint and a CONFIRM gate in the skills; an order identifier for idempotent placement was not checked (11 of 20). Few required parameters, SDKs in three languages and a CLI, but keys need the PC web site and a registered IP (13 of 15). 16 + 15 + 15 + 11 + 13 = 70.)
- Schema & documentation, Upbit Open API +6: KuCoin 60 (No OpenAPI or other machine-readable contract was found; the docs link a Postman workspace and the universal SDK is generated from an internal spec (8 of 25). No llms.txt; the skills hub ships Markdown SKILL.md files with endpoint tables for seven product areas, read-only (6 of 10). One docs page per endpoint with a description, permission and weight, but no when-to-use guidance (12 of 20). Typed parameter tables with enums for type and side and required flags (11 of 15). Request and response examples per endpoint and a unified six-digit error code scheme introduced with V2 (10 of 15). Dated changelog with V1 to V2 versioning (13 of 15). 60.); 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.)