/vendor/moonpay/AgentRouting.json or
/vendor/moonpay/AgentContext.json directly.
moonpay.com
Overview
Does moonpay.com support MCP?
Yes. moonpay.com has a confirmed MCP implementation. Loc al stdio MCP server exposing 54+ crypto operation tools (swaps, bridges, balance checks, fiat on/off ramps, DCA, limit orders, market data) via the MoonPay CLI (`mp mcp`); also a separate documentation-index MCP server for searching MoonPay developer docs.
What agentic protocols does moonpay.com support?
As of 2026-06-29, moonpay.com has confirmed support for MCP, openai_apps_sdk, and proprietary.
Is moonpay.com's API publicly accessible or partner-gated?
Access varies by protocol: open, partner only.
Does moonpay.com explicitly prohibit automated access?
Yes. moonpay.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is moonpay.com agent-ready?
Yes. moonpay.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.
Protocols
No evidence found that MoonPay has implemented or announced support for the Agent2Agent (A2A) protocol. MoonPay operates a payments-for-AI-agents offering called MoonAgents (moonpay.com/agents), but this is their own proprietary agent payments layer, not an A2A-protocol integration. Named A2A launch partners include Atlassian, Box, Cohere, PayPal, Salesforce, and SAP — MoonPay does not appear among them. The Agent Payments Protocol (AP2), a related Google-led initiative built atop A2A, lists Adyen, Coinbase, Mastercard, and PayPal as collaborators — again, not MoonPay.
No evidence that MoonPay has implemented the Agentic Commerce Protocol. ACP's confirmed launch partners are retail merchants — Etsy and Shopify merchants such as Glossier, Vuori, Spanx, and SKIMS. MoonPay does have a ChatGPT app integration, but it operates as a redirect-to-platform flow for crypto token purchases, not an in-chat ACP/Instant Checkout implementation. MoonPay's crypto-infrastructure business model sits outside ACP's current retail e-commerce merchant scope.
No evidence that MoonPay is among the ~60 launch partners that joined Google's AP2 donation to the FIDO Alliance (April 2026). Named partners in the announcement include Adyen, American Express, Coinbase, Mastercard, PayPal, Revolut, and Worldpay — MoonPay does not appear in any of the partner lists or supporting materials found. No_found rather than confirmed_absent because no MoonPay-specific statement on AP2 was located; absence is from omission in partner lists, not a direct vendor denial.
Loc al stdio MCP server exposing 54+ crypto operation tools (swaps, bridges, balance checks, fiat on/off ramps, DCA, limit orders, market data) via the MoonPay CLI (`mp mcp`); also a separate documentation-index MCP server for searching MoonPay developer docs
MoonPay ships a local stdio MCP server via the `@moonpay/cli` npm package (install globally, run `mp mcp`); this is vendor-documented at https://support.moonpay.com/en/articles/586583-moonpay-cli-for-ai-agents and https://support.moonpay.com/en/articles/592667-connect-moonpay-to-any-mcp-compatible-ai. A second, distinct MCP surface exists for querying the MoonPay developer documentation index, documented at https://dev.moonpay.com/platform/overview/using-agents.
MoonPay is not listed among MPP's named launch partners (Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, Visa) per Stripe's MPP blog and the KuCoin announcement. MoonPay's own press release references MPP only to describe the broader agentic payments landscape and to position its own Open Wallet Standard (OWS) as a complementary wallet layer — not as evidence of MPP adoption or participation. No vendor-specific evidence of MoonPay implementing or accepting MPP was found.
MoonPay offers a MCP server via its CLI tool (mp mcp), which is a stdio-based MCP integration for crypto operations — a completely distinct technology from NLWeb. No evidence found of MoonPay implementing NLWeb's /ask or /mcp endpoints as defined by the Microsoft Schema.org-grounded NLWeb framework. Named NLWeb launch partners and reference implementations reference generic websites/retail vendors, not MoonPay.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence found of MoonPay adopting WebMCP. WebMCP (the browser-native window.AICommands protocol co-developed by Google and Microsoft) only entered early Chrome Canary preview in April 2026 and has no publicly known consumer-facing launch partners. MoonPay does expose a standard MCP server for developer documentation queries and a CLI for AI agents, but neither constitutes a WebMCP implementation.
No evidence that MoonPay has adopted x402 as a payment protocol on moonpay.com. MoonPay appears in x402 ecosystem coverage only as a builder of adjacent products: the Open Wallet Standard for AI agent wallet interactions and the MoonAgents Card (a Mastercard-based card product for agent spending). The confirmed x402 launch partners and ecosystem participants are Coinbase, Cloudflare, Google, Stripe, Visa, Circle, Stellar, and NEAR — MoonPay is not among them.
Crypto fiat-to-crypto onramp within ChatGPT: users search 'MoonPay' in the ChatGPT Apps section, connect their MoonPay account, specify a purchase amount conversationally, and receive a checkout link redirecting to moonpay.com for KYC and payment. Supports Bitcoin, Ethereum, Solana, XRP, USDC, and 100+ tokens. Purchase completion occurs off-platform (on MoonPay's website); the in-ChatGPT portion handles discovery and checkout-link generation only.
MoonPay launched as the first and only crypto onramp in ChatGPT's App Store on May 22, 2026; multiple independent sources confirm this. The integration is user-facing (not developer-callable), with access via the ChatGPT Apps directory—no API key or partner approval required to use it. KYC and final payment are completed on moonpay.com, not within the ChatGPT interface.
Hosted widget integration for fiat-to-crypto on-ramp and off-ramp: partners embed a MoonPay-hosted UI that handles KYC, payments, and transaction lifecycle; supporting REST endpoints cover buy/sell quotes, currency/country availability, transaction lookup, and webhook notifications. Auth uses a publishable API key plus HMAC-SHA256 signature appended to widget URLs; webhooks include a Moonpay-Signature-V2 header for verification.
MoonPay's primary partner integration surface, documented at https://dev.moonpay.com/api-reference/widget. Covers on-ramp, off-ramp, swap pairs, and NFT checkout as a single widget-plus-REST product family. Requires a partner API key; no open self-serve credential issuance was confirmed.
Programmatic Virtual Accounts API: allows partners to provision virtual bank accounts for end-customers and retrieve associated fiat transaction data without embedding a hosted widget. Distinct from the widget surface in both auth mechanism and integration model — designed for partners who want full control over the UX.
Documented at https://dev.moonpay.com/docs/api-reference. Sandbox environment with sample transactions available for integration testing. Architecturally separate from the widget API: no hosted UI involvement, purely programmatic REST access to virtual account and transaction data.
Swaps API: DEX token swap pairs, quote generation, swap execution, and DeFi token list lookups. Listed as a distinct product line in the widget API reference alongside ramp endpoints, with its own architecture documentation.
Architecture documented at https://dev.moonpay.com/docs/swaps-api-architecture. Exposed both as standalone endpoints and as part of the widget SDK event system (SDK+API Swaps product). Distinct from on/off-ramp endpoints in scope and asset types covered.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Summary
Has agent interface: true
Integrate via the vendor-documented MoonPay CLI MCP server (`@moonpay/cli` npm package, `mp mcp` command) for agent-callable crypto operations; for partner embedding of fiat on/off-ramp flows, apply for a partner API key to access the widget and REST APIs at dev.moonpay.com.
AgentContext
Verified discrepancies
Vendor claim: MoonPay Commerce is presented as a payment service provider enabling merchants to accept crypto payments. MoonPay's own help documentation states that all transactions on the MoonPay Commerce platform are 'direct peer-to-peer payments' and instructs buyers: 'For refunds, please contact the merchant directly.' MoonPay simultaneously implies it is the infrastructure facilitating the transaction.
What actually happens: MoonPay occupies a contradictory position: it operates the payment rails, collects fees, and is recognized by at least one financial regulator as the merchant of record when payment flows through it — yet its published Commerce FAQ explicitly disclaims any ability to resolve disputes or reverse payments, redirecting consumers to an unnamed third-party 'merchant.' A UK Financial Ombudsman decision (DRN-3879035) confirmed that when a consumer paid MoonPay, Monzo's chargeback could only target MoonPay as the merchant of record, not any downstream party — yet MoonPay's own help materials tell buyers to seek redress from someone else. The result is that a consumer completing a transaction through MoonPay Commerce has no enforceable dispute path: MoonPay disclaims responsibility, and the underlying merchant may be unreachable.
Agent guidance: Before completing any purchase through a MoonPay Commerce-powered checkout, an agent should explicitly confirm in writing (via the merchant's own direct channel) who the legal counterparty is and what the dispute/refund process entails. Do not assume MoonPay will act as a dispute escalation point — its published policy disclaims this role entirely. If the underlying merchant is unverified or unreachable, the transaction should not proceed.
- MoonPay's own Commerce FAQ states 'MoonPay is unable to resolve payment disputes' and instructs buyers to 'contact the merchant directly,' even though MoonPay processes and holds the payment infrastructure.
- UK Financial Ombudsman decision DRN-3879035 found that MoonPay was the legal merchant of record for a card payment, meaning chargeback rights ran against MoonPay — contradicting MoonPay's practice of deflecting dispute responsibility to third parties.
Human handoff required for
Verify legal counterparty and dispute path before completing any purchase through a MoonPay Commerce-powered checkout, specifically when MoonPay's own documentation disclaims dispute responsibility and redirects buyers to 'the merchant' — escalate to a human if the underlying merchant is unverified, unreachable, or if there is any ambiguity about who holds the payment and who can authorize a refund or reversal.
- MoonPay's Commerce FAQ explicitly states that transactions are 'direct peer-to-peer payments' and instructs buyers to contact 'the merchant directly' for refunds, despite MoonPay operating the payment rails and collecting fees.
- A UK Financial Ombudsman published decision (DRN-3879035) confirmed that MoonPay was the legal merchant of record for a card transaction, directly contradicting MoonPay's own policy of deflecting dispute responsibility to downstream merchants.
Escalate to a human when a chargeback or payment reversal is needed on a transaction processed through MoonPay Commerce, specifically because MoonPay disclaims the ability to reverse payments while simultaneously being recognized by at least one financial regulator as the merchant of record — an agent cannot autonomously resolve the resulting gap between MoonPay's self-described role and its legal liability.
Five discrepancy categories were checked for moonpay.com. Pricing discrepancy (advertised vs. checkout totals): no documented pattern of hidden fees or bait-and-switch pricing was found; reviewer commentary noted fees are high but shown upfront. Availability discrepancy (rates or offers changing at checkout): no independently-verified reports of ghost inventory or last-minute rate changes were found. Identity discrepancy (merchant-of-record and dispute-responsibility ambiguity): a confirmed finding was identified, grounded in MoonPay's own Commerce FAQ and a published UK Financial Ombudsman decision (DRN-3879035), showing MoonPay simultaneously disclaims dispute responsibility while being recognized as the legal merchant of record. Policy discrepancy (stated vs. enforced cancellation/refund terms): BBB complaints showed individual service delays but no systematic, independently-verified enforcement gap was found. Undisclosed constraints (hidden payment method blocks or geographic restrictions): MoonPay's own help documentation appears to publicly disclose regional and payment-method limitations; no hidden platform constraints causing mid-transaction failures were confirmed. All five categories were searched; no scans were blocked or missing.