{ "data": { "a": { "slug": "gate-io", "name": "Gate", "vendor": "Gate", "vendorUrl": "https://www.gate.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Gate is a centralised crypto exchange for spot, margin, futures, options, earn and tokenised stocks, reached through its REST and WebSocket API v4, official SDKs, a CLI, and hosted and local MCP servers under its Gate for AI programme.", "url": "https://www.anchorterminal.com/tools/gate-io", "markdownUrl": "https://www.anchorterminal.com/tools/gate-io.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/gate-io.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/gate-io.json", "dns": "gate-io.grade.anchorterminal.com", "repo": "https://github.com/gate/gate-mcp", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://api.gatemcp.ai/mcp", "packages": [ { "registry": "npm", "name": "gate-mcp" } ], "auth": "mixed", "authNotes": "The API v4 takes an API key and secret minted on the APIv4 Keys page after a browser sign-up, signed per request with HMAC-SHA512 in the KEY, Timestamp and SIGN headers, with a 60 second timestamp window. Each key carries a permission per product group (spot and margin, perpetual, delivery, wallet, withdrawal and others) set to disabled, read-only or read-write, an IP allow-list of up to 20 addresses, and changes take up to 5 minutes. The hosted MCP trading endpoint uses Gate OAuth 2 at www.gate.com/apiw/v2/mcp/oauth with scopes base, read, asset, spot_trade, futures_trade, earn, cfd and stock, revocable on the API management page; the public market-data endpoints need no credential; the local `gate-mcp` package takes GATE_API_KEY and GATE_API_SECRET (https://www.gate.com/docs/developers/apiv4/en/, https://api.gatemcp.ai/.well-known/oauth-protected-resource/mcp/exchange and https://www.gate.com/docs/developers/agent/en/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API and the MCP servers cost nothing; trades carry Gate's fees. The fee page shows its tier table only after login. Gate's help centre gives the VIP 0 spot taker rate as 0.1 per cent and its learn articles give 0.1 per cent maker and taker with GT payment lowering it to 0.09 per cent; VIP tiers run from 0 to 16. The VIP 0 futures rate was not readable (https://www.gate.com/help/trade/spot/41629 and https://www.gate.com/fee, checked 2026-11-03).", "priceSummary": "0.1% fee", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API v4 docs, the agent guide, the gate-mcp README or the fee pages (checked 2026-11-03).", "endpoints": [] }, "toolCount": 58, "popularity": { "githubStars": 44, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.gate.com/docs/developers/apiv4/en/", "registryName": "io.github.gateio-dev/gate-mcp", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "closed-source", "api-key", "oauth", "usage-priced", "sandbox", "no-status-page", "mcp", "remote-mcp", "mcp-registry", "official", "read-only-mode", "agent-skills", "cli", "python", "typescript", "go", "java", "php", "dotnet" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 56.4, "grade": "C", "agentReady": false, "rank": 786, "ranked": true, "rankOf": 1349, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 77, "payments": 35, "reliability": 42, "schema": 70, "security": 60, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Hosted MCP at api.gatemcp.ai split by purpose, 58 market-data tools with no credential and trading tools behind Gate OAuth 2 with eight scopes, in the official MCP registry", "API keys with a disabled, read-only or read-write setting per product group, a withdrawal group of its own and an IP allow-list of up to 20 addresses", "Per-endpoint rate limits with X-Gate-RateLimit-Limit, X-Gate-RateLimit-Requests-Remain and X-Gate-RateLimit-Reset-Timestamp headers and a labelled error body", "Futures TestNet at api-testnet.gateapi.io with its own keys, and the complete REST and WebSocket docs downloadable as Markdown", "Official SDKs in Python, Java, PHP, Go, C#, Node.js and JavaScript, a CLI with JSON output, and 40 dated changelog entries in the last 90 days" ], "weaknesses": [ "No status page, incident history or SLA; the terms give no uptime guarantee and cap liability at three months of fees", "The MCP endpoints live on gatemcp.ai, not gate.com, and the registry namespace is a GitHub organisation; the OAuth scopes in the metadata differ from the ones the docs describe", "The local MCP server sets no readOnlyHint or destructiveHint annotations, and the hosted server's annotations could not be read without a session", "The fee table loads only after login, and the docs disagree with themselves on keys per account (5 against 20) and tool counts", "Clause 1.3(h) of the user agreement bans automated activity through any channel Gate has not designated, and the agreement names no legal entity" ], "agentNotes": [ "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", "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", "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", "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", "Rehearse futures logic on api-testnet.gateapi.io with TestNet keys; there is no spot testnet" ], "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": 56.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 77, "payments": 35, "reliability": 42, "schema": 70, "security": 60, "transparency": 37 }, "provenanceScore": 60, "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": "npx -y gate-mcp", "http": "curl https://api.gateio.ws/api/v4/spot/tickers?currency_pair=BTC_USDT", "claudeCode": "claude mcp add gate-mcp --transport http https://api.gatemcp.ai/mcp", "config": { "mcpServers": { "gate-mcp": { "transport": "streamable-http", "url": "https://api.gatemcp.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/gate-io" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, VIP 0 taker", "unit": "pct", "usd": 0.1, "note": "maker 0.1 per cent per Gate's learn articles; 0.09 per cent paid in GT" } ], "provenance": { "legalEntity": "", "domain": "gate.com", "domainRegistered": "1996-03-29", "endpointOnVendorDomain": true, "terms": "https://www.gate.com/user-agreement", "privacy": "https://www.gate.com/privacy-policy", "statusPage": "", "changelog": "https://www.gate.com/docs/developers/apiv4/en/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The user agreement (last updated 22 July 2026) and the privacy policy name only Gate, under the laws of the Republic of Panama with ICC arbitration; no company name or registration number appears. The about page names Gate Technology Ltd for the Malta licence only.", "www.gate.com/robots.txt allows the docs, help, legal and about paths and disallows /post/, search results, referral URLs and a list of internal API paths; nothing under those paths was fetched. The /about path answered 403 and /about-us loaded.", "RDAP gives gate.com a registration date of 29 March 1996 (Amazon Registrar); the exchange moved from gate.io to gate.com and traces its origin to 2013.", "https://www.gate.com/.well-known/security.txt answers 404. No status page found; status.gate.com does not resolve and the docs link none.", "The API endpoint api.gateio.ws is Gate's own; the MCP endpoints are on api.gatemcp.ai, a separate domain whose OAuth metadata points back to www.gate.com. The changelog is the versioned section of the API v4 docs page." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/gate-io.json", "live": { "slug": "gate-io", "probe": { "target": "https://api.gatemcp.ai/mcp", "method": "get", "lastAt": "2026-11-04T20:05:02.725528016Z", "lastOk": true, "lastStatus": 200, "lastMs": 10308, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 10329, "p95ms24h": 10631, "samples24h": 48, "samples30d": 48, "days": [ { "date": "2026-11-04", "probes": 48, "ok": 48 } ] }, "versions": [ { "registry": "mcp-registry", "name": "io.github.gateio-dev/gate-mcp", "version": "1.0.0", "seenAt": "2026-11-04T17:11:44.552009456Z" } ], "securityTxt": { "url": "https://gate.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-04T15:53:27.737532632Z" }, "updatedAt": "2026-11-04T20:05:02.725528016Z" } }, "answer": "OKX API scores 64.3 (B) on agent readiness against Gate's 56.4 (C), and leads in 6 of 7 scored categories. Gate leads on payments \u0026 pricing.", "b": { "slug": "okx", "name": "OKX API", "vendor": "OKX", "vendorUrl": "https://www.okx.com/docs-v5/en/", "kind": "http-api", "category": "crypto-exchanges", "summary": "OKX's V5 API covers spot, margin, perpetual, futures and options trading, account and market data over REST and WebSocket, with demo trading on the same host and an open-source Agent Trade Kit whose okx-trade-mcp package is a local MCP server.", "url": "https://www.anchorterminal.com/tools/okx", "markdownUrl": "https://www.anchorterminal.com/tools/okx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/okx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/okx.json", "dns": "okx.grade.anchorterminal.com", "repo": "https://github.com/okx/agent-trade-kit", "license": "Proprietary hosted service under OKX's Terms of Service (29 October 2026) and API Agreement (28 July 2026). The Agent Trade Kit (MCP server, CLI and skills) is MIT", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@okx_ai/okx-trade-mcp" }, { "registry": "npm", "name": "@okx_ai/okx-trade-cli" }, { "registry": "pypi", "name": "python-okx" } ], "auth": "api-key", "authNotes": "API key, secret and passphrase made at okx.com/account/my-api, with HMAC-SHA256 signatures over a timestamp and the request. Permissions are Read, Trade and Withdraw, singly or combined; each key binds up to 20 IP addresses or ranges, and a Trade or Withdraw key with no IP binding expires after 14 days without use. Demo trading uses the same host with the header `x-simulated-trading` set to 1 and keys that do not expire. US and Australian users call us.okx.com and EEA users eea.okx.com. The MCP server reads the key from ~/.okx/config.toml, checks its permissions at startup and hides order tools when the key cannot trade (https://www.okx.com/docs-v5/en/, https://www.okx.com/docs-v5/agent_en/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Trades carry maker and taker fees by regular and VIP level; the fee page at okx.com/fees loads its table by script and the fee FAQ says the rates that apply are the ones shown while logged in, so the lowest tier's rates are unread. Public market data and demo trading need no funded account.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the V5 docs, the API agreement or the Agent Trade Kit (checked 2026-11-03).", "endpoints": [] }, "toolCount": 170, "popularity": { "githubStars": 499, "npmWeekly": 1839, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.okx.com/docs-v5/en/", "llmsTxt": "https://www.okx.com/llms.txt", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "official", "closed-source", "api-key", "mcp", "cli", "llms-txt", "sandbox", "typescript", "python", "usage-priced", "no-card", "mit" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 64.3, "grade": "B", "agentReady": false, "rank": 413, "ranked": true, "rankOf": 1349, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 81, "payments": 20, "reliability": 65, "schema": 73, "security": 68, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "OKX publishes per-endpoint rate limits, Read, Trade and Withdraw key permissions with IP binding, demo trading on the production host, and an MIT MCP server with 170 tools, a read-only flag and a permission check at startup. The fee table and privacy policy were not read, no OpenAPI file was found, and the news tools return third-party text.", "bestFor": "An agent trading spot, perpetuals, futures or options on a person's OKX account from a local machine, with demo trading to test first and grid or DCA bots through the kit.", "strengths": [ "Official local MCP server, MIT, with modules, --read-only, a demo profile, readOnlyHint annotations and a startup check that hides order tools when the key cannot trade", "Keys limited to Read, Trade or Withdraw, bound to up to 20 IPs, with unbound Trade and Withdraw keys expiring after 14 idle days", "Rate limits published per endpoint and per User ID, with sub-account and WebSocket limits in numbers", "Demo trading on the production hosts with one header, keys that do not expire, and a demo profile in the kit", "An API Agreement written for agents, naming prohibited tactics, minimum key scope and rate-limit circumvention" ], "weaknesses": [ "The fee table loads by script and the fee FAQ defers to the logged-in view, so maker and taker rates were not read", "No OpenAPI file was found in the docs; the machine-readable contract is the kit's tool definitions", "The status page lists incidents without component history, and its newest entry is from March 2024", "The news and smart money tools return third-party text with no documented guidance on treating it as untrusted", "Trade tools in the kit carry destructiveHint false, and the npm package runs a postinstall script" ], "agentNotes": [ "Start okx-trade-mcp with --profile demo first, then --read-only on a live key; load only the modules the task needs", "Use a sub-account key with Read and Trade only, bound to the agent's IP; an unbound Trade key expires after 14 idle days", "Stay under 60 place-order requests per 2 seconds per instrument and at most 3 amendments in flight per order; 50011 means the limit was hit", "Send a clOrdId on every order and use the structured error block (code, message, endpoint) to diagnose with read-only tools before retrying", "Call us.okx.com or eea.okx.com for US, Australian and EEA accounts; openapi.okx.com does not serve those regions" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.3 } ], "editorialScores": { "ergonomics": 77, "maintenance": 81, "payments": 20, "reliability": 65, "schema": 73, "security": 68, "transparency": 38 }, "provenanceScore": 85, "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 @okx_ai/okx-trade-mcp @okx_ai/okx-trade-cli", "http": "curl https://www.okx.com/api/v5/market/ticker?instId=BTC-USDT", "config": { "mcpServers": { "okx-demo": { "args": [ "-y", "@okx_ai/okx-trade-mcp", "--profile", "demo" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/okx" }, "area": "payments", "provenance": { "legalEntity": "Aux Cayes FinTech Co. Ltd.", "domain": "okx.com", "domainRegistered": "2001-07-03", "endpointOnVendorDomain": true, "terms": "https://www.okx.com/help/terms-of-service", "privacy": "https://www.okx.com/help/privacy-policy", "statusPage": "https://www.okx.com/status", "changelog": "https://www.okx.com/docs-v5/log_en/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The Terms of Service (last updated 29 October 2026) name Aux Cayes FinTech Co. Ltd. for all users not served by a regional OKX entity; the page metadata of the API Agreement also lists it as publisher. The governing-law clause sat past the part of the page we read. The privacy policy URL is OKX's help-centre page and was not read.", "RDAP gives okx.com a registration date of 3 July 2001, long before OKX took the name in 2022.", "https://www.okx.com/.well-known/security.txt answers 404; the Agent Trade Kit's SECURITY.md names security@okx.com.", "www.okx.com/robots.txt allows the docs, help and status pages read and /llms.txt, and disallows account, KYC and other private paths.", "okx.com/status is OKX's own page with issue descriptions and maintenance notices in UTC+8, no component history and no feed found." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/okx.json", "live": { "slug": "okx", "vendorStatus": { "page": "https://www.okx.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:32:13.2375881Z" }, "securityTxt": { "url": "https://okx.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:49.77403161Z" }, "updatedAt": "2026-11-04T15:53:49.77403161Z" } }, "edges": [ { "by": 23, "category": "reliability", "leads": "okx", "name": "Reliability", "reasons": { "a": "Graded with the hosted lines on the API v4 at api.gateio.ws with the hosted MCP beside it. No status page found (status.gate.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per endpoint group with numbers and fill-ratio rules (15). Every response carries X-Gate-RateLimit-Limit, X-Gate-RateLimit-Requests-Remain and X-Gate-RateLimit-Reset-Timestamp, 429 answers with the label TOO_FAST, and spot orders take a user `text` identifier, but no retry or idempotency guidance is written down (12 of 15). No SLA (0). API v4 and the MCP endpoints are production surfaces (10). 42.", "b": "Read with the hosted lines on the V5 REST API. okx.com/status is OKX's own page with issue descriptions, maintenance notices and deposit and withdrawal status, but no component history or feed (10 of 20). It lists no incident between 5 August and 3 November 2026; its newest entry is from March 2024, and whether every incident reaches the page cannot be told, so read as clean with a doubt (20 of 30). Rate limits per endpoint, per User ID and per sub-account with numbers, and WebSocket limits (15). Error 50011 on a limit, a clOrdId on orders and a cap of 3 amendments in flight, but no Retry-After or backoff guidance found (10 of 15). No SLA (0). Generally available (10). 10 + 20 + 15 + 10 + 0 + 10 = 65." }, "scores": { "a": 42, "b": 65 } }, { "by": 15, "category": "payments", "leads": "gate-io", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No machine payment protocol (0). The fee table loads by script and the fee FAQ defers to the logged-in view, so no rate was read (0 of 20, unchecked). Public market data and demo trading need no funded account or card (20). A person signs up, verifies and mints a key (0). 0 + 0 + 20 + 0 = 20." }, "scores": { "a": 35, "b": 20 } }, { "by": 13, "category": "transparency", "leads": "okx", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The editorial half. A closed service with terms that name the contracting entities by region and an API Agreement for agents; the kit is MIT (17 of 30). The privacy policy was not read (5 of 30). The changelog dates sunsets and labels breaking changes, such as port 8443 on 31 October and 16 November 2026 (16 of 20). No subprocessor or data-location statement read; the MCP server is local and its npm package runs a postinstall script whose purpose we did not trace (0 of 20). 17 + 5 + 16 + 0 = 38." }, "scores": { "a": 49, "b": 62 } }, { "by": 11, "category": "ergonomics", "leads": "okx", "name": "Agent ergonomics", "reasons": { "a": "Read for the API with the hosted MCP beside it. The MCP is split by endpoint (58 public tools on /mcp, 400 or more on /mcp/exchange, smaller info and news servers) and the local package filters by module and read-only flag, which stands in for toolsets (5 of 25 for the trading server, 10 added back). Pagination by page and limit, from and to timestamps, status filters (15 of 20). Error labels such as INVALID_SIGNATURE, REQUEST_EXPIRED, IP_FORBIDDEN and READ_ONLY name the recovery (15 of 20). The `text` order identifier makes retries safe; the local server's source sets no readOnlyHint or destructiveHint and the hosted annotations are unread (8 of 20). Three required fields on a spot order, SDKs in seven languages and a CLI (13 of 15). 66.", "b": "limit parameters on books, candles and history, and in the kit --modules and --read-only narrow 170 tools to the three default modules; no field selection (17 of 25). after, before and limit cursors on history endpoints (18 of 20). Numeric codes with messages, such as 51020 for an invalid quantity, and the kit returns a structured error block with code, message and endpoint (17 of 20). clOrdId on orders, batch endpoints and a cap of 3 amendments in flight; the kit sets readOnlyHint on query tools but destructiveHint false on order tools and has no idempotency key (13 of 20). python-okx, the CLI and a demo profile, with passphrase and HMAC signing on every private call (12 of 15). 17 + 18 + 17 + 13 + 12 = 77." }, "scores": { "a": 66, "b": 77 } }, { "by": 8, "category": "security", "leads": "okx", "name": "Security \u0026 auth", "reasons": { "a": "Gate OAuth 2 for the hosted trading MCP with eight scopes per the protected-resource metadata and revocation on the API management page, and API keys with disabled, read-only or read-write per product group, a separate withdrawal group and an IP allow-list of 20 addresses (30). A read-only key and a GATE_READONLY switch exist, and the guide says fund-moving actions need the person's confirmation in the client, with no server-side cap documented (15 of 20). The news and info servers return third-party content with no guidance on treating it as untrusted (5 of 15). Key changes and OAuth grants are visible on the API management page; no per-call log found (5 of 15). No security.txt, no disclosure policy or bounty on a page we read, a proof-of-reserves repository (5 of 20). 60.", "b": "Key, secret and passphrase with Read, Trade and Withdraw permissions, up to 20 bound IPs, revocation in the account, and unbound Trade or Withdraw keys that expire after 14 idle days; no OAuth (28 of 30). Read-only keys, sub-account keys, demo trading, the kit's --read-only flag and its startup check that hides order tools when the key cannot trade, and an API Agreement requiring minimum scope; no confirmation step in the kit (18 of 20). The news and smartmoney modules return third-party text and the docs read give no guidance on treating it as untrusted (5 of 15). An account audit log tool in the kit and usage records for unbound keys in the Security Center, no per-call log (9 of 15). No security.txt; SECURITY.md with security@okx.com and GitHub private advisories; certifications and a bounty not read (8 of 20). 28 + 18 + 5 + 9 + 8 = 68." }, "scores": { "a": 60, "b": 68 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Gate", "b": "OKX", "name": "Vendor" }, { "a": "https://api.gatemcp.ai/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, stdio", "b": "stdio", "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": "none", "b": "Proprietary hosted service under OKX's Terms of Service (29 October 2026) and API Agreement (28 July 2026). The Agent Trade Kit (MCP server, CLI and skills) is MIT", "name": "Licence" }, { "a": "58", "b": "170", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "io.github.gateio-dev/gate-mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-11-02", "b": "2026-10-28", "name": "Last release" }, { "a": "2026-07-22", "b": "2026-10-29", "name": "Terms last updated" }, { "a": "no date given", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "44 stars", "b": "499 stars, 1.8k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "OKX API scores 64.3 (B) on agent readiness against Gate's 56.4 (C), and leads in 6 of 7 scored categories. Gate leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Gate or OKX API?" }, { "answer": "Gate takes an API key or an OAuth sign-in. OKX API needs an API key.", "question": "Do Gate and OKX API need an API key?" }, { "answer": "Gate has a hosted endpoint at https://api.gatemcp.ai/mcp. OKX API runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Gate and OKX API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 35 against 20" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "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.", "slug": "gate-io", "watchFor": "No status page, incident history or SLA; the terms give no uptime guarantee and cap liability at three months of fees" }, { "aheadOn": [ "Reliability, 65 against 42", "Agent ergonomics, 77 against 66", "Security \u0026 auth, 68 against 60", "Transparency \u0026 trust, 62 against 49" ], "also": [ "Free to start without a card" ], "goodFor": "An agent trading spot, perpetuals, futures or options on a person's OKX account from a local machine, with demo trading to test first and grid or DCA bots through the kit.", "slug": "okx", "watchFor": "The fee table loads by script and the fee FAQ defers to the logged-in view, so maker and taker rates were not read" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.json", "title": "Bitfinex API vs Gate", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-okx.json", "title": "Bitfinex API vs OKX API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-gate-io.json", "title": "Bitget vs Gate", "url": "https://www.anchorterminal.com/compare/bitget-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-okx.json", "title": "Bitget vs OKX API", "url": "https://www.anchorterminal.com/compare/bitget-vs-okx" }, { "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-okx.json", "title": "Bithumb Open API vs OKX API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.json", "title": "Bitstamp API vs Gate", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-okx.json", "title": "Bitstamp API vs OKX API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-gate-io.json", "title": "Bybit vs Gate", "url": "https://www.anchorterminal.com/compare/bybit-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-okx.json", "title": "Bybit vs OKX API", "url": "https://www.anchorterminal.com/compare/bybit-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io.json", "title": "Crypto.com Exchange API vs Gate", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx.json", "title": "Crypto.com Exchange API vs OKX API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange.json", "title": "Gate vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-htx.json", "title": "Gate vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid.json", "title": "Gate vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-kraken.json", "title": "Gate vs Kraken API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-kucoin.json", "title": "Gate vs KuCoin", "url": "https://www.anchorterminal.com/compare/gate-io-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-mexc.json", "title": "Gate vs MEXC API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-uniswap.json", "title": "Gate vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-uniswap" }, { "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-okx.json", "title": "Gemini Exchange API vs OKX API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-okx.json", "title": "HTX trading API vs OKX API", "url": "https://www.anchorterminal.com/compare/htx-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-okx.json", "title": "KuCoin vs OKX API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-okx.json", "title": "MEXC API vs OKX API", "url": "https://www.anchorterminal.com/compare/mexc-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-gate-io.json", "title": "Binance API vs Gate", "url": "https://www.anchorterminal.com/compare/binance-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-okx.json", "title": "Binance API vs OKX API", "url": "https://www.anchorterminal.com/compare/binance-vs-okx" }, { "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-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-mcp-vs-gate-io.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Gate", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-okx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs OKX API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-okx.json", "title": "Kraken API vs OKX API", "url": "https://www.anchorterminal.com/compare/kraken-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/okx-vs-uniswap.json", "title": "OKX API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/okx-vs-uniswap" }, { "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/deribit-vs-gate-io.json", "title": "Deribit vs Gate", "url": "https://www.anchorterminal.com/compare/deribit-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-okx.json", "title": "Deribit vs OKX API", "url": "https://www.anchorterminal.com/compare/deribit-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-gate-io.json", "title": "dYdX vs Gate", "url": "https://www.anchorterminal.com/compare/dydx-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-okx.json", "title": "dYdX vs OKX API", "url": "https://www.anchorterminal.com/compare/dydx-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-okx.json", "title": "Hyperliquid vs OKX API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-okx" } ], "panel": null, "scores": [ { "by": 23, "edge": "okx", "gate-io": 42, "key": "reliability", "name": "Reliability", "okx": 65, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 3, "edge": "okx", "gate-io": 70, "key": "schema", "name": "Schema \u0026 documentation", "okx": 73, "weight": 13 }, { "by": 11, "edge": "okx", "gate-io": 66, "key": "ergonomics", "name": "Agent ergonomics", "okx": 77, "weight": 13 }, { "by": 8, "edge": "okx", "gate-io": 60, "key": "security", "name": "Security \u0026 auth", "okx": 68, "weight": 14 }, { "by": 15, "edge": "gate-io", "gate-io": 35, "key": "payments", "name": "Payments \u0026 pricing", "okx": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "okx", "gate-io": 77, "key": "maintenance", "name": "Maintenance \u0026 community", "okx": 81, "weight": 7 }, { "by": 13, "edge": "okx", "gate-io": 49, "key": "transparency", "name": "Transparency \u0026 trust", "okx": 62, "weight": 7 } ], "summary": "OKX API scores 64.3 (B) on agent readiness against Gate's 56.4 (C), and leads in 6 of 7 scored categories. Gate leads on payments \u0026 pricing. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "gate-io": "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.", "okx": "OKX publishes per-endpoint rate limits, Read, Trade and Withdraw key permissions with IP binding, demo trading on the production host, and an MIT MCP server with 170 tools, a read-only flag and a permission check at startup. The fee table and privacy policy were not read, no OpenAPI file was found, and the news tools return third-party text." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/gate-io-vs-okx", "json": "https://www.anchorterminal.com/compare/gate-io-vs-okx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/gate-io-vs-okx.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/gate-io-vs-okx.min.md" }, "markdown": "OKX API scores 64.3 (B) on agent readiness against Gate's 56.4 (C), and leads in 6 of 7 scored categories. Gate leads on payments \u0026 pricing. Both do exchange market data.\n\n- Gate: grade C, 56.4/100, rank #786 of 1349. Markdown https://www.anchorterminal.com/tools/gate-io.md · JSON https://www.anchorterminal.com/api/v1/tools/gate-io.json\n- OKX API: grade B, 64.3/100, rank #413 of 1349. Markdown https://www.anchorterminal.com/tools/okx.md · JSON https://www.anchorterminal.com/api/v1/tools/okx.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### Gate (C)\n\nGood 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.\n\nAhead on:\n- Payments \u0026 pricing, 35 against 20\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No status page, incident history or SLA; the terms give no uptime guarantee and cap liability at three months of fees\n\n### OKX API (B)\n\nGood for: An agent trading spot, perpetuals, futures or options on a person's OKX account from a local machine, with demo trading to test first and grid or DCA bots through the kit.\n\nAhead on:\n- Reliability, 65 against 42\n- Agent ergonomics, 77 against 66\n- Security \u0026 auth, 68 against 60\n- Transparency \u0026 trust, 62 against 49\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The fee table loads by script and the fee FAQ defers to the logged-in view, so maker and taker rates were not read\n\n\n## Why the edge\n\n### Reliability: OKX API +23\n\n- Gate (42): Graded with the hosted lines on the API v4 at api.gateio.ws with the hosted MCP beside it. No status page found (status.gate.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per endpoint group with numbers and fill-ratio rules (15). Every response carries X-Gate-RateLimit-Limit, X-Gate-RateLimit-Requests-Remain and X-Gate-RateLimit-Reset-Timestamp, 429 answers with the label TOO_FAST, and spot orders take a user `text` identifier, but no retry or idempotency guidance is written down (12 of 15). No SLA (0). API v4 and the MCP endpoints are production surfaces (10). 42.\n- OKX API (65): Read with the hosted lines on the V5 REST API. okx.com/status is OKX's own page with issue descriptions, maintenance notices and deposit and withdrawal status, but no component history or feed (10 of 20). It lists no incident between 5 August and 3 November 2026; its newest entry is from March 2024, and whether every incident reaches the page cannot be told, so read as clean with a doubt (20 of 30). Rate limits per endpoint, per User ID and per sub-account with numbers, and WebSocket limits (15). Error 50011 on a limit, a clOrdId on orders and a cap of 3 amendments in flight, but no Retry-After or backoff guidance found (10 of 15). No SLA (0). Generally available (10). 10 + 20 + 15 + 10 + 0 + 10 = 65.\n\n### Payments \u0026 pricing: Gate +15\n\n- 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.\n- OKX API (20): No machine payment protocol (0). The fee table loads by script and the fee FAQ defers to the logged-in view, so no rate was read (0 of 20, unchecked). Public market data and demo trading need no funded account or card (20). A person signs up, verifies and mints a key (0). 0 + 0 + 20 + 0 = 20.\n\n### Transparency \u0026 trust: OKX API +13\n\n- 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.\n- OKX API (62): The editorial half. A closed service with terms that name the contracting entities by region and an API Agreement for agents; the kit is MIT (17 of 30). The privacy policy was not read (5 of 30). The changelog dates sunsets and labels breaking changes, such as port 8443 on 31 October and 16 November 2026 (16 of 20). No subprocessor or data-location statement read; the MCP server is local and its npm package runs a postinstall script whose purpose we did not trace (0 of 20). 17 + 5 + 16 + 0 = 38.\n\n### Agent ergonomics: OKX API +11\n\n- Gate (66): Read for the API with the hosted MCP beside it. The MCP is split by endpoint (58 public tools on /mcp, 400 or more on /mcp/exchange, smaller info and news servers) and the local package filters by module and read-only flag, which stands in for toolsets (5 of 25 for the trading server, 10 added back). Pagination by page and limit, from and to timestamps, status filters (15 of 20). Error labels such as INVALID_SIGNATURE, REQUEST_EXPIRED, IP_FORBIDDEN and READ_ONLY name the recovery (15 of 20). The `text` order identifier makes retries safe; the local server's source sets no readOnlyHint or destructiveHint and the hosted annotations are unread (8 of 20). Three required fields on a spot order, SDKs in seven languages and a CLI (13 of 15). 66.\n- OKX API (77): limit parameters on books, candles and history, and in the kit --modules and --read-only narrow 170 tools to the three default modules; no field selection (17 of 25). after, before and limit cursors on history endpoints (18 of 20). Numeric codes with messages, such as 51020 for an invalid quantity, and the kit returns a structured error block with code, message and endpoint (17 of 20). clOrdId on orders, batch endpoints and a cap of 3 amendments in flight; the kit sets readOnlyHint on query tools but destructiveHint false on order tools and has no idempotency key (13 of 20). python-okx, the CLI and a demo profile, with passphrase and HMAC signing on every private call (12 of 15). 17 + 18 + 17 + 13 + 12 = 77.\n\n### Security \u0026 auth: OKX API +8\n\n- Gate (60): Gate OAuth 2 for the hosted trading MCP with eight scopes per the protected-resource metadata and revocation on the API management page, and API keys with disabled, read-only or read-write per product group, a separate withdrawal group and an IP allow-list of 20 addresses (30). A read-only key and a GATE_READONLY switch exist, and the guide says fund-moving actions need the person's confirmation in the client, with no server-side cap documented (15 of 20). The news and info servers return third-party content with no guidance on treating it as untrusted (5 of 15). Key changes and OAuth grants are visible on the API management page; no per-call log found (5 of 15). No security.txt, no disclosure policy or bounty on a page we read, a proof-of-reserves repository (5 of 20). 60.\n- OKX API (68): Key, secret and passphrase with Read, Trade and Withdraw permissions, up to 20 bound IPs, revocation in the account, and unbound Trade or Withdraw keys that expire after 14 idle days; no OAuth (28 of 30). Read-only keys, sub-account keys, demo trading, the kit's --read-only flag and its startup check that hides order tools when the key cannot trade, and an API Agreement requiring minimum scope; no confirmation step in the kit (18 of 20). The news and smartmoney modules return third-party text and the docs read give no guidance on treating it as untrusted (5 of 15). An account audit log tool in the kit and usage records for unbound keys in the Security Center, no per-call log (9 of 15). No security.txt; SECURITY.md with security@okx.com and GitHub private advisories; certifications and a bounty not read (8 of 20). 28 + 18 + 5 + 9 + 8 = 68.\n\n## Score by category\n\n| Category | Weight | Gate | OKX API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 42 | 65 | OKX API +23 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 73 | OKX API +3 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 77 | OKX API +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 68 | OKX API +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 20 | Gate +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 81 | OKX API +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 62 | OKX API +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **56.4 · C** | **64.3 · B** | |\n\n## Facts side by side\n\n| Fact | Gate | OKX API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Gate | OKX |\n| Hosted endpoint | `https://api.gatemcp.ai/mcp` | no (local only) |\n| Transports | Streamable HTTP, stdio | stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary hosted service under OKX's Terms of Service (29 October 2026) and API Agreement (28 July 2026). The Agent Trade Kit (MCP server, CLI and skills) is MIT |\n| Tools exposed | 58 | 170 |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | yes |\n| MCP registry | `io.github.gateio-dev/gate-mcp` | not listed |\n| Last release | 2026-11-02 | 2026-10-28 |\n| Terms last updated | 2026-07-22 | 2026-10-29 |\n| Privacy policy last updated | no date given | couldn't be read |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 44 stars | 499 stars, 1.8k npm/wk |\n\n## Verdicts\n\n**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.\n\n**OKX API.** OKX publishes per-endpoint rate limits, Read, Trade and Withdraw key permissions with IP binding, demo trading on the production host, and an MIT MCP server with 170 tools, a read-only flag and a permission check at startup. The fee table and privacy policy were not read, no OpenAPI file was found, and the news tools return third-party text.\n\n## Before you call either\n\n### Gate\n\n1. 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\n2. 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\n3. 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\n4. 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\n5. Rehearse futures logic on api-testnet.gateapi.io with TestNet keys; there is no spot testnet\n\n### OKX API\n\n1. Start okx-trade-mcp with --profile demo first, then --read-only on a live key; load only the modules the task needs\n2. Use a sub-account key with Read and Trade only, bound to the agent's IP; an unbound Trade key expires after 14 idle days\n3. Stay under 60 place-order requests per 2 seconds per instrument and at most 3 amendments in flight per order; 50011 means the limit was hit\n4. Send a clOrdId on every order and use the structured error block (code, message, endpoint) to diagnose with read-only tools before retrying\n5. Call us.okx.com or eea.okx.com for US, Australian and EEA accounts; openapi.okx.com does not serve those regions\n\n## Questions\n\n### Which is better for AI agents, Gate or OKX API?\n\nOKX API scores 64.3 (B) on agent readiness against Gate's 56.4 (C), and leads in 6 of 7 scored categories. Gate leads on payments \u0026 pricing.\n\n### Do Gate and OKX API need an API key?\n\nGate takes an API key or an OAuth sign-in. OKX API needs an API key.\n\n### Can an agent call Gate and OKX API without installing anything?\n\nGate has a hosted endpoint at https://api.gatemcp.ai/mcp. OKX API runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/gate-io-vs-okx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gate-io-vs-okx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"gate-io\", \"b\": \"okx\"}`. From a terminal: `anchor compare gate-io okx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gate-io.json and https://www.anchorterminal.com/api/v1/tools/okx.json\n\n## Other comparisons with Gate or OKX API\n\n- [Bitfinex API vs Gate](https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.md)\n- [Bitfinex API vs OKX API](https://www.anchorterminal.com/compare/bitfinex-vs-okx.md)\n- [Bitget vs Gate](https://www.anchorterminal.com/compare/bitget-vs-gate-io.md)\n- [Bitget vs OKX API](https://www.anchorterminal.com/compare/bitget-vs-okx.md)\n- [Bithumb Open API vs Gate](https://www.anchorterminal.com/compare/bithumb-vs-gate-io.md)\n- [Bithumb Open API vs OKX API](https://www.anchorterminal.com/compare/bithumb-vs-okx.md)\n- [Bitstamp API vs Gate](https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.md)\n- [Bitstamp API vs OKX API](https://www.anchorterminal.com/compare/bitstamp-vs-okx.md)\n- [Bybit vs Gate](https://www.anchorterminal.com/compare/bybit-vs-gate-io.md)\n- [Bybit vs OKX API](https://www.anchorterminal.com/compare/bybit-vs-okx.md)\n- [Crypto.com Exchange API vs Gate](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io.md)\n- [Crypto.com Exchange API vs OKX API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx.md)\n- [Gate vs Gemini Exchange API](https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange.md)\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md)\n- [Gate vs Hyperliquid](https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid.md)\n- [Gate vs Kraken API](https://www.anchorterminal.com/compare/gate-io-vs-kraken.md)\n- [Gate vs KuCoin](https://www.anchorterminal.com/compare/gate-io-vs-kucoin.md)\n- [Gate vs MEXC API](https://www.anchorterminal.com/compare/gate-io-vs-mexc.md)\n- [Gate vs Uniswap Trading API](https://www.anchorterminal.com/compare/gate-io-vs-uniswap.md)\n- [Gate vs Upbit Open API](https://www.anchorterminal.com/compare/gate-io-vs-upbit.md)\n- [Gemini Exchange API vs OKX API](https://www.anchorterminal.com/compare/gemini-exchange-vs-okx.md)\n- [HTX trading API vs OKX API](https://www.anchorterminal.com/compare/htx-vs-okx.md)\n- [KuCoin vs OKX API](https://www.anchorterminal.com/compare/kucoin-vs-okx.md)\n- [MEXC API vs OKX API](https://www.anchorterminal.com/compare/mexc-vs-okx.md)\n- [Binance API vs Gate](https://www.anchorterminal.com/compare/binance-vs-gate-io.md)\n- [Binance API vs OKX API](https://www.anchorterminal.com/compare/binance-vs-okx.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 OKX API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Gate](https://www.anchorterminal.com/compare/coinbase-mcp-vs-gate-io.md)\n- [Coinbase MCP server (Coinbase for Agents) vs OKX API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-okx.md)\n- [Kraken API vs OKX API](https://www.anchorterminal.com/compare/kraken-vs-okx.md)\n- [OKX API vs Uniswap Trading API](https://www.anchorterminal.com/compare/okx-vs-uniswap.md)\n- [OKX API vs Upbit Open API](https://www.anchorterminal.com/compare/okx-vs-upbit.md)\n- [Deribit vs Gate](https://www.anchorterminal.com/compare/deribit-vs-gate-io.md)\n- [Deribit vs OKX API](https://www.anchorterminal.com/compare/deribit-vs-okx.md)\n- [dYdX vs Gate](https://www.anchorterminal.com/compare/dydx-vs-gate-io.md)\n- [dYdX vs OKX API](https://www.anchorterminal.com/compare/dydx-vs-okx.md)\n- [Hyperliquid vs OKX API](https://www.anchorterminal.com/compare/hyperliquid-vs-okx.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": "Gate vs OKX API", "url": "" } ], "description": "OKX scores 64.3 (B) to Gate's 56.4 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Gate C 56.4", "OKX API B 64.3", "scores" ], "h1": "Gate vs OKX API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/gate-io-vs-okx", "published": "2026-10-01", "section": "tools", "title": "Gate vs OKX for AI agents in 2026: scores and prices | Anchor Terminal", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/gate-io-vs-okx" }, "tokens": { "markdown": 4400, "slim": 2280 }, "version": 1 }