# Bithumb Open API vs Bybit (slim)

> Bybit scores 57.3 (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-bybit.md (~3,600 tokens) · this version ~1,380 tokens · JSON https://www.anchorterminal.com/compare/bithumb-vs-bybit.json · canonical https://www.anchorterminal.com/compare/bithumb-vs-bybit
- 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)

Bybit scores 57.3 (C) on agent readiness against Bithumb Open API's 50.6 (D), and leads in 4 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
- Bybit: C 57.3, rank #745 of 1349 · https://www.anchorterminal.com/tools/bybit.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.
- 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 Reliability, 45 against 34; Schema & documentation, 73 against 64; Payments & pricing, 40 against 15.

| Category | Bithumb Open API | Bybit |
| --- | --- | --- |
| Reliability (16%) | 34 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 73 |
| Agent ergonomics (13%) | 67 | 66 |
| Security & auth (14%) | 60 | 60 |
| Payments & pricing (10%) | 15 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 69 | 66 |
| Transparency & trust (7%) | 47 | 51 |

| Fact (where they differ) | Bithumb Open API | Bybit |
| --- | --- | --- |
| Vendor | Bithumb Co., Ltd. | Bybit |
| Tools exposed | 41 | 398 |
| llms.txt | yes | no |
| Last release | 2026-10-13 | 2026-10-30 |
| Privacy policy last updated | no document linked | couldn't be read |
| Popularity | 6 stars | 43 stars |

Why the edge:
- Payments & pricing, Bybit +25: Bithumb Open API 15 (No machine payment protocol (0). The fee page timed out on every attempt, so no price is recorded (0 of 20, unchecked). Public market data needs 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 in the browser (0). 0 + 0 + 15 + 0 = 15.); 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.)
- Reliability, Bybit +11: 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.); Bybit 45 (Graded with the hosted lines on the V5 API at api.bybit.com. No status page found (status.bybit.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per endpoint and per UID with numbers, plus a 600 per 5 second IP limit (15). Every response carries X-Bapi-Limit, X-Bapi-Limit-Status and X-Bapi-Limit-Reset-Timestamp, retCode 10006 and HTTP 403 are documented with a wait rule, and orders take a unique orderLinkId that amend and cancel accept (15). No SLA (0). V5 is the current production API, not a beta (10). 45.)
- Schema & documentation, Bybit +9: Bithumb Open API 64 (No OpenAPI found; the reference is a readme.io site with Markdown twins, and the MCP tool schemas weren't read since the server's source isn't published (5 of 25). llms.txt on apidocs.bithumb.com (10). Reference pages state purpose and the skills say when to use each module and when not to (15 of 20). Typed parameters with enums for side, order type and time in force (10 of 15). Examples in several languages and an error-code page with names, statuses and meanings (12 of 15). Versions per endpoint (v1, v2, v2.1.5) and notices with effective dates (12 of 15). 5 + 10 + 15 + 10 + 12 + 12 = 64.); 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.)