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

Bitpont API and MCP vs Upbit Open API

Bitpont API and MCP scores 62.9 (B) on agent readiness against Upbit Open API's 55.7 (C), and leads in 6 of 7 scored categories. Upbit 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

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

  • Schema & documentation, 82 against 66
  • Payments & pricing, 90 against 23

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

Upbit Open API C

Best for KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.

Ahead on

  • Maintenance & community, 83 against 14

Watch for

No MCP server; the agent route is the CLI through skills, which need a terminal

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.

Maintenance & community Upbit Open API +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.

Upbit Open API 83

Read as a closed service. SDK v1.1.0 on 20 October 2026 (30). The CLI 1.0.0 on 1 September, the rate-limit update of 7 October, the SDK on 20 October and the path-format notice for 16 November 2026 (20). open-api@upbit.com answers in turn on weekdays per the support notice, notices carry dates, and the six upbit-official repositories show no open issues (12 of 15). Current official SDKs in Python, TypeScript and Go (15). Apache-2.0 repositories pushed in October 2026; CI not checked (6 of 10). 30 + 20 + 12 + 15 + 6 = 83.

Payments & pricing Bitpont API and MCP +67

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.

Upbit Open API 23

No machine payment protocol (0). The fee schedule is on upbit.com, which disallows every crawler path, so no price is recorded (0 of 20, unchecked). Public quotation endpoints need 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 on the PC web site (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.

Schema & documentation Bitpont API and MCP +16

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.

Upbit Open API 66

No OpenAPI found; the reference is a readme.io site with a Markdown twin of every page (5 of 25). llms.txt on docs.upbit.com and a kr/llms.txt index (10). Each reference page states what the endpoint does, its group and its errors, with warnings such as market_offline after maintenance (14 of 20). Typed parameters with enums for order type, side and time in force and required flags (11 of 15). Recipes in Python, Java and Node.js and an error format of error.name and error.message with HTTP statuses (13 of 15). Feature versions in page histories (v1.6.1) and dated notices with effective dates, no single API version (13 of 15). 5 + 10 + 14 + 11 + 13 + 13 = 66.

Score by category

CategoryWeightBitpont API and MCPUpbit Open APIEdge
Reliability16%4542Bitpont API and MCP +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8266Bitpont API and MCP +16
Agent ergonomics13%7470Bitpont API and MCP +4
Security & auth14%6359Bitpont API and MCP +4
Payments & pricing10%9023Bitpont API and MCP +67
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1483Upbit Open API +69
Transparency & trust7%5854Bitpont API and MCP +4
Negative events≤1500
TotalB 62.9/100C 55.7/100

Facts side by side

FactBitpont API and MCPUpbit Open API
KindHTTP APIHTTP API
VendorBitpont (LiMiT)Dunamu Inc.
Hosted endpointhttps://www.bitpont.com/api/v1/mcpno (local only)
TransportsStreamable HTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicenceA 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 closednone
Tools exposed11480
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-20
Terms last updatedno date givenno document linked
Privacy policy last updated2026-11-11no date given
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone91 stars

How the scores have moved

Verdicts

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.

Upbit Open API

Upbit's Open API has a mandatory IP allow-list, scoped keys with a default withdrawal lock, per-group rate limits with 429 and 418 signalling, an order-test endpoint, official SDKs, a CLI and agent skills with a CONFIRM gate. There is no MCP server, sandbox or status page, and the fees and terms sit on a host our crawler may not read.

Before you call either

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

Upbit Open API

  1. Ask the person for a key with only the functions the task needs and your server's public IPv4 address registered; a private or unregistered IP is refused
  2. Sign every request with a fresh JWT (HS512, new nonce, SHA512 query hash) and branch on error.name, not error.message
  3. Run POST /v1/orders/test before a live order; it costs nothing and shares the 8-a-second order-test group
  4. Read Remaining-Req and keep orders under 12 a second per pocket; on 429 wait for the next second and on 418 wait out the stated block
  5. Leave the withdrawal safe-lock on unless the person lifts it in the app, and send paths with single slashes and no trailing slash before 16 November 2026

Questions

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

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

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

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

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

Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. No hosted endpoint is listed for Upbit Open API.

Other comparisons with Bitpont API and MCP or Upbit Open API

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.