# Bitpont API and MCP vs Upbit Open API (slim)

> Bitpont scores 62.9 (B) to Upbit Open's 55.7 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bitpont-vs-upbit.md (~3,900 tokens) · this version ~930 tokens · JSON https://www.anchorterminal.com/compare/bitpont-vs-upbit.json · canonical https://www.anchorterminal.com/compare/bitpont-vs-upbit
- 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-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Bitpont API and MCP: B 62.9, rank #659 of 1563 · https://www.anchorterminal.com/tools/bitpont.min.md
- Upbit Open API: C 55.7, rank #979 of 1563 · https://www.anchorterminal.com/tools/upbit.min.md
- Bitpont API and MCP, good 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 A hosted endpoint, with nothing to install; Free to start without a card.
- Upbit Open API, good 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.

| Category | Bitpont API and MCP | Upbit Open API |
| --- | --- | --- |
| Reliability (16%) | 45 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 82 | 66 |
| Agent ergonomics (13%) | 74 | 70 |
| Security & auth (14%) | 63 | 59 |
| Payments & pricing (10%) | 90 | 23 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 14 | 83 |
| Transparency & trust (7%) | 58 | 54 |

| Fact (where they differ) | Bitpont API and MCP | Upbit Open API |
| --- | --- | --- |
| Vendor | Bitpont (LiMiT) | Dunamu Inc. |
| Hosted endpoint | `https://www.bitpont.com/api/v1/mcp` | no (local only) |
| Transports | Streamable HTTP |  |
| Auth | OAuth or key | API key |
| Licence | A 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 | none |
| Tools exposed | 1148 | 0 |
| Last release | none | 2026-10-20 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | 2026-11-11 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 91 stars |

Why the edge:
- Maintenance & community, Upbit Open API +69: Bitpont API and MCP 14 (Read as a closed hosted service.); Upbit Open API 83 (Read as a closed service.)
- 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).); Upbit Open API 23 (No machine payment protocol (0).)
- 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).); Upbit Open API 66 (No OpenAPI found; the reference is a readme.io site with a Markdown twin of every page (5 of 25).)
