Sign in

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

Gate vs Upbit Open API

Gate scores 56.4 (C) on agent readiness against Upbit Open API's 54.7 (C), and leads in 3 of 7 scored categories. Upbit Open API leads on maintenance & community and transparency & trust. Both do exchange market data.

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

GateGate · HTTP API C56.4/100#786 of 1349 Upbit Open APIDunamu Inc. · HTTP API C54.7/100#860 of 1349

Which one, for what

Gate C

Best for An agent trading spot, futures and earn products in a person's Gate account outside the 35 restricted locations, with a keyless MCP for research and an OAuth MCP or scoped key for trading.

Ahead on

  • Payments & pricing, 35 against 15

Also in its favour

  • A hosted endpoint, with nothing to install
  • Runs on your own machine

Watch for

No status page, incident history or SLA; the terms give no uptime guarantee and cap liability at three months of fees

Upbit Open API C

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

Ahead on

  • Maintenance & community, 83 against 77
  • Transparency & trust, 54 against 49

Watch for

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

Why the edge

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

Payments & pricing Gate +20

Gate 35

No machine payment protocol (0). The fee page's table loads after login; help centre and learn articles give the VIP 0 spot rates (15 of 20). Market data over REST and the public MCP needs no account and no card (20). A person registers, verifies identity and mints the key or approves the grant in a browser (0). 35.

Upbit Open API 15

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.

Maintenance & community Upbit Open API +6

Gate 77

Read as a hosted service with open-source MCP packages. The API changelog's latest entry is 2 November 2026 and gate-skills was pushed 3 November (30). 40 dated changelog entries since 5 August 2026 (20). developer@gate.com, a help centre and issue trackers on gate-mcp and gate-skills, replies not checked (12 of 25). In the official MCP registry under io.github.gateio-dev, a GitHub namespace rather than gate.com, and official SDKs current (10 of 15). The local package has a publish workflow and no test workflow in CI, and its last tag is 16 April 2026 (5 of 10). 77.

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.

Transparency & trust Upbit Open API +5

Gate 49

The editorial half. A closed hosted service with a clear user agreement that names no company; the MCP packages are MIT (12 of 30). The privacy policy names a DPO address and categories of recipients, with no retention numbers and no named subprocessors (12 of 30). The changelog records breaking changes such as the amend endpoint path move of 16 October 2026 with no notice period or policy (8 of 20). Transfers outside the user's jurisdiction are disclosed with no locations or provider names (5 of 20). 37.

Upbit Open API 54

The editorial half. A closed service whose user and Open API terms could not be fetched under upbit.com's robots.txt, and whose SDK licence page calls the SDK material not open source while the repositories carry Apache-2.0 (8 of 30). The developer centre's privacy policy names Dunamu Inc., gives retention periods and names Zendesk in Japan; the main privacy policy was not read (14 of 30). Notices with effective dates, including the path-format change and the deprecated Remaining-Req min field (12 of 20). Zendesk and Google Analytics named with a location for the developer centre only (8 of 20). 8 + 14 + 12 + 8 = 42.

Score by category

CategoryWeight this runGateUpbit Open APIEdge
Reliability16%204242even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27066Gate +4
Agent ergonomics13%16.26670Upbit Open API +4
Security & auth14%17.56059Gate +1
Payments & pricing10%12.53515Gate +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87783Upbit Open API +6
Transparency & trust7%8.84954Upbit Open API +5
Negative events≤1500
TotalC 56.4/100C 54.7/100

Facts side by side

FactGateUpbit Open API
KindHTTP APIHTTP API
VendorGateDunamu Inc.
Hosted endpointhttps://api.gatemcp.ai/mcpno (local only)
TransportsStreamable HTTP, stdio
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
Tools exposed580
Read-only variant documentedyesno
llms.txtnoyes
MCP registryio.github.gateio-dev/gate-mcpnot listed
Last release2026-11-022026-10-20
Terms last updated2026-07-22no document linked
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularity44 stars91 stars

Verdicts

Gate

Gate runs official hosted MCP servers with keyless market data and OAuth-scoped trading, a local stdio server with a read-only switch, per-endpoint rate limits with headers and a futures testnet. There is no status page, SLA or OpenAPI file, the fee table needs a login, the MCP host is a separate domain, and the terms name no company.

Upbit Open API

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

Before you call either

Gate

  1. Start on https://api.gatemcp.ai/mcp for prices and order books with no credential; switch to /mcp/exchange only when the person has approved the OAuth grant with the narrowest scopes
  2. For a key-based route, create a key on a dedicated sub-account with read-only on every group but the one the task needs, withdrawal disabled and an IP allow-list; changes take up to 5 minutes
  3. Put a unique text value starting with t- on every spot order and reuse it on the retry; read the order back before placing again
  4. Read X-Gate-RateLimit-Requests-Remain and stop at zero; spot order placement is capped at 10 a second and withdrawals at 1 per 3 seconds
  5. Rehearse futures logic on api-testnet.gateapi.io with TestNet keys; there is no spot testnet

Upbit Open API

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

Questions

Which is better for AI agents, Gate or Upbit Open API?

Gate scores 56.4 (C) on agent readiness against Upbit Open API's 54.7 (C), and leads in 3 of 7 scored categories. Upbit Open API leads on maintenance & community and transparency & trust.

Do Gate and Upbit Open API need an API key?

Gate takes an API key or an OAuth sign-in. Upbit Open API needs an API key.

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

Gate has a hosted endpoint at https://api.gatemcp.ai/mcp. No hosted endpoint is listed for Upbit Open API.

Other comparisons with Gate or Upbit Open API

Machine-readable

For companies

Do agents find, use and choose your tools?

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

Get an auditSee a sample report