# Bybit vs Upbit Open API (slim)

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

- Full: https://www.anchorterminal.com/compare/bybit-vs-upbit.md (~3,600 tokens) · this version ~1,480 tokens · JSON https://www.anchorterminal.com/compare/bybit-vs-upbit.json · canonical https://www.anchorterminal.com/compare/bybit-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-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Bybit scores 57.3 (C) on agent readiness against Upbit Open API's 54.7 (C), and leads in 4 of 7 scored categories. Upbit Open API leads on maintenance & community. Both do exchange market data.

- Bybit: C 57.3, rank #712 of 1349 · https://www.anchorterminal.com/tools/bybit.min.md
- Upbit Open API: C 54.7, rank #802 of 1349 · https://www.anchorterminal.com/tools/upbit.min.md
- Bybit, good for An agent trading spot, perpetuals, futures and options in a person's Bybit account outside the excluded jurisdictions, with a demo environment to rehearse on. Ahead on Schema & documentation, 73 against 66; Payments & pricing, 40 against 15. 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 Maintenance & community, 83 against 66.

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

| Fact (where they differ) | Bybit | Upbit Open API |
| --- | --- | --- |
| Vendor | Bybit | Dunamu Inc. |
| Transports | stdio |  |
| Tools exposed | 398 | 0 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-10-30 | 2026-10-20 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | couldn't be read | 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 | 43 stars | 91 stars |

Why the edge:
- Payments & pricing, Bybit +25: Bybit 40 (No machine payment protocol (0). The fee schedule is public without login, with VIP 0 maker and taker rates per product and the tier criteria (20). Reading market data needs no key and the demo environment costs nothing, no card is asked for at sign-up (20). A person must register, pass identity verification and mint the key in a browser (0). 40.); 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 +17: Bybit 66 (Read as a hosted service with an open-source MCP server. The MCP package shipped 2.1.26 on 30 October 2026 and the V5 changelog's latest entry is 29 October (30). 31 npm versions since 16 April 2026, 11 of them in the last 90 days, and 24 changelog entries in the same window (20). The trading-mcp repository has 4 open issues and 18 forks; whether issues get answers was not checked, and the API has no public forum we could read (10 of 25). Not in the official MCP registry (0). The package has four dependencies, no install scripts, a publish workflow and no test workflow (6 of 10). 66.); 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.)
- Schema & documentation, Bybit +7: Bybit 73 (No OpenAPI or other machine-readable contract for the REST API; the MCP server's 398 tools have zod schemas turned into JSON Schema, so the contract exists for the MCP surface only (12 of 25). No llms.txt; the docs are a public Docusaurus repository (bybit-exchange/docs) whose MDX source an agent can read (5 of 10). The MCP tool descriptions state purpose, rules and an agent hint per tool, and the API reference gives one page per endpoint (15 of 20). Parameters are typed with enums such as category and orderType and required flags (12 of 15). Request and response examples on each endpoint page and an error code page of about 750 codes with text (14 of 15). A dated changelog with 24 entries in the last 90 days, versioned V3 to V5 (15). 73.); 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.)