/vendor/kraken/AgentRouting.json or
/vendor/kraken/AgentContext.json directly.
kraken.com
Overview
Does kraken.com support MCP?
No confirmed MCP support was found for kraken.com as of 2026-06-28.
What agentic protocols does kraken.com support?
As of 2026-06-28, kraken.com has confirmed support for proprietary.
Is kraken.com's API publicly accessible or partner-gated?
Open.
Does kraken.com explicitly prohibit automated access?
Yes. kraken.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is kraken.com agent-ready?
Partial. kraken.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence found that Kraken (kraken.com, the crypto exchange) supports or has implemented the A2A/Agent2Agent protocol. Kraken's AI-agent strategy centers on its own Kraken CLI with native MCP server support, not A2A. Named A2A launch partners include Atlassian, Box, Cohere, Salesforce, SAP, PayPal, and ServiceNow — Kraken is not among them.
Two targeted searches found no evidence that Kraken (kraken.com, the cryptocurrency exchange) participates in or has announced support for the Agentic Commerce Protocol. Named ACP launch and early partners identified in search results include URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, Ashley Furniture, Etsy, and Shopify merchants — all retail/e-commerce companies, not crypto exchanges. Kraken's product domain (digital asset trading, crypto custody) is structurally outside the retail checkout use case ACP targets.
No evidence found that Kraken (kraken.com) is a launch partner, listed adopter, or has any documented implementation of the Agent Payments Protocol (AP2). The Google Cloud AP2 announcement highlights crypto/Web3 collaboration with Coinbase, Ethereum Foundation, and MetaMask — not Kraken. No Kraken-specific AP2 references surfaced in searches covering both the FIDO Alliance donation announcement and crypto-sector AP2 adoption. Not_found rather than confirmed_absent because Kraken has not issued any statement specifically declining to adopt AP2.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Kraken has a confirmed partnership with Tempo (Tempo's first US centralized exchange partner), providing on/off-ramps, custody, and institutional settlement infrastructure for Tempo's stablecoin chain. However, no evidence was found that Kraken has implemented or exposed the MPP protocol itself — their role is as an institutional liquidity and settlement venue for Tempo, not as an MPP-callable endpoint. Named MPP launch participants include Stripe, Tempo, MultiversX, and xpay.sh, but not Kraken. The Kraken/Tempo relationship is infrastructure-layer, not a vendor-specific MPP integration.
No evidence that kraken.com has implemented NLWeb. Microsoft's published NLWeb pioneer/partner list includes Chicago Public Media, Common Sense Media, DDM (Allrecipes & Serious Eats), Milvus, Shopify, and Snowflake — Kraken does not appear. No /ask or /mcp endpoints attributable to kraken.com were found in any search result.
Kraken (kraken.com) is a cryptocurrency exchange offering trading, futures, staking, and payments — not a retail commerce merchant. UCP is a Google/Shopify-led agentic checkout protocol designed for retail merchants. No evidence was found of Kraken implementing, announcing, or participating in UCP. Searches of kraken.com, Kraken developer docs, and UCP ecosystem listings (ucp.dev, ucpchecker.com) returned no Kraken-specific UCP references; the 'protocols' language in Kraken's own developer docs refers exclusively to REST, WebSocket, and FIX for their trading API.
No evidence that Kraken (kraken.com) has implemented or announced support for the WebMCP browser-native agent protocol. Known early adopters and referenced implementers in the WebMCP ecosystem include HubSpot, Cloudflare (via Browser Run), and browser vendors Google Chrome and Microsoft Edge — none of the identified launch-partner contexts mention Kraken or any crypto exchange. This is a not_found rather than confirmed_absent because no vendor-specific statement or deprecation notice from Kraken addresses WebMCP.
No evidence of kraken.com involvement in x402 in either a targeted search or a broad x402 ecosystem/launch-partner search. Known named participants in the x402 ecosystem include Coinbase (originator), Cloudflare (x402 Foundation co-founder), Stripe, and Solana — Kraken appears in none of these lists. Sketchiness rated insufficient_data as no kraken.com-specific surface was examined.
No evidence of a first-party Kraken (kraken.com) app built on the OpenAI ChatGPT Apps SDK was found. The OpenAI ChatGPT app directory pilot partners (Booking.com, Canva, Coursera, Figma, etc.) do not include Kraken. A third-party app called 'Trade It' supports Kraken accounts as one of several connected brokerages, but that is not a Kraken-published Apps SDK integration. Kraken's own AI agent strategy centers on a Kraken CLI with MCP support (blog.kraken.com), not the ChatGPT Apps SDK.
Spot exchange API covering market data, order management, account balances, ledger, and staking via REST and WebSocket. Full trading capability including public (unauthenticated) market data and private (authenticated) order/account endpoints.
Kraken's Spot proprietary REST+WebSocket API is fully documented at https://docs.kraken.com/rest/. Public endpoints require no auth; private endpoints require an API key pair with HMAC-SHA512 signing. No named standard (e.g. FIX) underlies this interface — it is Kraken's own design. Self-serve key generation, no partner program required.
Derivatives/Futures exchange API (separate trading engine from Spot) covering perpetual and fixed-maturity futures contracts — order placement, position management, market data feeds — via REST and WebSocket. Entirely distinct endpoints, credentials, and auth flow from the Spot API.
Kraken's Derivatives/Futures proprietary API is documented at https://docs.kraken.com/api/docs/guides/futures-rest/. It is a genuinely distinct surface from the Spot API: separate base domain for key management (futures.kraken.com), different authentication algorithm, different rate-limit rules, and different endpoint paths. A sandbox/demo environment is also available for development testing.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Summary
Has agent interface: partial
Verify whether Kraken's published MCP server (referenced in their own blog at blog.kraken.com in the context of their Kraken CLI) constitutes a remotely callable agent interface or is CLI-local only; if remote, record a confirmed_present MCP entry. Also confirm whether the Derivatives/Futures API sandbox endpoint is publicly accessible without partner approval.
AgentContext
Five categories were checked for Kraken (kraken.com): pricing discrepancies, availability/inventory accuracy, merchant-of-record identity, policy enforcement consistency, and undisclosed transactional constraints. For pricing, searches found no evidence of a gap between quoted and charged amounts; Kraken's fee schedule explicitly disclaims hidden fees and no regulatory action has established otherwise. For availability, scheduled asset delistings were found to be publicly announced in advance, and no bait-and-switch or ghost-inventory pattern was identified. For identity, a now-dismissed SEC lawsuit and an ongoing B2B custody dispute with Etana were surfaced but neither constitutes a consumer-facing counterparty ambiguity; Kraken's published terms clearly name the contracting entities. For policy, 492 CFPB complaints were reviewed but centered on fraud and account-access issues rather than a documented gap between stated and enforced policies. For undisclosed constraints, Kraken's own support documentation covering verification tiers, withdrawal holds, and geo-restrictions was located, indicating the limitation framework is published even if not always prominently surfaced. No category produced a finding that rises to the level of a specific, independently verified discrepancy warranting an agent handoff trigger.