# Binance API vs Bithumb Open API (slim)

> Binance scores 63.2 (B) to Bithumb Open's 50.6 (D) for exchange spot trading. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/binance-vs-bithumb.md (~4,850 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/binance-vs-bithumb.json · canonical https://www.anchorterminal.com/compare/binance-vs-bithumb
- 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)

Binance API scores 63.2 (B) on agent readiness against Bithumb Open API's 50.6 (D), and leads in 6 of 7 scored categories. Both do exchange spot trading.

- Binance API: B 63.2, rank #473 of 1349 · https://www.anchorterminal.com/tools/binance.min.md
- Bithumb Open API: D 50.6, rank #940 of 1349 · https://www.anchorterminal.com/tools/bithumb.min.md
- Binance API, good for An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet. Ahead on Reliability, 45 against 34; Schema & documentation, 86 against 64; Agent ergonomics, 76 against 67; Security & auth, 72 against 60; Payments & pricing, 35 against 15; Maintenance & community, 81 against 69. Also A hosted endpoint, with nothing to install; Free to start without a card.
- 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.

| Category | Binance API | Bithumb Open API |
| --- | --- | --- |
| Reliability (16%) | 45 | 34 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 64 |
| Agent ergonomics (13%) | 76 | 67 |
| Security & auth (14%) | 72 | 60 |
| Payments & pricing (10%) | 35 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 81 | 69 |
| Transparency & trust (7%) | 43 | 47 |

| Fact (where they differ) | Binance API | Bithumb Open API |
| --- | --- | --- |
| Vendor | Binance | Bithumb Co., Ltd. |
| Hosted endpoint | `https://agent.binance.com/mcp/agentic` | no (local only) |
| Transports | Streamable HTTP | stdio |
| Auth | OAuth or key | API key |
| Licence | Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT | none |
| Tools exposed | none | 41 |
| Read-only variant documented | no | yes |
| Last release | 2026-10-30 | 2026-10-13 |
| Privacy policy last updated | couldn't be read | no document linked |
| Popularity | 4.9k stars | 6 stars |

Why the edge:
- Schema & documentation, Binance API +22: Binance API 86 (The docs are Markdown in a public repository with a Postman collection and a Swagger spec, but the spec was last pushed in October 2024 (20 of 25). llms.txt and llms-full.txt on developers.binance.com (10). Each endpoint states its weight, parameters and notes on behaviour, with less on when not to use one (15 of 20). Enums for order types, time in force and symbol filters, required columns in the parameter tables (12 of 15). Request and response examples throughout and an error code list with messages (14 of 15). A dated changelog since 2018 with retirements announced months ahead, such as the 2 September 2026 field removal notified on 2 December 2025 (15). 20 + 10 + 15 + 12 + 14 + 15 = 86.); 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.)
- Payments & pricing, Binance API +20: Binance API 35 (No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35.); 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.)
- Security & auth, Binance API +12: Binance API 72 (API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72.); Bithumb Open API 60 (Keys scoped to chosen permissions, mandatory registered IPs, one-year expiry, a JWT per request and a key-list endpoint with expiry (26 of 30). Read-only keys, `--read-only` on the MCP server, per-profile read_only on the CLI, a second factor on KRW deposits and withdrawals, and skills that refuse to switch profiles to bypass read-only; nothing server-side confirms an order (16 of 20). The API returns exchange data and the disclaimer warns about prompt injection through third-party plugins (11 of 15). A local audit log for CLI and MCP calls and a key-list endpoint; no server-side per-call log (7 of 15). security.txt timed out and no disclosure policy, bug bounty or certification was found (0 of 20, security.txt unchecked). 26 + 16 + 11 + 7 + 0 = 60.)
- Maintenance & community, Binance API +12: Binance API 81 (Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.); 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.)
- Reliability, Binance API +11: Binance API 45 (Read with the hosted lines on the spot REST API. No status page was found on binance.com or in the API docs (0), so no incident record (5). Rate limits are published as per-endpoint weights with numbers from exchangeInfo, 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 a day and 61,000 raw requests per 5 minutes, and FIX limits per session (15). 429 and 418 carry Retry-After, a 5xx is documented as unknown status to be queried, and orders take a client order id (15). No SLA (0). Generally available (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.); 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.)
- Agent ergonomics, Binance API +9: Binance API 76 (limit on depth, trades and klines, a symbols filter on exchangeInfo and tickers, and SBE encoding, though fields cannot be selected (16 of 25). fromId, startTime, endTime and limit on history endpoints (16 of 20). Error codes with messages an agent can branch on, such as the rate limit and timestamp errors (17 of 20). newClientOrderId on orders, a cancel-replace endpoint and the 5xx unknown-status rule, but no idempotency key on other writes (12 of 20). Connectors in nine languages, a CLI with testnet and demo profiles, and a timestamped HMAC or Ed25519 signature on every private call (15). 16 + 16 + 17 + 12 + 15 = 76.); Bithumb Open API 67 (Graded on the REST API with the MCP server. 41 tools in all, selectable by module, so 15 for 11 to 30 or more and 8 added back for the module switch (23 of 25). Candle counts, order paging and a 200-market cap on the ticker (13 of 20). Stable error.name values with retry guidance for order_not_ready and server_error (14 of 20). No client order id or idempotency key documented; the CLI's per-profile read-only flag, the MCP --read-only flag and the skills' read-only gate help, and readOnlyHint annotations weren't checked (9 of 20). Few required parameters, but no official SDK beyond the CLI and a CCXT guide (8 of 15). 23 + 13 + 14 + 9 + 8 = 67.)