1. Scenario 1

    An agent buys one API call

    A client agent finds a paid weather endpoint through the x402 Bazaar or an ERC-8004 registration, pays for one call with x402 V2 exact, and leaves ERC-8004 feedback whose proof of payment sits in an off-chain file.

    Verified

  2. Scenario 2

    Metered inference

    An agent streams tokens from an inference API and pays per unit through an MPP session on Tempo, with a deposit, off-chain vouchers, a top-up and a cooperative close; the forced close is the fallback. Compared with x402 upto and batch-settlement.

    Verified

  3. Scenario 3

    A shopper buys running shoes in Gemini

    A shopper asks Gemini for running shoes. UCP handles discovery, checkout, the Google Pay handler and signed order webhooks; an AP2 checkout mandate with the human present is shown as the specification describes it, with live use unverified. Google Pay on Google surfaces uses only PAN_ONLY.

    Verified

  4. Scenario 4

    Autonomous restock while the user is away

    A cafe owner signs AP2 v0.2 open mandates with allowed merchants, a per-order cap, a weekly recurrence and a total budget. While the owner is away the agent closes them with its own key, three verifiers check the bindings, and signed receipts come back. Specified only; production use is unverified.

    Verified

  5. Scenario 5

    An agent shops on a merchant website with a Visa card

    An agent browses a merchant site with TAP agent-browser-auth signatures, gets an agent-specific token from Visa Intelligent Commerce and a Payment Instruction the consumer authenticated with a passkey, then checks out with an agent-payer-auth signature and the agenticConsumer and agenticPaymentContainer objects. A CDN verifies the signatures at the edge. The JWKS the specification named until October 2026 held only an RSA sandbox key on 2026-10-11 and 2026-10-19, and the specification's examples cannot verify.

    Verified

  6. Scenario 6

    From ChatGPT discovery to merchant checkout

    A shopper finds a product in ChatGPT through merchant product feeds, business profiles and the web, then buys on the merchant's own checkout. Since 2026-11-13, in a limited rollout, a US ChatGPT Pro subscriber's dot can finish the purchase itself; its cloud browser signs certain requests with Web Bot Auth and, after the shopper approves, pays in the merchant's existing payment form with a ChatGPT Wallet token from the card network. A headless plugin can hand checkout back to the site with a continue_url, and the ChatGPT payment sheet stays a beta for select marketplaces. OpenAI's commerce docs no longer describe the Agentic Commerce Protocol (ACP); its merchant page still says shopping is built on it.

    Verified

  7. Scenario 7

    A Mastercard Virtual Card Token in an existing checkout form

    A registered agent signs its requests with RFC 9421 and Mastercard's single tag Agent-pay-auth, verified at the edge against a key directory whose public location is unknown. At checkout it types a Mastercard Virtual Card Token and a one-time DTVC into the merchant's standard card fields. Verifiable Intent L3a and L3b, linked by checkout_hash, are specified; no public record shows these Autonomous-mode layers in live use.

    Verified

  8. Scenario 8

    A crawler pays per page

    Two separate Cloudflare variants, never one path. (a) The Monetization Gateway closed beta of 2026-09-30 answers with an inline x402 402 and settles USDC on Base through Coinbase's x402 facilitator. (b) The credit-backed batch-settlement binding on the cloudflare:402 network has the crawler sign with RFC 9421 while Cloudflare, as merchant of record, bills later off chain, as the x402 spec describes it for pay-per-crawl.

    Verified

Source details

    Loading the index.

    Enter open Esc close ? shortcuts