A2A (Agent2Agent)
Has a pageAn open protocol for agents to find each other through Agent Cards and hand off tasks over JSON-RPC, gRPC or HTTP bindings.
Related protocols and standards
The protocols, programs and standards that circle the eight: agent messaging, identity, wallet permissions, machine money, card programs and the court cases that shape them. Starred items have a short page of their own.
45 items in 6 groups; 13 with a page of their own. Cards without one link to their primary source.
An open protocol for agents to find each other through Agent Cards and hand off tasks over JSON-RPC, gRPC or HTTP bindings.
An open JSON-RPC protocol that lets LLM applications connect to servers that offer tools, resources and prompts.
A simple open Markdown file format that gives coding agents project instructions and context.
AGENTS.md is a plain Markdown file in a repository that gives coding agents the project instructions and context they need. OpenAI contributed it to the when the Linux Foundation formed the foundation on 2025-12-09, alongside Anthropic’s and Block’s goose. Source [12] It carries no payment or commerce semantics, but repositories of two of the eight ship one: the UCP repository and the mppx SDK repository for MPP. Source [26, 27]
AGNTCY's Open Agentic Schema Framework (OASF), a standardized schema system that describes an agent's capabilities, interactions and metadata as machine-readable records.
is AGNTCY’s standardized schema system for , interactions and metadata, so that directories and other agents can read what an agent offers. Source [28] The ERC-8004 best-practices guide credits OASF from AGNTCY, which it says is now part of the Linux Foundation, with standardized taxonomies for agent capabilities. Source [29] In ERC-8004 the example lists an OASF service at version 0.8, and feedback entries may carry oasf.skills and oasf.domains. Source [10]
An open-source protocol for agents to discover each other and collaborate securely across the open internet, built on decentralized identifiers.
ANP targets agents that find and talk to each other on the open internet rather than inside one platform. A 2025 survey of interoperability protocols groups it with , IBM’s Agent Communication Protocol and , and describes it as using decentralized identifiers (DIDs) and JSON-LD for open-network discovery and secure collaboration. Source [3] None of the eight protocols reference ANP in their specifications.
Primary source for ANP (Agent Network Protocol) (external link)
An open-source, extensible AI agent from Block that uses MCP servers as extensions.
goose is an open-source AI from Block that gains its abilities through servers. Block contributed it to the when the Linux Foundation formed the foundation on 2025-12-09, together with Anthropic’s MCP and OpenAI’s AGENTS.md. Source [12] None of the eight protocols reference goose. As an MCP client it could in principle call the MCP transports that x402 and MPP define, but that was not verified. Source [13, 15]
OpenAI's MCP-based framework for building apps that run inside ChatGPT, including checkout from the app's interface.
Apps built with the SDK connect ChatGPT to a developer’s server. Its monetization guide makes external checkout generally available and has a in private beta: the widget calls window.openai.requestCheckout, ChatGPT sends a to the developer’s MCP server in a complete_checkout tool call, and the merchant’s PSP (Adyen, Checkout.com, Fiserv, PayPal, Stripe or Worldpay) charges it. Source [30, 32] Raw payment methods require the ACP endpoint and PCI DSS Level 1, and the ACP README points merchants to OpenAI’s implementation for ChatGPT. Source [30, 31] In March 2026 trade press reported an OpenAI spokesperson saying that was moving to Apps (reported). Source [33]
Primary source for OpenAI Apps SDK (ChatGPT apps) (external link)
A draft EMVCo framework for card-based agentic payments, built around Intent Services, a shared layer to register, look up and manage the intent a consumer has authorized.
A Final Ethereum token standard for permissioned (regulated) tokens whose holders need an ONCHAINID identity contract carrying claims signed by trusted issuers.
The FIDO Alliance publishes the passkey standards (CTAP, with W3C WebAuthn) and, since 2026-04-28, hosts standards work on AI agents, including AP2 and Mastercard's Verifiable Intent.
Read the FIDO passkeys and the FIDO agentic working groups page
An IETF working group that standardizes how bots, crawlers and AI agents prove who they are to websites by signing HTTP requests with RFC 9421 HTTP Message Signatures.
Know Your Agent names efforts to tie an AI agent to a verified person or organization before it pays; this cluster covers Skyfire KYAPay, Mastercard's agent registration and the GLEIF vLEI agent mandate proposal.
Two IETF Proposed Standards from February 2024; RFC 9421 signs chosen parts of an HTTP message, and RFC 9530 carries a digest of the message content so a signature can cover the body.
Read the RFC 9421 HTTP Message Signatures and RFC 9530 Digest Fields page
The family of standards for signed, selectively disclosable credentials and how a wallet presents them; AP2 v0.2 uses SD-JWT VC, OpenID4VP and the Digital Credentials API, while VC 2.0 and DIDs are the wider family.
Two proposals for finding and checking AI agents by name; ANS anchors an agent to a DNS domain with certificates and a transparency log, and NANDA maps agent identifiers to signed AgentFacts metadata.
The started as draft-narajala-ans-00 on 2025-05-16, with a matching arXiv paper (2505.10609) a day earlier. Source [115, 116] Its successor draft-narajala-courtney-ansv2 had revisions -00 and -01 posted on 2026-04-13 as an Independent Submission aimed at Informational status. It anchors an to a DNS domain: a Registration Authority checks domain ownership over ACME, issues certificates that bind a versioned name of the form ans://v{version}.{agentHost}, and seals lifecycle events into an append-only transparency log, with Bronze, Silver and Gold assurance tiers. It references and agent cards but none of the eight protocols. Source [114] A separate draft from 2026-07-25 proposes an IANA registry for ANS protocol identifiers. Source [117]
(Networked AI Agents in Decentralized Architecture) is an MIT Media Lab project. Source [118] Its paper on the NANDA Index and verified AgentFacts appeared on arXiv on 2025-07-18, followed by an enterprise paper on 2025-08-05. Source [119, 120] AgentFacts is a JSON Schema for an agent’s identity, provider, endpoints, and certification, and the NANDA Index v2 maps urn:air: identifiers to an AI catalog, an A2A or another card, without hosting agents. Source [121, 122, 123] The project’s nanda-payments repository implements “x402-NP”, which reuses the x402 pattern with NANDA Points instead of crypto. Source [124]
Primary source for Agent Name Service and the MIT NANDA Index (external link)
An open-source toolkit from Catena Labs with two protocols, ACK-ID for agent identity and ACK-Pay for payments; a v2 redesign around JOSE grants and RFC 9421 signatures is an open proposal, not a release.
ACK’s v1 releases use W3C DIDs and Verifiable Credentials, with payment receipts issued as credentials; the latest release is agentcommercekit 0.11.0 of 2026-08-04. Source [112, 125] ACK v2 has not shipped. On 2026-08-27 Catena opened a draft pull request, “RFC: ACK-ID + ACK-Pay v2”, which calls itself a proposal and was still open on 2026-10-11. It would replace credentials with plain JOSE grants (typ grant+jwt with a required cnf.jkt ), carry grants in a signed Grant header under so infrastructure can check them, and give ACK-Pay a profile that adopts the x402 offer and receipt artifacts. It also renames “” to “grant” to avoid confusion with AP2. Source [113] Catena appears among participants for Mastercard Agent Pay. Source [86]
Primary source for Catena Labs Agent Commerce Kit (ACK) (external link)
Cloudflare's program for bots and agents that identify themselves honestly; since 2026-07-01 agents that sign requests with Web Bot Auth are Verified bots labeled Direct or Intermediary.
Cloudflare introduced signed agents on 2025-08-28 as an of its Verified bots program, for agents that sign their HTTP requests with and follow a signed policy. Source [128] Its Verified bots documentation (last updated 2026-10-08) says signed agents are now Verified: as of 2026-07-01 a bot record carries a “Direct versus Intermediary access” field, where Direct means one narrow operator and Intermediary means an agentic service that many end users can operate. The cf.bot_management.signed_agent rules field now matches a Verified bot labeled Intermediary and needs an Enterprise plan with Bot Management. Source [126, 127] The 2026-07-01 changelog entry launched BotBase but does not mention the merge, so the docs page is the only source for it. Source [129] Cloudflare checks Visa TAP and Mastercard Agent Pay signatures at its edge. Source [74, 76]
Primary source for Cloudflare Verified Bots and signed agents (external link)
A Draft ERC (RAMS) that lets a KYC-verified principal give an on-chain agent scoped, time-bounded and capped authority over a regulated token, which the token checks at execution time.
ERC-8226 splits compliance into three layers: token compliance (for example ERC-7943 or ERC-3643), compliance (this ERC) and identity (a registry such as ERC-8004). Source [49, 133] The principal signs a mandate with (EIP-1271 for contract accounts) that sets validity dates and per-transaction and cumulative caps; tokens call canExecute before acting and recordExecution to consume the cap, enforcers can freeze an agent or principal, and only the principal can revoke. Source [49] Created on 2026-04-12 and first merged into ethereum/ERCs on 2026-05-12, it moved to one mandate per agent, principal and asset on 2026-10-09; its Ethereum Magicians thread had 50 posts by then. Source [130, 131] The spec text does not mention AP2, x402 or any card network; see ERC-3643 for how it bridges token compliance and agent identity. Source [49, 132]
Primary source for ERC-8226 Regulated Agent Mandate (external link)
Two Ethereum building blocks for naming and vouching; EAS records signed attestations against registered schemas, and ENS maps human-readable names to addresses and text records, now including draft agent records.
The Ethereum Attestation Service is an open contract system for attestations on EVM chains: anyone registers a schema and then attests against it, on-chain or off-chain, with optional resolver contracts. It has no EIP number. Source [134, 135] Its mainnet contract was deployed in block 16756728 on 2023-03-04, and the project’s site reports more than 9.5 million attestations and 450,000 attesters, its own figures as of 2026-10-11. Source [134, 136] None of the eight protocols cites EAS.
ENS resolves human-readable names to addresses and records; its core proposal, now ENSIP-1, dates from 2016-04-04, and the ENS DAO governs the protocol. Source [137, 139] Two Draft ENSIPs target agents. ENSIP-25, merged 2026-02-18, defines a text record agent-registration[<registry>][<agentId>] with which a name owner confirms a link to an registry entry, using the ERC-8004 Identity Registry as its example. ENSIP-26, merged 2026-05-06, adds agent-context and agent-endpoint[<protocol>] keys aligned with ERC-8004 service names. Source [138, 140, 141] From the other side, ERC-8004’s registration example lists an ENS service, and agents may advertise an ENS name. Source [10]
Primary source for Ethereum Attestation Service and ENS (external link)
The OpenID Foundation's AI Identity Management community group studies agent identity gaps; nearby proposals (OIDC-A, an expired OAuth on-behalf-of draft) and older standards (RFC 8693, RFC 9396, CIBA) are context, not parts of the eight.
The OpenID Foundation’s Artificial Intelligence Identity Management community group studies identity use cases and gaps; protocol work is outside its charter. Source [142] It released the white paper “Identity Management for Agentic AI” on 2025-10-07, later posted to arXiv as 2510.25819, answered a NIST request for information on 2026-03-11, and published expert comments on the agentic framework on 2026-10-08. Source [38, 143, 144, 145] OIDC-A (OpenID Connect for Agents) is a single-author proposal on arXiv (2509.25974, 2025-09-30), not an OpenID Foundation specification. Source [146, 147] The individual draft draft-oauth-ai-agents-on-behalf-of-user from WSO2 authors added requested_actor and actor_token to OAuth 2.0; its last revision, -02, is dated 2025-08-26, and it expired on 2026-02-27 without adoption. Source [148]
Three older standards often come up as building blocks: RFC 8693 OAuth 2.0 Token Exchange (January 2020), RFC 9396 Rich Authorization Requests with authorization_details (May 2023), and OpenID Connect CIBA Core 1.0, final on 2021-09-01, which lets a service ask a user to approve a request on another device. Source [149, 150, 151] Among the eight only UCP uses one of them: its accelerated flow exchanges a token through RFC 8693 for a JWT authorization grant. Source [152] AP2 uses rather than any of the three. Source [39] No specification among the eight cites RFC 9396, CIBA, OIDC-A or the on-behalf-of draft.
Primary source for OpenID Foundation AI identity work and related OAuth standards (external link)
A beta toolkit from World that lets a person verified with World ID delegate proof of being a unique human to an AI agent, so x402 sites can tell human-backed agents from bots.
World announced the AgentKit beta on 2026-03-17, and the docs still label it beta. Source [153, 154] A person registers an ’s wallet in AgentBook with a World ID proof. An x402 site then asks the agent to sign a message, looks up the human behind the wallet in AgentBook and applies its own access policy; the client sends an agentkit header and tries this check before paying. The npm package @worldcoin/agentkit reached 0.2.1 on 2026-08-24 and depends on @x402/core. Source [155] The x402 docs list it as a third-party for verifying human-backed agents. Source [156]
Two Draft Ethereum standards that let a user grant an app or agent scoped spending authority; ERC-7715 is how the app asks the wallet for permissions, and ERC-7710 is how the granted delegation is redeemed on-chain.
Read the ERC-7715 wallet execution permissions and ERC-7710 delegation page
The Ethereum building blocks the on-chain rails rely on, from smart accounts (ERC-4337, EIP-7702) and signatures (EIP-712, ERC-1271) to token authorizations (EIP-3009, Permit2), chain-agnostic ids (CAIP-2, CAIP-10, CAIP-122) and builder codes (ERC-8021).
ERC-4337 adds smart accounts without a protocol change: user operations go to a separate mempool and are bundled into calls to a shared EntryPoint contract. It became Final on 2026-06-02, and its EntryPoint has shipped versions 0.6 (2023-04-24) through 0.9 (2025-11-16), with 0.8 adding native EIP-7702 support. Source [170, 171, 172] EIP-7702 lets an ordinary account (EOA) set delegated code through a new transaction type; it went live with the Pectra upgrade on 2025-05-07 and is Final. Source [173, 174] lets a contract validate signatures and defines typed-data signing, both Final; transfer with authorization is Draft; is Uniswap’s signature-based approval contract. Source [175, 176, 177, 178] and name chains and accounts across ecosystems, and defines Sign in With X. Source [179, 180, 181] builder codes (transaction attribution through a calldata suffix) carry a Draft header dated 2025-09-11, but their pull request was still open on 2026-10-11, so the standard has no published page. Source [182]
Among the eight, x402 uses most of these: CAIP-2 network ids, EIP-3009 by default plus Permit2 in the exact EVM , CAIP-122 in its sign-in and ERC-8021 schema 2 in its builder-code extension. Source [169, 183, 184, 185] ERC-8004 checks EIP-712 or ERC-1271 signatures when an is set, and its implementation EIP-7702 delegated accounts. Source [10, 186] MPP’s evm method accepts Permit2 and EIP-3009 credentials, and its proof is EIP-712. Source [187, 188] AP2 touches them only in its x402 samples, which sign EIP-3009 authorizations. Source [22] No use was found in the specifications of , ACP, UCP or Mastercard Pay.
Primary source for ERC-4337, EIP-7702 and friends (external link)
An HTTP 402 authentication scheme from Lightning Labs in which a server returns a Lightning invoice plus a bearer token, and the client proves payment by presenting the token with the invoice preimage.
The USDC issuer, whose agent-facing products are Nanopayments through Circle Gateway (sub-cent USDC payments inside the x402 flow), the Circle Agent Stack and the Arc Layer 1 chain that charges fees in USDC.
Nanopayments, live on mainnet since 2026-04-29, let a buyer sign authorizations off-chain at zero gas for amounts from $0.000001 , which Gateway batches and settles in bulk inside the x402 flow; the docs page lists no fee schedule. Source [198, 199] Circle says it launched the Stack (policy-controlled Agent Wallets plus Nanopayments) in May 2026 and opened Arc’s public mainnet on 2026-09-16 with a permissioned founding validator cohort that includes BlackRock, DTCC, Mastercard and Visa. Source [200, 201, 202] The Arc release says Arc has not been reviewed or approved by the New York State Department of Financial Services or any other regulator, and it claims that USDC accounts for 98.8% of agent-driven transaction volume, a vendor figure with no stated method (as of 2026-09-16). Source [200]
Primary source for Circle: Nanopayments, Agent Stack and Arc (external link)
Cloudflare's agent payment products (the Monetization Gateway, Cloudflare Wallets and the announced NET Dollar stablecoin), plus the Radar dataset that reports AI crawler traffic.
Cloudflare co-founded the x402 Foundation with Coinbase (announced 2025-09-23), and its Monetization Gateway entered closed beta on 2026-09-30 for eligible US-based sellers and buyers, settling on Base through Coinbase’s x402 ; the separate credit-backed cloudflare:402 network in the x402 spec is not the beta’s settlement path. Source [78, 203, 204, 205, 206] Cloudflare Wallets were announced on 2026-08-04 with only handle reservation open, and NET Dollar, announced on 2025-09-25 as a planned US dollar-backed , had no launch found as of 2026-10-11. Source [207, 208, 209, 210] Cloudflare verifies Visa TAP and Mastercard Agent Pay signatures at its edge and, since 2026-07-01, lists signed agents as a category of Verified Bots. Source [74, 126] The Radar API needs an API token, and Radar data is licensed under CC BY-NC 4.0. Source [211]
Coinbase Developer Platform products that give AI agents wallets and payment tools built around x402: Payments MCP, Agentic Wallets and Base MCP.
Payments , launched on 2025-10-23, is a local MCP server that lets an create a wallet, fund it through an onramp and pay x402 services; Coinbase tested it with Claude Desktop, Claude Code, Codex, Gemini and Cherry Studio. Source [212, 213] Agentic Wallets, launched on 2026-02-11, keep keys in Trusted Execution Environments and apply caps, per-transaction limits and KYT screening, with x402 as the payment protocol. Source [214, 215, 216] Fortune reported on 2026-05-26 that Base MCP lets Claude or ChatGPT propose transfers and swaps that the user confirms in the Base wallet, without the agent holding keys (reported). Source [217] Coinbase originated x402, whose governance now sits with the x402 Foundation at the Linux Foundation. Source [218]
Primary source for Coinbase: Payments MCP, Agentic Wallets and Base MCP (external link)
A Crossmint API, public since 2026-06-02, that lets developers connect eligible US-issued Visa credit and debit cards to AI agents as tokenized credentials through Visa Intelligent Commerce and Basis Theory, with spend limits.
Crossmint launched the Agentic Cards API publicly on 2026-06-02, built on and Basis Theory: developers connect eligible US-issued Visa cards to AI agents as tokenized credentials with spend limits, and issuer approval and controls still apply. Source [219] The SDK Crossmint/crossmint-sdk is Apache-2.0. Source [220] The launch post does not say whether Visa TAP is used, so the link to runs through Visa Intelligent Commerce tokens.
Primary source for Crossmint Agentic Cards API (external link)
Open Payments is an Interledger Foundation REST API standard, with GNAP authorization, for requesting and sending payments between accounts on Open Payments-enabled wallets; Web Monetization is a browser-side draft that streams payments from a visitor's wallet to a page's wallet address.
Open Payments has a public specification and SDK repository and a reference implementation, Rafiki; the npm package @interledger/open-payments reached 7.4.0 on 2026-03-11. Source [221, 222] Web Monetization is a Draft Community Group Report, republished on 2026-09-15 by Interledger Foundation editors, and not a W3C standard. Source [223] No official AI-agent program was found on the Interledger Foundation blog or openpayments.dev on 2026-10-11, and none of the eight reference Open Payments; a community post that explores it as an x402 settlement rail is one researcher’s work (reported). Source [224, 225]
Primary source for Interledger Open Payments and Web Monetization (external link)
A Layer 1 settlement chain for agent payments plus an Agent Passport that gives an agent a programmable wallet with user-set spending limits and allowed destinations.
Kite launched the Kite Chain mainnet and Kite Passport on 2026-04-30; the passport gives an agent a programmable wallet with user-set spending limits and allowed destinations, and Kite says it integrates over 90 service providers (company figure). Source [226] Kite AI was listed as a general member at the x402 Foundation’s operational launch on 2026-07-14. Source [218] Claims of product support for x402, AP2 and MPP appear only on Kite’s social account and are unverified.
Primary source for Kite AI (Kite Chain and Agent Passport) (external link)
A payments platform for AI agents that runs an x402 facilitator with an ERC-4337 smart-account scheme supporting plans, credits and subscriptions, and documents AP2 and A2A integration.
Nevermined runs an x402 and describes an x402 Smart Accounts built on ERC-4337 smart accounts for plans, credits and subscriptions. Source [227] Its docs show an ADK demo that carries Nevermined x402 payments inside AP2 and messages. Source [228] The facilitator also MPP, which Nevermined’s docs expand as “Merchant Payment Protocol”, a different name from the Machine Payments Protocol. Source [227] The company has also published a third-party review of , and its SDK nevermined-io/payments is Apache-2.0. Source [229, 230]
A payments-focused EVM Layer 1 incubated by Stripe and Paradigm that launched on mainnet together with the Machine Payments Protocol and serves as MPP's home rail.
’s mainnet ( 4217) went live on 2026-03-18, and the same post introduced MPP as an open standard co-authored by Stripe and Tempo that supports , cards and other methods, so Tempo is one MPP payment method among several rather than a requirement. Source [231] Tempo Labs and Stripe maintain the MPP specifications repository, and the Apache-2.0 node software tempoxyz/tempo had release 1.16.0 on 2026-10-06. Source [232, 233] Coverage dates the project announcement to 2025-09-04 and the public testnet to 2025-12-09 (reported). Source [234]
Two x402-adjacent proposals with confusable names: x402r, a third-party non-custodial refund and arbitration protocol for x402 payments, and A402, an academic paper that binds crypto payments to service execution with Atomic Service Channels.
x402r is a third-party, non-custodial refund and arbitration protocol for x402 payments; the x402 docs list it as a third-party , and its SDK @x402r/sdk was first published on npm on 2026-03-20 (version 0.2.1 at the time of writing). Source [156, 235] A402 is a separate paper (arXiv:2603.01179, 2026-03-01) that argues x402 does not make execution, payment and delivery atomic and proposes Atomic Service Channels with TEE-assisted adaptor signatures. Source [236] No A402 deployment was found.
Primary source for x402r (refunds) and A402 (academic proposal) (external link)
Pilots in which AI assistants (first ChatGPT, then Claude) pay Indian merchants over UPI, using UPI Reserve Pay so the user approves one spending limit for a merchant and the agent then completes several debits within it.
Visa's program and API platform for agent-initiated card payments (tokenized credentials for agents, passkey-confirmed payment instructions and transaction signals back to Visa), with the Trusted Agent Protocol as one component.
A suite of modular Adyen APIs (Agentic Feed, Agentic Cart, Agentic Payments) that lets enterprise merchants sell through AI platforms without rebuilding checkout for each one.
Adyen Agentic, announced on 2026-06-16, is in limited availability for US enterprise merchants with global expansion planned; the release calls Adyen an early endorser of UCP, names AP2 and ACP, and quotes Mastercard on Pay. Source [253] Adyen publishes integration docs for Agentic Payments with UCP. Source [254] Adyen signed the ACP CLA, and ACP added adyen to its payment and authentication provider enums in the 2026-01-16 release. Source [255, 256] Adyen was also an AP2 launch collaborator and a Premier member at the x402 Foundation’s operational launch on 2026-07-14. Source [218, 257]
American Express's Agentic Commerce Experiences (ACE) Developer Kit, with five agent-facing services, and Agent Purchase Protection, a commitment to protect eligible Card Members from charges caused by errors of registered AI agents.
American Express announced the ACE Developer Kit on 2026-04-14 with five services: registration, account enablement, intent intelligence, payment credentials and cart context. Source [258] The same release introduced Agent Purchase Protection for eligible Card Members against charges caused by errors of registered AI agents, subject to terms, and the program page says only verified AI agents can transact; the wording is forward-looking. Source [258, 259] American Express was named among AP2 launch collaborators, is listed as a UCP endorser, and was a Premier member at the x402 Foundation’s operational launch on 2026-07-14. Source [218, 252, 257]
Primary source for American Express ACE Developer Kit and Agent Purchase Protection (external link)
A Google shopping product (not the UCP protocol) that keeps one cart across merchants and across Search, Gemini, YouTube and Gmail, tracks prices and restocks, and checks out through UCP with Google Pay.
Google announced Universal Cart on 2026-05-19 as a shopping product, distinct from the UCP protocol, that checks out through UCP with Google Pay while the brand remains . Source [260] US rollout across Search and the Gemini app was scheduled for summer 2026, with YouTube and Gmail later; whether the rollout completed was not verified. Source [260] The same post says AP2 will come to Google products “in the coming months”, starting with Gemini Spark, and announces UCP checkout expansion to Canada and Australia, then the UK. Source [260]
An open product-feed specification and API from Klarna that gives AI agents structured, live product, price and availability data.
Klarna launched the Agentic Product Protocol on 2025-12-15 as an open product-feed specification and API, saying both were available that day. Source [261] Klarna claims more than 100 million products and 400 million prices across 12 markets (company figures, as of 2025-12-15). Source [261] As a feed format it overlaps with ACP product feeds and UCP catalog , and Klarna is also a listed UCP endorser. Source [252]
Primary source for Klarna Agentic Product Protocol (external link)
In-chat checkout on Copilot.com where the merchant stays merchant of record, fed by product data from Microsoft Merchant Center.
Microsoft announced Copilot Checkout on 2026-01-08 with PayPal, Shopify and Stripe, rolling out in the US; the merchant stays and Copilot does not take that role. Source [262, 263] Microsoft’s requirements page says Copilot Checkout requires a UCP-compliant feed (present tense) and that Microsoft Merchant Center “will support” UCP (future tense). Source [263, 264] Microsoft also says it is adopting open standards like ACP, without documenting an ACP binding. Source [262, 264]
Primary source for Microsoft Copilot Checkout (external link)
PayPal services that let merchants accept payments from AI assistants with minimal changes (Agent Ready) and expose catalogs, carts and orders to AI shopping platforms (Store Sync).
PayPal announced Ready and Store Sync on 2025-10-28; Store Sync was available first and Agent Ready payments were slated for early 2026 (reported), and both are described in PayPal’s developer docs. Source [265, 266] The same day PayPal said it would adopt ACP and run an ACP server for its merchants, and it signed the ACP corporate CLA on 2026-04-16. Source [255, 267] PayPal is a listed PSP for the beta, a launch partner of Microsoft Copilot Checkout (2026-01-08), a listed UCP endorser and a named AP2 launch collaborator. Source [30, 252, 257, 262]
Primary source for PayPal agentic commerce services (Agent Ready, Store Sync) (external link)
In-chat checkout in Perplexity for PayPal merchants, using PayPal identity verification and purchase protection.
PayPal and Perplexity launched Instant Buy for US Perplexity users on 2025-11-25, with checkout for PayPal merchants inside Perplexity backed by PayPal identity verification and purchase protection. Source [268] Early retailers named include Abercrombie & Fitch, Ashley Furniture, Fabletics, Adorama and Newegg. Source [268] The releases name none of the eight protocols; PayPal’s own ACP and UCP ties are listed under its separate entry, and Perplexity’s Comet browser is the subject of the Amazon v. Perplexity case. Source [269]
Primary source for Perplexity Instant Buy (with PayPal) (external link)
A Shopify admin channel that syndicates a merchant's Shopify Catalog data to AI assistants and, where enabled, lets buyers check out inside the AI channel; an Agentic plan opens the catalog to brands without a Shopify store.
Shopify announced Agentic Storefronts and an Agentic plan on 2026-01-11 alongside UCP, which it co-develops; the channel surfaces Shopify Catalog data in ChatGPT, Microsoft Copilot, Google AI Mode and Gemini. Source [252, 270] Shopify’s Help Center says checkout is active by default for eligible US stores, while the Copilot, AI Mode and Gemini storefronts are in early access, and the channel got its own admin page on 2026-05-11. Source [271, 272, 273] Secondary reports say eligible US merchants were enrolled in Google AI Mode checkout from about 2026-09-18 to 2026-09-22 with an opt-out (reported). Source [274] OpenAI said on 2026-03-24 that Shopify catalog data reaches ChatGPT, with purchases completed on the merchant’s store. Source [275]
Primary source for Shopify Agentic Storefronts (external link)
Stripe's merchant product for selling through AI agents (Agentic Commerce Suite) and its scoped, revocable payment credential that an agent passes to a seller without exposing card details (Shared Payment Token, SPT).
Stripe launched Shared Payment Tokens with ACP on 2025-09-29 and the Agentic Commerce Suite on 2025-12-11. Source [276, 278] An carries usage_limits (currency, max_amount, expires_at) and seller_details, and the seller confirms a PaymentIntent with it; OpenAI describes SPT as the first implementation compatible with the ACP Delegated Payment spec, but SPT itself is not part of the ACP spec. Source [277, 279] Stripe’s MPP integration cards through SPTs, its machine payments preview added x402 on Base (reported, February 2026), and Stripe is a listed UCP co-developer. Source [252, 280, 281]
Primary source for Stripe Agentic Commerce Suite and Shared Payment Tokens (external link)
A US lawsuit in which Amazon sued Perplexity under the Computer Fraud and Abuse Act and California's CDAFA over the Comet browser agent shopping on Amazon.com for users; the first appellate ruling on whether an AI agent acting for a user accesses a site without authorization.
Amazon sued Perplexity in November 2025 (district docket opened 2025-11-04) over the Comet browser logging in to and shopping on Amazon.com for users. Source [283] The district court granted a preliminary injunction, reported as dated 2026-03-09, that barred Comet’s agent from password-protected areas of Amazon. Source [284, 285] In an opinion filed on 2026-08-04 in No. 26-1444, the Ninth Circuit vacated the injunction and remanded, holding that on these facts the user rather than Perplexity accessed Amazon, using the agent as a tool, and describing its holding as narrow. Source [282] Commentators note that site operators are left with terms of service and technical measures, which is the gap that signed agent identification such as Visa TAP and Mastercard Agent Pay targets; no source links the case to those programs. Source [286]
Primary source for Amazon v. Perplexity (Comet shopping agent) (external link)