/vendor/coinbase/AgentRouting.json or
/vendor/coinbase/AgentContext.json directly.
coinbase.com
Overview
Does coinbase.com support MCP?
Yes. coinbase.com has a confirmed MCP implementation. Onchain wallet and DeFi operations via AgentKit MCP extension (token transfers, wallet management, smart contract calls on Base/EVM); plus a separate 'Coinbase for Agents' MCP (launched June 2026) enabling AI agents to trade, pay, and execute workflows against a user's Coinbase account; and a developer-facing x402 MCP server bridging paid API access via the HTTP 402 payment protocol.
What agentic protocols does coinbase.com support?
As of 2026-06-28, coinbase.com has confirmed support for A2A, MCP, x402, and proprietary.
Is coinbase.com's API publicly accessible or partner-gated?
Access varies by protocol: open, partner only.
Does coinbase.com explicitly prohibit automated access?
Yes. coinbase.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is coinbase.com agent-ready?
Yes. coinbase.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.
Protocols
A2A serves as the messaging/coordination layer within Coinbase's AP2 (Agent Payments Protocol), co-developed with Google. Coinbase's x402 stablecoin payment rail is layered on top of A2A's agent-to-agent communication fabric, enabling agents to coordinate and pay each other using USDC. Scope is limited to payment and commerce coordination flows; Coinbase is a protocol co-author and infrastructure provider, not an A2A endpoint consumer.
Coinbase and Google jointly launched the Agent Payments Protocol (AP2) in September 2025, which layers Coinbase's x402 payment rail on top of Google's A2A framework. Evidence is from Coinbase's own developer platform blog at https://www.coinbase.com/developer-platform/discover/launches/google_x402. Coinbase is a co-creator of AP2 and contributes the payment infrastructure; A2A usage here is confirmed by Coinbase's own published documentation.
No evidence found that Coinbase (coinbase.com) has adopted or integrated the OpenAI/Stripe Agentic Commerce Protocol as a merchant or platform participant. Coinbase is associated with the entirely separate x402 protocol, which is its own agentic payments initiative. Named ACP launch and merchant partners found in research include Shopify, PayPal, Walmart, Target, Sephora, Nordstrom, Best Buy, Lowe's, and Wayfair — Coinbase does not appear in any of these lists. Choosing not_found rather than confirmed_absent because no vendor-specific statement from Coinbase explicitly ruling out ACP participation was located.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Onchain wallet and DeFi operations via AgentKit MCP extension (token transfers, wallet management, smart contract calls on Base/EVM); plus a separate 'Coinbase for Agents' MCP (launched June 2026) enabling AI agents to trade, pay, and execute workflows against a user's Coinbase account; and a developer-facing x402 MCP server bridging paid API access via the HTTP 402 payment protocol
...
MPP (Machine Payments Protocol) was launched March 2026 by Stripe and Tempo; Coinbase is not a launch partner or participant. Named launch partners include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa. Coinbase operates its own competing agentic payment protocol (x402) on the Base network, positioned as a distinct alternative to MPP.
Microsoft's NLWeb launch partners — as confirmed by VentureBeat and Microsoft's own announcement — include Chicago Public Media, Allrecipes, Eventbrite, Hearst (Delish), O'Reilly Media, Tripadvisor, and Shopify. Coinbase does not appear in any known launch partner list, and no evidence of NLWeb adoption at coinbase.com was found via targeted search. NLWeb is also not a natural fit for a crypto-exchange context, further reducing prior probability of adoption.
No evidence that coinbase.com has adopted or implemented UCP. The protocol's publicly named endorsers (Stripe, Visa, Mastercard, Adyen, Etsy, Wayfair, Target, Walmart) do not include Coinbase. One third-party explainer (eco.com) used Coinbase hypothetically as a payment handler example ('a Coinbase handler might list supported chains and stablecoins'), which is not evidence of actual integration. Coinbase's own agentic payment surface is its separately developed x402 protocol (HTTP 402-based stablecoin payments), which Google's AP2 references alongside UCP but as a distinct mechanism.
Coinbase's documented agent-facing work centers on its Payments MCP server and the x402 payment protocol — not WebMCP. The agenticplug.ai agentic-commerce tracker lists Coinbase alongside Cloudflare, Stripe, and Visa, but that grouping reflects broad agentic-commerce participation, not WebMCP implementation specifically. No Coinbase-specific WebMCP tooling, origin-trial enrollment, or developer documentation was found; confirmed WebMCP adopters include Cloudflare (via Browser Run) but not coinbase.com.
Coinbase is the originator and co-governing foundation member of x402; coinbase.com hosts both the canonical launch documentation and the developer SDK/facilitator infrastructure (TypeScript, Go, Python SDKs; Coinbase-operated payment facilitator endpoint) enabling server-side monetization and client-side stablecoin payment of HTTP resources on Base, Ethereum, Arbitrum, Polygon, and Solana — not a downstream integrator of someone else's protocol
x402 was launched by Coinbase in May 2025 and is co-governed by the x402 Foundation alongside Cloudflare, with Google and Visa as foundation members. Official developer documentation is at https://docs.cdp.coinbase.com/x402/welcome and the launch announcement at https://www.coinbase.com/developer-platform/discover/launches/x402. As of early 2026, the protocol had processed over 119 million transactions on Base alone, with a V2 release (December 2025) adding multi-chain support and reusable sessions.
No evidence that Coinbase has published or submitted an app through OpenAI's ChatGPT Apps SDK platform or the ChatGPT App Directory. Coinbase's ChatGPT-compatible integration ("Coinbase for Agents," launched June 2026; "Base MCP," launched May 2026) uses the Model Context Protocol — a cross-platform standard — not the platform-specific Apps SDK surface. The ChatGPT App Directory's listed crypto apps include MoonPay, Kraken, OKX, CryptoAudit, and RealOpen, but not Coinbase; the not_found designation is chosen over confirmed_absent because no Coinbase-specific statement or deprecation notice was found — simply no evidence of ever building on this platform.
Advanced Trade API: retail and self-directed brokerage REST API (v3) for placing and managing market/limit/stop orders, querying portfolios, fees, and products; endpoint base: https://api.coinbase.com/api/v3/brokerage/
Coinbase's primary consumer-facing trading REST API, documented at docs.cdp.coinbase.com and publicly accessible without a partner relationship. Distinct from the institutional Exchange and Prime APIs in scope and intended user base.
Exchange API: institutional and pro-trader REST + WebSocket API for high-volume order placement, real-time market data, and account management on Coinbase's pro exchange; documented REST and WebSocket feeds are the proprietary surfaces (FIX is a named standard and excluded)
Documented at https://docs.cdp.coinbase.com/exchange/introduction/welcome as part of the Coinbase Developer Platform. Targets higher-frequency traders and institutions; distinct product surface from Advanced Trade and Prime.
Prime API: institutional custody and trading REST API covering order management, portfolio and account administration, real-time market data, and reporting for institutional clients on Coinbase Prime
Documented at https://docs.cdp.coinbase.com/prime/docs/welcome. Requires a Coinbase Prime institutional relationship to obtain credentials; not self-serve for the general public. Distinct in scope and access tier from the retail Advanced Trade and pro Exchange APIs.
Commerce API: merchant-facing REST API for creating crypto payment charges and checkouts, retrieving payment status, and integrating cryptocurrency acceptance into e-commerce applications
Documented at https://docs.cdp.coinbase.com/commerce/integrations/3rd-party-integrations and related Commerce docs pages. Serves a distinct use case (merchant payment acceptance) entirely separate from Coinbase's trading-oriented APIs.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Summary
Has agent interface: true
Integrate directly via Coinbase's confirmed agent-facing surfaces: the MCP servers (AgentKit MCP using CDP API key credentials; 'Coinbase for Agents' MCP using OAuth; x402 MCP server for paid API access), the x402 payment protocol (wallet-signed PAYMENT-SIGNATURE header, no API key required), and the proprietary REST APIs (Advanced Trade, Exchange, Commerce — all open-access; Prime requires institutional relationship). A2A is confirmed present as infrastructure Coinbase co-authors rather than an endpoint to call into. Prioritize MCP and x402 for agentic workflows; use REST APIs for direct trading and commerce integration.
AgentContext
Verified discrepancies
Vendor claim: Coinbase presents users with a quoted price for cryptocurrency purchases and sales, implying that the quoted rate is the price the user will transact at.
What actually happens: Coinbase embeds a hidden 'spread fee' by inflating or deflating the quoted cryptocurrency price before displaying it to the user, meaning the real cost of a transaction is higher than the visible price quote suggests. Users filing a federal class action alleged this markup is concealed within the price and not separately disclosed at the point of search or pre-confirmation, making the all-in cost opaque at checkout.
Agent guidance: When an agent quotes or confirms a buy/sell price on Coinbase's retail interface (coinbase.com), it should explicitly retrieve and add the spread component (advertised as ~0.5%) on top of any stated transaction fee before presenting the all-in cost to the user. The agent should not treat the displayed quote as the final cost; it should prompt the user to review the full fee breakdown on the confirmation screen before submitting the order.
- A California federal court ruled in August 2025 that crypto traders who accused Coinbase of charging hidden 'spread fees' by deceptively inflating cryptocurrency prices and concealing those fees in the price quotes must resolve their dispute in arbitration — confirming the core pricing-deception allegations survive and are being actively litigated.
- Coinbase's own fee disclosure acknowledges a 'spread' of approximately 0.5% built into the quoted price for simple buy/sell transactions on its retail interface, separate from explicit transaction fees — a component that is not always prominently surfaced before a user commits to a trade.
Vendor claim: Coinbase presents itself as a fully-functional platform on which users can buy, sell, and transfer cryptocurrency; account access and transaction capability are implied to be available to any verified user at any time.
What actually happens: Coinbase's own risk models automatically freeze or restrict accounts mid-session based on undisclosed triggers — including the use of a VPN — without warning users in advance that these activities will result in an account lock. Users have reported being locked out of accounts for months or years after triggering an automated restriction during an attempted transaction. The platform's CEO acknowledged in June 2025 that unnecessary account restrictions had been 'a major issue for longer than is acceptable,' and that the problem had only been reduced (by 82%) rather than eliminated.
Agent guidance: Before initiating any transaction on Coinbase, an agent must confirm it is not operating through a VPN or anonymizing proxy, as these are confirmed undisclosed triggers for automated account freezes that will halt the transaction mid-execution. If an account restriction occurs mid-transaction, the agent should not retry; it should surface the block to the user immediately, as restrictions can persist for extended periods and cannot be self-resolved through the platform UI.
Human handoff required for
Escalate to a human when the all-in cost of a Coinbase retail buy or sell order — including the embedded spread (~0.5%) plus any explicit transaction fee — materially exceeds the price shown on the initial quote screen, and the user has not explicitly acknowledged the spread component before submitting the order.
- An active federal class action (Northern District of California, as of August 2025) alleges Coinbase conceals 'spread fees' by inflating quoted cryptocurrency prices, with the court routing the dispute to arbitration rather than dismissing the underlying claims.
- Coinbase's own help documentation acknowledges an embedded spread of approximately 0.5% in retail quoted prices, separate from explicitly stated transaction fees.
Escalate to a human if a Coinbase account becomes restricted or frozen mid-transaction — including cases triggered by VPN or anonymizing proxy usage — because the restriction cannot be self-resolved through the platform UI and may persist for an extended, indeterminate period.
- Coinbase's automated risk system applies account freezes based on triggers including VPN usage that are not disclosed to users prior to transacting, leaving users locked out mid-transaction for months or years.
- Coinbase's CEO acknowledged in June 2025 that unnecessary account restrictions had been 'a major issue for longer than is acceptable,' with the problem reduced by 82% but not eliminated.
Escalate to a human when a user disputes a completed Coinbase transaction on the grounds that the actual execution price differed from the quoted price due to the undisclosed spread, and the user is seeking a fee adjustment or refund — because the platform and user may disagree on whether the spread was disclosed at the point of quote.
- The federal class action alleges Coinbase does not separately disclose the spread at the point of search or pre-confirmation, making the all-in cost opaque and creating a structural basis for post-transaction disputes.
- Coinbase's help documentation describes the spread as an inherent part of the quoted price rather than a line-item fee, which is the core of the disclosure gap alleged by plaintiffs.
Five categories were checked for Coinbase. Pricing discrepancy: a finding was confirmed — Coinbase embeds an undisclosed spread fee in retail quoted prices, supported by an active federal class action and Coinbase's own help documentation. Availability discrepancy: no finding — searches surfaced a May 2024 platform outage and a $0 balance display glitch, but no persistent pattern of bait-and-switch pricing or systematically unavailable quoted rates at execution. Identity discrepancy: no finding — CFPB complaint data and a CFTC settlement were located, but none established a verified merchant-of-record or counterparty identity ambiguity. Policy discrepancy: no finding — high CFPB complaint volume exists, but no regulatory enforcement action documenting a systematic gap between Coinbase's written policies and actual enforcement practice was found. Undisclosed constraint discrepancy: a finding was confirmed — Coinbase's automated risk system freezes accounts based on undisclosed triggers including VPN usage, with the CEO publicly acknowledging the systemic problem as recently as June 2025.