# Bithumb Open API vs Crypto.com Exchange API

> Bithumb Open scores 50.6 (D) to Crypto.com Exchange's 46.8 (D) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange
- Markdown: https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.md (~5,150 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-03

Bithumb Open API scores 50.6 (D) on agent readiness against Crypto.com Exchange API's 46.8 (D), and leads in 4 of 7 scored categories. Crypto.com Exchange API leads on reliability, payments & pricing and transparency & trust. Both do exchange market data.

- Bithumb Open API: grade D, 50.6/100, rank #999 of 1349. Markdown https://www.anchorterminal.com/tools/bithumb.md · JSON https://www.anchorterminal.com/api/v1/tools/bithumb.json
- Crypto.com Exchange API: grade D, 46.8/100, rank #1100 of 1349. Markdown https://www.anchorterminal.com/tools/crypto-com-exchange.md · JSON https://www.anchorterminal.com/api/v1/tools/crypto-com-exchange.json
- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md
- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md

## Which one, for what

### Bithumb Open API (D)

Good for: KRW-market trading for agents acting for a verified Korean account, with a vendor-built MCP server, CLI and skills.

Ahead on:
- Schema & documentation, 64 against 42
- Agent ergonomics, 67 against 50
- Security & auth, 60 against 54
- Maintenance & community, 69 against 29

Watch for: No sandbox or testnet; every order uses real funds

### Crypto.com Exchange API (D)

Good for: An agent trading spot or perpetuals on Crypto.com through a local MCP server with safety tiers, for a person outside the App's restricted list.

Ahead on:
- Reliability, 50 against 34
- Payments & pricing, 40 against 15
- Transparency & trust, 55 against 47

Watch for: exchange-docs.crypto.com and the OpenAPI host answered 403 to robots.txt, so rate limits, key permissions, errors and the changelog could not be read


## Why the edge

### Maintenance & community: Bithumb Open API +40

- 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.
- Crypto.com Exchange API (29): Read as a closed service with an open CLI. The last change we could date is cdcx-cli v1.2.6 on 18 June 2026, 138 days before the check, with no commit since; the API changelog is unread (10). No three dated releases in the last 90 days (0). Five of six open items on cdcx-cli, all by collaborators or Dependabot since May, have no comment; the Exchange has a support chat and contact@crypto.com (8 of 25). Not in the official MCP registry and no official SDK beyond the CLI (5 of 15). CI tests on three operating systems with clippy and fmt; the npm wrapper's postinstall downloads the binary and two Dependabot bumps are open (6 of 10). 10 + 0 + 8 + 5 + 6 = 29.

### Payments & pricing: Crypto.com Exchange API +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.
- Crypto.com Exchange API (40): No machine payment protocol (0). Spot fee tiers published without login, 0.25% maker and 0.50% taker at Level 1 (20). The API is free, public market data needs no key, UAT and paper trading need no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 20 + 20 + 0 = 40.

### Schema & documentation: Bithumb Open API +22

- 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.
- Crypto.com Exchange API (42): An OpenAPI spec exists, since cdcx-cli generates its 95 commands and tools from it at run time, but its host (exchange-developer.crypto.com) answered 403 to robots.txt and the spec was not read; the vendor's own tooling is evidence it exists, not of its quality (15 of 25). No llms.txt on crypto.com or the Exchange pages (0). For descriptions, cdcx's tool descriptions come from the spec, which we couldn't read; the Exchange skill documents 52 endpoints in prose (8 of 20). cdcx's README says the tools carry typed parameters and enum validation, a vendor claim not checked against the spec (8 of 15). For examples, the skills and cdcx README carry worked commands, but the API's error codes and response examples sit on the unread host (6 of 15). Versioned path (v1); the API changelog and announcements page could not be read (5 of 15). 15 + 0 + 8 + 8 + 6 + 5 = 42.

### Agent ergonomics: Bithumb Open API +17

- 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.
- Crypto.com Exchange API (50): Graded on the REST API as an agent calls it, with the MCP server noted. cdcx serves up to 95 tools, more than 30, but the default serves the `market` group alone and groups are enabled one by one, which is a read-only subset switch (5 + 10 = 15). Pagination and output controls for the API are on the unread docs host; cdcx adds `-o json|table|ndjson` (8 of 20). cdcx returns structured JSON errors and the safety gate names what is missing; the API's own error table is unread (8 of 20). cdcx's tiers (mutate needs `acknowledged: true`, dangerous needs `--allow-dangerous`), `--dry-run` and paper trading give safe rehearsal, though no MCP annotations or API idempotency keys were seen (12 of 20). No official SDK beyond the CLI; defaults in cdcx are sensible (7 of 15). 15 + 8 + 8 + 12 + 7 = 50.

### Reliability: Crypto.com Exchange API +16

- 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.
- Crypto.com Exchange API (50): Read with the hosted lines on the Exchange API at api.crypto.com. status.crypto.com is a Statuspage site with component history (20). Its feed for 18 August to 3 November 2026 has 25 entries; the Exchange is named in two, an 11-minute database upgrade on 18 August and a one-hour balance display issue on 6 October, while the longer disruptions (Android login on 1 and 5 October, card 3DS on 23 September, Main App predictions on 3 November) are App incidents. There is no Exchange API component, so the record may be incomplete. Minor only (20). Rate limits are documented on exchange-docs.crypto.com, which answered 403 to robots.txt and was not read (0, unchecked). 429 handling and client order ids are on the same host (0, unchecked). No SLA found (0). Generally available (10). 20 + 20 + 0 + 0 + 0 + 10 = 50.

### Transparency & trust: Crypto.com Exchange API +8

- 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.
- Crypto.com Exchange API (55): The editorial half. A closed service whose terms and trading rules loaded empty for our reader; cdcx and the skills are MIT or Apache-2.0 (10 of 30). The Exchange privacy notice of 12 March 2025 names Foris DAX Limited, gives retention examples (6 years for correspondence, 5 years for EEA AML records) and provider categories, with no DPA or subprocessor list (16 of 30). No deprecation policy or notice period was found (0). Transfers outside the Cayman Islands and the EEA are stated with no countries named (6 of 20). 10 + 16 + 0 + 6 = 32.

## Score by category

| Category | Weight | Bithumb Open API | Crypto.com Exchange API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 34 | 50 | Crypto.com Exchange API +16 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 64 | 42 | Bithumb Open API +22 |
| Agent ergonomics | 13% (16.2 this run) | 67 | 50 | Bithumb Open API +17 |
| Security & auth | 14% (17.5 this run) | 60 | 54 | Bithumb Open API +6 |
| Payments & pricing | 10% (12.5 this run) | 15 | 40 | Crypto.com Exchange API +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 69 | 29 | Bithumb Open API +40 |
| Transparency & trust | 7% (8.8 this run) | 47 | 55 | Crypto.com Exchange API +8 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **50.6 · D** | **46.8 · D** | |

## Facts side by side

| Fact | Bithumb Open API | Crypto.com Exchange API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Bithumb Co., Ltd. | Foris DAX Limited (Crypto.com) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | none | Proprietary hosted API under the Exchange terms and conditions, which our reader couldn't load. cdcx-cli, the official CLI and MCP server, is MIT or Apache-2.0 |
| Tools exposed | 41 | 95 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-10-13 | 2026-06-18 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | no document linked | 2025-03-12 |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | 6 stars | 27 stars, 59 npm/wk |

## Verdicts

**Bithumb Open API.** Bithumb runs an official local MCP server with 41 tools, module selection and a read-only flag, beside a CLI with per-profile read-only gating and six agent skills, over an API with scoped one-year keys and a mandatory IP list. There is no sandbox, no status page, no documented 429 behaviour, and the fees and terms couldn't be read.

**Crypto.com Exchange API.** Crypto.com is one of two exchanges here with an official MCP server, cdcx-cli, whose 95 generated tools are grouped by service and gated by safety tier. The API docs, OpenAPI file, terms and trading rules refused or hid from our reader, so rate limits, key permissions and the automated-trading clauses are unchecked, and cdcx has no release since June 2026.

## Before you call either

### Bithumb Open API

1. Ask for a key with asset and order inquiry plus order placement only, never withdrawals, with your IP registered; keys expire after one year and a wrong IP answers 401 NotAllowIP
2. Start the server with `--modules market,account,trade --read-only` for analysis and drop `--read-only` only when the person asks to trade; deposit and withdraw modules stay off
3. Prefer the `bithumb` CLI for writes, as the skills do, and check `bithumb config show --json` for a read-only profile before any order
4. Keep the ticker's markets parameter at 200 or fewer, batch orders at 30 and cancels at 30 per request, and stay under 140 private calls a second per category
5. Retry 422 order_not_ready and 500 server_error after a pause; there is no sandbox, so start with the smallest order the market allows

### Crypto.com Exchange API

1. Enable only the service groups the task needs with `cdcx mcp config --enable trade,account` (the default serves `market` alone), and leave `--allow-dangerous` off unless the person asks for withdrawals or cancel-all
2. Rehearse on `--env uat` or `cdcx paper` first; production keys trade real funds, and the skill requires explicit user confirmation before each live order
3. Put the key in CDCX_API_KEY and CDCX_API_SECRET or `~/.config/cdcx/config.toml` at 0600; there is no key flag, and the key should have no withdrawal permission and an IP allow-list
4. Pass `acknowledged: true` on mutate tools and `--dry-run` while testing; read the tool's generated schema before calling, since the docs host is unreadable to agents without a browser
5. Check the person's country against Crypto.com's geo-restriction article and the Exchange terms before trading; New York and about 70 countries are excluded from the App, and the Exchange list was unreadable

## Questions

### Which is better for AI agents, Bithumb Open API or Crypto.com Exchange API?

Bithumb Open API scores 50.6 (D) on agent readiness against Crypto.com Exchange API's 46.8 (D), and leads in 4 of 7 scored categories. Crypto.com Exchange API leads on reliability, payments & pricing and transparency & trust.

### Do Bithumb Open API and Crypto.com Exchange API need an API key?

Both need an API key.

### Can an agent call Bithumb Open API and Crypto.com Exchange API without installing anything?

Bithumb Open API runs on your own machine, with no hosted endpoint listed. Crypto.com Exchange API runs on your own machine, with no hosted endpoint listed.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "bithumb", "b": "crypto-com-exchange"}`. From a terminal: `anchor compare bithumb crypto-com-exchange`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bithumb.json and https://www.anchorterminal.com/api/v1/tools/crypto-com-exchange.json

## Other comparisons with Bithumb Open API or Crypto.com Exchange API

- [Bitfinex API vs Bithumb Open API](https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.md)
- [Bitfinex API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.md)
- [Bitget vs Bithumb Open API](https://www.anchorterminal.com/compare/bitget-vs-bithumb.md)
- [Bitget vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange.md)
- [Bithumb Open API vs Bitstamp API](https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.md)
- [Bithumb Open API vs Bybit](https://www.anchorterminal.com/compare/bithumb-vs-bybit.md)
- [Bithumb Open API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.md)
- [Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.md)
- [Bithumb Open API vs Deribit](https://www.anchorterminal.com/compare/bithumb-vs-deribit.md)
- [Bithumb Open API vs dYdX](https://www.anchorterminal.com/compare/bithumb-vs-dydx.md)
- [Bithumb Open API vs Gate](https://www.anchorterminal.com/compare/bithumb-vs-gate-io.md)
- [Bithumb Open API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.md)
- [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.md)
- [Bithumb Open API vs Hyperliquid](https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.md)
- [Bithumb Open API vs Kraken API](https://www.anchorterminal.com/compare/bithumb-vs-kraken.md)
- [Bithumb Open API vs KuCoin](https://www.anchorterminal.com/compare/bithumb-vs-kucoin.md)
- [Bithumb Open API vs MEXC API](https://www.anchorterminal.com/compare/bithumb-vs-mexc.md)
- [Bithumb Open API vs OKX API](https://www.anchorterminal.com/compare/bithumb-vs-okx.md)
- [Bithumb Open API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bithumb-vs-uniswap.md)
- [Bithumb Open API vs Upbit Open API](https://www.anchorterminal.com/compare/bithumb-vs-upbit.md)
- [Bitstamp API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.md)
- [Bybit vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange.md)
- [Crypto.com Exchange API vs Deribit](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-deribit.md)
- [Crypto.com Exchange API vs dYdX](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx.md)
- [Crypto.com Exchange API vs Gate](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io.md)
- [Crypto.com Exchange API vs Gemini Exchange API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange.md)
- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md)
- [Crypto.com Exchange API vs Hyperliquid](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid.md)
- [Crypto.com Exchange API vs Kraken API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken.md)
- [Crypto.com Exchange API vs KuCoin](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.md)
- [Crypto.com Exchange API vs MEXC API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc.md)
- [Crypto.com Exchange API vs OKX API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx.md)
- [Crypto.com Exchange API vs Uniswap Trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap.md)
- [Crypto.com Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.md)
- [Binance API vs Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md)
- [Binance API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.md)
- [Coinbase Advanced Trade API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange.md)
- [Coinbase MCP server (Coinbase for Agents) vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-crypto-com-exchange.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp