# Bithumb Open API > Bithumb, a Korean exchange, runs a REST and WebSocket Open API for KRW market data, orders, balances, deposits and withdrawals, and an official AI Trade Kit with a local MCP server, a CLI and agent skills. - Canonical: https://www.anchorterminal.com/tools/bithumb - Pricing: https://www.anchorterminal.com/tools/bithumb#pricing - Reviews: https://www.anchorterminal.com/tools/bithumb#reviews - Markdown: https://www.anchorterminal.com/tools/bithumb.md (~8,550 tokens) - Slim: https://www.anchorterminal.com/tools/bithumb.min.md (~2,180 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/bithumb.json (this page as data, same URL with Accept: application/json) - 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 bithumb.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. 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-04 ## Overview **Grade D · 50.6/100 · rank #999 of 1349 · #17 in Crypto exchanges · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Bithumb Co., Ltd. (https://apidocs.bithumb.com) | | Kind | HTTP API | | Category | Crypto exchanges (https://www.anchorterminal.com/categories/crypto-exchanges) | | Transport | stdio | | Auth | API key · Access and secret keys issued under My Page > API Management on bithumb.com after identity verification. The person picks permissions (asset inquiry, order inquiry, place orders, withdrawals and others) and registers the IP addresses allowed to call. Each request carries a JWT signed with the secret as a Bearer token. Keys are valid for one year from issue and can't be extended; up to 10 per account including expired ones; the secret is shown once. The MCP server and CLI read BITHUMB_ACCESS_KEY and BITHUMB_SECRET_KEY, and market tools need no key (https://apidocs.bithumb.com/docs/빠른-시작-가이드.md, checked 2026-11-03). | | Pricing | Pay per use (Pay per use) · Trading fees per fill. The fee page at bithumb.com/react/info/fee/trade timed out on every attempt, so no rate is recorded; press reports from 2024 describe a 0.04 per cent rate with a monthly coupon and 0.25 per cent without, which is a lead and not a source. Public market data needs no key and no account (https://www.bithumb.com/react/info/fee/trade, checked 2026-11-03). | | x402 | No · No x402, MPP or L402 in the API docs, the AI Trade Kit repository or llms.txt (checked 2026-11-03). Fees are taken from each fill. | | Licence | unknown | | Tools exposed | 41 | | Packages | npm: `@bithumb-official/bithumb-mcp`; npm: `@bithumb-official/bithumb-cli` | | Source | https://github.com/bithumb-official/bithumb-ai-trade-kit | | Docs | https://apidocs.bithumb.com/reference/api-레퍼런스 | | llms.txt | https://apidocs.bithumb.com/llms.txt | | Last release | 2026-10-13 | | GitHub stars | 6 (as of 2026-11-03) | | Surface listed | The Open API v2.1.5 (REST at api.bithumb.com, WebSocket at ws-api.bithumb.com) with the AI Trade Kit's MCP server and CLI, read from apidocs.bithumb.com and its llms.txt, a shallow clone of bithumb-official/bithumb-ai-trade-kit, npm and the MCP registry on 3 November 2026. No account was made, no private endpoint was called and neither the MCP server nor the CLI was run | | MCP server | Official, local. `@bithumb-official/bithumb-mcp` on npm (0.8.5, 9 June 2026, MIT), stdio, 41 tools in seven modules selected with `--modules`, `--read-only` to block writes, keys from environment variables only, a local execution log. Not in the official MCP registry (its bithumb entries are a third party's io.github.mrfentmen/bithumb-mcp). The server's source is not in the kit repository | | Key permissions | Asset inquiry, order inquiry, place orders, withdrawals and others chosen at issuance; registered IP addresses required; valid one year, not extendable; up to 10 keys per account including expired; GET /v1/api_keys lists keys with expiry. KRW deposits and withdrawals through the API need a second factor. The kit's disclaimer advises against withdrawal permission and pre-registered addresses for an AI | | Rate limits | Per IP and per category, updated 27 October 2026: public 150 a second per category (candles, order book, ticker, trades, other), private 140 a second per category (orders, cancels, other), batch orders and cancels 20 a second. More than 20 orders or cancels a second on one asset may restrict the account. A breach restricts the category for a while, with no status code or header documented; limits may be lowered without notice in surges. WebSocket idle timeout about 120 seconds | | Testnet | None. The trade skill says all orders are real funds and Bithumb has no demo or simulated mode | | Countries | A Korean exchange with KRW markets, Korean identity verification and a Korean phone support line (1661-5566). No served or excluded country list was readable; the terms on bithumb.com timed out or answered a title only | | Fees | Unchecked. bithumb.com/react/info/fee/trade timed out on every attempt. The API has a deposit and withdrawal fee endpoint and the market skill reads fees | | FIX and WebSocket | WebSocket public v1 (ticker, trade, orderbook) at wss://ws-api.bithumb.com/websocket/v1 and private v2 (MyOrder, MyAsset) at /websocket/v2/private, with v1 private retired on 30 September 2026. No FIX found in the docs | | Terms on automation | The Open API terms at bithumb.com/react/terms/info-api answered a title only. The kit's disclaimer says AI orders face the same FDS and AML monitoring, abnormal or excessive short-term orders may get the key restricted without notice, automated programs should include a final confirmation step and an emergency stop, and commercial use of the kit is not permitted | | CLI and skills | `@bithumb-official/bithumb-cli` 0.8.5 with market, account, trade, twap, deposit, withdraw, config and system groups, profiles with read_only in ~/.bithumb/config.toml, --json output and an audit log. Six skills installed with `npx skills add bithumb-official/bithumb-ai-trade-kit --all`, with a read-only pre-flight gate the agent must not bypass | | Changelog | Ten notices on apidocs.bithumb.com, dated items among them Private v2 and new order types effective 30 June 2026, batch orders 20 to 30 on 20 August 2026 and the 200-market ticker cap on 13 October 2026 | | Legal entity | Bithumb Co., Ltd., per the kit's disclaimer; the npm packages are maintained by bithumb-npm (developers@bithumbcorp.com). The terms on bithumb.com couldn't be read | | Capabilities | exchange.market-data, exchange.spot-trading, exchange.balances, exchange.transfers, market.crypto | | Tags | hosted, api-key, closed-source, usage-priced, mcp, cli, agent-skills, read-only-mode, llms-txt, mit, no-status-page | | JSON | https://www.anchorterminal.com/api/v1/tools/bithumb.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 34 | 6.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 64 | 10.4 | | Agent ergonomics | 13% | 16.2 | 67 | 10.9 | | Security & auth | 14% | 17.5 | 60 | 10.5 | | Payments & pricing | 10% | 12.5 | 15 | 1.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 69 | 6.0 | | Transparency & trust (editorial 24, provenance 69) | 7% | 8.8 | 47 | 4.1 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **50.6 → D** | ### Why each score - Reliability 34 (checked 2026-11-03): 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. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 64 (checked 2026-11-03): 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. - Agent ergonomics 67 (checked 2026-11-03): 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. - Security & auth 60 (checked 2026-11-03): 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. - Payments & pricing 15 (checked 2026-11-03): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 69 (checked 2026-11-03): 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. - Transparency & trust 47 (checked 2026-11-03): 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. Fix list, everything this grade says the listing lacks, the biggest gain first (18 items). What it covers is at https://www.anchorterminal.com/fixes/bithumb.md (JSON https://www.anchorterminal.com/fixes/bithumb.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "bithumb", "plan": "read"}`, free while the beta runs ### What we couldn't check - Kind http-api: the REST and WebSocket API is the main surface and the docs lead with it; the MCP server is one of three kit components, so it is recorded in packages, transports, toolCount and details. - unchecked: the fee schedule, the terms of service, the Open API terms, the company page and security.txt on bithumb.com, which timed out on every attempt or answered a page title (script-drawn). Payments pricing, the terms' automation clauses and the privacy policy are scored absent for that reason. - unchecked: the MCP server's tool schemas, descriptions and annotations (no session opened, and the npm package's source is not in the kit repository), a client order id or idempotency parameter on orders, WebSocket connection limits, and the full permission list on the key issuance screen. - firstReleased is 22 April 2026, the oldest dated first-hand page found (the API key list reference); the Open API is years older and no launch date was found. lastRelease is 13 October 2026, the ticker cap's effective date; the rate-limit page was updated on 27 October 2026. - The MCP docs count 41 tools by module and the npm package is 0.8.5 of 9 June 2026; the skills changelog dates 0.8.5 to 8 June 2026 and the repository's single commit to 9 June. Consistent to a day. - Humans: no person with a role on a readable first-hand page; the company page timed out. Ownership unknown from the pages read; no investor search was made. - Our own products. It doesn't do LocalGhost's or letme's job. ### Sources - robots.txt (www.bithumb.com no active rules; apidocs.bithumb.com allows): (seen 2026-11-03) - llms.txt index: (seen 2026-11-03) - API reference overview (hosts, versions, JWT, v1 WebSocket retirement): (seen 2026-11-03) - quick start (key issuance, permissions, IP registration, 10 keys): (seen 2026-11-03) - API key list endpoint (one-year validity): (seen 2026-11-03) - rate limits, 27 October 2026: (seen 2026-11-03) - error codes: (seen 2026-11-03) - WebSocket connection management: (seen 2026-11-03) - MCP page (package, flags, 41 tools, clients): (seen 2026-11-03) - AI Trade Kit start page: (seen 2026-11-03) - CLI page (profiles, read_only, audit log, two-factor): (seen 2026-11-03) - changelog index and the ticker cap notice effective 13 October 2026: (seen 2026-11-03) - batch order notice effective 20 August 2026: (seen 2026-11-03) - order types and Private v2 notice (30 June 2026; v1 retired 30 September 2026): (seen 2026-11-03) - AI Trade Kit repository, shallow clone (README, skills, read-only gate, disclaimer, changelog): (seen 2026-11-03) - bithumb-official repositories: (seen 2026-11-03) - npm @bithumb-official/bithumb-mcp (versions 0.1.16 to 0.8.5, 29 May to 9 June 2026): (seen 2026-11-03) - npm @bithumb-official/bithumb-cli 0.8.5: (seen 2026-11-03) - official MCP registry search for bithumb (third-party entries only): (seen 2026-11-03) - bithumb.com sitemap (fee, terms, API terms and company URLs): (seen 2026-11-03) - Open API terms (title only): (seen 2026-11-03) - fee page (timed out): (seen 2026-11-03) - RDAP for bithumb.com: (seen 2026-11-03) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/bithumb/history.json - 2026-11-03: graded 50.6 D (methodology 0.7) ## Who's behind it (provenance 69/100, checked 2026-11-03) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Bithumb Co., Ltd. | 20/20 | | Domain age | bithumb.com, registered 2015-06-16 (11 years) | 15/15 | | Endpoint on the vendor's domain | bithumb.com | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | not found | 0/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | could not be fetched | 0/10 | | People named | not researched yet | n/a | | Support route | help pages, a community | 5/5 | Bithumb Co., Ltd. is named in the AI Trade Kit's disclaimer (compliance review 007441, 29 May 2026 to 28 May 2027). The terms of service at bithumb.com/react/terms/info-terms answered a page title only on two attempts, and the Open API terms, company page and fee pages timed out or did the same; no privacy policy URL was found in the sitemap's first part, so it is left empty. www.bithumb.com/robots.txt has no active rules (comments only) and two sitemaps; apidocs.bithumb.com/robots.txt allows everything but edit, login and api-next paths and points to llms.txt. https://www.bithumb.com/.well-known/security.txt timed out twice; recorded as unknown. RDAP gives bithumb.com a registration date of 16 June 2015. No status page found; the API has wallet-status and notices endpoints. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.bithumb.com/react/terms/info-terms), read 2026-11-03. Our reader couldn't read it (no answer (stream error: stream ID 3; INTERNAL_ERROR; received from peer)). **Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0. ## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade) ### Key people - No people named yet. - Note: No first-hand page naming a founder or executive could be read. bithumb.com's company page (react/biz/intro), terms and fee pages timed out or answered a page title only on 3 November 2026, and apidocs.bithumb.com and the AI Trade Kit repository name no people. The kit's disclaimer names Bithumb Co., Ltd. under compliance review 007441, and the npm packages are maintained by the bithumb-npm account at developers@bithumbcorp.com. Ownership is recorded as unknown because no page read states whether the company is privately held or listed, and no investor search was made since the company's own pages couldn't be read. - Bithumb Co., Ltd.: GitHub https://github.com/bithumb-official ### Getting support - Help: https://apidocs.bithumb.com - Help: https://apidocs.bithumb.com/docs/api-요청-수-제한-안내 - Community (AI Trade Kit issues): https://github.com/bithumb-official/bithumb-ai-trade-kit/issues - General contact: developers@bithumbcorp.com - Sources: https://github.com/bithumb-official/bithumb-ai-trade-kit, https://registry.npmjs.org/@bithumb-official%2fbithumb-mcp, https://apidocs.bithumb.com/docs/api-요청-수-제한-안내.md, https://www.bithumb.com/react/biz/intro ## Live (updated 2026-11-04 15:54 UTC) - security.txt: none - Always current: https://www.anchorterminal.com/api/v1/live/bithumb.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - An official MCP server from Bithumb with 41 tools in seven selectable modules and a `--read-only` flag that blocks orders, deposits and withdrawals - Keys scoped to chosen permissions, limited to registered IPs and expiring after one year, with a key-list endpoint that shows expiry - The CLI's per-profile read-only flag, local audit log and second factor on KRW deposits and withdrawals, and skills that refuse to bypass read-only - Rate limits published per category with numbers, and notices with effective dates for changes such as the 200-market ticker cap - Errors return a stable error.name under an HTTP status, with retry guidance for order_not_ready and server_error ## Weaknesses - No sandbox or testnet; every order uses real funds - A rate-limit breach is signalled only as a temporary restriction, with no status code, header or Retry-After documented - No status page, incident history or SLA - The MCP server is local only, not in the official MCP registry, and its source is not published (the kit repository holds skills and setup files) - The fee schedule, terms of service and Open API terms on bithumb.com timed out or answered a title only, so none is recorded first-hand ## Before you call it (notes for agents) 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 ## Connect Install: ```bash npm install -g @bithumb-official/bithumb-cli ``` First request: ```bash curl 'https://api.bithumb.com/v1/market/all?isDetails=false' ``` MCP client configuration: ```json { "mcpServers": { "bithumb": { "args": [ "-y", "@bithumb-official/bithumb-mcp", "--modules", "market,account,trade", "--read-only" ], "command": "npx", "env": { "BITHUMB_ACCESS_KEY": "${BITHUMB_ACCESS_KEY}", "BITHUMB_SECRET_KEY": "${BITHUMB_SECRET_KEY}" } } } } ``` Through letme: https://letme.dev/bithumb. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Gemini Exchange API | BB | 74.6 | 70 | exchange.market-data, exchange.spot-trading, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/gemini-exchange.md | | Kraken API | BB | 71 | 159 | exchange.spot-trading, exchange.market-data, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/kraken.md | | OKX API | B | 64.3 | 413 | exchange.spot-trading, exchange.market-data, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/okx.md | | Binance API | B | 63.2 | 448 | exchange.spot-trading, exchange.market-data, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/binance.md | | Coinbase Advanced Trade API | C | 61.7 | 493 | exchange.spot-trading, exchange.market-data, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/coinbase-advanced-trade.md | | Deribit | C | 59 | 650 | exchange.market-data, exchange.spot-trading, exchange.balances, exchange.transfers, market.crypto | no | https://www.anchorterminal.com/tools/deribit.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - MCP server, official, local. `npx -y @bithumb-official/bithumb-mcp --modules all` runs a stdio server with 41 tools in seven modules (market 11, account 4, trade 6, TWAP 3, deposit 7, withdraw 8, system 2); `--modules` picks modules and `--read-only` blocks orders, deposits and withdrawals. npm version 0.8.5 of 9 June 2026, MIT, Node 18 or later, one dependency on @modelcontextprotocol/sdk. It is not in the official MCP registry, whose bithumb entries are a third party's io.github.mrfentmen/bithumb-mcp (source: ) - The AI Trade Kit (bithumb-official/bithumb-ai-trade-kit, MIT, created 29 May 2026 with one commit, 'release: v0.8.5' of 9 June 2026) holds six skills (market, account, trade, deposit, withdraw, system) and agent setup files; the skills tell agents to prefer the CLI for writes because it carries per-profile read-only gating, and the trade skill says there is no demo or simulated mode. The README credits OKX's Agent Trade Kit as the inspiration (source: ) - The kit's disclaimer, under Bithumb Co., Ltd. compliance review 007441 (29 May 2026 to 28 May 2027), says orders placed by an AI fall under the same fraud-detection and anti-money-laundering monitoring, that the company may restrict a key without notice on abnormal trading, that it advises against giving an AI withdrawal permission or pre-registered addresses, that automated programs should include a final confirmation step and an emergency stop, and that commercial use of the kit is not permitted (source: ) - Rate limits, updated 27 October 2026, are per IP and per API category, 150 requests a second for each public category (candles, order book, ticker, trades, other) and 140 a second for each private category (orders, cancellations, other), batch orders and cancels 20 a second. A breach restricts the category for a while; no status code or header is documented, and the error-code page lists no 429 (source: ) - No sandbox or testnet; the trade skill says all orders are real funds (source: ) - Dated notices include order types with time in force and WebSocket Private v2 effective 30 June 2026 with Private v1 retired on 30 September 2026; batch orders raised from 20 to 30 per request on 20 August 2026; the ticker endpoint capped at 200 markets per request from 13 October 2026, answering 400 above that (source: ) - Errors come back as an error object with name and message under an HTTP status, such as 401 NotAllowIP, 401 out_of_scope, 403 blocked_member_id, 422 order_not_ready (retry later) and 500 server_error (source: ) - The CLI `@bithumb-official/bithumb-cli` 0.8.5 keeps named profiles in ~/.bithumb/config.toml with a per-profile read_only flag, prints --json, writes every command to a local audit log that the MCP server's system_get_audit_log tool reads, and needs a second factor (--two-factor-type) for KRW deposits and withdrawals (source: ) - bithumb.com's fee, terms, Open API terms, company and security.txt pages timed out or answered a title only, so none is recorded first-hand (source: ) - #17 of 21 in 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 ## Compare - [Bitfinex API vs Bithumb Open API](https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.md): C 58.4 vs D 50.6 - [Bitget vs Bithumb Open API](https://www.anchorterminal.com/compare/bitget-vs-bithumb.md): D 53.9 vs D 50.6 - [Bithumb Open API vs Bitstamp API](https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.md): D 50.6 vs D 50.4 - [Bithumb Open API vs Bybit](https://www.anchorterminal.com/compare/bithumb-vs-bybit.md): D 50.6 vs C 57.3 - [Bithumb Open API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.md): D 50.6 vs C 61.7 - [Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.md): D 50.6 vs C 60 - [Bithumb Open API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.md): D 50.6 vs D 46.8 - [Bithumb Open API vs Deribit](https://www.anchorterminal.com/compare/bithumb-vs-deribit.md): D 50.6 vs C 59 - [Bithumb Open API vs dYdX](https://www.anchorterminal.com/compare/bithumb-vs-dydx.md): D 50.6 vs B 69.5 - [Bithumb Open API vs Gate](https://www.anchorterminal.com/compare/bithumb-vs-gate-io.md): D 50.6 vs C 56.4 - [Bithumb Open API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.md): D 50.6 vs BB 74.6 - [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.md): D 50.6 vs E 43.3 - [Bithumb Open API vs Hyperliquid](https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.md): D 50.6 vs D 50 - [Bithumb Open API vs Kraken API](https://www.anchorterminal.com/compare/bithumb-vs-kraken.md): D 50.6 vs BB 71 - [Bithumb Open API vs KuCoin](https://www.anchorterminal.com/compare/bithumb-vs-kucoin.md): D 50.6 vs D 53.9 - [Bithumb Open API vs MEXC API](https://www.anchorterminal.com/compare/bithumb-vs-mexc.md): D 50.6 vs C 56.3 - [Bithumb Open API vs OKX API](https://www.anchorterminal.com/compare/bithumb-vs-okx.md): D 50.6 vs B 64.3 - [Bithumb Open API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bithumb-vs-uniswap.md): D 50.6 vs B 63.3 - [Bithumb Open API vs Upbit Open API](https://www.anchorterminal.com/compare/bithumb-vs-upbit.md): D 50.6 vs C 54.7 - [Binance API vs Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md): B 63.2 vs D 50.6 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on bithumb.com or one of its subdomains, or the README at the root of github.com/bithumb-official/bithumb-ai-trade-kit. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "bithumb", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Bithumb Open API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Bithumb Open API on Anchor Terminal](https://www.anchorterminal.com/badges/bithumb.svg)](https://www.anchorterminal.com/tools/bithumb) ``` Plain link: ```html Bithumb Open API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Bithumb Open API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/bithumb-dark.png - Light: https://www.anchorterminal.com/assets/share/bithumb-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp