metamask.io

Crypto payment layer contributor to the A2A x402 extension — a production-ready extension to the Agent2Agent (A2A/AP2) protocol enabling stablecoin and cryptocurrency payments between agents. MetaMask's participation is scoped to this payments extension, not to general A2A agent interoperability.

MetaMask (ConsenSys) is named as a collaborator alongside Coinbase and the Ethereum Foundation on the A2A x402 extension announced in Google's AP2 launch blog post, which includes a direct MetaMask quote. This is vendor-specific evidence of A2A involvement, though scoped narrowly to the crypto payments extension rather than full A2A protocol implementation. Source: https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol

No evidence that metamask.io (MetaMask, a crypto wallet by Consensys) has any involvement with the Agentic Commerce Protocol. Confirmed ACP launch partners and merchants are retail/e-commerce entities such as Etsy, Shopify, Walmart, Target, Sephora, and URBN-brand retailers. MetaMask appears once in research results only in the unrelated context of Google's A2A x402 crypto payments extension, not ACP. Chosen not_found rather than confirmed_absent because no MetaMask-specific statement or deprecation notice addresses ACP — the protocol simply appears to have no applicability to a crypto wallet product.

Named launch partner for AP2 interoperability; MetaMask's role is specifically enabling users to pay AI agents using self-custody wallets with full composability, and providing developers maximum interoperability via AP2 and x402 integration.

MetaMask is explicitly named as a launch partner in Google's AP2 announcement (Google Cloud Blog) and listed among supporters on the AP2 EU perspective site. Their stated contribution is delivering wallet-level interoperability and user self-custody for agent payments via AP2 and x402. No MetaMask-specific AP2 endpoint or developer docs were found — participation is at the protocol commitment/partner level, not a callable API surface.

Documentation search and SDK reference access for MetaMask Embedded Wallets — provides five tools for AI coding assistants to search docs, fetch code examples, and look up SDK types; scoped to the Embedded Wallets (formerly Web3Auth) product only, not the broader MetaMask wallet or blockchain node APIs

MetaMask's official developer documentation at https://docs.metamask.io/embedded-wallets/build-with-ai/ documents a remote MCP server hosted at https://mcp.web3auth.io, operated by Web3Auth (the underlying infrastructure brand for MetaMask Embedded Wallets). The server is listed on the official MCP registry (Glama) and is cross-referenced in multiple docs.metamask.io pages including the Web SDK v11 migration guide. No authentication is required; it is publicly accessible with no partner enrollment needed. Third-party community wrappers (e.g., metamask-mcp on GitHub) also exist but are unsanctioned and distinct from this official server.

No evidence that MetaMask (metamask.io) is an MPP launch partner or has any integration with the Stripe/Tempo Machine Payment Protocol. Named MPP/Tempo ecosystem partners include Anthropic, OpenAI, Shopify, Mastercard, Visa, Revolut, Ramp, Nubank, DoorDash, Standard Chartered, UBS, and Klarna — MetaMask does not appear among them. The sole MetaMask mention found in MPP-adjacent search results concerns a separate protocol (Google's A2A x402 extension), not MPP itself.

No evidence that metamask.io (a browser-based crypto wallet by MetaMask/ConsenSys) has implemented or been named as an NLWeb participant. Microsoft's confirmed NLWeb launch partners are content, commerce, and travel platforms — Tripadvisor, O'Reilly, Shopify, Condé Nast, Redfin, Eventbrite, and Priceline — with no crypto-wallet or Web3 vendors listed. No /ask or /mcp endpoint at metamask.io was found in any public source.

Four targeted searches found no evidence that MetaMask (metamask.io) participates in, implements, or is listed as a partner of the Universal Commerce Protocol (UCP). UCP documentation references Google Pay and Shop Pay as payment handlers, and MetaRouter (metarouter.io) appeared in results — neither is MetaMask. MetaMask's own developer documentation focuses exclusively on EVM/non-EVM wallet APIs, Snaps, and Infura-backed RPC services, with no mention of UCP commerce checkout integration.

No evidence found that MetaMask (metamask.io) has implemented or is listed as a launch partner for WebMCP. Search results naming WebMCP adopters reference marketplace and lead-gen platforms (Thumbtack, Angi) and describe the protocol as a Google/Microsoft browser-spec initiative — MetaMask does not appear among them. MetaMask's own documented developer surface centers on its Ethereum provider API (window.ethereum) and Snaps, not the window.AICommands interface WebMCP requires.

Buyer-side x402 payment client integrated into MetaMask Smart Accounts Kit; enables smart accounts to use ERC-7710 delegation to authorize and execute HTTP 402 stablecoin micropayments as the paying party in machine-to-machine and AI-agent flows. Also announced as a native capability of the MetaMask Embedded Wallets Developer Platform (2026).

MetaMask publishes explicit x402 integration guides under their Smart Accounts Kit documentation, covering both seller endpoint setup and buyer payment flows using ERC-7710 delegation. The v1.5.0 docs at https://docs.metamask.io/smart-accounts-kit/1.5.0/guides/x402/overview/ are marked no longer actively maintained; v1.6.0 is the current version. x402 payments were also listed as a headline feature in MetaMask's 2026 Embedded Wallets Developer Platform announcement at https://metamask.io/news/embedded-wallets-developer-platform.

No evidence of MetaMask (metamask.io) having built or submitted an app to OpenAI's ChatGPT Apps platform. Searches surfaced MetaMask's 'Agent Wallet' product, which lists OpenAI Codex as a compatible framework, but this is a framework-agnostic SDK offering rather than a ChatGPT Apps SDK submission. No MetaMask listing was found in the ChatGPT app store or on the OpenAI developer app directory.

Plugin/extension authoring runtime — Snaps API provides MetaMask-proprietary RPC methods (snap_*, wallet_snap, wallet_invokeSnap) for building sandboxed JavaScript mini-apps that run inside the MetaMask extension, enabling custom network support, account types, and transaction insights not expressible through any named standard

Fully documented at https://docs.metamask.io/snaps/. The snap_* and wallet_invokeSnap RPC methods are MetaMask-proprietary and have no equivalent in EIP-1193 or other open standards. Access is self-serve via npm publish; no partner approval required.

AI agent wallet operations CLI — the MetaMask Agent Wallet (mm CLI) provides a proprietary command-line interface for AI agents to perform wallet operations (transfer, swap, sign, chain queries) using server-side key management in a trusted execution environment; not a browser-injected or JSON-RPC surface

Documented at https://docs.metamask.io/agent-wallet/. Launched in early 2026 as an Early Access Program for a limited group of traders and developers; general availability is not yet confirmed. This is a fully proprietary interface with no analogous open standard.

Hosted/embedded wallet provisioning API — allows web/mobile app developers to embed MetaMask-managed wallets directly in their applications, including wallet pregeneration via REST API, smart account management, and user auth flows; distinct from the browser extension surface

Documented at https://docs.metamask.io/embedded-wallets/. Provides proprietary REST endpoints and a JavaScript SDK for in-app wallet creation, pregeneration of EOA and ERC-4337 smart accounts, and wallet-preload flows. Fully distinct from both the Snaps API and the Agent Wallet CLI.

llms.txt index on the main metamask.io domain providing AI-agent-readable summaries of product announcements, feature launches, and partnerships (e.g. RWA/Ondo integration, tokenized assets) aimed at consumer and marketing content — not developer API documentation

A public llms.txt is served at https://metamask.io/llms.txt containing curated content summaries for AI agents. A separate llms.txt index is available at https://docs.metamask.io/llms.txt on the developer documentation subdomain; every page on docs.metamask.io carries a sitewide banner explicitly advertising it to AI agents. No AGENTS.md or /.well-known/agent file was found.

llms.txt index on the docs.metamask.io developer documentation subdomain providing a structured index of developer-facing content (SDKs, Wallet API, Snaps, Agent Wallet, Embedded Wallets, Smart Accounts, tutorials) for AI coding assistants and agents — explicitly referenced in a sitewide banner across all developer docs pages

Every page on docs.metamask.io displays a banner stating 'For AI agents: a documentation index is available at /llms.txt,' confirming deliberate, vendor-intentional self-declaration. The 'Build with AI' page (https://docs.metamask.io/embedded-wallets/build-with-ai/) also references a full-content variant at https://docs.metamask.io/llms-embedded-wallets-full.txt, indicating a tiered disclosure structure. No AGENTS.md or /.well-known/agent equivalent was found.