Head to head · Exchange market data · October 2026 research run

Bithumb Open API vs Bitpont API and MCP

Bitpont API and MCP scores 62.9 (B) on agent readiness against Bithumb Open API's 51.6 (D), and leads in 6 of 7 scored categories. Bithumb Open API leads on maintenance & community. Both do exchange market data.

Best crypto exchange APIs and MCP servers for AI agents · All 231 exchanges comparisons

Which one, for what

Bithumb Open API D

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

Ahead on

  • Maintenance & community, 69 against 14

Also in its favour

  • Runs on your own machine

Watch for

No sandbox or testnet; every order uses real funds

Bitpont API and MCP B

Best for An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.

Ahead on

  • Reliability, 45 against 34
  • Schema & documentation, 82 against 64
  • Agent ergonomics, 74 against 67
  • Payments & pricing, 90 against 23
  • Transparency & trust, 58 against 47

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

No status page, no SLA and no sandbox or testnet in the reviewed documentation

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Bitpont API and MCP +67

Bithumb Open API 23

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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Bitpont API and MCP 90

No x402, MPP or L402; a verified trading fee lifting quotas for an hour is not a payment protocol (0). The API is free under published limits and the 0.40% interface fee is published per route without a login (30). Free access with no card (30). An agent starts with no signup by creating a private workspace through the API (30). Total 90.

Maintenance & community Bithumb Open API +55

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.

Bitpont API and MCP 14

Read as a closed hosted service. The changelog names versions (Bitpont 5.102.20, API 1.9) with no dates, so the time since the last release can't be established (0) and there are no dated entries (0). A public changelog and a support email; no answer observed and the GitHub organisation is closed to our reader (6 of 15). A first-party JavaScript client and TypeScript declarations as downloads, not on a package registry, and no MCP registry entry (8 of 15). No package or public CI seen (0). The public announcement was on 20 November 2026, so the record is days old. Total 14.

Schema & documentation Bitpont API and MCP +18

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.

Bitpont API and MCP 82

OpenAPI 3.1 file Bitpont Developer API 1.33.0 with 1,149 operations, read once as the reference viewer's source (25). llms.txt, Markdown downloads of the developer pages and Markdown agent guides (10). Every operation has a description and most a summary that states its job, and the guides say which tool to use for which task, though few say when not to (14 of 20). Enums, regex patterns and length limits on addresses and base-unit amounts, required fields; some inputs still allow free-form objects and the MCP operation takes a generic params object (12 of 15). Code examples in the guides and a shared error schema with code, requestId and retryable on 400 to 504 (13 of 15). A versioned changelog, but its entries carry no dates and its latest API version (1.9) doesn't match the file's 1.33.0 (8 of 15). Total 82.

Reliability Bitpont API and MCP +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.

Bitpont API and MCP 45

Read with the hosted lines on the REST API and hosted MCP server. No status page linked from any page read (0). No readable incident history (5). Rate limits with numbers, 30 request units a minute per IP for free access, 60 for partner keys, six items a batch (15). RateLimit and Retry-After headers documented, a retryable flag on every error, and stable request IDs and saved tasks for recovering a write after a lost response (15). No SLA (0). Nothing in the reviewed pages marks the API as beta or preview (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.

Transparency & trust Bitpont API and MCP +11

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.

Bitpont API and MCP 58

The editorial half. Closed source under readable terms, which licence the published SDK and documentation for integrations (15 of 30). A detailed privacy notice naming the operator, bases, recipients and browser storage, but it promises no deletion period for server logs and support records and no DPA was found (18 of 30). No deprecation policy or dated notices; the changelog only says changes are additive (5 of 20). Integration providers named by function (Jupiter, deBridge, Velocity, Jito, Kamino, KyberSwap, LI.FI, 1inch); the hosting provider and data locations are given only on request (10 of 20). Total 48.

Agent ergonomics Bitpont API and MCP +7

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.

Bitpont API and MCP 74

Read for the hosted MCP server, whose catalogue has 1,148 tools (5), with 10 added back for ?product= profiles, bitpont_findTools and bitpont_describeTool and paginated tools/list (15 of 25). Cursors, limits, product and network filters and read batches (18 of 20). Errors carry code, retryable and requestId, and checkInputs returns JSON Pointer paths before any provider is called (19 of 20). Idempotent tasks and stable request IDs, with a documented rule never to repeat an unknown submission; readOnlyHint and destructiveHint unchecked because tools/list was not sent, and the catalogue carries no annotations (14 of 20). A JavaScript client with TypeScript declarations, OpenAI function definitions and a Postman collection, one language (8 of 15). Total 74.

Score by category

CategoryWeightBithumb Open APIBitpont API and MCPEdge
Reliability16%3445Bitpont API and MCP +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6482Bitpont API and MCP +18
Agent ergonomics13%6774Bitpont API and MCP +7
Security & auth14%6063Bitpont API and MCP +3
Payments & pricing10%2390Bitpont API and MCP +67
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6914Bithumb Open API +55
Transparency & trust7%4758Bitpont API and MCP +11
Negative events≤1500
TotalD 51.6/100B 62.9/100

Facts side by side

FactBithumb Open APIBitpont API and MCP
KindHTTP APIHTTP API
VendorBithumb Co., Ltd.Bitpont (LiMiT)
Hosted endpointno (local only)https://www.bitpont.com/api/v1/mcp
TransportsstdioStreamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicencenoneA proprietary hosted service under the Bitpont Terms of Use (LIMIT SRL). The terms licence the published SDK, declarations, examples and API documentation for building integrations, with no copyright fee; the backend is closed
Tools exposed411148
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-13none
Terms last updatedcouldn't be readno date given
Privacy policy last updatedno document linked2026-11-11
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity6 starsnone

How the scores have moved

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.

Bitpont API and MCP

Public market reads, quotes and unsigned transaction drafts work without an account, every trade is signed in the owner's wallet, and an OpenAPI 3.1 file covers all 1,148 operations. There is no status page, the changelog carries no dates, and the hosted MCP server exposes the same 1,148 tools, narrowed by product filters and a search tool.

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

Bitpont API and MCP

  1. Connect with ?product=swap or another product ID, then call bitpont_findTools and bitpont_describeTool rather than loading all 1,148 tools
  2. Create a private workspace before the first ticket and store its secret and your requestId; reuse both to recover an order
  3. Call bitpont_checkInputs before preparing a transaction; amounts are base-unit decimal strings
  4. If a request returns 429, wait for the Retry-After value. The free budget is 30 units a minute per IP and a batch costs one unit per item
  5. Never repeat a submission whose outcome is unknown; read the execution receipt first

Questions

Which is better for AI agents, Bithumb Open API or Bitpont API and MCP?

Bitpont API and MCP scores 62.9 (B) on agent readiness against Bithumb Open API's 51.6 (D), and leads in 6 of 7 scored categories. Bithumb Open API leads on maintenance & community.

Do Bithumb Open API and Bitpont API and MCP need an API key?

Bithumb Open API needs an API key. Bitpont API and MCP takes an API key or an OAuth sign-in.

Can an agent call Bithumb Open API and Bitpont API and MCP without installing anything?

Bithumb Open API runs on your own machine, with no hosted endpoint listed. Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp.

Other comparisons with Bithumb Open API or Bitpont API and MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.