{ "data": { "a": { "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" } }, "answer": "Gemini Exchange API scores 74.6 (BB) on agent readiness against OKX API's 64.3 (B), and leads in every scored category.", "b": { "slug": "okx", "name": "OKX API", "vendor": "OKX", "vendorUrl": "https://www.okx.com/docs-v5/en/", "kind": "http-api", "category": "crypto-exchanges", "summary": "OKX's V5 API covers spot, margin, perpetual, futures and options trading, account and market data over REST and WebSocket, with demo trading on the same host and an open-source Agent Trade Kit whose okx-trade-mcp package is a local MCP server.", "url": "https://www.anchorterminal.com/tools/okx", "markdownUrl": "https://www.anchorterminal.com/tools/okx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/okx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/okx.json", "dns": "okx.grade.anchorterminal.com", "repo": "https://github.com/okx/agent-trade-kit", "license": "Proprietary hosted service under OKX's Terms of Service (29 October 2026) and API Agreement (28 July 2026). The Agent Trade Kit (MCP server, CLI and skills) is MIT", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@okx_ai/okx-trade-mcp" }, { "registry": "npm", "name": "@okx_ai/okx-trade-cli" }, { "registry": "pypi", "name": "python-okx" } ], "auth": "api-key", "authNotes": "API key, secret and passphrase made at okx.com/account/my-api, with HMAC-SHA256 signatures over a timestamp and the request. Permissions are Read, Trade and Withdraw, singly or combined; each key binds up to 20 IP addresses or ranges, and a Trade or Withdraw key with no IP binding expires after 14 days without use. Demo trading uses the same host with the header `x-simulated-trading` set to 1 and keys that do not expire. US and Australian users call us.okx.com and EEA users eea.okx.com. The MCP server reads the key from ~/.okx/config.toml, checks its permissions at startup and hides order tools when the key cannot trade (https://www.okx.com/docs-v5/en/, https://www.okx.com/docs-v5/agent_en/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Trades carry maker and taker fees by regular and VIP level; the fee page at okx.com/fees loads its table by script and the fee FAQ says the rates that apply are the ones shown while logged in, so the lowest tier's rates are unread. Public market data and demo trading need no funded account.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the V5 docs, the API agreement or the Agent Trade Kit (checked 2026-11-03).", "endpoints": [] }, "toolCount": 170, "popularity": { "githubStars": 499, "npmWeekly": 1839, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.okx.com/docs-v5/en/", "llmsTxt": "https://www.okx.com/llms.txt", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "official", "closed-source", "api-key", "mcp", "cli", "llms-txt", "sandbox", "typescript", "python", "usage-priced", "no-card", "mit" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 64.3, "grade": "B", "agentReady": false, "rank": 413, "ranked": true, "rankOf": 1349, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 81, "payments": 20, "reliability": 65, "schema": 73, "security": 68, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "OKX publishes per-endpoint rate limits, Read, Trade and Withdraw key permissions with IP binding, demo trading on the production host, and an MIT MCP server with 170 tools, a read-only flag and a permission check at startup. The fee table and privacy policy were not read, no OpenAPI file was found, and the news tools return third-party text.", "bestFor": "An agent trading spot, perpetuals, futures or options on a person's OKX account from a local machine, with demo trading to test first and grid or DCA bots through the kit.", "strengths": [ "Official local MCP server, MIT, with modules, --read-only, a demo profile, readOnlyHint annotations and a startup check that hides order tools when the key cannot trade", "Keys limited to Read, Trade or Withdraw, bound to up to 20 IPs, with unbound Trade and Withdraw keys expiring after 14 idle days", "Rate limits published per endpoint and per User ID, with sub-account and WebSocket limits in numbers", "Demo trading on the production hosts with one header, keys that do not expire, and a demo profile in the kit", "An API Agreement written for agents, naming prohibited tactics, minimum key scope and rate-limit circumvention" ], "weaknesses": [ "The fee table loads by script and the fee FAQ defers to the logged-in view, so maker and taker rates were not read", "No OpenAPI file was found in the docs; the machine-readable contract is the kit's tool definitions", "The status page lists incidents without component history, and its newest entry is from March 2024", "The news and smart money tools return third-party text with no documented guidance on treating it as untrusted", "Trade tools in the kit carry destructiveHint false, and the npm package runs a postinstall script" ], "agentNotes": [ "Start okx-trade-mcp with --profile demo first, then --read-only on a live key; load only the modules the task needs", "Use a sub-account key with Read and Trade only, bound to the agent's IP; an unbound Trade key expires after 14 idle days", "Stay under 60 place-order requests per 2 seconds per instrument and at most 3 amendments in flight per order; 50011 means the limit was hit", "Send a clOrdId on every order and use the structured error block (code, message, endpoint) to diagnose with read-only tools before retrying", "Call us.okx.com or eea.okx.com for US, Australian and EEA accounts; openapi.okx.com does not serve those regions" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.3 } ], "editorialScores": { "ergonomics": 77, "maintenance": 81, "payments": 20, "reliability": 65, "schema": 73, "security": 68, "transparency": 38 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @okx_ai/okx-trade-mcp @okx_ai/okx-trade-cli", "http": "curl https://www.okx.com/api/v5/market/ticker?instId=BTC-USDT", "config": { "mcpServers": { "okx-demo": { "args": [ "-y", "@okx_ai/okx-trade-mcp", "--profile", "demo" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/okx" }, "area": "payments", "provenance": { "legalEntity": "Aux Cayes FinTech Co. Ltd.", "domain": "okx.com", "domainRegistered": "2001-07-03", "endpointOnVendorDomain": true, "terms": "https://www.okx.com/help/terms-of-service", "privacy": "https://www.okx.com/help/privacy-policy", "statusPage": "https://www.okx.com/status", "changelog": "https://www.okx.com/docs-v5/log_en/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The Terms of Service (last updated 29 October 2026) name Aux Cayes FinTech Co. Ltd. for all users not served by a regional OKX entity; the page metadata of the API Agreement also lists it as publisher. The governing-law clause sat past the part of the page we read. The privacy policy URL is OKX's help-centre page and was not read.", "RDAP gives okx.com a registration date of 3 July 2001, long before OKX took the name in 2022.", "https://www.okx.com/.well-known/security.txt answers 404; the Agent Trade Kit's SECURITY.md names security@okx.com.", "www.okx.com/robots.txt allows the docs, help and status pages read and /llms.txt, and disallows account, KYC and other private paths.", "okx.com/status is OKX's own page with issue descriptions and maintenance notices in UTC+8, no component history and no feed found." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/okx.json", "live": { "slug": "okx", "vendorStatus": { "page": "https://www.okx.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:32:13.2375881Z" }, "securityTxt": { "url": "https://okx.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:49.77403161Z" }, "updatedAt": "2026-11-04T15:53:49.77403161Z" } }, "edges": [ { "by": 20, "category": "payments", "leads": "gemini-exchange", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No machine payment protocol (0). The fee table loads by script and the fee FAQ defers to the logged-in view, so no rate was read (0 of 20, unchecked). Public market data and demo trading need no funded account or card (20). A person signs up, verifies and mints a key (0). 0 + 0 + 20 + 0 = 20." }, "scores": { "a": 40, "b": 20 } }, { "by": 15, "category": "schema", "leads": "gemini-exchange", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3 for REST (specs/openapi/rest.yaml), AsyncAPI for WebSocket, a prediction-markets OpenAPI file and a specs/index.json catalogue; the MCP server's tools take zod schemas published as JSON Schema (25). llms.txt, llms-full.txt, agents.md, an agent card and an agent skills index (10). Endpoint pages state purpose, the Build an agent guide says what to establish before acting and when to stop, and MCP tool descriptions tell the model when to confirm; the docs don't say when not to use an endpoint (15 of 20). Typed inputs with enums for order types, options and sessions, required fields marked, decimals as strings since 7 July 2026 (12 of 15). Examples throughout, samples in three languages, and an error-codes page with 53 named reasons and their HTTP statuses (14 of 15). A revision history dated from 2015 to 28 October 2026 and versioned paths (v1, v2), but the upcoming-changes page reads \"TBD\" (12 of 15). 25 + 10 + 15 + 12 + 14 + 12 = 88.", "b": "No OpenAPI file was found in the V5 docs; the kit's tool definitions are typed TypeScript with annotations, and the organisation has an undescribed ai-builder-openapi-md repository we did not read (12 of 25). okx.com/llms.txt exists and links the API and Agent Trade Kit pages, though the V5 docs have no Markdown twins (5 of 10). Each endpoint states its rate limit, rule, parameters and notes (15 of 20). Enums for ordType, tdMode and instType with required flags (12 of 15). Request and response examples per endpoint and an error code list with messages (14 of 15). A dated changelog with an upcoming-changes section that labels breaking changes and dates sunsets (15). 12 + 5 + 15 + 12 + 14 + 15 = 73." }, "scores": { "a": 88, "b": 73 } }, { "by": 13, "category": "transparency", "leads": "gemini-exchange", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The editorial half. A closed service with terms that name the contracting entities by region and an API Agreement for agents; the kit is MIT (17 of 30). The privacy policy was not read (5 of 30). The changelog dates sunsets and labels breaking changes, such as port 8443 on 31 October and 16 November 2026 (16 of 20). No subprocessor or data-location statement read; the MCP server is local and its npm package runs a postinstall script whose purpose we did not trace (0 of 20). 17 + 5 + 16 + 0 = 38." }, "scores": { "a": 75, "b": 62 } }, { "by": 10, "category": "security", "leads": "gemini-exchange", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Key, secret and passphrase with Read, Trade and Withdraw permissions, up to 20 bound IPs, revocation in the account, and unbound Trade or Withdraw keys that expire after 14 idle days; no OAuth (28 of 30). Read-only keys, sub-account keys, demo trading, the kit's --read-only flag and its startup check that hides order tools when the key cannot trade, and an API Agreement requiring minimum scope; no confirmation step in the kit (18 of 20). The news and smartmoney modules return third-party text and the docs read give no guidance on treating it as untrusted (5 of 15). An account audit log tool in the kit and usage records for unbound keys in the Security Center, no per-call log (9 of 15). No security.txt; SECURITY.md with security@okx.com and GitHub private advisories; certifications and a bounty not read (8 of 20). 28 + 18 + 5 + 9 + 8 = 68." }, "scores": { "a": 78, "b": 68 } }, { "by": 8, "category": "reliability", "leads": "gemini-exchange", "name": "Reliability", "reasons": { "a": "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.", "b": "Read with the hosted lines on the V5 REST API. okx.com/status is OKX's own page with issue descriptions, maintenance notices and deposit and withdrawal status, but no component history or feed (10 of 20). It lists no incident between 5 August and 3 November 2026; its newest entry is from March 2024, and whether every incident reaches the page cannot be told, so read as clean with a doubt (20 of 30). Rate limits per endpoint, per User ID and per sub-account with numbers, and WebSocket limits (15). Error 50011 on a limit, a clOrdId on orders and a cap of 3 amendments in flight, but no Retry-After or backoff guidance found (10 of 15). No SLA (0). Generally available (10). 10 + 20 + 15 + 10 + 0 + 10 = 65." }, "scores": { "a": 73, "b": 65 } }, { "by": 7, "category": "maintenance", "leads": "gemini-exchange", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed service with an open-source kit. Changelog entry of 27 October 2026 and kit v1.5.0 on 28 October (30). Changelog entries on 3, 6, 11, 18, 20 and 26 August, 15, 29 and 30 September and 27 October, and kit releases on 20 and 21 August, 1, 7, 14 and 23 September, 19 and 28 October (20). A public changelog, a Telegram community for the kit and GitHub issues whose replies were not read (10 of 15). python-okx is named as the official SDK and the kit is current; the MCP server is not in the official registry (12 of 15). The kit runs CI on push and pull request across Node 18, 20 and 26 with unit tests and coverage (9 of 10). 30 + 20 + 10 + 12 + 9 = 81." }, "scores": { "a": 88, "b": 81 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Gemini Trust Company, LLC", "b": "OKX", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "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": "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", "b": "Proprietary hosted service under OKX's Terms of Service (29 October 2026) and API Agreement (28 July 2026). The Agent Trade Kit (MCP server, CLI and skills) is MIT", "name": "Licence" }, { "a": "87", "b": "170", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-28", "b": "2026-10-28", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-10-29", "name": "Terms last updated" }, { "a": "no date given", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "8 stars, 99 npm/wk", "b": "499 stars, 1.8k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Gemini Exchange API scores 74.6 (BB) on agent readiness against OKX API's 64.3 (B), and leads in every scored category.", "question": "Which is better for AI agents, Gemini Exchange API or OKX API?" }, { "answer": "Gemini Exchange API takes an API key or an OAuth sign-in. OKX API needs an API key.", "question": "Do Gemini Exchange API and OKX API need an API key?" }, { "answer": "Gemini Exchange API runs on your own machine, with no hosted endpoint listed. OKX API runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Gemini Exchange API and OKX API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 73 against 65", "Schema \u0026 documentation, 88 against 73", "Security \u0026 auth, 78 against 68", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 88 against 81", "Transparency \u0026 trust, 75 against 62" ], "also": [ "Agent-ready, a grade of BB or better" ], "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" }, { "aheadOn": null, "also": [ "Free to start without a card" ], "goodFor": "An agent trading spot, perpetuals, futures or options on a person's OKX account from a local machine, with demo trading to test first and grid or DCA bots through the kit.", "slug": "okx", "watchFor": "The fee table loads by script and the fee FAQ defers to the logged-in view, so maker and taker rates were not read" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-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/bitfinex-vs-okx.json", "title": "Bitfinex API vs OKX API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-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/bitget-vs-okx.json", "title": "Bitget vs OKX API", "url": "https://www.anchorterminal.com/compare/bitget-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-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/bithumb-vs-okx.json", "title": "Bithumb Open API vs OKX API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-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/bitstamp-vs-okx.json", "title": "Bitstamp API vs OKX API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-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/bybit-vs-okx.json", "title": "Bybit vs OKX API", "url": "https://www.anchorterminal.com/compare/bybit-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-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/crypto-com-exchange-vs-okx.json", "title": "Crypto.com Exchange API vs OKX API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange.json", "title": "Gate vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-okx.json", "title": "Gate vs OKX API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-okx" }, { "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-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/htx-vs-okx.json", "title": "HTX trading API vs OKX API", "url": "https://www.anchorterminal.com/compare/htx-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-okx.json", "title": "KuCoin vs OKX API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-okx.json", "title": "MEXC API vs OKX API", "url": "https://www.anchorterminal.com/compare/mexc-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.json", "title": "Binance API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-okx.json", "title": "Binance API vs OKX API", "url": "https://www.anchorterminal.com/compare/binance-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-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-advanced-trade-vs-okx.json", "title": "Coinbase Advanced Trade API vs OKX API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-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/coinbase-mcp-vs-okx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs OKX API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-okx.json", "title": "Kraken API vs OKX API", "url": "https://www.anchorterminal.com/compare/kraken-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/okx-vs-uniswap.json", "title": "OKX API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/okx-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/okx-vs-upbit.json", "title": "OKX API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/okx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-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/deribit-vs-okx.json", "title": "Deribit vs OKX API", "url": "https://www.anchorterminal.com/compare/deribit-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.json", "title": "dYdX vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-okx.json", "title": "dYdX vs OKX API", "url": "https://www.anchorterminal.com/compare/dydx-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-okx.json", "title": "Hyperliquid vs OKX API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-okx" } ], "panel": null, "scores": [ { "by": 8, "edge": "gemini-exchange", "gemini-exchange": 73, "key": "reliability", "name": "Reliability", "okx": 65, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 15, "edge": "gemini-exchange", "gemini-exchange": 88, "key": "schema", "name": "Schema \u0026 documentation", "okx": 73, "weight": 13 }, { "by": 2, "edge": "gemini-exchange", "gemini-exchange": 79, "key": "ergonomics", "name": "Agent ergonomics", "okx": 77, "weight": 13 }, { "by": 10, "edge": "gemini-exchange", "gemini-exchange": 78, "key": "security", "name": "Security \u0026 auth", "okx": 68, "weight": 14 }, { "by": 20, "edge": "gemini-exchange", "gemini-exchange": 40, "key": "payments", "name": "Payments \u0026 pricing", "okx": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "edge": "gemini-exchange", "gemini-exchange": 88, "key": "maintenance", "name": "Maintenance \u0026 community", "okx": 81, "weight": 7 }, { "by": 13, "edge": "gemini-exchange", "gemini-exchange": 75, "key": "transparency", "name": "Transparency \u0026 trust", "okx": 62, "weight": 7 } ], "summary": "Gemini Exchange API scores 74.6 (BB) on agent readiness against OKX API's 64.3 (B), and leads in every scored category. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "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.", "okx": "OKX publishes per-endpoint rate limits, Read, Trade and Withdraw key permissions with IP binding, demo trading on the production host, and an MIT MCP server with 170 tools, a read-only flag and a permission check at startup. The fee table and privacy policy were not read, no OpenAPI file was found, and the news tools return third-party text." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/gemini-exchange-vs-okx", "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-okx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/gemini-exchange-vs-okx.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/gemini-exchange-vs-okx.min.md" }, "markdown": "Gemini Exchange API scores 74.6 (BB) on agent readiness against OKX API's 64.3 (B), and leads in every scored category. Both do exchange market data.\n\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- OKX API: grade B, 64.3/100, rank #413 of 1349. Markdown https://www.anchorterminal.com/tools/okx.md · JSON https://www.anchorterminal.com/api/v1/tools/okx.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Which one, for what\n\n### 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 65\n- Schema \u0026 documentation, 88 against 73\n- Security \u0026 auth, 78 against 68\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 88 against 81\n- Transparency \u0026 trust, 75 against 62\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\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### OKX API (B)\n\nGood for: An agent trading spot, perpetuals, futures or options on a person's OKX account from a local machine, with demo trading to test first and grid or DCA bots through the kit.\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The fee table loads by script and the fee FAQ defers to the logged-in view, so maker and taker rates were not read\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Gemini Exchange API +20\n\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- OKX API (20): No machine payment protocol (0). The fee table loads by script and the fee FAQ defers to the logged-in view, so no rate was read (0 of 20, unchecked). Public market data and demo trading need no funded account or card (20). A person signs up, verifies and mints a key (0). 0 + 0 + 20 + 0 = 20.\n\n### Schema \u0026 documentation: Gemini Exchange API +15\n\n- Gemini Exchange API (88): OpenAPI 3 for REST (specs/openapi/rest.yaml), AsyncAPI for WebSocket, a prediction-markets OpenAPI file and a specs/index.json catalogue; the MCP server's tools take zod schemas published as JSON Schema (25). llms.txt, llms-full.txt, agents.md, an agent card and an agent skills index (10). Endpoint pages state purpose, the Build an agent guide says what to establish before acting and when to stop, and MCP tool descriptions tell the model when to confirm; the docs don't say when not to use an endpoint (15 of 20). Typed inputs with enums for order types, options and sessions, required fields marked, decimals as strings since 7 July 2026 (12 of 15). Examples throughout, samples in three languages, and an error-codes page with 53 named reasons and their HTTP statuses (14 of 15). A revision history dated from 2015 to 28 October 2026 and versioned paths (v1, v2), but the upcoming-changes page reads \"TBD\" (12 of 15). 25 + 10 + 15 + 12 + 14 + 12 = 88.\n- OKX API (73): No OpenAPI file was found in the V5 docs; the kit's tool definitions are typed TypeScript with annotations, and the organisation has an undescribed ai-builder-openapi-md repository we did not read (12 of 25). okx.com/llms.txt exists and links the API and Agent Trade Kit pages, though the V5 docs have no Markdown twins (5 of 10). Each endpoint states its rate limit, rule, parameters and notes (15 of 20). Enums for ordType, tdMode and instType with required flags (12 of 15). Request and response examples per endpoint and an error code list with messages (14 of 15). A dated changelog with an upcoming-changes section that labels breaking changes and dates sunsets (15). 12 + 5 + 15 + 12 + 14 + 15 = 73.\n\n### Transparency \u0026 trust: Gemini Exchange API +13\n\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- OKX API (62): The editorial half. A closed service with terms that name the contracting entities by region and an API Agreement for agents; the kit is MIT (17 of 30). The privacy policy was not read (5 of 30). The changelog dates sunsets and labels breaking changes, such as port 8443 on 31 October and 16 November 2026 (16 of 20). No subprocessor or data-location statement read; the MCP server is local and its npm package runs a postinstall script whose purpose we did not trace (0 of 20). 17 + 5 + 16 + 0 = 38.\n\n### Security \u0026 auth: Gemini Exchange API +10\n\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- OKX API (68): Key, secret and passphrase with Read, Trade and Withdraw permissions, up to 20 bound IPs, revocation in the account, and unbound Trade or Withdraw keys that expire after 14 idle days; no OAuth (28 of 30). Read-only keys, sub-account keys, demo trading, the kit's --read-only flag and its startup check that hides order tools when the key cannot trade, and an API Agreement requiring minimum scope; no confirmation step in the kit (18 of 20). The news and smartmoney modules return third-party text and the docs read give no guidance on treating it as untrusted (5 of 15). An account audit log tool in the kit and usage records for unbound keys in the Security Center, no per-call log (9 of 15). No security.txt; SECURITY.md with security@okx.com and GitHub private advisories; certifications and a bounty not read (8 of 20). 28 + 18 + 5 + 9 + 8 = 68.\n\n### Reliability: Gemini Exchange API +8\n\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- OKX API (65): Read with the hosted lines on the V5 REST API. okx.com/status is OKX's own page with issue descriptions, maintenance notices and deposit and withdrawal status, but no component history or feed (10 of 20). It lists no incident between 5 August and 3 November 2026; its newest entry is from March 2024, and whether every incident reaches the page cannot be told, so read as clean with a doubt (20 of 30). Rate limits per endpoint, per User ID and per sub-account with numbers, and WebSocket limits (15). Error 50011 on a limit, a clOrdId on orders and a cap of 3 amendments in flight, but no Retry-After or backoff guidance found (10 of 15). No SLA (0). Generally available (10). 10 + 20 + 15 + 10 + 0 + 10 = 65.\n\n### Maintenance \u0026 community: Gemini Exchange API +7\n\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- OKX API (81): Read as a closed service with an open-source kit. Changelog entry of 27 October 2026 and kit v1.5.0 on 28 October (30). Changelog entries on 3, 6, 11, 18, 20 and 26 August, 15, 29 and 30 September and 27 October, and kit releases on 20 and 21 August, 1, 7, 14 and 23 September, 19 and 28 October (20). A public changelog, a Telegram community for the kit and GitHub issues whose replies were not read (10 of 15). python-okx is named as the official SDK and the kit is current; the MCP server is not in the official registry (12 of 15). The kit runs CI on push and pull request across Node 18, 20 and 26 with unit tests and coverage (9 of 10). 30 + 20 + 10 + 12 + 9 = 81.\n\n## Score by category\n\n| Category | Weight | Gemini Exchange API | OKX API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 65 | Gemini Exchange API +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 73 | Gemini Exchange API +15 |\n| Agent ergonomics | 13% (16.2 this run) | 79 | 77 | Gemini Exchange API +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 78 | 68 | Gemini Exchange API +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 20 | Gemini Exchange API +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 88 | 81 | Gemini Exchange API +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 62 | Gemini Exchange API +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.6 · BB** | **64.3 · B** | |\n\n## Facts side by side\n\n| Fact | Gemini Exchange API | OKX API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Gemini Trust Company, LLC | OKX |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | 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 | Proprietary hosted service under OKX's Terms of Service (29 October 2026) and API Agreement (28 July 2026). The Agent Trade Kit (MCP server, CLI and skills) is MIT |\n| Tools exposed | 87 | 170 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-28 | 2026-10-28 |\n| Terms last updated | couldn't be read | 2026-10-29 |\n| Privacy policy last updated | no date given | couldn't be read |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 8 stars, 99 npm/wk | 499 stars, 1.8k npm/wk |\n\n## Verdicts\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**OKX API.** OKX publishes per-endpoint rate limits, Read, Trade and Withdraw key permissions with IP binding, demo trading on the production host, and an MIT MCP server with 170 tools, a read-only flag and a permission check at startup. The fee table and privacy policy were not read, no OpenAPI file was found, and the news tools return third-party text.\n\n## Before you call either\n\n### 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### OKX API\n\n1. Start okx-trade-mcp with --profile demo first, then --read-only on a live key; load only the modules the task needs\n2. Use a sub-account key with Read and Trade only, bound to the agent's IP; an unbound Trade key expires after 14 idle days\n3. Stay under 60 place-order requests per 2 seconds per instrument and at most 3 amendments in flight per order; 50011 means the limit was hit\n4. Send a clOrdId on every order and use the structured error block (code, message, endpoint) to diagnose with read-only tools before retrying\n5. Call us.okx.com or eea.okx.com for US, Australian and EEA accounts; openapi.okx.com does not serve those regions\n\n## Questions\n\n### Which is better for AI agents, Gemini Exchange API or OKX API?\n\nGemini Exchange API scores 74.6 (BB) on agent readiness against OKX API's 64.3 (B), and leads in every scored category.\n\n### Do Gemini Exchange API and OKX API need an API key?\n\nGemini Exchange API takes an API key or an OAuth sign-in. OKX API needs an API key.\n\n### Can an agent call Gemini Exchange API and OKX API without installing anything?\n\nGemini Exchange API runs on your own machine, with no hosted endpoint listed. OKX API runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/gemini-exchange-vs-okx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gemini-exchange-vs-okx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"gemini-exchange\", \"b\": \"okx\"}`. From a terminal: `anchor compare gemini-exchange okx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gemini-exchange.json and https://www.anchorterminal.com/api/v1/tools/okx.json\n\n## Other comparisons with Gemini Exchange API or OKX API\n\n- [Bitfinex API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.md)\n- [Bitfinex API vs OKX API](https://www.anchorterminal.com/compare/bitfinex-vs-okx.md)\n- [Bitget vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.md)\n- [Bitget vs OKX API](https://www.anchorterminal.com/compare/bitget-vs-okx.md)\n- [Bithumb Open API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.md)\n- [Bithumb Open API vs OKX API](https://www.anchorterminal.com/compare/bithumb-vs-okx.md)\n- [Bitstamp API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.md)\n- [Bitstamp API vs OKX API](https://www.anchorterminal.com/compare/bitstamp-vs-okx.md)\n- [Bybit vs Gemini Exchange API](https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.md)\n- [Bybit vs OKX API](https://www.anchorterminal.com/compare/bybit-vs-okx.md)\n- [Crypto.com Exchange API vs Gemini Exchange API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange.md)\n- [Crypto.com Exchange API vs OKX API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx.md)\n- [Gate vs Gemini Exchange API](https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange.md)\n- [Gate vs OKX API](https://www.anchorterminal.com/compare/gate-io-vs-okx.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 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- [HTX trading API vs OKX API](https://www.anchorterminal.com/compare/htx-vs-okx.md)\n- [KuCoin vs OKX API](https://www.anchorterminal.com/compare/kucoin-vs-okx.md)\n- [MEXC API vs OKX API](https://www.anchorterminal.com/compare/mexc-vs-okx.md)\n- [Binance API vs Gemini Exchange API](https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.md)\n- [Binance API vs OKX API](https://www.anchorterminal.com/compare/binance-vs-okx.md)\n- [Coinbase Advanced Trade API vs Gemini Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange.md)\n- [Coinbase Advanced Trade API vs OKX API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Gemini Exchange API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-gemini-exchange.md)\n- [Coinbase MCP server (Coinbase for Agents) vs OKX API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-okx.md)\n- [Kraken API vs OKX API](https://www.anchorterminal.com/compare/kraken-vs-okx.md)\n- [OKX API vs Uniswap Trading API](https://www.anchorterminal.com/compare/okx-vs-uniswap.md)\n- [OKX API vs Upbit Open API](https://www.anchorterminal.com/compare/okx-vs-upbit.md)\n- [Deribit vs Gemini Exchange API](https://www.anchorterminal.com/compare/deribit-vs-gemini-exchange.md)\n- [Deribit vs OKX API](https://www.anchorterminal.com/compare/deribit-vs-okx.md)\n- [dYdX vs Gemini Exchange API](https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.md)\n- [dYdX vs OKX API](https://www.anchorterminal.com/compare/dydx-vs-okx.md)\n- [Hyperliquid vs OKX API](https://www.anchorterminal.com/compare/hyperliquid-vs-okx.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Gemini Exchange API vs OKX API", "url": "" } ], "description": "Gemini Exchange scores 74.6 (BB) to OKX's 64.3 (B) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Gemini Exchange API BB 74.6", "OKX API B 64.3", "scores" ], "h1": "Gemini Exchange API vs OKX API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/gemini-exchange-vs-okx", "published": "2026-10-01", "section": "tools", "title": "Gemini Exchange vs OKX for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-okx" }, "tokens": { "markdown": 5200, "slim": 2930 }, "version": 1 }