{ "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": "Gate and MEXC API score within a point of each other on agent readiness, 56.4 (C) and 56.3 (C). MEXC API leads on security \u0026 auth and transparency \u0026 trust.", "b": { "slug": "mexc", "name": "MEXC API", "vendor": "MEXC (Comoros) Ltd", "vendorUrl": "https://www.mexc.com/mexc-api", "kind": "http-api", "category": "crypto-exchanges", "summary": "MEXC's spot and futures API gives programmatic access to market data, orders, balances, transfers and withdrawals over REST and WebSocket, with an official command-line tool that also runs as a local MCP server for AI agents.", "url": "https://www.anchorterminal.com/tools/mexc", "markdownUrl": "https://www.anchorterminal.com/tools/mexc.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mexc.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mexc.json", "dns": "mexc.grade.anchorterminal.com", "repo": "https://github.com/mexcdevelop", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@mexc-ai/cli" } ], "auth": "api-key", "authNotes": "API keys made at mexc.com/user/openapi after a browser sign-up; the futures API also needs identity verification. The key goes in the X-MEXC-APIKEY header and signed endpoints carry an HMAC SHA256 signature with a timestamp and a recvWindow of up to 60 seconds. Permissions are granular (SPOT_ACCOUNT_READ, SPOT_DEAL_WRITE, SPOT_WITHDRAW_WRITE, SPOT_TRANSFER_WRITE and the futures equivalents), a key can be limited to chosen trading pairs and linked to up to 10 IP addresses, and a key with no linked IP is valid for 90 days and can be renewed for 90 more from 5 days before expiry. Up to 30 keys per account (https://www.mexc.com/api-docs/spot-v3/introduction, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "Trading fees per fill. MEXC's own fee guide of 20 October 2026 gives spot 0 per cent maker and 0.05 per cent taker (0.04 per cent with MX deduction), futures from 0 per cent maker and 0.02 per cent taker on BTCUSDT to 0.01 and 0.04 per cent on standard contracts, and a separate API futures schedule of 0.06 per cent maker and 0.08 per cent taker since 1 June 2026. Zero-fee campaigns and MX discounts don't apply to API trading. The fee page itself is drawn by script. Market data needs no key (https://www.mexc.com/learn/article/17827791510370, checked 2026-11-03).", "priceSummary": "0.05% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the CLI docs, llms.txt or the terms (checked 2026-11-03). Fees are taken from each fill.", "endpoints": [] }, "toolCount": 299, "popularity": { "githubStars": 315, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.mexc.com/api-docs/spot-v3/introduction", "llmsTxt": "https://www.mexc.com/llms.txt", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "api-key", "closed-source", "usage-priced", "mcp", "cli", "agent-skills", "read-only-mode", "llms-txt", "python", "java", "go", "no-status-page" ], "lastRelease": "2026-10-23", "graded": true, "anchor": { "graded": true, "score": 56.3, "grade": "C", "agentReady": false, "rank": 791, "ranked": true, "rankOf": 1349, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 75, "payments": 31, "reliability": 43, "schema": 64, "security": 65, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "MEXC publishes granular key permissions, per-pair key limits, weighted rate limits with Retry-After and a dated changelog, and its official CLI runs a read-only-capable MCP server with confirmation before any fund movement. There is no sandbox or status page, API futures orders pay a higher fee schedule, and the user agreement excludes the US, UK, EU members and others.", "bestFor": "Spot and futures for agents in served countries that want a vendor-built MCP server with read-only and confirmation modes.", "strengths": [ "Granular key permissions (account read, trade, withdraw, transfer), per-pair restriction, up to 10 linked IPs and a 90-day expiry for unbound keys", "An official MCP mode in the `@mexc-ai/cli` tool with `--read-only`, a read-only market subset of 22 tools and a confirmation step before orders and transfers", "Rate limits published as weight buckets per IP and UID, with Retry-After on 429 and 418", "A dated changelog of 72 spot and 26 futures entries, the newest 23 October 2026", "Fees published on MEXC's own pages, with the API futures schedule stated separately" ], "weaknesses": [ "No sandbox or testnet; only an order-validation endpoint", "No status page, incident history or SLA", "The MCP server is local only, not in the official MCP registry, and the CLI is UNLICENSED with no public source", "API futures orders pay 0.06 per cent maker and 0.08 per cent taker, and zero-fee campaigns exclude API trading", "The user agreement bars users in the United States, the United Kingdom, Mainland China, Singapore, Hong Kong, Canada, France and other jurisdictions" ], "agentNotes": [ "Use a key limited to SPOT_ACCOUNT_READ and SPOT_DEAL_WRITE, the pairs you trade and your IP addresses; keys without a linked IP expire after 90 days", "Start the MCP server as `mexc mcp spot --read-only` unless the task trades, and never pass `--yes`; orders and transfers wait for the person's confirmation", "Call POST /api/v3/order/test before a live order, since there is no sandbox", "On 429 or 418 wait for Retry-After; order placement and cancellation share 12 requests a second per UID, and repeated breaches ban the IP for up to 3 days", "Treat a 5xx on an order as unknown, not failed, and query the order before retrying; set newClientOrderId so the order can be found" ], "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.3 } ], "editorialScores": { "ergonomics": 64, "maintenance": 75, "payments": 31, "reliability": 43, "schema": 64, "security": 65, "transparency": 38 }, "provenanceScore": 78, "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 @mexc-ai/cli", "http": "curl 'https://api.mexc.com/api/v3/ticker/price?symbol=BTCUSDT'", "config": { "mcpServers": { "mexc-spot": { "args": [ "mcp", "spot", "--read-only" ], "command": "mexc" } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/mexc" }, "area": "payments", "unitPrices": [ { "item": "Spot taker fee", "unit": "pct", "usd": 0.05, "note": "maker 0 per cent; 0.04 per cent with MX deduction, not for API trading" }, { "item": "API futures taker fee", "unit": "pct", "usd": 0.08, "note": "maker 0.06 per cent, since 1 June 2026, outside the Innovation Zone" } ], "provenance": { "legalEntity": "MEXC (Comoros) Ltd", "domain": "mexc.com", "domainRegistered": "2000-02-27", "endpointOnVendorDomain": true, "terms": "https://www.mexc.com/terms", "privacy": "https://www.mexc.com/privacypolicy", "statusPage": "", "changelog": "https://www.mexc.com/api-docs/spot-v3/change-log", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "MEXC (Comoros) Ltd is named in the user agreement, last updated 13 October 2026, with a registered address in Mutsamudu, Anjouan. The privacy policy, last updated 1 June 2026, names no entity.", "RDAP gives mexc.com a registration date of 27 February 2000; the exchange says it began in 2018, so the domain predates it.", "www.mexc.com/robots.txt allows the root and disallows /user/, /orders/ and some locale paths; it lists llms.txt as a sitemap. mexcdevelop.github.io has no robots.txt.", "https://www.mexc.com/.well-known/security.txt answered 404. status.mexc.com does not resolve; no status page was found.", "The fee page at mexc.com/fee is drawn by script; the fee figures come from MEXC's own fee guide and a 2024 announcement." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mexc.json", "live": { "slug": "mexc", "securityTxt": { "url": "https://mexc.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:36.213483882Z" }, "updatedAt": "2026-11-04T15:54:36.213483882Z" } }, "edges": [ { "by": 9, "category": "transparency", "leads": "mexc", "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 a dated user agreement naming MEXC (Comoros) Ltd; the CLI is UNLICENSED on npm (15 of 30). The privacy policy names no entity, states no retention periods and relies on standard contractual clauses for transfers (10 of 30). The changelog flags endpoints as \"will be discontinued soon\" without dates and the futures log records removals (8 of 20). Third parties are named by category only, with no subprocessor list or data locations (5 of 20). 15 + 10 + 8 + 5 = 38." }, "scores": { "a": 49, "b": 58 } }, { "by": 6, "category": "schema", "leads": "gate-io", "name": "Schema \u0026 documentation", "reasons": { "a": "No public OpenAPI file was found, though the SDKs are generated and the MCP tools carry typed parameters per the tool reference; the hosted tools' JSON Schema could not be read without a session (12 of 25). The whole REST and WebSocket documentation is downloadable as Markdown and the agent guide is a plain page (10). The tool reference gives one line and the main parameters per tool, the API reference a description per endpoint, no when-not-to-use guidance (12 of 20). Required flags, enums for side, type and time_in_force (11 of 15). Examples per endpoint and a labelled error body with a fixed label list the docs tell you to branch on instead of messages (13 of 15). A versioned changelog, v4.106.177 on 2 November 2026 (12 of 15, since entries are terse). 70.", "b": "No OpenAPI found; a Postman collection and the CLI's 25 capability reference files are the nearest machine-readable contract (5 of 25). llms.txt on mexc.com, written for assistants and pointing at the API docs and legal pages (7 of 10). Per-endpoint pages with purpose, parameters and permissions, without when-not-to-use guidance (13 of 20). Typed parameters with enums for order types, statuses and intervals (11 of 15). Examples on each endpoint and a separate error-code page with numeric codes and messages (13 of 15). Versioned API (v3) with a dated changelog of 72 entries to 23 October 2026 (15). 5 + 7 + 13 + 11 + 13 + 15 = 64." }, "scores": { "a": 70, "b": 64 } }, { "by": 5, "category": "security", "leads": "mexc", "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": "Granular permissions (account read, trade, withdraw, transfer), per-pair restriction, up to 10 linked IPs, 90-day expiry without an IP, renewal and revocation in the account, 30 keys per account (26 of 30). A read-only MCP mode that hides write tools, a confirmation step before orders and transfers in the CLI and MCP, and --yes that agents are told not to add; nothing server-side confirms an API order (17 of 20). The API returns exchange data, and the CLI security page warns that agents may be led by web pages or files into unwanted actions (12 of 15). CLI confirmations are logged and reported to MEXC with no operator access described; an apiKeyInfo endpoint shows key settings (6 of 15). No security.txt, disclosure policy or bug bounty found; a proof-of-reserves page exists (4 of 20). 26 + 17 + 12 + 6 + 4 = 65." }, "scores": { "a": 60, "b": 65 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Gate", "b": "MEXC (Comoros) Ltd", "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": "58", "b": "299", "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-23", "name": "Last release" }, { "a": "2026-07-22", "b": "2026-10-13", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-06-01", "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": "yes", "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": "315 stars", "name": "Popularity" } ], "faq": [ { "answer": "Gate and MEXC API score within a point of each other on agent readiness, 56.4 (C) and 56.3 (C). MEXC API leads on security \u0026 auth and transparency \u0026 trust.", "question": "Which is better for AI agents, Gate or MEXC API?" }, { "answer": "Gate takes an API key or an OAuth sign-in. MEXC API needs an API key.", "question": "Do Gate and MEXC API need an API key?" }, { "answer": "Gate has a hosted endpoint at https://api.gatemcp.ai/mcp. MEXC API runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Gate and MEXC API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 70 against 64" ], "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": [ "Security \u0026 auth, 65 against 60", "Transparency \u0026 trust, 58 against 49" ], "also": null, "goodFor": "Spot and futures for agents in served countries that want a vendor-built MCP server with read-only and confirmation modes.", "slug": "mexc", "watchFor": "No sandbox or testnet; only an order-validation endpoint" } ], "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-mexc.json", "title": "Bitfinex API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc" }, { "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-mexc.json", "title": "Bitget vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitget-vs-mexc" }, { "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-mexc.json", "title": "Bithumb Open API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-mexc" }, { "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-mexc.json", "title": "Bitstamp API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-mexc" }, { "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-mexc.json", "title": "Bybit vs MEXC API", "url": "https://www.anchorterminal.com/compare/bybit-vs-mexc" }, { "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-mexc.json", "title": "Crypto.com Exchange API vs MEXC API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc" }, { "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-okx.json", "title": "Gate vs OKX API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-okx" }, { "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-mexc.json", "title": "Gemini Exchange API vs MEXC API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-mexc.json", "title": "HTX trading API vs MEXC API", "url": "https://www.anchorterminal.com/compare/htx-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-mexc.json", "title": "KuCoin vs MEXC API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-mexc" }, { "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/mexc-vs-uniswap.json", "title": "MEXC API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/mexc-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-upbit.json", "title": "MEXC API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/mexc-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-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-mexc.json", "title": "Binance API vs MEXC API", "url": "https://www.anchorterminal.com/compare/binance-vs-mexc" }, { "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-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-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-mexc.json", "title": "Coinbase MCP server (Coinbase for Agents) vs MEXC API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-mexc.json", "title": "Kraken API vs MEXC API", "url": "https://www.anchorterminal.com/compare/kraken-vs-mexc" }, { "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-mexc.json", "title": "Deribit vs MEXC API", "url": "https://www.anchorterminal.com/compare/deribit-vs-mexc" }, { "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-mexc.json", "title": "dYdX vs MEXC API", "url": "https://www.anchorterminal.com/compare/dydx-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-mexc.json", "title": "Hyperliquid vs MEXC API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-mexc" } ], "panel": null, "scores": [ { "by": 1, "edge": "mexc", "gate-io": 42, "key": "reliability", "mexc": 43, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 6, "edge": "gate-io", "gate-io": 70, "key": "schema", "mexc": 64, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 2, "edge": "gate-io", "gate-io": 66, "key": "ergonomics", "mexc": 64, "name": "Agent ergonomics", "weight": 13 }, { "by": 5, "edge": "mexc", "gate-io": 60, "key": "security", "mexc": 65, "name": "Security \u0026 auth", "weight": 14 }, { "by": 4, "edge": "gate-io", "gate-io": 35, "key": "payments", "mexc": 31, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "gate-io", "gate-io": 77, "key": "maintenance", "mexc": 75, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 9, "edge": "mexc", "gate-io": 49, "key": "transparency", "mexc": 58, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Gate and MEXC API score within a point of each other on agent readiness, 56.4 (C) and 56.3 (C). MEXC API leads on security \u0026 auth and transparency \u0026 trust. 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.", "mexc": "MEXC publishes granular key permissions, per-pair key limits, weighted rate limits with Retry-After and a dated changelog, and its official CLI runs a read-only-capable MCP server with confirmation before any fund movement. There is no sandbox or status page, API futures orders pay a higher fee schedule, and the user agreement excludes the US, UK, EU members and others." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/gate-io-vs-mexc", "json": "https://www.anchorterminal.com/compare/gate-io-vs-mexc.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/gate-io-vs-mexc.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/gate-io-vs-mexc.min.md" }, "markdown": "Gate and MEXC API score within a point of each other on agent readiness, 56.4 (C) and 56.3 (C). MEXC API leads on security \u0026 auth and transparency \u0026 trust. 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- MEXC API: grade C, 56.3/100, rank #791 of 1349. Markdown https://www.anchorterminal.com/tools/mexc.md · JSON https://www.anchorterminal.com/api/v1/tools/mexc.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- Schema \u0026 documentation, 70 against 64\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### MEXC API (C)\n\nGood for: Spot and futures for agents in served countries that want a vendor-built MCP server with read-only and confirmation modes.\n\nAhead on:\n- Security \u0026 auth, 65 against 60\n- Transparency \u0026 trust, 58 against 49\n\nWatch for: No sandbox or testnet; only an order-validation endpoint\n\n\n## Why the edge\n\n### Transparency \u0026 trust: MEXC API +9\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- MEXC API (58): The editorial half. A closed service with a dated user agreement naming MEXC (Comoros) Ltd; the CLI is UNLICENSED on npm (15 of 30). The privacy policy names no entity, states no retention periods and relies on standard contractual clauses for transfers (10 of 30). The changelog flags endpoints as \"will be discontinued soon\" without dates and the futures log records removals (8 of 20). Third parties are named by category only, with no subprocessor list or data locations (5 of 20). 15 + 10 + 8 + 5 = 38.\n\n### Schema \u0026 documentation: Gate +6\n\n- Gate (70): No public OpenAPI file was found, though the SDKs are generated and the MCP tools carry typed parameters per the tool reference; the hosted tools' JSON Schema could not be read without a session (12 of 25). The whole REST and WebSocket documentation is downloadable as Markdown and the agent guide is a plain page (10). The tool reference gives one line and the main parameters per tool, the API reference a description per endpoint, no when-not-to-use guidance (12 of 20). Required flags, enums for side, type and time_in_force (11 of 15). Examples per endpoint and a labelled error body with a fixed label list the docs tell you to branch on instead of messages (13 of 15). A versioned changelog, v4.106.177 on 2 November 2026 (12 of 15, since entries are terse). 70.\n- MEXC API (64): No OpenAPI found; a Postman collection and the CLI's 25 capability reference files are the nearest machine-readable contract (5 of 25). llms.txt on mexc.com, written for assistants and pointing at the API docs and legal pages (7 of 10). Per-endpoint pages with purpose, parameters and permissions, without when-not-to-use guidance (13 of 20). Typed parameters with enums for order types, statuses and intervals (11 of 15). Examples on each endpoint and a separate error-code page with numeric codes and messages (13 of 15). Versioned API (v3) with a dated changelog of 72 entries to 23 October 2026 (15). 5 + 7 + 13 + 11 + 13 + 15 = 64.\n\n### Security \u0026 auth: MEXC API +5\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- MEXC API (65): Granular permissions (account read, trade, withdraw, transfer), per-pair restriction, up to 10 linked IPs, 90-day expiry without an IP, renewal and revocation in the account, 30 keys per account (26 of 30). A read-only MCP mode that hides write tools, a confirmation step before orders and transfers in the CLI and MCP, and --yes that agents are told not to add; nothing server-side confirms an API order (17 of 20). The API returns exchange data, and the CLI security page warns that agents may be led by web pages or files into unwanted actions (12 of 15). CLI confirmations are logged and reported to MEXC with no operator access described; an apiKeyInfo endpoint shows key settings (6 of 15). No security.txt, disclosure policy or bug bounty found; a proof-of-reserves page exists (4 of 20). 26 + 17 + 12 + 6 + 4 = 65.\n\n## Score by category\n\n| Category | Weight | Gate | MEXC API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 42 | 43 | MEXC API +1 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 64 | Gate +6 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 64 | Gate +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 65 | MEXC API +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 31 | Gate +4 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 75 | Gate +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 58 | MEXC API +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **56.4 · C** | **56.3 · C** | |\n\n## Facts side by side\n\n| Fact | Gate | MEXC API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Gate | MEXC (Comoros) Ltd |\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| Tools exposed | 58 | 299 |\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-23 |\n| Terms last updated | 2026-07-22 | 2026-10-13 |\n| Privacy policy last updated | no date given | 2026-06-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\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 | 315 stars |\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**MEXC API.** MEXC publishes granular key permissions, per-pair key limits, weighted rate limits with Retry-After and a dated changelog, and its official CLI runs a read-only-capable MCP server with confirmation before any fund movement. There is no sandbox or status page, API futures orders pay a higher fee schedule, and the user agreement excludes the US, UK, EU members and others.\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### MEXC API\n\n1. Use a key limited to SPOT_ACCOUNT_READ and SPOT_DEAL_WRITE, the pairs you trade and your IP addresses; keys without a linked IP expire after 90 days\n2. Start the MCP server as `mexc mcp spot --read-only` unless the task trades, and never pass `--yes`; orders and transfers wait for the person's confirmation\n3. Call POST /api/v3/order/test before a live order, since there is no sandbox\n4. On 429 or 418 wait for Retry-After; order placement and cancellation share 12 requests a second per UID, and repeated breaches ban the IP for up to 3 days\n5. Treat a 5xx on an order as unknown, not failed, and query the order before retrying; set newClientOrderId so the order can be found\n\n## Questions\n\n### Which is better for AI agents, Gate or MEXC API?\n\nGate and MEXC API score within a point of each other on agent readiness, 56.4 (C) and 56.3 (C). MEXC API leads on security \u0026 auth and transparency \u0026 trust.\n\n### Do Gate and MEXC API need an API key?\n\nGate takes an API key or an OAuth sign-in. MEXC API needs an API key.\n\n### Can an agent call Gate and MEXC API without installing anything?\n\nGate has a hosted endpoint at https://api.gatemcp.ai/mcp. MEXC 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-mexc.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gate-io-vs-mexc.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"gate-io\", \"b\": \"mexc\"}`. From a terminal: `anchor compare gate-io mexc`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gate-io.json and https://www.anchorterminal.com/api/v1/tools/mexc.json\n\n## Other comparisons with Gate or MEXC API\n\n- [Bitfinex API vs Gate](https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.md)\n- [Bitfinex API vs MEXC API](https://www.anchorterminal.com/compare/bitfinex-vs-mexc.md)\n- [Bitget vs Gate](https://www.anchorterminal.com/compare/bitget-vs-gate-io.md)\n- [Bitget vs MEXC API](https://www.anchorterminal.com/compare/bitget-vs-mexc.md)\n- [Bithumb Open API vs Gate](https://www.anchorterminal.com/compare/bithumb-vs-gate-io.md)\n- [Bithumb Open API vs MEXC API](https://www.anchorterminal.com/compare/bithumb-vs-mexc.md)\n- [Bitstamp API vs Gate](https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.md)\n- [Bitstamp API vs MEXC API](https://www.anchorterminal.com/compare/bitstamp-vs-mexc.md)\n- [Bybit vs Gate](https://www.anchorterminal.com/compare/bybit-vs-gate-io.md)\n- [Bybit vs MEXC API](https://www.anchorterminal.com/compare/bybit-vs-mexc.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 MEXC API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc.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 OKX API](https://www.anchorterminal.com/compare/gate-io-vs-okx.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 MEXC API](https://www.anchorterminal.com/compare/gemini-exchange-vs-mexc.md)\n- [HTX trading API vs MEXC API](https://www.anchorterminal.com/compare/htx-vs-mexc.md)\n- [KuCoin vs MEXC API](https://www.anchorterminal.com/compare/kucoin-vs-mexc.md)\n- [MEXC API vs OKX API](https://www.anchorterminal.com/compare/mexc-vs-okx.md)\n- [MEXC API vs Uniswap Trading API](https://www.anchorterminal.com/compare/mexc-vs-uniswap.md)\n- [MEXC API vs Upbit Open API](https://www.anchorterminal.com/compare/mexc-vs-upbit.md)\n- [Binance API vs Gate](https://www.anchorterminal.com/compare/binance-vs-gate-io.md)\n- [Binance API vs MEXC API](https://www.anchorterminal.com/compare/binance-vs-mexc.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 MEXC API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc.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 MEXC API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-mexc.md)\n- [Kraken API vs MEXC API](https://www.anchorterminal.com/compare/kraken-vs-mexc.md)\n- [Deribit vs Gate](https://www.anchorterminal.com/compare/deribit-vs-gate-io.md)\n- [Deribit vs MEXC API](https://www.anchorterminal.com/compare/deribit-vs-mexc.md)\n- [dYdX vs Gate](https://www.anchorterminal.com/compare/dydx-vs-gate-io.md)\n- [dYdX vs MEXC API](https://www.anchorterminal.com/compare/dydx-vs-mexc.md)\n- [Hyperliquid vs MEXC API](https://www.anchorterminal.com/compare/hyperliquid-vs-mexc.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 MEXC API", "url": "" } ], "description": "Gate and MEXC score within a point of each other for exchange market data, 56.4 and 56.3 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Gate C 56.4", "MEXC API C 56.3", "scores" ], "h1": "Gate vs MEXC API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/gate-io-vs-mexc", "published": "2026-10-01", "section": "tools", "title": "Gate vs MEXC for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/gate-io-vs-mexc" }, "tokens": { "markdown": 3750, "slim": 1630 }, "version": 1 }