{ "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 Kraken API's 71 (BB), and leads in 4 of 7 scored categories.", "b": { "slug": "kraken", "name": "Kraken API", "vendor": "Payward, Inc.", "vendorUrl": "https://docs.kraken.com/api/", "kind": "http-api", "category": "crypto-exchanges", "summary": "Kraken's exchange APIs cover spot, tokenised US stocks, forex and futures over REST, WebSocket and FIX, with rate limits by client tier, a self-service futures demo and kraken-cli, an open-source CLI whose kraken-mcp binary is a local MCP server.", "url": "https://www.anchorterminal.com/tools/kraken", "markdownUrl": "https://www.anchorterminal.com/tools/kraken.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kraken.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kraken.json", "dns": "kraken.grade.anchorterminal.com", "repo": "https://github.com/krakenfx/kraken-cli", "license": "Proprietary hosted service under Kraken's Global Terms of Service (30 October 2026). kraken-cli, which carries the kraken-mcp server, is MIT", "transports": [ "stdio" ], "packages": [], "auth": "mixed", "authNotes": "Spot API key and private key, signed with HMAC-SHA512 over the path, nonce and POST data, sent as API-Key and API-Sign. Permissions per key are Query Funds, Deposit Funds, Withdraw Funds, Query Open Orders \u0026 Trades, Query Closed Orders \u0026 Trades, Modify Orders, Cancel/Close Orders, Query Ledger Entries and Export Data, with optional Key Expiration, IP Address Restriction, a custom nonce window and a WebSocket interface setting. Futures keys are separate. kraken auth login signs in with OAuth (authorisation code with PKCE) in a browser and saves a restricted spot key with no withdrawal rights that expires after at most 90 days, or a read-only one with --read-only (https://support.kraken.com/hc/en-us/articles/360000919966, https://github.com/krakenfx/kraken-cli, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Kraken Pro spot fees at the lowest 30-day volume tier are 0.40 per cent maker and 0.80 per cent taker, stablecoin, pegged token and FX pairs 0.20 per cent each way, and futures 0.02 per cent maker and 0.05 per cent taker. Public market data, paper trading in kraken-cli and the futures demo need no account.", "priceSummary": "0.4% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the CLI or the MCP docs (checked 2026-11-03).", "endpoints": [] }, "toolCount": 152, "popularity": { "githubStars": 795, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.kraken.com/api/", "llmsTxt": "https://raw.githubusercontent.com/krakenfx/kraken-cli/main/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", "cli", "llms-txt", "status-page", "bug-bounty", "rust", "go", "usage-priced", "no-card", "mit" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 71, "grade": "BB", "agentReady": true, "rank": 159, "ranked": true, "rankOf": 1349, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 81, "payments": 40, "reliability": 67, "schema": 80, "security": 80, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Kraken pairs a documented REST, WebSocket and FIX API with the open-source kraken-cli, whose kraken-mcp server gates 33 dangerous tools behind approval and signs in by OAuth with a no-withdrawal key. Spot has no self-service sandbox, no OpenAPI file was found, and a 59-minute connectivity outage hit every interface on 30 October 2026.", "bestFor": "An agent that trades spot, xStocks, forex or futures on a person's Kraken account from a local machine, with paper trading to test first and an approval gate on live orders.", "strengths": [ "Official local MCP server with 152 typed tools in services, destructive_hint on dangerous tools and an elicitation approval before each unless disabled", "OAuth sign-in from the CLI mints a restricted spot key with no withdrawal rights that expires within 90 days, or a read-only key", "Rate limits published with numbers by client tier for REST and the matching engine, shared across REST, WebSocket and FIX", "Fees published without login, 0.40 per cent maker and 0.80 per cent taker at the lowest Pro tier, 0.02 and 0.05 on futures", "Dated changelog of 120 entries with deprecations announced by date, a Statuspage site with API components and a valid security.txt" ], "weaknesses": [ "No self-service spot sandbox; the spot UAT environment is on request through an account manager, and paper trading lives in the CLI", "No OpenAPI file was found for the REST API; the machine-readable contract is the CLI's tool catalogue", "Spot and derivatives clients could not connect or submit orders on any interface for 59 minutes on 30 October 2026", "The CLI's feedback tool can upload a local file it names with no approval step, so the docs say to drop it for agents reading untrusted input", "The terms bar bots, scripts and third-party applications on Kraken's content without written consent, alongside the documented API" ], "agentNotes": [ "Start kraken-mcp with -s market,paper,feedback or the default services; add trade only with a least-privilege key, and never pass --allow-dangerous on an agent that reads untrusted input", "Ask the person to run kraken auth login in their own terminal; it needs a browser and saves a no-withdrawal key that expires in 90 days at most", "Send a fresh --cl-ord-id on each order and run it with --validate first; after a network error look the order up before sending it again", "Keep the nonce strictly increasing per key and stay under the tier's counter, since EAPI:Rate limit exceeded has no Retry-After header", "Test strategies in a paper workspace, which fills at live prices with no account, before a live workspace" ], "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": 71 } ], "editorialScores": { "ergonomics": 79, "maintenance": 81, "payments": 40, "reliability": 67, "schema": 80, "security": 80, "transparency": 36 }, "provenanceScore": 94, "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": "curl --proto '=https' --tlsv1.2 -LsSf https://github.com/krakenfx/kraken-cli/releases/latest/download/kraken-cli-installer.sh | sh", "http": "curl https://api.kraken.com/0/public/Ticker?pair=XBTUSD", "claudeCode": "claude mcp add --scope user kraken -- kraken-mcp -s market,paper,feedback", "config": { "mcpServers": { "kraken": { "args": [ "-s", "market,paper,feedback" ], "command": "kraken-mcp" } } } }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/kraken" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, maker, tier 1", "unit": "pct", "usd": 0.4, "note": "Kraken Pro, under $10,000 30-day volume" }, { "item": "Spot trade, taker, tier 1", "unit": "pct", "usd": 0.8, "note": "Kraken Pro, under $10,000 30-day volume" }, { "item": "Futures trade, maker, tier 1", "unit": "pct", "usd": 0.02, "note": "under $5M 30-day volume" }, { "item": "Futures trade, taker, tier 1", "unit": "pct", "usd": 0.05, "note": "under $5M 30-day volume" } ], "provenance": { "legalEntity": "Payward, Inc.", "domain": "kraken.com", "domainRegistered": "2000-04-03", "endpointOnVendorDomain": true, "terms": "https://www.kraken.com/legal/global-terms", "privacy": "https://www.kraken.com/legal/privacy", "statusPage": "https://status.kraken.com", "changelog": "https://docs.kraken.com/api/docs/change-log", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The Global Terms of Service (last updated 30 October 2026) name Payward Interactive, Inc., Payward Ltd., Bit Trade Pty Limited and Payward Trading Ltd as contracting entities by region under California law; the site footer is © 2011 to 2026 Payward, Inc. The privacy notice was linked from the legal hub and not read.", "RDAP gives kraken.com a registration date of 3 April 2000, before the exchange's 2011 founding.", "https://www.kraken.com/.well-known/security.txt names bugbounty@kraken.com and a bug bounty policy page on kraken.com, expiring 13 February 2027.", "www.kraken.com, docs.kraken.com and support.kraken.com robots.txt disallow only /u/ and /lp/ (docs allows all but /cdn-cgi/ and /_next/).", "status.kraken.com is a Statuspage site; its history page renders by script, so incidents were read from its incidents.json feed, which reached back to 4 September 2026." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kraken.json", "live": { "slug": "kraken", "vendorStatus": { "page": "https://status.kraken.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-04T19:31:42.054244668Z" }, "securityTxt": { "url": "https://kraken.com/.well-known/security.txt", "state": "valid", "expires": "2027-02-13T00:00:00.000Z", "checkedAt": "2026-11-04T15:54:35.804472383Z" }, "updatedAt": "2026-11-04T19:31:42.054244668Z" } }, "edges": [ { "by": 10, "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 clear terms naming regional Payward entities under California law; the CLI is MIT (15 of 30). The privacy notice was not read (5 of 30). The changelog dates deprecations and the terms carry a last-updated date (16 of 20). No subprocessor or data-location statement read (0 of 20). 15 + 5 + 16 + 0 = 36." }, "scores": { "a": 75, "b": 65 } }, { "by": 8, "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 for the REST API in the docs read; the CLI's agents/tool-catalog.json gives JSON Schema inputs for all 188 commands and the 152 MCP tools (15 of 25). The docs serve Markdown twins such as quickstart.md and the CLI ships llms.txt, AGENTS.md and CONTEXT.md (10). Endpoint pages and guides on order lifecycle, errors and rate limits say what each call does, with less on when not to use one (15 of 20). Enums for order types, time in force and flags, and enums and required fields in the tool catalogue (12 of 15). Python, Node.js and cURL examples, an errors guide and the CLI's error-catalog.json with retry guidance (13 of 15). A changelog of 120 dated entries with deprecations dated (15). 15 + 10 + 15 + 12 + 13 + 15 = 80." }, "scores": { "a": 88, "b": 80 } }, { "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 client. Changelog entry of 27 October 2026 and kraken-cli v0.5.1 on 29 October (30). Fourteen changelog entries since 19 August 2026 and CLI tags on 6 and 7 August and 28 and 29 October (20). A public changelog, api@kraken.com, a status page and a CLI repository merging pull requests at the end of October; issue replies not read (11 of 15). An official Rust SDK pushed in October 2026 and a Go module from January; the MCP server is not in the official registry (12 of 15). The CLI has release and secure SDLC workflows, deny.toml and a pinned toolchain; the SDK's CI not read (8 of 10). 30 + 20 + 11 + 12 + 8 = 81." }, "scores": { "a": 88, "b": 81 } }, { "by": 6, "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 spot API. status.kraken.com is a Statuspage site with REST, WebSocket and FIX components (20). The incidents feed read covers 4 September to 3 November 2026. On 30 October spot and derivatives clients could not connect or submit orders across web, mobile, REST, WebSocket and FIX for 59 minutes 39 seconds, rated minor by Kraken; on 28 October some FIX clients were rejected on reconnection for 1 hour 59 minutes while other interfaces worked; the futures engine was degraded for 3 minutes on 13 October. A whole-exchange order outage 21 seconds short of an hour is read as one major (10 of 30). Numeric limits per key by tier and per pair for the matching engine (15). EAPI:Rate limit exceeded and EService:Throttled with a retry timestamp, a client order id and a validate flag on orders, but no Retry-After header (12 of 15). No SLA (0). Generally available (10). 20 + 10 + 15 + 12 + 0 + 10 = 67." }, "scores": { "a": 73, "b": 67 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Gemini Trust Company, LLC", "b": "Payward, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "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 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 Kraken's Global Terms of Service (30 October 2026). kraken-cli, which carries the kraken-mcp server, is MIT", "name": "Licence" }, { "a": "87", "b": "152", "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-29", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-10-30", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-10-21", "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": "yes", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "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": "795 stars", "name": "Popularity" } ], "faq": [ { "answer": "Gemini Exchange API scores 74.6 (BB) on agent readiness against Kraken API's 71 (BB), and leads in 4 of 7 scored categories.", "question": "Which is better for AI agents, Gemini Exchange API or Kraken API?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Gemini Exchange API and Kraken API need an API key?" }, { "answer": "Gemini Exchange API runs on your own machine, with no hosted endpoint listed. Kraken API runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Gemini Exchange API and Kraken API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 73 against 67", "Schema \u0026 documentation, 88 against 80", "Maintenance \u0026 community, 88 against 81", "Transparency \u0026 trust, 75 against 65" ], "also": null, "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 that trades spot, xStocks, forex or futures on a person's Kraken account from a local machine, with paper trading to test first and an approval gate on live orders.", "slug": "kraken", "watchFor": "No self-service spot sandbox; the spot UAT environment is on request through an account manager, and paper trading lives in the CLI" } ], "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-kraken.json", "title": "Bitfinex API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-kraken" }, { "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-kraken.json", "title": "Bitget vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitget-vs-kraken" }, { "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-kraken.json", "title": "Bithumb Open API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-kraken" }, { "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-kraken.json", "title": "Bitstamp API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken" }, { "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-kraken.json", "title": "Bybit vs Kraken API", "url": "https://www.anchorterminal.com/compare/bybit-vs-kraken" }, { "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-kraken.json", "title": "Crypto.com Exchange API vs Kraken API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken" }, { "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-kraken.json", "title": "Gate vs Kraken API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-kraken" }, { "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-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/htx-vs-kraken.json", "title": "HTX trading API vs Kraken API", "url": "https://www.anchorterminal.com/compare/htx-vs-kraken" }, { "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-kraken.json", "title": "Binance API vs Kraken API", "url": "https://www.anchorterminal.com/compare/binance-vs-kraken" }, { "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-kraken.json", "title": "Coinbase Advanced Trade API vs Kraken API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken" }, { "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-kraken.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Kraken API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-kucoin.json", "title": "Kraken API vs KuCoin", "url": "https://www.anchorterminal.com/compare/kraken-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-mexc.json", "title": "Kraken API vs MEXC API", "url": "https://www.anchorterminal.com/compare/kraken-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/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/kraken-vs-uniswap.json", "title": "Kraken API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/kraken-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-upbit.json", "title": "Kraken API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/kraken-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-kraken.json", "title": "Deribit vs Kraken API", "url": "https://www.anchorterminal.com/compare/deribit-vs-kraken" }, { "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-kraken.json", "title": "dYdX vs Kraken API", "url": "https://www.anchorterminal.com/compare/dydx-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-kraken.json", "title": "Hyperliquid vs Kraken API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-kraken" } ], "panel": null, "scores": [ { "by": 6, "edge": "gemini-exchange", "gemini-exchange": 73, "key": "reliability", "kraken": 67, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "gemini-exchange", "gemini-exchange": 88, "key": "schema", "kraken": 80, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 0, "edge": "", "gemini-exchange": 79, "key": "ergonomics", "kraken": 79, "name": "Agent ergonomics", "weight": 13 }, { "by": 2, "edge": "kraken", "gemini-exchange": 78, "key": "security", "kraken": 80, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "edge": "", "gemini-exchange": 40, "key": "payments", "kraken": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "edge": "gemini-exchange", "gemini-exchange": 88, "key": "maintenance", "kraken": 81, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 10, "edge": "gemini-exchange", "gemini-exchange": 75, "key": "transparency", "kraken": 65, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Gemini Exchange API scores 74.6 (BB) on agent readiness against Kraken API's 71 (BB), and leads in 4 of 7 scored categories. 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.", "kraken": "Kraken pairs a documented REST, WebSocket and FIX API with the open-source kraken-cli, whose kraken-mcp server gates 33 dangerous tools behind approval and signs in by OAuth with a no-withdrawal key. Spot has no self-service sandbox, no OpenAPI file was found, and a 59-minute connectivity outage hit every interface on 30 October 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken", "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken.min.md" }, "markdown": "Gemini Exchange API scores 74.6 (BB) on agent readiness against Kraken API's 71 (BB), and leads in 4 of 7 scored categories. 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- Kraken API: grade BB, 71/100, rank #159 of 1349. Markdown https://www.anchorterminal.com/tools/kraken.md · JSON https://www.anchorterminal.com/api/v1/tools/kraken.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 67\n- Schema \u0026 documentation, 88 against 80\n- Maintenance \u0026 community, 88 against 81\n- Transparency \u0026 trust, 75 against 65\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### Kraken API (BB)\n\nGood for: An agent that trades spot, xStocks, forex or futures on a person's Kraken account from a local machine, with paper trading to test first and an approval gate on live orders.\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No self-service spot sandbox; the spot UAT environment is on request through an account manager, and paper trading lives in the CLI\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Gemini Exchange API +10\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- Kraken API (65): The editorial half. A closed service with clear terms naming regional Payward entities under California law; the CLI is MIT (15 of 30). The privacy notice was not read (5 of 30). The changelog dates deprecations and the terms carry a last-updated date (16 of 20). No subprocessor or data-location statement read (0 of 20). 15 + 5 + 16 + 0 = 36.\n\n### Schema \u0026 documentation: Gemini Exchange API +8\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- Kraken API (80): No OpenAPI file was found for the REST API in the docs read; the CLI's agents/tool-catalog.json gives JSON Schema inputs for all 188 commands and the 152 MCP tools (15 of 25). The docs serve Markdown twins such as quickstart.md and the CLI ships llms.txt, AGENTS.md and CONTEXT.md (10). Endpoint pages and guides on order lifecycle, errors and rate limits say what each call does, with less on when not to use one (15 of 20). Enums for order types, time in force and flags, and enums and required fields in the tool catalogue (12 of 15). Python, Node.js and cURL examples, an errors guide and the CLI's error-catalog.json with retry guidance (13 of 15). A changelog of 120 dated entries with deprecations dated (15). 15 + 10 + 15 + 12 + 13 + 15 = 80.\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- Kraken API (81): Read as a closed service with an open-source client. Changelog entry of 27 October 2026 and kraken-cli v0.5.1 on 29 October (30). Fourteen changelog entries since 19 August 2026 and CLI tags on 6 and 7 August and 28 and 29 October (20). A public changelog, api@kraken.com, a status page and a CLI repository merging pull requests at the end of October; issue replies not read (11 of 15). An official Rust SDK pushed in October 2026 and a Go module from January; the MCP server is not in the official registry (12 of 15). The CLI has release and secure SDLC workflows, deny.toml and a pinned toolchain; the SDK's CI not read (8 of 10). 30 + 20 + 11 + 12 + 8 = 81.\n\n### Reliability: Gemini Exchange API +6\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- Kraken API (67): Read with the hosted lines on the spot API. status.kraken.com is a Statuspage site with REST, WebSocket and FIX components (20). The incidents feed read covers 4 September to 3 November 2026. On 30 October spot and derivatives clients could not connect or submit orders across web, mobile, REST, WebSocket and FIX for 59 minutes 39 seconds, rated minor by Kraken; on 28 October some FIX clients were rejected on reconnection for 1 hour 59 minutes while other interfaces worked; the futures engine was degraded for 3 minutes on 13 October. A whole-exchange order outage 21 seconds short of an hour is read as one major (10 of 30). Numeric limits per key by tier and per pair for the matching engine (15). EAPI:Rate limit exceeded and EService:Throttled with a retry timestamp, a client order id and a validate flag on orders, but no Retry-After header (12 of 15). No SLA (0). Generally available (10). 20 + 10 + 15 + 12 + 0 + 10 = 67.\n\n## Score by category\n\n| Category | Weight | Gemini Exchange API | Kraken API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 67 | Gemini Exchange API +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 80 | Gemini Exchange API +8 |\n| Agent ergonomics | 13% (16.2 this run) | 79 | 79 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 78 | 80 | Kraken API +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\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 | 65 | Gemini Exchange API +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.6 · BB** | **71 · BB** | |\n\n## Facts side by side\n\n| Fact | Gemini Exchange API | Kraken API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Gemini Trust Company, LLC | Payward, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | 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 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 Kraken's Global Terms of Service (30 October 2026). kraken-cli, which carries the kraken-mcp server, is MIT |\n| Tools exposed | 87 | 152 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-28 | 2026-10-29 |\n| Terms last updated | couldn't be read | 2026-10-30 |\n| Privacy policy last updated | no date given | 2026-10-21 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | yes |\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 | 795 stars |\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**Kraken API.** Kraken pairs a documented REST, WebSocket and FIX API with the open-source kraken-cli, whose kraken-mcp server gates 33 dangerous tools behind approval and signs in by OAuth with a no-withdrawal key. Spot has no self-service sandbox, no OpenAPI file was found, and a 59-minute connectivity outage hit every interface on 30 October 2026.\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### Kraken API\n\n1. Start kraken-mcp with -s market,paper,feedback or the default services; add trade only with a least-privilege key, and never pass --allow-dangerous on an agent that reads untrusted input\n2. Ask the person to run kraken auth login in their own terminal; it needs a browser and saves a no-withdrawal key that expires in 90 days at most\n3. Send a fresh --cl-ord-id on each order and run it with --validate first; after a network error look the order up before sending it again\n4. Keep the nonce strictly increasing per key and stay under the tier's counter, since EAPI:Rate limit exceeded has no Retry-After header\n5. Test strategies in a paper workspace, which fills at live prices with no account, before a live workspace\n\n## Questions\n\n### Which is better for AI agents, Gemini Exchange API or Kraken API?\n\nGemini Exchange API scores 74.6 (BB) on agent readiness against Kraken API's 71 (BB), and leads in 4 of 7 scored categories.\n\n### Do Gemini Exchange API and Kraken API need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Gemini Exchange API and Kraken API without installing anything?\n\nGemini Exchange API runs on your own machine, with no hosted endpoint listed. Kraken 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-kraken.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"gemini-exchange\", \"b\": \"kraken\"}`. From a terminal: `anchor compare gemini-exchange kraken`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gemini-exchange.json and https://www.anchorterminal.com/api/v1/tools/kraken.json\n\n## Other comparisons with Gemini Exchange API or Kraken API\n\n- [Bitfinex API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.md)\n- [Bitfinex API vs Kraken API](https://www.anchorterminal.com/compare/bitfinex-vs-kraken.md)\n- [Bitget vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.md)\n- [Bitget vs Kraken API](https://www.anchorterminal.com/compare/bitget-vs-kraken.md)\n- [Bithumb Open API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-gemini-exchange.md)\n- [Bithumb Open API vs Kraken API](https://www.anchorterminal.com/compare/bithumb-vs-kraken.md)\n- [Bitstamp API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.md)\n- [Bitstamp API vs Kraken API](https://www.anchorterminal.com/compare/bitstamp-vs-kraken.md)\n- [Bybit vs Gemini Exchange API](https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.md)\n- [Bybit vs Kraken API](https://www.anchorterminal.com/compare/bybit-vs-kraken.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 Kraken API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken.md)\n- [Gate vs Gemini Exchange API](https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange.md)\n- [Gate vs Kraken API](https://www.anchorterminal.com/compare/gate-io-vs-kraken.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 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- [HTX trading API vs Kraken API](https://www.anchorterminal.com/compare/htx-vs-kraken.md)\n- [Binance API vs Gemini Exchange API](https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.md)\n- [Binance API vs Kraken API](https://www.anchorterminal.com/compare/binance-vs-kraken.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 Kraken API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken.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 Kraken API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-kraken.md)\n- [Kraken API vs KuCoin](https://www.anchorterminal.com/compare/kraken-vs-kucoin.md)\n- [Kraken API vs MEXC API](https://www.anchorterminal.com/compare/kraken-vs-mexc.md)\n- [Kraken API vs OKX API](https://www.anchorterminal.com/compare/kraken-vs-okx.md)\n- [Kraken API vs Uniswap Trading API](https://www.anchorterminal.com/compare/kraken-vs-uniswap.md)\n- [Kraken API vs Upbit Open API](https://www.anchorterminal.com/compare/kraken-vs-upbit.md)\n- [Deribit vs Gemini Exchange API](https://www.anchorterminal.com/compare/deribit-vs-gemini-exchange.md)\n- [Deribit vs Kraken API](https://www.anchorterminal.com/compare/deribit-vs-kraken.md)\n- [dYdX vs Gemini Exchange API](https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.md)\n- [dYdX vs Kraken API](https://www.anchorterminal.com/compare/dydx-vs-kraken.md)\n- [Hyperliquid vs Kraken API](https://www.anchorterminal.com/compare/hyperliquid-vs-kraken.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 Kraken API", "url": "" } ], "description": "Gemini Exchange scores 74.6 (BB) to Kraken's 71 (BB) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Gemini Exchange API BB 74.6", "Kraken API BB 71", "scores" ], "h1": "Gemini Exchange API vs Kraken API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/gemini-exchange-vs-kraken", "published": "2026-10-01", "section": "tools", "title": "Gemini Exchange vs Kraken for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kraken" }, "tokens": { "markdown": 4550, "slim": 2280 }, "version": 1 }