{ "data": { "a": { "slug": "bithumb", "name": "Bithumb Open API", "vendor": "Bithumb Co., Ltd.", "vendorUrl": "https://apidocs.bithumb.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "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.", "url": "https://www.anchorterminal.com/tools/bithumb", "markdownUrl": "https://www.anchorterminal.com/tools/bithumb.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bithumb.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bithumb.json", "dns": "bithumb.grade.anchorterminal.com", "repo": "https://github.com/bithumb-official/bithumb-ai-trade-kit", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@bithumb-official/bithumb-mcp" }, { "registry": "npm", "name": "@bithumb-official/bithumb-cli" } ], "auth": "api-key", "authNotes": "Access and secret keys issued under My Page \u003e 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": "usage", "pricingNotes": "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).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "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.", "endpoints": [] }, "toolCount": 41, "popularity": { "githubStars": 6, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://apidocs.bithumb.com/reference/api-레퍼런스", "llmsTxt": "https://apidocs.bithumb.com/llms.txt", "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" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 50.6, "grade": "D", "agentReady": false, "rank": 999, "ranked": true, "rankOf": 1349, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 69, "payments": 15, "reliability": 34, "schema": 64, "security": 60, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "KRW-market trading for agents acting for a verified Korean account, with a vendor-built MCP server, CLI and skills.", "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" ], "agentNotes": [ "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", "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", "Prefer the `bithumb` CLI for writes, as the skills do, and check `bithumb config show --json` for a read-only profile before any order", "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", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.6 } ], "editorialScores": { "ergonomics": 67, "maintenance": 69, "payments": 15, "reliability": 34, "schema": 64, "security": 60, "transparency": 24 }, "provenanceScore": 69, "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", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @bithumb-official/bithumb-cli", "http": "curl 'https://api.bithumb.com/v1/market/all?isDetails=false'", "config": { "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}" } } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/bithumb" }, "area": "payments", "provenance": { "legalEntity": "Bithumb Co., Ltd.", "domain": "bithumb.com", "domainRegistered": "2015-06-16", "endpointOnVendorDomain": true, "terms": "https://www.bithumb.com/react/terms/info-terms", "privacy": "", "statusPage": "", "changelog": "https://apidocs.bithumb.com/changelog", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "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." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bithumb.json", "live": { "slug": "bithumb", "versions": [ { "registry": "npm", "name": "@bithumb-official/bithumb-cli", "version": "0.8.5", "seenAt": "2026-11-04T20:02:56.600783413Z" }, { "registry": "npm", "name": "@bithumb-official/bithumb-mcp", "version": "0.8.5", "seenAt": "2026-11-04T20:02:55.754674786Z" } ], "githubStars": 6, "npmWeekly": 87, "securityTxt": { "url": "https://bithumb.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:26.914675257Z" }, "updatedAt": "2026-11-04T20:02:57.989976217Z" } }, "answer": "Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bithumb Open API's 50.6 (D), and leads in 6 of 7 scored categories. Bithumb Open API leads on maintenance \u0026 community.", "b": { "slug": "coinbase-advanced-trade", "name": "Coinbase Advanced Trade API", "vendor": "Coinbase, Inc.", "vendorUrl": "https://docs.cdp.coinbase.com/advanced-trade/docs/welcome", "kind": "http-api", "category": "crypto-exchanges", "summary": "Coinbase's Advanced Trade API is the trading API of a Coinbase account, with REST, WebSocket feeds and a static sandbox for spot, US futures and, since October 2026, perpetuals on a Deribit-based gateway, authenticated by CDP API keys.", "url": "https://www.anchorterminal.com/tools/coinbase-advanced-trade", "markdownUrl": "https://www.anchorterminal.com/tools/coinbase-advanced-trade.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/coinbase-advanced-trade.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/coinbase-advanced-trade.json", "dns": "coinbase-advanced-trade.grade.anchorterminal.com", "repo": "https://github.com/coinbase/coinbase-advanced-py", "license": "Proprietary hosted service under the Coinbase User Agreement, which answered a bot check and wasn't read. The official Python SDK coinbase-advanced-py is on GitHub", "transports": [], "packages": [ { "registry": "pypi", "name": "coinbase-advanced-py" } ], "auth": "mixed", "authNotes": "CDP secret API key made in the CDP portal, with view, trade and transfer permissions, a portfolio restriction and an optional IP allowlist. Each request carries a JWT signed with ECDSA (ES256) that expires after 2 minutes, so a new token is minted per call. Ed25519 keys are not accepted by Coinbase App APIs. The OpenAPI spec also lists OAuth2 with wallet:* scopes for acting on other people's accounts. Keys are regenerated or disabled in the portal. Six public market endpoints need no key (https://docs.cdp.coinbase.com/coinbase-app/authentication-authorization/api-key-authentication.md, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Trades carry Advanced Trade maker and taker fees by 30-day volume tier; the fee page at coinbase.com/advanced-fees and help.coinbase.com both answered our reader with 403 on 3 November 2026, so the lowest tier's rates are unread. The sandbox and the public market endpoints need no account.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Advanced Trade endpoints in the OpenAPI spec or docs (checked 2026-11-03). Coinbase's account MCP server, listed as coinbase-mcp, pays x402 resources as a buyer; that is a separate surface.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.cdp.coinbase.com/advanced-trade/docs/welcome", "llmsTxt": "https://docs.cdp.coinbase.com/llms.txt", "openapi": "https://docs.cdp.coinbase.com/api-reference/advanced-trade-api/rest-api/advanced-trade-spec.yaml", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "official", "closed-source", "api-key", "oauth", "openapi", "llms-txt", "sandbox", "status-page", "python", "usage-priced", "no-card", "bug-bounty" ], "lastRelease": "2026-10-01", "graded": true, "anchor": { "graded": true, "score": 61.7, "grade": "C", "agentReady": false, "rank": 493, "ranked": true, "rankOf": 1349, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 57, "payments": 20, "reliability": 58, "schema": 80, "security": 68, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Advanced Trade has a public OpenAPI spec, keys limited to view, trade or transfer and to one portfolio, and a keyless static sandbox. No REST rate limit is published, the fee schedule, user agreement and country list sit behind a bot check, and an agent that wants an MCP route uses the separate coinbase-mcp listing.", "bestFor": "An agent trading a person's or a treasury's Coinbase account with its own key, where the person wants sandbox tests and portfolio scoping.", "strengths": [ "Public OpenAPI 3.1 and AsyncAPI specs with typed enums, plus llms.txt and a Markdown twin of every docs page", "CDP keys carry view, trade and transfer permissions, a portfolio restriction and an IP allowlist, and signed JWTs expire after 2 minutes", "Keyless sandbox with static responses and header-driven error simulation for accounts and orders", "Six public market data endpoints need no key, and most WebSocket channels are open without authentication", "Dated retirement of INTX endpoints with a read-only grace period, announced in the docs" ], "weaknesses": [ "No REST rate limit numbers found; the old rate-limits page answers 404 and only the WebSocket limit of 8 per second per IP is published", "The fee schedule, user agreement, privacy policy and supported-countries pages answered a bot check and were not read", "No FIX connectivity is documented for Advanced Trade", "The OpenAPI spec documents only a default error response, with no 4xx or 429 shapes", "security.txt expired on 1 June 2024 and no status component exists for the Global Derivatives gateway" ], "agentNotes": [ "Mint a fresh ES256 JWT for every request; tokens expire after 2 minutes and Ed25519 keys are rejected", "Send a unique client_order_id on every order and reuse it on retry so a dropped connection does not place a second order", "Develop against api-sandbox.coinbase.com first; its responses are static, so do not read prices or fills from it", "Use a key with view only, or trade without transfer, and restrict it to a portfolio funded for the agent", "For perpetuals call the Global Derivatives JSON-RPC gateway at drb.coinbase.com; the /intx/* endpoints are retired" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.7 } ], "editorialScores": { "ergonomics": 73, "maintenance": 57, "payments": 20, "reliability": 58, "schema": 80, "security": 68, "transparency": 42 }, "provenanceScore": 92, "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", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install coinbase-advanced-py", "http": "curl https://api.coinbase.com/api/v3/brokerage/market/products/BTC-USD/ticker?limit=1" }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/coinbase-advanced-trade" }, "sameCompany": [ "coinbase-mcp" ], "area": "payments", "provenance": { "legalEntity": "Coinbase, Inc.", "domain": "coinbase.com", "domainRegistered": "2011-07-02", "endpointOnVendorDomain": true, "terms": "https://www.coinbase.com/legal/user_agreement", "privacy": "https://www.coinbase.com/legal/privacy", "statusPage": "https://status.coinbase.com", "changelog": "https://docs.cdp.coinbase.com/get-started/changelog", "securityTxt": "expired", "checked": "2026-11-03", "notes": [ "The user agreement, privacy policy, fee schedule and help centre answered a bot check or 403 on 3 November 2026. The terms and privacy URLs are Coinbase's standard ones; Coinbase, Inc. is the entity named in the coinbase-cdp-agentkit and coinbase-mcp listings.", "Domain registration date per the RDAP read of 24 October 2026 for coinbase-mcp, not re-read.", "https://www.coinbase.com/.well-known/security.txt points to HackerOne and expired on 1 June 2024, re-read 3 November 2026.", "docs.cdp.coinbase.com/robots.txt disallows only /cdn-cgi/ and /_next/. help.coinbase.com answered 403 to robots.txt, so nothing on that host was requested further.", "The CDP changelog's newest entry is 23 October 2026; its only trading entries since August concern the agents MCP server (17 and 21 August)." ], "score": 92 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/coinbase-advanced-trade.json", "live": { "slug": "coinbase-advanced-trade", "vendorStatus": { "page": "https://status.coinbase.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-04T20:04:59.232209364Z" }, "versions": [ { "registry": "github", "name": "coinbase/coinbase-advanced-py", "version": "v1.8.4", "released": "2026-06-19", "seenAt": "2026-11-04T20:07:55.498790392Z" }, { "registry": "pypi", "name": "coinbase-advanced-py", "version": "1.8.4", "released": "2026-06-19", "seenAt": "2026-11-04T20:07:55.303074368Z" } ], "githubStars": 364, "pypiWeekly": 31348, "securityTxt": { "url": "https://coinbase.com/.well-known/security.txt", "state": "valid", "expires": "2024-06-01T00:00:00z", "checkedAt": "2026-11-04T15:52:53.816413711Z" }, "updatedAt": "2026-11-04T20:07:55.498790392Z" } }, "edges": [ { "by": 24, "category": "reliability", "leads": "coinbase-advanced-trade", "name": "Reliability", "reasons": { "a": "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.", "b": "Read with the hosted lines. status.coinbase.com is a Statuspage site with Coinbase Advanced Trade, API, US Derivatives and International Derivatives components (20). The incidents feed we could read runs from 16 September to 3 November 2026. In it Advanced Trade was degraded for 25 minutes on 21 September, the website had a 3-minute major on 14 October, converts were down 1 hour 4 minutes on 26 October, and no incident named the API; 5 August to 15 September was beyond the feed, so minor only for the seven weeks read (15 of 30). No REST rate limit with numbers was found; the older rate-limits page answers 404 and llms.txt lists none, while the WebSocket page gives 8 connections and 8 unauthenticated messages per second per IP (5 of 15). Orders take a client_order_id, but no 429 or Retry-After guidance was found for Advanced Trade (8 of 15). No SLA (0). REST and WebSocket are generally available; the Global Derivatives gateway is a month old and not marked beta (10). 20 + 15 + 5 + 8 + 0 + 10 = 58." }, "scores": { "a": 34, "b": 58 } }, { "by": 20, "category": "transparency", "leads": "coinbase-advanced-trade", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The editorial half. A closed service whose user agreement answered a bot check; the OpenAPI spec is public and the Python SDK is open on GitHub (12 of 30). Privacy facts per the coinbase-cdp-agentkit check of 1 October 2026 (Coinbase, Inc., processing countries, retention tied to need without numbers), not re-read (10 of 30). INTX endpoints retired on 1 October 2026 with a dated notice and a read-only grace period (12 of 20). Processing countries and provider categories per the same earlier check, no subprocessor list (8 of 20). 12 + 10 + 12 + 8 = 42." }, "scores": { "a": 47, "b": 67 } }, { "by": 16, "category": "schema", "leads": "coinbase-advanced-trade", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "Public OpenAPI 3.1 spec (45 paths, 51 operations) and an AsyncAPI document (25). llms.txt and a Markdown twin of every docs page (10). Every operation has a summary and description, some one line, several with multi-sentence guidance for equities (14 of 20). Enums on product_type, granularity, order_status, time_in_forces, order_types, order_side and sort_by, with defaults (13 of 15). Examples in the docs and the sandbox's simulated errors, but the spec documents only a default error referencing grpc.gateway.runtime.Error, with no 4xx or 429 shapes (8 of 15). Paths carry /api/v3, the CDP changelog is dated, and the INTX retirement was announced with a date, but the spec's info.version is 0.1 and the October gateway change has no changelog entry (10 of 15). 25 + 10 + 14 + 13 + 8 + 10 = 80." }, "scores": { "a": 64, "b": 80 } }, { "by": 12, "category": "maintenance", "leads": "bithumb", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed hosted service. The last change to the API itself is the Global Derivatives gateway and INTX retirement of 1 October 2026, 33 days before this check; the Python SDK's v2.0.0rc1 is from 30 September (20 of 30). Dated changes in 90 days are the 1 October migration and the agents entries of 17 and 21 August, which run through Advanced Trade (12 of 20). A public changelog and a CDP Discord; SDK issues not read (8 of 15). Official Python SDK current, the rest samples (12 of 15). SDK CI not read (5 of 10). 20 + 12 + 8 + 12 + 5 = 57." }, "scores": { "a": 69, "b": 57 } }, { "by": 8, "category": "security", "leads": "coinbase-advanced-trade", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "CDP keys with view, trade and transfer permissions, a portfolio restriction, an optional IP allowlist, revocation in the portal, ES256 JWTs that expire after 2 minutes, and OAuth2 with wallet:* scopes for other people's accounts; no key expiry (28 of 30). View-only keys and portfolio scoping limit an agent, and transfer is a separate permission, but no withdrawal address allow-list for API keys and no confirmation step were found (14 of 20). The API returns no untrusted content (10). key_permissions reports a key's scope and account activity shows in the app, but no per-call log was found (6 of 15). HackerOne bug bounty named in a security.txt that expired on 1 June 2024; certifications unread behind a bot check (10 of 20). 28 + 14 + 10 + 6 + 10 = 68." }, "scores": { "a": 60, "b": 68 } }, { "by": 6, "category": "ergonomics", "leads": "coinbase-advanced-trade", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Product lists filter by product_type and product_ids with limit and offset, candles take a granularity, but fields cannot be selected and the docs warn that product lists run to hundreds of entries (15 of 25). Cursor pagination with limit on orders and fills, filters by status, product and time (16 of 20). Error codes such as INSUFFICIENT_FUND, ORDER_NOT_FOUND and PERMISSION_DENIED are documented and can be simulated in the sandbox, though the spec gives no shapes (14 of 20). client_order_id on every order; no idempotency key on other writes (16 of 20). Few required fields, an official Python SDK and sample SDKs in three languages, but each request needs a freshly signed JWT (12 of 15). 15 + 16 + 14 + 16 + 12 = 73." }, "scores": { "a": 67, "b": 73 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Bithumb Co., Ltd.", "b": "Coinbase, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "b": "", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary hosted service under the Coinbase User Agreement, which answered a bot check and wasn't read. The official Python SDK coinbase-advanced-py is on GitHub", "name": "Licence" }, { "a": "41", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-13", "b": "2026-10-01", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-05-27", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "6 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bithumb Open API's 50.6 (D), and leads in 6 of 7 scored categories. Bithumb Open API leads on maintenance \u0026 community.", "question": "Which is better for AI agents, Bithumb Open API or Coinbase Advanced Trade API?" }, { "answer": "Bithumb Open API needs an API key. Coinbase Advanced Trade API takes an API key or an OAuth sign-in.", "question": "Do Bithumb Open API and Coinbase Advanced Trade API need an API key?" }, { "answer": "Bithumb Open API runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Coinbase Advanced Trade API.", "question": "Can an agent call Bithumb Open API and Coinbase Advanced Trade API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Maintenance \u0026 community, 69 against 57" ], "also": [ "Runs on your own machine" ], "goodFor": "KRW-market trading for agents acting for a verified Korean account, with a vendor-built MCP server, CLI and skills.", "slug": "bithumb", "watchFor": "No sandbox or testnet; every order uses real funds" }, { "aheadOn": [ "Reliability, 58 against 34", "Schema \u0026 documentation, 80 against 64", "Agent ergonomics, 73 against 67", "Security \u0026 auth, 68 against 60", "Payments \u0026 pricing, 20 against 15", "Transparency \u0026 trust, 67 against 47" ], "also": [ "Free to start without a card" ], "goodFor": "An agent trading a person's or a treasury's Coinbase account with its own key, where the person wants sandbox tests and portfolio scoping.", "slug": "coinbase-advanced-trade", "watchFor": "No REST rate limit numbers found; the old rate-limits page answers 404 and only the WebSocket limit of 8 per second per IP is published" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.json", "title": "Bitfinex API vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bithumb" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.json", "title": "Bitfinex API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-bithumb.json", "title": "Bitget vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/bitget-vs-bithumb" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade.json", "title": "Bitget vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.json", "title": "Bithumb Open API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-bybit.json", "title": "Bithumb Open API vs Bybit", "url": "https://www.anchorterminal.com/compare/bithumb-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.json", "title": "Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.json", "title": "Bithumb Open API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-deribit.json", "title": "Bithumb Open API vs Deribit", "url": "https://www.anchorterminal.com/compare/bithumb-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-dydx.json", "title": "Bithumb Open API vs dYdX", "url": "https://www.anchorterminal.com/compare/bithumb-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-gate-io.json", "title": "Bithumb Open API vs Gate", "url": "https://www.anchorterminal.com/compare/bithumb-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.json", "title": "Bithumb Open API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-htx.json", "title": "Bithumb Open API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.json", "title": "Bithumb Open API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-kraken.json", "title": "Bithumb Open API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-kucoin.json", "title": "Bithumb Open API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bithumb-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-mexc.json", "title": "Bithumb Open API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-okx.json", "title": "Bithumb Open API vs OKX API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-uniswap.json", "title": "Bithumb Open API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-uniswap" }, { "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/bitstamp-vs-coinbase-advanced-trade.json", "title": "Bitstamp API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.json", "title": "Bybit vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bithumb.json", "title": "Binance API vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-bithumb" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.json", "title": "Binance API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp.json", "title": "Coinbase Advanced Trade API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange.json", "title": "Coinbase Advanced Trade API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit.json", "title": "Coinbase Advanced Trade API vs Deribit", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gate-io.json", "title": "Coinbase Advanced Trade API vs Gate", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange.json", "title": "Coinbase Advanced Trade API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.json", "title": "Coinbase Advanced Trade API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid.json", "title": "Coinbase Advanced Trade API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken.json", "title": "Coinbase Advanced Trade API vs Kraken API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin.json", "title": "Coinbase Advanced Trade API vs KuCoin", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc.json", "title": "Coinbase Advanced Trade API vs MEXC API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx.json", "title": "Coinbase Advanced Trade API vs OKX API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap.json", "title": "Coinbase Advanced Trade API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap" }, { "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-advanced-trade-vs-dydx.json", "title": "Coinbase Advanced Trade API vs dYdX", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx" } ], "panel": null, "scores": [ { "bithumb": 34, "by": 24, "coinbase-advanced-trade": 58, "edge": "coinbase-advanced-trade", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bithumb": 64, "by": 16, "coinbase-advanced-trade": 80, "edge": "coinbase-advanced-trade", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bithumb": 67, "by": 6, "coinbase-advanced-trade": 73, "edge": "coinbase-advanced-trade", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bithumb": 60, "by": 8, "coinbase-advanced-trade": 68, "edge": "coinbase-advanced-trade", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bithumb": 15, "by": 5, "coinbase-advanced-trade": 20, "edge": "coinbase-advanced-trade", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bithumb": 69, "by": 12, "coinbase-advanced-trade": 57, "edge": "bithumb", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bithumb": 47, "by": 20, "coinbase-advanced-trade": 67, "edge": "coinbase-advanced-trade", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bithumb Open API's 50.6 (D), and leads in 6 of 7 scored categories. Bithumb Open API leads on maintenance \u0026 community. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "bithumb": "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.", "coinbase-advanced-trade": "Advanced Trade has a public OpenAPI spec, keys limited to view, trade or transfer and to one portfolio, and a keyless static sandbox. No REST rate limit is published, the fee schedule, user agreement and country list sit behind a bot check, and an agent that wants an MCP route uses the separate coinbase-mcp listing." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade", "json": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.min.md" }, "markdown": "Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bithumb Open API's 50.6 (D), and leads in 6 of 7 scored categories. Bithumb Open API leads on maintenance \u0026 community. Both do exchange market data.\n\n- Bithumb Open API: grade D, 50.6/100, rank #999 of 1349. Markdown https://www.anchorterminal.com/tools/bithumb.md · JSON https://www.anchorterminal.com/api/v1/tools/bithumb.json\n- Coinbase Advanced Trade API: grade C, 61.7/100, rank #493 of 1349. Markdown https://www.anchorterminal.com/tools/coinbase-advanced-trade.md · JSON https://www.anchorterminal.com/api/v1/tools/coinbase-advanced-trade.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Which one, for what\n\n### Bithumb Open API (D)\n\nGood for: KRW-market trading for agents acting for a verified Korean account, with a vendor-built MCP server, CLI and skills.\n\nAhead on:\n- Maintenance \u0026 community, 69 against 57\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No sandbox or testnet; every order uses real funds\n\n### Coinbase Advanced Trade API (C)\n\nGood for: An agent trading a person's or a treasury's Coinbase account with its own key, where the person wants sandbox tests and portfolio scoping.\n\nAhead on:\n- Reliability, 58 against 34\n- Schema \u0026 documentation, 80 against 64\n- Agent ergonomics, 73 against 67\n- Security \u0026 auth, 68 against 60\n- Payments \u0026 pricing, 20 against 15\n- Transparency \u0026 trust, 67 against 47\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No REST rate limit numbers found; the old rate-limits page answers 404 and only the WebSocket limit of 8 per second per IP is published\n\n\n## Why the edge\n\n### Reliability: Coinbase Advanced Trade API +24\n\n- 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.\n- Coinbase Advanced Trade API (58): Read with the hosted lines. status.coinbase.com is a Statuspage site with Coinbase Advanced Trade, API, US Derivatives and International Derivatives components (20). The incidents feed we could read runs from 16 September to 3 November 2026. In it Advanced Trade was degraded for 25 minutes on 21 September, the website had a 3-minute major on 14 October, converts were down 1 hour 4 minutes on 26 October, and no incident named the API; 5 August to 15 September was beyond the feed, so minor only for the seven weeks read (15 of 30). No REST rate limit with numbers was found; the older rate-limits page answers 404 and llms.txt lists none, while the WebSocket page gives 8 connections and 8 unauthenticated messages per second per IP (5 of 15). Orders take a client_order_id, but no 429 or Retry-After guidance was found for Advanced Trade (8 of 15). No SLA (0). REST and WebSocket are generally available; the Global Derivatives gateway is a month old and not marked beta (10). 20 + 15 + 5 + 8 + 0 + 10 = 58.\n\n### Transparency \u0026 trust: Coinbase Advanced Trade API +20\n\n- 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.\n- Coinbase Advanced Trade API (67): The editorial half. A closed service whose user agreement answered a bot check; the OpenAPI spec is public and the Python SDK is open on GitHub (12 of 30). Privacy facts per the coinbase-cdp-agentkit check of 1 October 2026 (Coinbase, Inc., processing countries, retention tied to need without numbers), not re-read (10 of 30). INTX endpoints retired on 1 October 2026 with a dated notice and a read-only grace period (12 of 20). Processing countries and provider categories per the same earlier check, no subprocessor list (8 of 20). 12 + 10 + 12 + 8 = 42.\n\n### Schema \u0026 documentation: Coinbase Advanced Trade API +16\n\n- 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.\n- Coinbase Advanced Trade API (80): Public OpenAPI 3.1 spec (45 paths, 51 operations) and an AsyncAPI document (25). llms.txt and a Markdown twin of every docs page (10). Every operation has a summary and description, some one line, several with multi-sentence guidance for equities (14 of 20). Enums on product_type, granularity, order_status, time_in_forces, order_types, order_side and sort_by, with defaults (13 of 15). Examples in the docs and the sandbox's simulated errors, but the spec documents only a default error referencing grpc.gateway.runtime.Error, with no 4xx or 429 shapes (8 of 15). Paths carry /api/v3, the CDP changelog is dated, and the INTX retirement was announced with a date, but the spec's info.version is 0.1 and the October gateway change has no changelog entry (10 of 15). 25 + 10 + 14 + 13 + 8 + 10 = 80.\n\n### Maintenance \u0026 community: Bithumb Open API +12\n\n- 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.\n- Coinbase Advanced Trade API (57): Read as a closed hosted service. The last change to the API itself is the Global Derivatives gateway and INTX retirement of 1 October 2026, 33 days before this check; the Python SDK's v2.0.0rc1 is from 30 September (20 of 30). Dated changes in 90 days are the 1 October migration and the agents entries of 17 and 21 August, which run through Advanced Trade (12 of 20). A public changelog and a CDP Discord; SDK issues not read (8 of 15). Official Python SDK current, the rest samples (12 of 15). SDK CI not read (5 of 10). 20 + 12 + 8 + 12 + 5 = 57.\n\n### Security \u0026 auth: Coinbase Advanced Trade API +8\n\n- Bithumb Open API (60): 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.\n- Coinbase Advanced Trade API (68): CDP keys with view, trade and transfer permissions, a portfolio restriction, an optional IP allowlist, revocation in the portal, ES256 JWTs that expire after 2 minutes, and OAuth2 with wallet:* scopes for other people's accounts; no key expiry (28 of 30). View-only keys and portfolio scoping limit an agent, and transfer is a separate permission, but no withdrawal address allow-list for API keys and no confirmation step were found (14 of 20). The API returns no untrusted content (10). key_permissions reports a key's scope and account activity shows in the app, but no per-call log was found (6 of 15). HackerOne bug bounty named in a security.txt that expired on 1 June 2024; certifications unread behind a bot check (10 of 20). 28 + 14 + 10 + 6 + 10 = 68.\n\n### Agent ergonomics: Coinbase Advanced Trade API +6\n\n- 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.\n- Coinbase Advanced Trade API (73): Product lists filter by product_type and product_ids with limit and offset, candles take a granularity, but fields cannot be selected and the docs warn that product lists run to hundreds of entries (15 of 25). Cursor pagination with limit on orders and fills, filters by status, product and time (16 of 20). Error codes such as INSUFFICIENT_FUND, ORDER_NOT_FOUND and PERMISSION_DENIED are documented and can be simulated in the sandbox, though the spec gives no shapes (14 of 20). client_order_id on every order; no idempotency key on other writes (16 of 20). Few required fields, an official Python SDK and sample SDKs in three languages, but each request needs a freshly signed JWT (12 of 15). 15 + 16 + 14 + 16 + 12 = 73.\n\n## Score by category\n\n| Category | Weight | Bithumb Open API | Coinbase Advanced Trade API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 34 | 58 | Coinbase Advanced Trade API +24 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 80 | Coinbase Advanced Trade API +16 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 73 | Coinbase Advanced Trade API +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 68 | Coinbase Advanced Trade API +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 20 | Coinbase Advanced Trade API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 57 | Bithumb Open API +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 47 | 67 | Coinbase Advanced Trade API +20 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.6 · D** | **61.7 · C** | |\n\n## Facts side by side\n\n| Fact | Bithumb Open API | Coinbase Advanced Trade API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bithumb Co., Ltd. | Coinbase, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary hosted service under the Coinbase User Agreement, which answered a bot check and wasn't read. The official Python SDK coinbase-advanced-py is on GitHub |\n| Tools exposed | 41 | none |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-13 | 2026-10-01 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | no document linked | 2026-05-27 |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 6 stars | none |\n\n## Verdicts\n\n**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.\n\n**Coinbase Advanced Trade API.** Advanced Trade has a public OpenAPI spec, keys limited to view, trade or transfer and to one portfolio, and a keyless static sandbox. No REST rate limit is published, the fee schedule, user agreement and country list sit behind a bot check, and an agent that wants an MCP route uses the separate coinbase-mcp listing.\n\n## Before you call either\n\n### Bithumb Open API\n\n1. 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\n2. 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\n3. Prefer the `bithumb` CLI for writes, as the skills do, and check `bithumb config show --json` for a read-only profile before any order\n4. 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\n5. 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\n\n### Coinbase Advanced Trade API\n\n1. Mint a fresh ES256 JWT for every request; tokens expire after 2 minutes and Ed25519 keys are rejected\n2. Send a unique client_order_id on every order and reuse it on retry so a dropped connection does not place a second order\n3. Develop against api-sandbox.coinbase.com first; its responses are static, so do not read prices or fills from it\n4. Use a key with view only, or trade without transfer, and restrict it to a portfolio funded for the agent\n5. For perpetuals call the Global Derivatives JSON-RPC gateway at drb.coinbase.com; the /intx/* endpoints are retired\n\n## Questions\n\n### Which is better for AI agents, Bithumb Open API or Coinbase Advanced Trade API?\n\nCoinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bithumb Open API's 50.6 (D), and leads in 6 of 7 scored categories. Bithumb Open API leads on maintenance \u0026 community.\n\n### Do Bithumb Open API and Coinbase Advanced Trade API need an API key?\n\nBithumb Open API needs an API key. Coinbase Advanced Trade API takes an API key or an OAuth sign-in.\n\n### Can an agent call Bithumb Open API and Coinbase Advanced Trade API without installing anything?\n\nBithumb Open API runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Coinbase Advanced Trade API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bithumb\", \"b\": \"coinbase-advanced-trade\"}`. From a terminal: `anchor compare bithumb coinbase-advanced-trade`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bithumb.json and https://www.anchorterminal.com/api/v1/tools/coinbase-advanced-trade.json\n\n## Other comparisons with Bithumb Open API or Coinbase Advanced Trade API\n\n- [Bitfinex API vs Bithumb Open API](https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.md)\n- [Bitfinex API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.md)\n- [Bitget vs Bithumb Open API](https://www.anchorterminal.com/compare/bitget-vs-bithumb.md)\n- [Bitget vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade.md)\n- [Bithumb Open API vs Bitstamp API](https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.md)\n- [Bithumb Open API vs Bybit](https://www.anchorterminal.com/compare/bithumb-vs-bybit.md)\n- [Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.md)\n- [Bithumb Open API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.md)\n- [Bithumb Open API vs Deribit](https://www.anchorterminal.com/compare/bithumb-vs-deribit.md)\n- [Bithumb Open API vs dYdX](https://www.anchorterminal.com/compare/bithumb-vs-dydx.md)\n- [Bithumb Open API vs Gate](https://www.anchorterminal.com/compare/bithumb-vs-gate-io.md)\n- [Bithumb Open API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.md)\n- [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.md)\n- [Bithumb Open API vs Hyperliquid](https://www.anchorterminal.com/compare/bithumb-vs-hyperliquid.md)\n- [Bithumb Open API vs Kraken API](https://www.anchorterminal.com/compare/bithumb-vs-kraken.md)\n- [Bithumb Open API vs KuCoin](https://www.anchorterminal.com/compare/bithumb-vs-kucoin.md)\n- [Bithumb Open API vs MEXC API](https://www.anchorterminal.com/compare/bithumb-vs-mexc.md)\n- [Bithumb Open API vs OKX API](https://www.anchorterminal.com/compare/bithumb-vs-okx.md)\n- [Bithumb Open API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bithumb-vs-uniswap.md)\n- [Bithumb Open API vs Upbit Open API](https://www.anchorterminal.com/compare/bithumb-vs-upbit.md)\n- [Bitstamp API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.md)\n- [Bybit vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.md)\n- [Binance API vs Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md)\n- [Binance API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.md)\n- [Coinbase Advanced Trade API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp.md)\n- [Coinbase Advanced Trade API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange.md)\n- [Coinbase Advanced Trade API vs Deribit](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit.md)\n- [Coinbase Advanced Trade API vs Gate](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gate-io.md)\n- [Coinbase Advanced Trade API vs Gemini Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange.md)\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md)\n- [Coinbase Advanced Trade API vs Hyperliquid](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid.md)\n- [Coinbase Advanced Trade API vs Kraken API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken.md)\n- [Coinbase Advanced Trade API vs KuCoin](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin.md)\n- [Coinbase Advanced Trade API vs MEXC API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc.md)\n- [Coinbase Advanced Trade API vs OKX API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx.md)\n- [Coinbase Advanced Trade API vs Uniswap Trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap.md)\n- [Coinbase Advanced Trade API vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.md)\n- [Coinbase Advanced Trade API vs dYdX](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx.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-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "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": "Bithumb Open API vs Coinbase Advanced Trade API", "url": "" } ], "description": "Coinbase Advanced Trade scores 61.7 (C) to Bithumb Open's 50.6 (D) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bithumb Open API D 50.6", "Coinbase Advanced Trade API C 61.7", "scores" ], "h1": "Bithumb Open API vs Coinbase Advanced Trade API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bithumb-vs-coinbase-advanced-trade", "published": "2026-10-01", "section": "tools", "title": "Bithumb Open vs Coinbase Advanced Trade for AI agents (2026)", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade" }, "tokens": { "markdown": 5350, "slim": 2830 }, "version": 1 }