{ "data": { "a": { "slug": "binance", "name": "Binance API", "vendor": "Binance", "vendorUrl": "https://developers.binance.com/", "kind": "http-api", "category": "crypto-exchanges", "summary": "Binance's API covers spot, margin and futures trading, market data and account endpoints over REST, WebSocket and FIX, with a free spot testnet and a remote MCP server, documented on 30 October 2026, that trades inside a dedicated Agentic sub-account.", "url": "https://www.anchorterminal.com/tools/binance", "markdownUrl": "https://www.anchorterminal.com/tools/binance.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/binance.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/binance.json", "dns": "binance.grade.anchorterminal.com", "repo": "https://github.com/binance/binance-spot-api-docs", "license": "Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://agent.binance.com/mcp/agentic", "packages": [], "auth": "mixed", "authNotes": "API key with an HMAC secret, or a self-generated RSA or Ed25519 key pair whose public key is registered, sent as X-MBX-APIKEY with a signed query and timestamp (recvWindow 5000 ms by default). Permissions are reading, spot and margin trading, futures and withdrawals; an HMAC key without an IP restriction can only read since 30 January 2023, and withdrawals need an IP restriction. Only Verified Plus accounts can create keys. The MCP server uses OAuth in a desktop browser with four scopes (market data, account, trade, transfer) on a dedicated Agentic sub-account and no withdrawal scope (https://www.binance.com/en/support/faq/detail/360002502072, https://developers.binance.com/en/docs/agent-native/mcp-server/agentic, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Spot trades carry a standard fee of 0.1 per cent for regular users per the fee FAQ; the maker and taker table on the fee page loads by script and wasn't read, nor were futures fees. Public market data and the spot testnet need no account; the testnet needs a GitHub login.", "priceSummary": "0.1% fee", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the exchange API or the MCP server in the docs read (checked 2026-11-03). A separate Binance x402 product is named in press coverage of Agent OS, which wasn't read first-hand.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 4903, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developers.binance.com/docs/binance-spot-api-docs/README", "llmsTxt": "https://developers.binance.com/en/docs/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", "oauth", "mcp", "remote-mcp", "llms-txt", "sandbox", "python", "typescript", "java", "go", "cli", "usage-priced", "no-card" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 63.2, "grade": "B", "agentReady": false, "rank": 448, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 81, "payments": 35, "reliability": 45, "schema": 86, "security": 72, "transparency": 43 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.", "bestFor": "An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.", "strengths": [ "Rate limits published as per-endpoint weights with 6,000 a minute, 50 orders per 10 seconds and Retry-After on 429 and 418", "Spot testnet with REST, WebSocket and FIX endpoints, virtual balances and production limits, free with a GitHub login", "Official remote MCP server with OAuth scopes, an isolated Agentic sub-account, no withdrawal scope and confirmation before writes", "Keys with reading, trading, futures and withdrawal permissions; unrestricted-IP HMAC keys can only read and withdrawals need an IP restriction", "Dated changelog since 2018 with retirement dates announced months ahead, llms.txt and llms-full.txt" ], "weaknesses": [ "No status page or incident history found on binance.com or in the API docs", "The Terms of Use and privacy notice load by script and weren't read, so what they say about bots and API use is unknown", "The MCP server's tool list and schemas are not published; the docs describe four scopes", "The maker and taker fee table loads by script; only the 0.1 per cent standard rate in a FAQ was read", "binance-api-swagger was last pushed in October 2024, so the machine-readable spec lags the docs" ], "agentNotes": [ "Read the X-MBX-USED-WEIGHT and X-MBX-ORDER-COUNT headers and stop on 429 for the Retry-After seconds; a 418 ban runs 2 minutes to 3 days", "Treat a 5xx on an order as unknown, not failed, and query the order by origClientOrderId before retrying", "Use an Ed25519 key with an IP restriction and only the reading and trading permissions; never enable withdrawals for an agent key", "Develop on testnet.binance.vision with BINANCE_API_ENV=testnet; it resets about monthly without notice", "For the MCP route, the person must fund the Agentic sub-account from the web UI first; the agent cannot move funds in from the main account" ], "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": 63.2 } ], "editorialScores": { "ergonomics": 76, "maintenance": 81, "payments": 35, "reliability": 45, "schema": 86, "security": 72, "transparency": 31 }, "provenanceScore": 54, "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": { "http": "curl https://api.binance.com/api/v3/ticker/price?symbol=BTCUSDT", "claudeCode": "claude mcp add binance-mcp-server --transport http https://agent.binance.com/mcp/agentic", "config": { "mcpServers": { "binance-mcp-server": { "url": "https://agent.binance.com/mcp/agentic" } } } }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/binance" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, regular user", "unit": "pct", "usd": 0.1, "note": "standard fee per the fee FAQ; maker and taker table not read" } ], "provenance": { "legalEntity": "", "domain": "binance.com", "domainRegistered": "2017-04-01", "endpointOnVendorDomain": true, "terms": "https://www.binance.com/en/terms", "privacy": "https://www.binance.com/en-GB/about-legal/privacy-portal", "statusPage": "", "changelog": "https://developers.binance.com/docs/binance-spot-api-docs/CHANGELOG", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "The Terms of Use and the privacy pages answered our reader with navigation and footer only, so no contracting entity, governing law or data-handling statement was read. The about page names three ADGM entities as regulated subsidiaries, not as the contracting party.", "RDAP gives binance.com a registration date of 1 April 2017.", "https://www.binance.com/.well-known/security.txt has a Contact line (security@binance.com) and no Expires or Policy line, so its validity is unknown under RFC 9116.", "No status page was found. www.binance.com/robots.txt allows the pages read and disallows */api/, */bapi/ and */my/; developers.binance.com and agent.binance.com have no robots.txt (404); api.binance.com and testnet.binance.vision disallow all crawlers, so no API call was made to either.", "The spot API changelog is dated, newest 30 October 2026." ], "score": 54 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/binance.json", "live": { "slug": "binance", "probe": { "target": "https://agent.binance.com/mcp/agentic", "method": "get", "lastAt": "2026-11-04T19:34:23.262708367Z", "lastOk": true, "lastStatus": 404, "lastMs": 594, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 475, "p95ms24h": 582, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-04", "probes": 43, "ok": 43 } ] }, "securityTxt": { "url": "https://binance.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:53:46.658619838Z" }, "updatedAt": "2026-11-04T19:34:23.262708367Z" } }, "answer": "Gemini Exchange API scores 74.6 (BB) on agent readiness against Binance API's 63.2 (B), and leads in every scored category.", "b": { "slug": "gemini-exchange", "name": "Gemini Exchange API", "vendor": "Gemini Trust Company, LLC", "vendorUrl": "https://developer.gemini.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Gemini's exchange API for spot, margin, perpetuals, prediction markets and staking, through REST, WebSocket and FIX, with API key roles or OAuth, plus an official MCP server and SDKs from its developer-platform repository.", "url": "https://www.anchorterminal.com/tools/gemini-exchange", "markdownUrl": "https://www.anchorterminal.com/tools/gemini-exchange.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/gemini-exchange.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/gemini-exchange.json", "dns": "gemini-exchange.grade.anchorterminal.com", "repo": "https://github.com/gemini/developer-platform", "license": "Proprietary hosted API under Gemini's user agreement. The developer-platform repository (MCP server, TypeScript and Go SDKs, samples and skills) is Apache-2.0", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@gemini-markets/sdk" } ], "auth": "mixed", "authNotes": "API key and secret made at exchange.gemini.com/settings/api after a browser signup with identity checks, sent as X-GEMINI-APIKEY, X-GEMINI-PAYLOAD (base64 JSON with a nonce) and X-GEMINI-SIGNATURE (HMAC-SHA384). Keys carry one role, Trader by default, Fund Manager for withdrawals and transfers, Auditor read-only, Administrator for master keys only, and a `master-` key reaches subaccounts. A key can require a heartbeat that cancels its session's orders after 30 seconds of silence. OAuth 2.0 (authorisation code, PKCE S256 for public clients, 24-hour access tokens, single-use refresh tokens, RFC 7009 revocation) is open in the sandbox at once and reviewed by Gemini before production. No IP allow-list was found in the docs (https://developer.gemini.com/roles, https://developer.gemini.com/authentication/api-key, https://developer.gemini.com/authentication/oauth, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API itself costs nothing. Trades pay the API fee schedule, effective 1 September 2026, 0.600% maker and 1.200% taker at the base tier (under $10,000 of 30-day volume), falling to 0.000% maker and 0.020% taker above $250M. Stablecoin pairs 0.00% maker and 0.01% taker. Derivatives from 0.02% maker and 0.07% taker, charged in GUSD. Liquidations 0.5%. The sandbox at api.sandbox.gemini.com credits each new account with test funds and needs no card (https://www.gemini.com/fees/api-fee-schedule, https://developer.gemini.com/get-started/sandbox, checked 2026-11-03).", "priceSummary": "0.6% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, llms.txt, agents.md, the OpenAPI catalogue or the fee schedule (checked 2026-11-03). Trading fees are taken from the account; onboarding is a browser signup.", "endpoints": [] }, "toolCount": 87, "popularity": { "githubStars": 8, "npmWeekly": 99, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developer.gemini.com", "llmsTxt": "https://developer.gemini.com/llms.txt", "openapi": "https://developer.gemini.com/specs/openapi/rest.yaml", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "official", "hosted", "api-key", "oauth", "mcp", "llms-txt", "openapi", "sandbox", "status-page", "bug-bounty", "typescript", "go", "usage-priced" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 74.6, "grade": "BB", "agentReady": true, "rank": 70, "ranked": true, "rankOf": 1349, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 88, "payments": 40, "reliability": 73, "schema": 88, "security": 78, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Gemini publishes an OpenAPI and AsyncAPI contract, API key roles that keep withdrawals off a trading key, a funded sandbox, and an official MCP server whose tools carry read-only and destructive annotations and a confirm gate. Client order ids are not checked for duplicates, there is no SLA, and UK, EEA and Australian accounts closed in April 2026.", "bestFor": "An agent trading spot, perpetuals or prediction markets for a US customer with a role-limited key and a sandbox to rehearse on.", "strengths": [ "Key roles enforce least privilege, since Trader cannot withdraw, Fund Manager cannot trade, Auditor is read-only, and a 403 `MissingRole` names the role an endpoint needs", "Official MCP server with readOnlyHint and destructiveHint on every tool, a `confirm: true` gate on funds-moving tools, untrusted-output framing and redaction of free-text fields", "OpenAPI 3 and AsyncAPI files, llms.txt, llms-full.txt, agents.md, an agent card and an error-codes page with 53 named reasons", "A sandbox with the same REST, WebSocket and FIX surfaces, test balances on signup and a documented 2FA bypass for automated tests", "Fee schedule published per tier without login, and a Statuspage feed with component-level incidents" ], "weaknesses": [ "Client order ids are only recommended to be unique and no duplicate rejection is documented, so a retried order can execute twice", "No Retry-After, backoff guidance or SLA; 429 continues until the rate drops, and the upcoming-changes page reads \"TBD\"", "The MCP server lists 87 tools with no toolset or read-only subset switch, which costs context on every session", "The hosted MCP address in the repository's plugin manifest is on no docs page and gave no complete answer to a GET", "Accounts in the United Kingdom, the EEA and Australia closed on 6 April 2026, and the availability page still lists those countries" ], "agentNotes": [ "Create a Trader key for order flow and a separate Fund Manager key only if withdrawals are in scope; never combine them, and keep the secret out of prompts and logs", "Set a `client_order_id` per order and look it up with `get_order_status` before resending after a timeout, because Gemini does not reject duplicates", "Start on api.sandbox.gemini.com with the same code; sandbox apps register at once, production OAuth apps wait for Gemini's review", "Stay under 1 public and 5 private requests a second; a 429 keeps answering 429 until the rate falls, with no Retry-After to read", "Check the person's country against the availability page first; UK, EEA and Australian accounts were closed on 6 April 2026" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 74.6 } ], "editorialScores": { "ergonomics": 79, "maintenance": 88, "payments": 40, "reliability": 73, "schema": 88, "security": 78, "transparency": 54 }, "provenanceScore": 95, "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 @gemini-markets/sdk", "http": "curl https://api.gemini.com/v1/pubticker/btcusd", "claudeCode": "claude mcp add gemini -s user -e GEMINI_API_KEY=your_key -e GEMINI_API_SECRET=your_secret -- node /absolute/path/to/mcp-server/dist/index.js", "config": { "mcpServers": { "gemini": { "args": [ "/absolute/path/to/mcp-server/dist/index.js" ], "command": "node", "env": { "GEMINI_ACCOUNT": "primary", "GEMINI_API_KEY": "your_api_key_here", "GEMINI_API_SECRET": "your_api_secret_here", "GEMINI_WS_URL": "wss://ws.gemini.com" } } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/gemini-exchange" }, "area": "payments", "unitPrices": [ { "item": "Spot maker fee, base tier (under $10,000 of 30-day volume)", "unit": "pct", "usd": 0.6, "note": "API fee schedule effective 1 September 2026" }, { "item": "Spot taker fee, base tier", "unit": "pct", "usd": 1.2, "note": "falls to 0.02% above $250M of 30-day volume" }, { "item": "Derivatives taker fee, base tier", "unit": "pct", "usd": 0.07, "note": "maker 0.02%, charged in GUSD" } ], "provenance": { "legalEntity": "Gemini Trust Company, LLC", "domain": "gemini.com", "domainRegistered": "1994-02-14", "endpointOnVendorDomain": true, "terms": "https://www.gemini.com/legal/user-agreement", "privacy": "https://www.gemini.com/legal/privacy-policy", "statusPage": "https://status.gemini.com", "changelog": "https://developer.gemini.com/changelog/revision-history", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The user agreement page of 19 February 2026 names Gemini Trust Company, LLC and Gemini Moonbase, LLC by state of residence; the privacy policy of 11 May 2026 lists the affiliates by region. The SEC's submissions record names the parent Gemini Space Station, Inc., Nasdaq GEMI.", "RDAP gives gemini.com a registration date of 14 February 1994.", "https://www.gemini.com/.well-known/security.txt is a PGP-signed file with Contact psirt@gemini.com, a bug bounty policy with payouts from $150 to $20,000 and a sandbox-only scope, but no Expires line.", "www.gemini.com/robots.txt allows the pages read and sets Crawl-delay 600; developer.gemini.com and status.gemini.com allow all (the status site disallows /api/ and /embed/, so the history feed was read, not the incidents API). support.gemini.com answered 403 to an article fetch.", "status.gemini.com is a Statuspage site with an Atom history feed." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/gemini-exchange.json", "live": { "slug": "gemini-exchange", "vendorStatus": { "page": "https://status.gemini.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T19:31:36.16016617Z" }, "securityTxt": { "url": "https://gemini.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:53:25.749980755Z" }, "updatedAt": "2026-11-04T19:31:36.16016617Z" } }, "edges": [ { "by": 32, "category": "transparency", "leads": "gemini-exchange", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed service whose Terms of Use couldn't be read; the docs, connectors, CLI and skills are MIT on GitHub (10 of 30). The privacy notice couldn't be read, so no retention or subprocessor statement was checked; the prohibited-countries list is public and dated (5 of 30). The changelog gives retirement dates for SBE schemas and FIX fields months ahead (16 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 5 + 16 + 0 = 31.", "b": "The editorial half. A closed service under a user agreement that names its entities by state, with the MCP server and SDKs open under Apache-2.0 (18 of 30). The privacy policy of 11 May 2026 names entities and processing countries, ties retention to need without numbers and names provider categories only, with no DPA or subprocessor list found (16 of 30). The revision history records removals and type changes with dates, but the upcoming-changes page is \"TBD\" and no notice period is stated (8 of 20). Processing countries are named (US, Ireland, UK, Malta, Singapore, Australia) and providers by category, with no named subprocessors (12 of 20). 18 + 16 + 8 + 12 = 54." }, "scores": { "a": 43, "b": 75 } }, { "by": 28, "category": "reliability", "leads": "gemini-exchange", "name": "Reliability", "reasons": { "a": "Read with the hosted lines on the spot REST API. No status page was found on binance.com or in the API docs (0), so no incident record (5). Rate limits are published as per-endpoint weights with numbers from exchangeInfo, 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 a day and 61,000 raw requests per 5 minutes, and FIX limits per session (15). 429 and 418 carry Retry-After, a 5xx is documented as unknown status to be queried, and orders take a client order id (15). No SLA (0). Generally available (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.", "b": "Read with the hosted lines on the REST API at api.gemini.com. status.gemini.com is a Statuspage site with component history (20). Its Atom feed for 10 September to 3 November 2026 holds 25 entries, mostly scheduled trading and FIX upgrades of 15 to 60 minutes with possible order timeouts, single-network deposit delays, and incorrect perpetual index prices for about 3.5 hours on 15 and 16 October; a 3-hour scheduled eOTC window was planned and outside the core API. Minor only (20). Rate limits with numbers, 120 a minute public and 600 private plus per-endpoint limits (15). 429 is documented but with no Retry-After or backoff guidance, and client order ids are recommended without duplicate rejection, so retries are not safe by contract; the heartbeat cancel is a safety net rather than idempotency (8 of 15). No SLA found (0). Generally available (10). 20 + 20 + 15 + 8 + 0 + 10 = 73." }, "scores": { "a": 45, "b": 73 } }, { "by": 7, "category": "maintenance", "leads": "gemini-exchange", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.", "b": "Read as a closed hosted service with an open repository. The revision history's latest entry is 28 October 2026 and the repository was pushed on 5 October (30). Thirteen dated entries between 2 September and 28 October 2026 (20). The nine open items on the repository are all pull requests with replies, Dependabot included, and the docs name trading@gemini.com for developer support; no public issue tracker was tested (15 of 25). Not in the official MCP registry, but current official SDKs, TypeScript 0.1.1 of 23 September and Go 0.1.0 of 29 August 2026 (15). CI workflows validate and publish both SDKs and the MCP server has tests; dependencies are current (8 of 10). 30 + 20 + 15 + 15 + 8 = 88." }, "scores": { "a": 81, "b": 88 } }, { "by": 6, "category": "security", "leads": "gemini-exchange", "name": "Security \u0026 auth", "reasons": { "a": "API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72.", "b": "Revocable API keys with one role each (Trader, Fund Manager, Auditor, Administrator), HMAC-SHA384 signing with a nonce, and OAuth 2.0 with scopes, PKCE S256, single-use refresh tokens and RFC 7009 revocation; no IP allow-list documented and no key expiry (28 of 30). Auditor is read-only, a Trader key cannot withdraw, approved withdrawal addresses are a Fund Manager action, and the MCP server refuses funds-moving tools without `confirm: true` (18 of 20). The MCP server wraps every response in untrusted-output markers, strips control and bidi characters and redacts memos, labels and agreement text; the REST docs say nothing on the subject (13 of 15). Order and transfer history are readable, but no per-key audit log or API access log was found (5 of 15). security.txt with a PGP contact and a bug bounty paying $150 to $20,000, scoped to the sandbox hosts; no certification was read and no public advisory process was found (14 of 20). 28 + 18 + 13 + 5 + 14 = 78." }, "scores": { "a": 72, "b": 78 } }, { "by": 5, "category": "payments", "leads": "gemini-exchange", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35.", "b": "No machine payment protocol (0). The API fee schedule is public per tier without login, 0.6% maker and 1.2% taker at the base tier (20). The API is free to call, public market data needs no key, and the sandbox credits test funds with no card (20). A person must sign up in a browser with identity checks, mint a key or approve an OAuth grant, and production OAuth apps wait for Gemini's review (0). 0 + 20 + 20 + 0 = 40." }, "scores": { "a": 35, "b": 40 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Binance", "b": "Gemini Trust Company, LLC", "name": "Vendor" }, { "a": "https://agent.binance.com/mcp/agentic", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT", "b": "Proprietary hosted API under Gemini's user agreement. The developer-platform repository (MCP server, TypeScript and Go SDKs, samples and skills) is Apache-2.0", "name": "Licence" }, { "a": "none", "b": "87", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-10-28", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "yes", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "4.9k stars", "b": "8 stars, 99 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Gemini Exchange API scores 74.6 (BB) on agent readiness against Binance API's 63.2 (B), and leads in every scored category.", "question": "Which is better for AI agents, Binance API or Gemini Exchange API?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Binance API and Gemini Exchange API need an API key?" }, { "answer": "Binance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. Gemini Exchange API runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Binance API and Gemini Exchange API without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card" ], "goodFor": "An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.", "slug": "binance", "watchFor": "No status page or incident history found on binance.com or in the API docs" }, { "aheadOn": [ "Reliability, 73 against 45", "Security \u0026 auth, 78 against 72", "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 88 against 81", "Transparency \u0026 trust, 75 against 43" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine" ], "goodFor": "An agent trading spot, perpetuals or prediction markets for a US customer with a role-limited key and a sandbox to rehearse on.", "slug": "gemini-exchange", "watchFor": "Client order ids are only recommended to be unique and no duplicate rejection is documented, so a retried order can execute twice" } ], "history": null, "job": { "capability": "exchange.spot-trading", "name": "Exchange spot trading" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.json", "title": "Bitfinex API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.json", "title": "Bitget vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.json", "title": "Bithumb Open API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.json", "title": "Bitstamp API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.json", "title": "Bybit vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange.json", "title": "Crypto.com Exchange API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange" }, { "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/gemini-exchange-vs-htx.json", "title": "Gemini Exchange API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-hyperliquid.json", "title": "Gemini Exchange API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken.json", "title": "Gemini Exchange API vs Kraken API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin.json", "title": "Gemini Exchange API vs KuCoin", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin" }, { "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/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/gemini-exchange-vs-uniswap.json", "title": "Gemini Exchange API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit.json", "title": "Gemini Exchange API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitfinex.json", "title": "Binance API vs Bitfinex API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitfinex" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitget.json", "title": "Binance API vs Bitget", "url": "https://www.anchorterminal.com/compare/binance-vs-bitget" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bithumb.json", "title": "Binance API vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-bithumb" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitstamp.json", "title": "Binance API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bybit.json", "title": "Binance API vs Bybit", "url": "https://www.anchorterminal.com/compare/binance-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.json", "title": "Binance API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.json", "title": "Binance API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.json", "title": "Binance API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-deribit.json", "title": "Binance API vs Deribit", "url": "https://www.anchorterminal.com/compare/binance-vs-deribit" }, { "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-htx.json", "title": "Binance API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/binance-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-hyperliquid.json", "title": "Binance API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/binance-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-kraken.json", "title": "Binance API vs Kraken API", "url": "https://www.anchorterminal.com/compare/binance-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-kucoin.json", "title": "Binance API vs KuCoin", "url": "https://www.anchorterminal.com/compare/binance-vs-kucoin" }, { "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/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/binance-vs-uniswap.json", "title": "Binance API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/binance-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-upbit.json", "title": "Binance API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange.json", "title": "Coinbase Advanced Trade API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-gemini-exchange.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-dydx.json", "title": "Binance API vs dYdX", "url": "https://www.anchorterminal.com/compare/binance-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-gemini-exchange.json", "title": "Deribit vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/deribit-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.json", "title": "dYdX vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange" } ], "panel": null, "scores": [ { "binance": 45, "by": 28, "edge": "gemini-exchange", "gemini-exchange": 73, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "binance": 86, "by": 2, "edge": "gemini-exchange", "gemini-exchange": 88, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "binance": 76, "by": 3, "edge": "gemini-exchange", "gemini-exchange": 79, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "binance": 72, "by": 6, "edge": "gemini-exchange", "gemini-exchange": 78, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "binance": 35, "by": 5, "edge": "gemini-exchange", "gemini-exchange": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "binance": 81, "by": 7, "edge": "gemini-exchange", "gemini-exchange": 88, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "binance": 43, "by": 32, "edge": "gemini-exchange", "gemini-exchange": 75, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Gemini Exchange API scores 74.6 (BB) on agent readiness against Binance API's 63.2 (B), and leads in every scored category. Both do exchange spot trading.", "tasks": null, "tutorials": [], "verdicts": { "binance": "Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.", "gemini-exchange": "Gemini publishes an OpenAPI and AsyncAPI contract, API key roles that keep withdrawals off a trading key, a funded sandbox, and an official MCP server whose tools carry read-only and destructive annotations and a confirm gate. Client order ids are not checked for duplicates, there is no SLA, and UK, EEA and Australian accounts closed in April 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange", "json": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.min.md" }, "markdown": "Gemini Exchange API scores 74.6 (BB) on agent readiness against Binance API's 63.2 (B), and leads in every scored category. Both do exchange spot trading.\n\n- Binance API: grade B, 63.2/100, rank #448 of 1349. Markdown https://www.anchorterminal.com/tools/binance.md · JSON https://www.anchorterminal.com/api/v1/tools/binance.json\n- Gemini Exchange API: grade BB, 74.6/100, rank #70 of 1349. Markdown https://www.anchorterminal.com/tools/gemini-exchange.md · JSON https://www.anchorterminal.com/api/v1/tools/gemini-exchange.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### Binance API (B)\n\nGood for: An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: No status page or incident history found on binance.com or in the API docs\n\n### Gemini Exchange API (BB)\n\nGood for: An agent trading spot, perpetuals or prediction markets for a US customer with a role-limited key and a sandbox to rehearse on.\n\nAhead on:\n- Reliability, 73 against 45\n- Security \u0026 auth, 78 against 72\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 88 against 81\n- Transparency \u0026 trust, 75 against 43\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n\nWatch for: Client order ids are only recommended to be unique and no duplicate rejection is documented, so a retried order can execute twice\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Gemini Exchange API +32\n\n- Binance API (43): The editorial half. A closed service whose Terms of Use couldn't be read; the docs, connectors, CLI and skills are MIT on GitHub (10 of 30). The privacy notice couldn't be read, so no retention or subprocessor statement was checked; the prohibited-countries list is public and dated (5 of 30). The changelog gives retirement dates for SBE schemas and FIX fields months ahead (16 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 5 + 16 + 0 = 31.\n- Gemini Exchange API (75): The editorial half. A closed service under a user agreement that names its entities by state, with the MCP server and SDKs open under Apache-2.0 (18 of 30). The privacy policy of 11 May 2026 names entities and processing countries, ties retention to need without numbers and names provider categories only, with no DPA or subprocessor list found (16 of 30). The revision history records removals and type changes with dates, but the upcoming-changes page is \"TBD\" and no notice period is stated (8 of 20). Processing countries are named (US, Ireland, UK, Malta, Singapore, Australia) and providers by category, with no named subprocessors (12 of 20). 18 + 16 + 8 + 12 = 54.\n\n### Reliability: Gemini Exchange API +28\n\n- Binance API (45): Read with the hosted lines on the spot REST API. No status page was found on binance.com or in the API docs (0), so no incident record (5). Rate limits are published as per-endpoint weights with numbers from exchangeInfo, 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 a day and 61,000 raw requests per 5 minutes, and FIX limits per session (15). 429 and 418 carry Retry-After, a 5xx is documented as unknown status to be queried, and orders take a client order id (15). No SLA (0). Generally available (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.\n- Gemini Exchange API (73): Read with the hosted lines on the REST API at api.gemini.com. status.gemini.com is a Statuspage site with component history (20). Its Atom feed for 10 September to 3 November 2026 holds 25 entries, mostly scheduled trading and FIX upgrades of 15 to 60 minutes with possible order timeouts, single-network deposit delays, and incorrect perpetual index prices for about 3.5 hours on 15 and 16 October; a 3-hour scheduled eOTC window was planned and outside the core API. Minor only (20). Rate limits with numbers, 120 a minute public and 600 private plus per-endpoint limits (15). 429 is documented but with no Retry-After or backoff guidance, and client order ids are recommended without duplicate rejection, so retries are not safe by contract; the heartbeat cancel is a safety net rather than idempotency (8 of 15). No SLA found (0). Generally available (10). 20 + 20 + 15 + 8 + 0 + 10 = 73.\n\n### Maintenance \u0026 community: Gemini Exchange API +7\n\n- Binance API (81): Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.\n- Gemini Exchange API (88): Read as a closed hosted service with an open repository. The revision history's latest entry is 28 October 2026 and the repository was pushed on 5 October (30). Thirteen dated entries between 2 September and 28 October 2026 (20). The nine open items on the repository are all pull requests with replies, Dependabot included, and the docs name trading@gemini.com for developer support; no public issue tracker was tested (15 of 25). Not in the official MCP registry, but current official SDKs, TypeScript 0.1.1 of 23 September and Go 0.1.0 of 29 August 2026 (15). CI workflows validate and publish both SDKs and the MCP server has tests; dependencies are current (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.\n\n### Security \u0026 auth: Gemini Exchange API +6\n\n- Binance API (72): API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72.\n- Gemini Exchange API (78): Revocable API keys with one role each (Trader, Fund Manager, Auditor, Administrator), HMAC-SHA384 signing with a nonce, and OAuth 2.0 with scopes, PKCE S256, single-use refresh tokens and RFC 7009 revocation; no IP allow-list documented and no key expiry (28 of 30). Auditor is read-only, a Trader key cannot withdraw, approved withdrawal addresses are a Fund Manager action, and the MCP server refuses funds-moving tools without `confirm: true` (18 of 20). The MCP server wraps every response in untrusted-output markers, strips control and bidi characters and redacts memos, labels and agreement text; the REST docs say nothing on the subject (13 of 15). Order and transfer history are readable, but no per-key audit log or API access log was found (5 of 15). security.txt with a PGP contact and a bug bounty paying $150 to $20,000, scoped to the sandbox hosts; no certification was read and no public advisory process was found (14 of 20). 28 + 18 + 13 + 5 + 14 = 78.\n\n### Payments \u0026 pricing: Gemini Exchange API +5\n\n- Binance API (35): No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35.\n- Gemini Exchange API (40): No machine payment protocol (0). The API fee schedule is public per tier without login, 0.6% maker and 1.2% taker at the base tier (20). The API is free to call, public market data needs no key, and the sandbox credits test funds with no card (20). A person must sign up in a browser with identity checks, mint a key or approve an OAuth grant, and production OAuth apps wait for Gemini's review (0). 0 + 20 + 20 + 0 = 40.\n\n## Score by category\n\n| Category | Weight | Binance API | Gemini Exchange API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 73 | Gemini Exchange API +28 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 88 | Gemini Exchange API +2 |\n| Agent ergonomics | 13% (16.2 this run) | 76 | 79 | Gemini Exchange API +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 78 | Gemini Exchange API +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Gemini Exchange API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 88 | Gemini Exchange API +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 43 | 75 | Gemini Exchange API +32 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.2 · B** | **74.6 · BB** | |\n\n## Facts side by side\n\n| Fact | Binance API | Gemini Exchange API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Binance | Gemini Trust Company, LLC |\n| Hosted endpoint | `https://agent.binance.com/mcp/agentic` | no (local only) |\n| Transports | Streamable HTTP | stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT | Proprietary hosted API under Gemini's user agreement. The developer-platform repository (MCP server, TypeScript and Go SDKs, samples and skills) is Apache-2.0 |\n| Tools exposed | none | 87 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-30 | 2026-10-28 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | no date given |\n| Customer content may train models | couldn't be read | yes |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 4.9k stars | 8 stars, 99 npm/wk |\n\n## Verdicts\n\n**Binance API.** Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.\n\n**Gemini Exchange API.** Gemini publishes an OpenAPI and AsyncAPI contract, API key roles that keep withdrawals off a trading key, a funded sandbox, and an official MCP server whose tools carry read-only and destructive annotations and a confirm gate. Client order ids are not checked for duplicates, there is no SLA, and UK, EEA and Australian accounts closed in April 2026.\n\n## Before you call either\n\n### Binance API\n\n1. Read the X-MBX-USED-WEIGHT and X-MBX-ORDER-COUNT headers and stop on 429 for the Retry-After seconds; a 418 ban runs 2 minutes to 3 days\n2. Treat a 5xx on an order as unknown, not failed, and query the order by origClientOrderId before retrying\n3. Use an Ed25519 key with an IP restriction and only the reading and trading permissions; never enable withdrawals for an agent key\n4. Develop on testnet.binance.vision with BINANCE_API_ENV=testnet; it resets about monthly without notice\n5. For the MCP route, the person must fund the Agentic sub-account from the web UI first; the agent cannot move funds in from the main account\n\n### Gemini Exchange API\n\n1. Create a Trader key for order flow and a separate Fund Manager key only if withdrawals are in scope; never combine them, and keep the secret out of prompts and logs\n2. Set a `client_order_id` per order and look it up with `get_order_status` before resending after a timeout, because Gemini does not reject duplicates\n3. Start on api.sandbox.gemini.com with the same code; sandbox apps register at once, production OAuth apps wait for Gemini's review\n4. Stay under 1 public and 5 private requests a second; a 429 keeps answering 429 until the rate falls, with no Retry-After to read\n5. Check the person's country against the availability page first; UK, EEA and Australian accounts were closed on 6 April 2026\n\n## Questions\n\n### Which is better for AI agents, Binance API or Gemini Exchange API?\n\nGemini Exchange API scores 74.6 (BB) on agent readiness against Binance API's 63.2 (B), and leads in every scored category.\n\n### Do Binance API and Gemini Exchange API need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Binance API and Gemini Exchange API without installing anything?\n\nBinance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. Gemini Exchange 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/binance-vs-gemini-exchange.json, and with the fewest tokens: https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"binance\", \"b\": \"gemini-exchange\"}`. From a terminal: `anchor compare binance gemini-exchange`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/binance.json and https://www.anchorterminal.com/api/v1/tools/gemini-exchange.json\n\n## Other comparisons with Binance API or Gemini Exchange API\n\n- [Bitfinex API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.md)\n- [Bitget vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.md)\n- [Bithumb Open API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.md)\n- [Bitstamp API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.md)\n- [Bybit vs Gemini Exchange API](https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.md)\n- [Crypto.com Exchange API vs Gemini Exchange API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange.md)\n- [Gate vs Gemini Exchange API](https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange.md)\n- [Gemini Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.md)\n- [Gemini Exchange API vs Hyperliquid](https://www.anchorterminal.com/compare/gemini-exchange-vs-hyperliquid.md)\n- [Gemini Exchange API vs Kraken API](https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken.md)\n- [Gemini Exchange API vs KuCoin](https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin.md)\n- [Gemini Exchange API vs MEXC API](https://www.anchorterminal.com/compare/gemini-exchange-vs-mexc.md)\n- [Gemini Exchange API vs OKX API](https://www.anchorterminal.com/compare/gemini-exchange-vs-okx.md)\n- [Gemini Exchange API vs Uniswap Trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-uniswap.md)\n- [Gemini Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit.md)\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)\n- [Binance API vs Bitget](https://www.anchorterminal.com/compare/binance-vs-bitget.md)\n- [Binance API vs Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md)\n- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.md)\n- [Binance API vs Bybit](https://www.anchorterminal.com/compare/binance-vs-bybit.md)\n- [Binance API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.md)\n- [Binance API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.md)\n- [Binance API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.md)\n- [Binance API vs Deribit](https://www.anchorterminal.com/compare/binance-vs-deribit.md)\n- [Binance API vs Gate](https://www.anchorterminal.com/compare/binance-vs-gate-io.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Binance API vs Hyperliquid](https://www.anchorterminal.com/compare/binance-vs-hyperliquid.md)\n- [Binance API vs Kraken API](https://www.anchorterminal.com/compare/binance-vs-kraken.md)\n- [Binance API vs KuCoin](https://www.anchorterminal.com/compare/binance-vs-kucoin.md)\n- [Binance API vs MEXC API](https://www.anchorterminal.com/compare/binance-vs-mexc.md)\n- [Binance API vs OKX API](https://www.anchorterminal.com/compare/binance-vs-okx.md)\n- [Binance API vs Uniswap Trading API](https://www.anchorterminal.com/compare/binance-vs-uniswap.md)\n- [Binance API vs Upbit Open API](https://www.anchorterminal.com/compare/binance-vs-upbit.md)\n- [Coinbase Advanced Trade API vs Gemini Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Gemini Exchange API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-gemini-exchange.md)\n- [Binance API vs dYdX](https://www.anchorterminal.com/compare/binance-vs-dydx.md)\n- [Deribit vs Gemini Exchange API](https://www.anchorterminal.com/compare/deribit-vs-gemini-exchange.md)\n- [dYdX vs Gemini Exchange API](https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.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": "Binance API vs Gemini Exchange API", "url": "" } ], "description": "Gemini Exchange scores 74.6 (BB) to Binance's 63.2 (B) for exchange spot trading. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Binance API B 63.2", "Gemini Exchange API BB 74.6", "scores" ], "h1": "Binance API vs Gemini Exchange API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/binance-vs-gemini-exchange", "published": "2026-10-01", "section": "tools", "title": "Binance vs Gemini Exchange for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange" }, "tokens": { "markdown": 4750, "slim": 2430 }, "version": 1 }