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

Bithumb Open API vs Coinbase Advanced Trade API

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 & community. Both do exchange market data.

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

Which one, for what

Bithumb Open API D

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

Ahead on

  • Maintenance & community, 69 against 57

Also in its favour

  • Runs on your own machine

Watch for

No sandbox or testnet; every order uses real funds

Coinbase Advanced Trade API C

Best 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.

Ahead on

  • Reliability, 58 against 34
  • Schema & documentation, 80 against 64
  • Agent ergonomics, 73 against 67
  • Security & auth, 68 against 60
  • Payments & pricing, 20 against 15
  • Transparency & trust, 67 against 47

Also in its favour

  • Free to start without a card

Watch 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

Why the edge

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

Reliability Coinbase Advanced Trade API +24

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.

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.

Transparency & trust Coinbase Advanced Trade API +20

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.

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.

Schema & documentation Coinbase Advanced Trade API +16

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.

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.

Maintenance & community Bithumb Open API +12

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.

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.

Security & auth Coinbase Advanced Trade API +8

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.

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.

Agent ergonomics Coinbase Advanced Trade API +6

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.

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.

Score by category

CategoryWeight this runBithumb Open APICoinbase Advanced Trade APIEdge
Reliability16%203458Coinbase Advanced Trade API +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26480Coinbase Advanced Trade API +16
Agent ergonomics13%16.26773Coinbase Advanced Trade API +6
Security & auth14%17.56068Coinbase Advanced Trade API +8
Payments & pricing10%12.51520Coinbase Advanced Trade API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86957Bithumb Open API +12
Transparency & trust7%8.84767Coinbase Advanced Trade API +20
Negative events≤1500
TotalD 50.6/100C 61.7/100

Facts side by side

FactBithumb Open APICoinbase Advanced Trade API
KindHTTP APIHTTP API
VendorBithumb Co., Ltd.Coinbase, Inc.
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicencenoneProprietary 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
Tools exposed41none
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-132026-10-01
Terms last updatedcouldn't be readcouldn't be read
Privacy policy last updatedno document linked2026-05-27
Customer content may train modelscouldn't be readcouldn't be read
Terms restrict automated accesscouldn't be readcouldn't be read
Terms restrict benchmarkingcouldn't be readcouldn't be read
Terms or service can change without noticecouldn't be readcouldn't be read
Arbitration or class-action waivercouldn't be readcouldn't be read
Popularity6 starsnone

Verdicts

Bithumb Open API

Bithumb runs an official local MCP server with 41 tools, module selection and a read-only flag, beside a CLI with per-profile read-only gating and six agent skills, over an API with scoped one-year keys and a mandatory IP list. There is no sandbox, no status page, no documented 429 behaviour, and the fees and terms couldn't be read.

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.

Before you call either

Bithumb Open API

  1. Ask for a key with asset and order inquiry plus order placement only, never withdrawals, with your IP registered; keys expire after one year and a wrong IP answers 401 NotAllowIP
  2. Start the server with --modules market,account,trade --read-only for analysis and drop --read-only only when the person asks to trade; deposit and withdraw modules stay off
  3. Prefer the bithumb CLI for writes, as the skills do, and check bithumb config show --json for a read-only profile before any order
  4. Keep the ticker's markets parameter at 200 or fewer, batch orders at 30 and cancels at 30 per request, and stay under 140 private calls a second per category
  5. Retry 422 order_not_ready and 500 server_error after a pause; there is no sandbox, so start with the smallest order the market allows

Coinbase Advanced Trade API

  1. Mint a fresh ES256 JWT for every request; tokens expire after 2 minutes and Ed25519 keys are rejected
  2. Send a unique client_order_id on every order and reuse it on retry so a dropped connection does not place a second order
  3. Develop against api-sandbox.coinbase.com first; its responses are static, so do not read prices or fills from it
  4. Use a key with view only, or trade without transfer, and restrict it to a portfolio funded for the agent
  5. For perpetuals call the Global Derivatives JSON-RPC gateway at drb.coinbase.com; the /intx/* endpoints are retired

Questions

Which is better for AI agents, Bithumb Open API or Coinbase Advanced Trade API?

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 & community.

Do Bithumb Open API and Coinbase Advanced Trade API need an API key?

Bithumb Open API needs an API key. Coinbase Advanced Trade API takes an API key or an OAuth sign-in.

Can an agent call Bithumb Open API and Coinbase Advanced Trade API without installing anything?

Bithumb Open API runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Coinbase Advanced Trade API.

Other comparisons with Bithumb Open API or Coinbase Advanced Trade API

Machine-readable

For companies

Do agents find, use and choose your tools?

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