{
  "data": {
    "a": {
      "slug": "bitpont",
      "name": "Bitpont API and MCP",
      "vendor": "Bitpont (LiMiT)",
      "vendorUrl": "https://www.bitpont.com/developers/",
      "company": "bitpont.com",
      "kind": "http-api",
      "category": "crypto-exchanges",
      "summary": "Bitpont is a wallet-connected DeFi front end for swaps, bridges, lending, liquidity and perpetuals on EVM networks and Solana. Its REST API and hosted MCP server quote, read positions and prepare transactions the owner's wallet signs.",
      "url": "https://www.anchorterminal.com/tools/bitpont",
      "markdownUrl": "https://www.anchorterminal.com/tools/bitpont.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitpont.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/bitpont.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitpont.json",
      "dns": "bitpont.grade.anchorterminal.com",
      "repo": "https://github.com/bitpont",
      "license": "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",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://www.bitpont.com/api/v1/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Standard access needs no key. A client-created private workspace, sent as the `X-Bitpont-Workspace` header, keeps tickets and receipts together. Optional partner bearer keys are issued by the operator on request, with scopes (`discovery:read`, `positions:read`, `transactions:prepare`, `transactions:submit`), expiry and revocation. The owner's wallet signs every trade locally (https://www.bitpont.com/developers/authentication/, checked 2026-11-20).",
      "pricing": "usage",
      "pricingNotes": "The API is free under a shared budget of 30 request units a minute per IP; partner keys default to 60 units a minute. Bitpont takes a 0.40% interface fee on supported swaps, limit orders and direct deBridge bridges, and none on lending, Earn or liquidity actions. A verified fee lifts request quotas for an hour. No card or account is needed (https://www.bitpont.com/fees/, checked 2026-11-20).",
      "priceSummary": "0.4% fee",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the OpenAPI file, llms.txt or developer pages read on 20 November 2026. A finalised Bitpont trading fee, verified through `feeAccess`, unlocks an hour without standard quotas, which is not a machine payment protocol.",
        "endpoints": []
      },
      "toolCount": 1148,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-20"
      },
      "docsUrl": "https://www.bitpont.com/developers/",
      "llmsTxt": "https://www.bitpont.com/llms.txt",
      "openapi": "https://www.bitpont.com/assets/docs/bitpont-openapi.json",
      "capabilities": [
        "exchange.market-data",
        "exchange.spot-trading",
        "exchange.derivatives",
        "exchange.balances",
        "exchange.transfers",
        "exchange.staking",
        "market.crypto",
        "wallet.onchain"
      ],
      "tags": [
        "official",
        "hosted",
        "closed-source",
        "openapi",
        "llms-txt",
        "no-key",
        "no-card",
        "usage-priced",
        "typescript",
        "mcp",
        "rest",
        "no-status-page"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.9,
        "grade": "B",
        "agentReady": false,
        "rank": 659,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 8,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 74,
          "maintenance": 14,
          "payments": 90,
          "reliability": 45,
          "schema": 82,
          "security": 63,
          "transparency": 58
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-20"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.",
        "strengths": [
          "Market reads, quotes and transaction drafts work with no account, key or card",
          "Every value transfer needs the owner's wallet signature; partner keys carry scopes such as `positions:read` and `transactions:submit`",
          "OpenAPI 3.1, llms.txt, Markdown guides, a Postman collection and OpenAI function definitions, with typed inputs and patterns on amounts and addresses",
          "Every error carries `code`, `requestId` and `retryable`, and `checkInputs` returns JSON Pointer paths before a provider is called",
          "Stable request IDs and saved tasks let an agent recover an order after a lost response without resubmitting"
        ],
        "weaknesses": [
          "No status page, no SLA and no sandbox or testnet in the reviewed documentation",
          "The changelog lists versions with no dates, and its latest API version (1.9) differs from the OpenAPI file's 1.33.0",
          "1,148 tools behind one MCP endpoint, a 5.4 MB OpenAPI file and a 1.7 MB tools catalogue",
          "No security.txt, bug bounty or certification; the security page says Bitpont itself has no independent audit",
          "A DeFi interface that takes 0.40% on swaps and bridges; funds sit in third-party protocols with their own risks"
        ],
        "agentNotes": [
          "Connect with `?product=swap` or another product ID, then call `bitpont_findTools` and `bitpont_describeTool` rather than loading all 1,148 tools",
          "Create a private workspace before the first ticket and store its secret and your `requestId`; reuse both to recover an order",
          "Call `bitpont_checkInputs` before preparing a transaction; amounts are base-unit decimal strings",
          "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",
          "Never repeat a submission whose outcome is unknown; read the execution receipt first"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.9
          }
        ],
        "editorialScores": {
          "ergonomics": 74,
          "maintenance": 14,
          "payments": 90,
          "reliability": 45,
          "schema": 82,
          "security": 63,
          "transparency": 48
        },
        "provenanceScore": 68,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-20",
            "maintenance": "2026-11-20",
            "payments": "2026-11-20",
            "reliability": "2026-11-20",
            "schema": "2026-11-20",
            "security": "2026-11-20",
            "transparency": "2026-11-20"
          },
          "last": "2026-11-20",
          "oldest": "2026-11-20",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -fsS https://www.bitpont.com/api/v1/agent/tools -H 'Content-Type: application/json' -d '{\"product\":\"bridge\",\"q\":\"quote\",\"limit\":5}'",
        "claudeCode": "claude mcp add --transport http bitpont \"https://www.bitpont.com/api/v1/mcp?product=swap\""
      },
      "letme": {
        "capability": "https://letme.dev/exchange.market-data",
        "tool": "https://letme.dev/bitpont"
      },
      "area": "payments",
      "unitPrices": [
        {
          "item": "Swap and bridge interface fee",
          "unit": "pct",
          "usd": 0.4,
          "note": "0.40% of input on supported swaps, limit orders and direct deBridge routes; network and protocol fees extra"
        }
      ],
      "provenance": {
        "legalEntity": "LIMIT SRL",
        "domain": "bitpont.com",
        "domainRegistered": "2020-08-15",
        "endpointOnVendorDomain": true,
        "terms": "https://www.bitpont.com/terms/",
        "privacy": "https://www.bitpont.com/privacy/",
        "statusPage": "",
        "changelog": "https://www.bitpont.com/developers/changelog/",
        "securityTxt": "none",
        "checked": "2026-11-20",
        "notes": [
          "The terms, privacy notice and about page say Bitpont is a LiMiT product operated by LIMIT SRL, published identifiers RO21411289 and J05/751/2007. limit.ro gives the same identifiers, an Oradea address and EUID ROONRC.J05/751/2007, and lists bitpont.com as an owned project.",
          "The terms permit search engines and AI retrieval services to crawl and render public pages.",
          "www.bitpont.com/robots.txt allows all agents and disallows /api/ apart from nine named paths; the MCP endpoint and /api/v1/usage are among the closed paths.",
          "RDAP (Verisign) gives bitpont.com a registration date of 15 August 2020.",
          "/.well-known/security.txt answered 404. No status page was linked from any page read."
        ],
        "score": 68
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/bitpont.json",
      "live": {
        "slug": "bitpont",
        "probe": {
          "target": "https://www.bitpont.com/api/v1/mcp",
          "method": "get",
          "lastAt": "2026-11-20T21:48:32.606649764Z",
          "lastOk": true,
          "lastStatus": 405,
          "lastMs": 146,
          "authRequired": false,
          "uptime24h": 98.36,
          "uptime30d": 98.36,
          "p50ms24h": 129,
          "p95ms24h": 422,
          "samples24h": 61,
          "samples30d": 61,
          "days": [
            {
              "date": "2026-11-20",
              "probes": 61,
              "ok": 60
            }
          ],
          "since": "2026-11-20T15:54:23.354107122Z"
        },
        "securityTxt": {
          "url": "https://bitpont.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:36:59.418435314Z"
        },
        "llmsTxt": {
          "url": "https://www.bitpont.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-20T16:21:44.038986512Z"
        },
        "updatedAt": "2026-11-20T21:48:32.606649764Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-20",
        "sinceWatching": true,
        "best": 0
      }
    },
    "answer": "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 \u0026 community.",
    "b": {
      "slug": "upbit",
      "name": "Upbit Open API",
      "vendor": "Dunamu Inc.",
      "vendorUrl": "https://docs.upbit.com",
      "company": "upbit.com",
      "kind": "http-api",
      "category": "crypto-exchanges",
      "summary": "Upbit, the Korean exchange run by Dunamu, has a REST and WebSocket Open API for KRW, BTC and USDT market data, orders, balances, deposits and withdrawals, with official SDKs, a CLI and agent skills but no MCP server.",
      "url": "https://www.anchorterminal.com/tools/upbit",
      "markdownUrl": "https://www.anchorterminal.com/tools/upbit.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/upbit.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/upbit.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/upbit.json",
      "dns": "upbit.grade.anchorterminal.com",
      "repo": "https://github.com/upbit-official",
      "transports": [],
      "packages": [
        {
          "registry": "npm",
          "name": "@upbit-official/upbit-cli"
        },
        {
          "registry": "pypi",
          "name": "upbit-sdk"
        }
      ],
      "auth": "api-key",
      "authNotes": "Access and secret keys issued on the PC web site under My Page \u003e Open API Management after identity verification and two-factor authentication. At issuance the person picks the functions the key may use and must register at least one public IPv4 address, since the allow-list is mandatory. Each request carries a JWT signed with HMAC SHA512 over the access key, a fresh nonce and a SHA512 hash of the query, as a Bearer token. A key with withdrawal permission gets a withdrawal safe-lock by default that is lifted only in the mobile app. Up to 10 keys on the main pocket and 5 per sub-pocket; expired keys answer expired_access_key (https://docs.upbit.com/kr/docs/api-key.md, checked 2026-11-03).",
      "pricing": "usage",
      "pricingNotes": "Trading fees per fill. The fee schedule is on upbit.com, whose robots.txt disallows every path for our crawler, so no rate is recorded. Public quotation endpoints need no key and no account (https://upbit.com/robots.txt, checked 2026-11-03).",
      "priceSummary": "Pay per use",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the developer docs, llms.txt, the SDK licence or the CLI docs (checked 2026-11-03). Fees are taken from each fill.",
        "endpoints": []
      },
      "toolCount": 0,
      "popularity": {
        "githubStars": 91,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-03"
      },
      "docsUrl": "https://docs.upbit.com/kr/reference/api-overview",
      "llmsTxt": "https://docs.upbit.com/llms.txt",
      "capabilities": [
        "exchange.market-data",
        "exchange.spot-trading",
        "exchange.balances",
        "exchange.transfers",
        "market.crypto"
      ],
      "tags": [
        "hosted",
        "api-key",
        "closed-source",
        "usage-priced",
        "cli",
        "agent-skills",
        "llms-txt",
        "python",
        "typescript",
        "go",
        "no-status-page"
      ],
      "lastRelease": "2026-10-20",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 55.7,
        "grade": "C",
        "agentReady": false,
        "rank": 979,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 17,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 70,
          "maintenance": 83,
          "payments": 23,
          "reliability": 42,
          "schema": 66,
          "security": 59,
          "transparency": 54
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-03"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.",
        "strengths": [
          "Keys need a registered public IP, carry only the chosen functions and get a withdrawal safe-lock by default that only the mobile app lifts",
          "Rate limits published per group with numbers, a Remaining-Req header on every response, 429 then 418 with a stated block length",
          "POST /v1/orders/test checks an order and the pair's state at no cost, and the skills run it before a live order",
          "Official Python, TypeScript and Go SDKs at v1.1.0 (20 October 2026), a CLI with JSON output and agent skills that require a typed CONFIRM before any write",
          "Notices carry effective dates, such as the path-format change of 16 November 2026"
        ],
        "weaknesses": [
          "No MCP server; the agent route is the CLI through skills, which need a terminal",
          "No sandbox or testnet beyond the order-test endpoint, and no status page or SLA",
          "Keys can only be issued on the PC web site after Korean identity verification and 2FA, and the exchange serves the Korean market",
          "The fee schedule, user terms and Open API terms are on upbit.com, which disallows every crawler path, so none is recorded first-hand",
          "The SDK licence page says the SDK material is not open source while the GitHub repositories carry Apache-2.0"
        ],
        "agentNotes": [
          "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",
          "Sign every request with a fresh JWT (HS512, new nonce, SHA512 query hash) and branch on error.name, not error.message",
          "Run POST /v1/orders/test before a live order; it costs nothing and shares the 8-a-second order-test group",
          "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",
          "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"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 55.7
          }
        ],
        "editorialScores": {
          "ergonomics": 70,
          "maintenance": 83,
          "payments": 23,
          "reliability": 42,
          "schema": 66,
          "security": 59,
          "transparency": 42
        },
        "provenanceScore": 66,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-03",
            "maintenance": "2026-11-03",
            "payments": "2026-11-03",
            "reliability": "2026-11-03",
            "schema": "2026-11-03",
            "security": "2026-11-03",
            "transparency": "2026-11-03"
          },
          "last": "2026-11-03",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-03",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install -g @upbit-official/upbit-cli",
        "http": "curl 'https://api.upbit.com/v1/ticker?markets=KRW-BTC'"
      },
      "letme": {
        "capability": "https://letme.dev/exchange.market-data",
        "tool": "https://letme.dev/upbit"
      },
      "area": "payments",
      "provenance": {
        "legalEntity": "Dunamu Inc.",
        "domain": "upbit.com",
        "domainRegistered": "2004-01-10",
        "endpointOnVendorDomain": true,
        "terms": "",
        "privacy": "https://docs.upbit.com/kr/page/privacy_policy_v1_5.md",
        "statusPage": "",
        "changelog": "https://docs.upbit.com/kr/changelog",
        "securityTxt": "unknown",
        "checked": "2026-11-03",
        "notes": [
          "Dunamu Inc. is named as the licensor in the Upbit Developer SDK License v1.0 and as the company in the developer centre's privacy policy V1.5 (from 18 May 2026).",
          "upbit.com/robots.txt disallows every path for User-agent * (a second group adds /terms_and_policy and others), allowing only Googlebot, MSNBot, Yeti and Daumoa; sg.upbit.com and www.dunamu.com do the same. The user terms, the Open API terms, the fee schedule and security.txt on those hosts were therefore not fetched; the terms URL is left empty.",
          "docs.upbit.com/robots.txt allows everything but edit, login and api-next paths and points to llms.txt, with Content-Signal ai-train=yes, search=yes, ai-input=yes.",
          "RDAP gives upbit.com a registration date of 10 January 2004.",
          "No status page found; the API has a service-status (wallet status) endpoint and an announcements WebSocket stream."
        ],
        "score": 66
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/upbit.json",
      "live": {
        "slug": "upbit",
        "versions": [
          {
            "registry": "npm",
            "name": "@upbit-official/upbit-cli",
            "version": "1.0.0",
            "seenAt": "2026-11-20T21:22:10.749252069Z"
          },
          {
            "registry": "pypi",
            "name": "upbit-sdk",
            "version": "1.1.0",
            "released": "2026-10-20",
            "seenAt": "2026-11-20T21:22:11.201431083Z"
          }
        ],
        "npmWeekly": 125,
        "pypiWeekly": 321,
        "securityTxt": {
          "url": "https://upbit.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:34:58.584111118Z"
        },
        "llmsTxt": {
          "url": "https://docs.upbit.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-20T16:24:45.822729055Z"
        },
        "domain": {
          "domain": "upbit.com",
          "registered": "2004-01-10",
          "source": "https://rdap.verisign.com/com/v1/domain/upbit.com",
          "checkedAt": "2026-11-15T15:20:19.035223765Z"
        },
        "pages": [
          {
            "url": "https://docs.upbit.com/kr/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-19T22:23:12.482203118Z",
            "changedAt": "2026-11-19T22:23:12.482203118Z",
            "fingerprint": "05b815098a06"
          },
          {
            "url": "https://docs.upbit.com/kr/page/privacy_policy_v1_5.md",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-19T22:23:15.24550476Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "95fbffb1ce06"
          }
        ],
        "updatedAt": "2026-11-20T21:22:11.201431083Z"
      }
    },
    "edges": [
      {
        "by": 69,
        "category": "maintenance",
        "leads": "upbit",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 14,
          "b": 83
        }
      },
      {
        "by": 67,
        "category": "payments",
        "leads": "bitpont",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 90,
          "b": 23
        }
      },
      {
        "by": 16,
        "category": "schema",
        "leads": "bitpont",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 82,
          "b": 66
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Bitpont (LiMiT)",
        "b": "Dunamu Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://www.bitpont.com/api/v1/mcp",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "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",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "1148",
        "b": "0",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "none",
        "b": "2026-10-20",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "2026-11-11",
        "b": "no date given",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "91 stars",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 community.",
        "question": "Which is better for AI agents, Bitpont API and MCP or Upbit Open API?"
      },
      {
        "answer": "Bitpont API and MCP takes an API key or an OAuth sign-in. Upbit Open API needs an API key.",
        "question": "Do Bitpont API and MCP and Upbit Open API need an API key?"
      },
      {
        "answer": "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.",
        "question": "Can an agent call Bitpont API and MCP and Upbit Open API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 82 against 66",
          "Payments \u0026 pricing, 90 against 23"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "Free to start without a card"
        ],
        "goodFor": "An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.",
        "slug": "bitpont",
        "watchFor": "No status page, no SLA and no sandbox or testnet in the reviewed documentation"
      },
      {
        "aheadOn": [
          "Maintenance \u0026 community, 83 against 14"
        ],
        "also": null,
        "goodFor": "KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.",
        "slug": "upbit",
        "watchFor": "No MCP server; the agent route is the CLI through skills, which need a terminal"
      }
    ],
    "history": {
      "bitpont": null,
      "upbit": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1,
          "from": 54.7,
          "fromGrade": "C",
          "to": 55.7,
          "toGrade": "C"
        }
      ]
    },
    "job": {
      "capability": "exchange.market-data",
      "name": "Exchange market data"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.json",
        "title": "Bitfinex API vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit.json",
        "title": "Bitfinex API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-bitpont.json",
        "title": "Bitget vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-bitpont"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-upbit.json",
        "title": "Bitget vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bithumb-vs-bitpont.json",
        "title": "Bithumb Open API vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/bithumb-vs-bitpont"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bithumb-vs-upbit.json",
        "title": "Bithumb Open API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/bithumb-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-bitstamp.json",
        "title": "Bitpont API and MCP vs Bitstamp API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-bitstamp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-bybit.json",
        "title": "Bitpont API and MCP vs Bybit",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-bybit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-coinbase-advanced-trade.json",
        "title": "Bitpont API and MCP vs Coinbase Advanced Trade API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-coinbase-advanced-trade"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-coinbase-mcp.json",
        "title": "Bitpont API and MCP vs Coinbase MCP server (Coinbase for Agents)",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-coinbase-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-crypto-com-exchange.json",
        "title": "Bitpont API and MCP vs Crypto.com Exchange API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-crypto-com-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-deribit.json",
        "title": "Bitpont API and MCP vs Deribit",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-deribit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-dydx.json",
        "title": "Bitpont API and MCP vs dYdX",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-dydx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-gate-io.json",
        "title": "Bitpont API and MCP vs Gate",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-gate-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-gemini-exchange.json",
        "title": "Bitpont API and MCP vs Gemini Exchange API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-gemini-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-htx.json",
        "title": "Bitpont API and MCP vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-hyperliquid.json",
        "title": "Bitpont API and MCP vs Hyperliquid",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-hyperliquid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-kraken.json",
        "title": "Bitpont API and MCP vs Kraken API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-kraken"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-kucoin.json",
        "title": "Bitpont API and MCP vs KuCoin",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-kucoin"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-mexc.json",
        "title": "Bitpont API and MCP vs MEXC API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-mexc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-okx.json",
        "title": "Bitpont API and MCP vs OKX API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-okx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-uniswap.json",
        "title": "Bitpont API and MCP vs Uniswap Trading API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-uniswap"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit.json",
        "title": "Bitstamp API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-upbit.json",
        "title": "Bybit vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.json",
        "title": "Crypto.com Exchange API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deribit-vs-upbit.json",
        "title": "Deribit vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/deribit-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dydx-vs-upbit.json",
        "title": "dYdX vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/dydx-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gate-io-vs-upbit.json",
        "title": "Gate vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/gate-io-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit.json",
        "title": "Gemini Exchange API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/htx-vs-upbit.json",
        "title": "HTX trading API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/htx-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-upbit.json",
        "title": "Hyperliquid vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kucoin-vs-upbit.json",
        "title": "KuCoin vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/kucoin-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mexc-vs-upbit.json",
        "title": "MEXC API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/mexc-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/binance-vs-bitpont.json",
        "title": "Binance API vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/binance-vs-bitpont"
      },
      {
        "json": "https://www.anchorterminal.com/compare/binance-vs-upbit.json",
        "title": "Binance API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/binance-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.json",
        "title": "Coinbase Advanced Trade API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit.json",
        "title": "Coinbase MCP server (Coinbase for Agents) vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kraken-vs-upbit.json",
        "title": "Kraken API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/kraken-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/okx-vs-upbit.json",
        "title": "OKX API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/okx-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/uniswap-vs-upbit.json",
        "title": "Uniswap Trading API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/uniswap-vs-upbit"
      }
    ],
    "panel": null,
    "scores": [
      {
        "bitpont": 45,
        "by": 3,
        "edge": "bitpont",
        "key": "reliability",
        "name": "Reliability",
        "upbit": 42,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "bitpont": 82,
        "by": 16,
        "edge": "bitpont",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "upbit": 66,
        "weight": 13
      },
      {
        "bitpont": 74,
        "by": 4,
        "edge": "bitpont",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "upbit": 70,
        "weight": 13
      },
      {
        "bitpont": 63,
        "by": 4,
        "edge": "bitpont",
        "key": "security",
        "name": "Security \u0026 auth",
        "upbit": 59,
        "weight": 14
      },
      {
        "bitpont": 90,
        "by": 67,
        "edge": "bitpont",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "upbit": 23,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "bitpont": 14,
        "by": 69,
        "edge": "upbit",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "upbit": 83,
        "weight": 7
      },
      {
        "bitpont": 58,
        "by": 4,
        "edge": "bitpont",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "upbit": 54,
        "weight": 7
      }
    ],
    "summary": "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 \u0026 community. Both do exchange market data.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "bitpont": "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": "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/bitpont-vs-upbit",
    "json": "https://www.anchorterminal.com/compare/bitpont-vs-upbit.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/bitpont-vs-upbit.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/bitpont-vs-upbit.min.md"
  },
  "markdown": "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 \u0026 community. Both do exchange market data.\n\n- Bitpont API and MCP: grade B, 62.9/100, rank #659 of 1563. Markdown https://www.anchorterminal.com/tools/bitpont.md · JSON https://www.anchorterminal.com/api/v1/tools/bitpont.json\n- Upbit Open API: grade C, 55.7/100, rank #979 of 1563. Markdown https://www.anchorterminal.com/tools/upbit.md · JSON https://www.anchorterminal.com/api/v1/tools/upbit.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 231 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Which one, for what\n\n### Bitpont API and MCP (B)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 82 against 66\n- Payments \u0026 pricing, 90 against 23\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: No status page, no SLA and no sandbox or testnet in the reviewed documentation\n\n### Upbit Open API (C)\n\nGood for: KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.\n\nAhead on:\n- Maintenance \u0026 community, 83 against 14\n\nWatch for: No MCP server; the agent route is the CLI through skills, which need a terminal\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Upbit Open API +69\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: Bitpont API and MCP +67\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: Bitpont API and MCP +16\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | Bitpont API and MCP | Upbit Open API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 45 | 42 | Bitpont API and MCP +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 82 | 66 | Bitpont API and MCP +16 |\n| Agent ergonomics | 13% | 74 | 70 | Bitpont API and MCP +4 |\n| Security \u0026 auth | 14% | 63 | 59 | Bitpont API and MCP +4 |\n| Payments \u0026 pricing | 10% | 90 | 23 | Bitpont API and MCP +67 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 14 | 83 | Upbit Open API +69 |\n| Transparency \u0026 trust | 7% | 58 | 54 | Bitpont API and MCP +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.9 · B** | **55.7 · C** | |\n\n## Facts side by side\n\n| Fact | Bitpont API and MCP | Upbit Open API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bitpont (LiMiT) | Dunamu Inc. |\n| Hosted endpoint | `https://www.bitpont.com/api/v1/mcp` | no (local only) |\n| Transports | Streamable HTTP |  |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 1148 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-20 |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | 2026-11-11 | no date given |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | none | 91 stars |\n\n## How the scores have moved\n\n### Bitpont API and MCP\n\nNo score change since it was listed.\n\n### Upbit Open API\n\n- +1.0 on 13 November 2026: checklist\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Bitpont API and MCP\n\n1. Connect with `?product=swap` or another product ID, then call `bitpont_findTools` and `bitpont_describeTool` rather than loading all 1,148 tools\n2. Create a private workspace before the first ticket and store its secret and your `requestId`; reuse both to recover an order\n3. Call `bitpont_checkInputs` before preparing a transaction; amounts are base-unit decimal strings\n4. 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\n5. Never repeat a submission whose outcome is unknown; read the execution receipt first\n\n### Upbit Open API\n\n1. 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\n2. Sign every request with a fresh JWT (HS512, new nonce, SHA512 query hash) and branch on error.name, not error.message\n3. Run POST /v1/orders/test before a live order; it costs nothing and shares the 8-a-second order-test group\n4. 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\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Bitpont API and MCP or Upbit Open API?\n\nBitpont 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 \u0026 community.\n\n### Do Bitpont API and MCP and Upbit Open API need an API key?\n\nBitpont API and MCP takes an API key or an OAuth sign-in. Upbit Open API needs an API key.\n\n### Can an agent call Bitpont API and MCP and Upbit Open API without installing anything?\n\nBitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. No hosted endpoint is listed for Upbit Open API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitpont-vs-upbit.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitpont-vs-upbit.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitpont\", \"b\": \"upbit\"}`. From a terminal: `anchor compare bitpont upbit`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitpont.json and https://www.anchorterminal.com/api/v1/tools/upbit.json\n\n## Other comparisons with Bitpont API and MCP or Upbit Open API\n\n- [Bitfinex API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.md)\n- [Bitfinex API vs Upbit Open API](https://www.anchorterminal.com/compare/bitfinex-vs-upbit.md)\n- [Bitget vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitget-vs-bitpont.md)\n- [Bitget vs Upbit Open API](https://www.anchorterminal.com/compare/bitget-vs-upbit.md)\n- [Bithumb Open API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bithumb-vs-bitpont.md)\n- [Bithumb Open API vs Upbit Open API](https://www.anchorterminal.com/compare/bithumb-vs-upbit.md)\n- [Bitpont API and MCP vs Bitstamp API](https://www.anchorterminal.com/compare/bitpont-vs-bitstamp.md)\n- [Bitpont API and MCP vs Bybit](https://www.anchorterminal.com/compare/bitpont-vs-bybit.md)\n- [Bitpont API and MCP vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitpont-vs-coinbase-advanced-trade.md)\n- [Bitpont API and MCP vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitpont-vs-coinbase-mcp.md)\n- [Bitpont API and MCP vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitpont-vs-crypto-com-exchange.md)\n- [Bitpont API and MCP vs Deribit](https://www.anchorterminal.com/compare/bitpont-vs-deribit.md)\n- [Bitpont API and MCP vs dYdX](https://www.anchorterminal.com/compare/bitpont-vs-dydx.md)\n- [Bitpont API and MCP vs Gate](https://www.anchorterminal.com/compare/bitpont-vs-gate-io.md)\n- [Bitpont API and MCP vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitpont-vs-gemini-exchange.md)\n- [Bitpont API and MCP vs HTX trading API](https://www.anchorterminal.com/compare/bitpont-vs-htx.md)\n- [Bitpont API and MCP vs Hyperliquid](https://www.anchorterminal.com/compare/bitpont-vs-hyperliquid.md)\n- [Bitpont API and MCP vs Kraken API](https://www.anchorterminal.com/compare/bitpont-vs-kraken.md)\n- [Bitpont API and MCP vs KuCoin](https://www.anchorterminal.com/compare/bitpont-vs-kucoin.md)\n- [Bitpont API and MCP vs MEXC API](https://www.anchorterminal.com/compare/bitpont-vs-mexc.md)\n- [Bitpont API and MCP vs OKX API](https://www.anchorterminal.com/compare/bitpont-vs-okx.md)\n- [Bitpont API and MCP vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitpont-vs-uniswap.md)\n- [Bitstamp API vs Upbit Open API](https://www.anchorterminal.com/compare/bitstamp-vs-upbit.md)\n- [Bybit vs Upbit Open API](https://www.anchorterminal.com/compare/bybit-vs-upbit.md)\n- [Crypto.com Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.md)\n- [Deribit vs Upbit Open API](https://www.anchorterminal.com/compare/deribit-vs-upbit.md)\n- [dYdX vs Upbit Open API](https://www.anchorterminal.com/compare/dydx-vs-upbit.md)\n- [Gate vs Upbit Open API](https://www.anchorterminal.com/compare/gate-io-vs-upbit.md)\n- [Gemini Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit.md)\n- [HTX trading API vs Upbit Open API](https://www.anchorterminal.com/compare/htx-vs-upbit.md)\n- [Hyperliquid vs Upbit Open API](https://www.anchorterminal.com/compare/hyperliquid-vs-upbit.md)\n- [KuCoin vs Upbit Open API](https://www.anchorterminal.com/compare/kucoin-vs-upbit.md)\n- [MEXC API vs Upbit Open API](https://www.anchorterminal.com/compare/mexc-vs-upbit.md)\n- [Binance API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/binance-vs-bitpont.md)\n- [Binance API vs Upbit Open API](https://www.anchorterminal.com/compare/binance-vs-upbit.md)\n- [Coinbase Advanced Trade API vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit.md)\n- [Kraken API vs Upbit Open API](https://www.anchorterminal.com/compare/kraken-vs-upbit.md)\n- [OKX API vs Upbit Open API](https://www.anchorterminal.com/compare/okx-vs-upbit.md)\n- [Uniswap Trading API vs Upbit Open API](https://www.anchorterminal.com/compare/uniswap-vs-upbit.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-20",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Bitpont API and MCP vs Upbit Open API",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": [
      "Bitpont API and MCP B 62.9",
      "Upbit Open API C 55.7",
      "scores"
    ],
    "h1": "Bitpont API and MCP vs Upbit Open API",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/bitpont-vs-upbit",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Bitpont vs Upbit Open for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-20",
    "url": "https://www.anchorterminal.com/compare/bitpont-vs-upbit"
  },
  "tokens": {
    "markdown": 3900,
    "slim": 930
  },
  "version": 1
}
