Am I Ready for Agents?

Whether to accept agent payments

In short

Decide whether to accept payments made by agents through the routes shopping surfaces use, such as UCP, ACP, x402 and Stripe Link, and through which provider. Most businesses do not need a new method first. Ask your payment provider what it supports for each surface you sell on, and set a date to review.

The decision

Decide whether to accept payments made by agents through the protocols the shopping surfaces use (UCP, ACP, x402, MPP, Stripe Link and others), and through which provider.

Who decides: The head of payments or ecommerce decides; the processor says what is possible.

The options

  1. Accept through your existing processorAsk your payment provider which agent protocols it supports; Stripe, PayPal and Shopify already run checkout for Copilot. Microsoft Advertising: Copilot Checkout and Brand Agents (Jan 2026), read 4 Nov 2026.
  2. Accept per-request payments for content or APIsx402 lets a server ask for payment in the HTTP response and an agent pay in the same exchange. x402, read 4 Nov 2026.
  3. Not yet, with a review dateReasonable for most; Ora scores the payment protocols so that supporting any one counts and the rest are not failures. Ora llms.txt, read 4 Nov 2026.

What we found

  • 4 Nov 2026

    In the network's own crawl, run of 4 Nov 2026 (13,071 of 13,071 domains from Tranco list 746WX plus Ora leaderboard domains), 0.59 percent of 10,439 sites published a UCP profile at /.well-known/ucp.json.

    Scorecard methodology: the crawl of 4 Nov 2026, read 4 Nov 2026
  • 19 Oct 2026

    Ora's lab found agents paying through Stripe Link got 92.3 percent of test checkouts right (733 of 794 runs in a cloud browser), across 26 agent setups on the same 33 checkout tasks (AgentReady guide, October 2026).

    Vendor claim. AgentReady.org guide, read 4 Nov 2026
  • 8 Sep 2026

    Meta says Muse keeps passwords and payment methods out of the agent's view.

    Vendor claim. Meta: Introducing Muse (8 Sep 2026), read 4 Nov 2026

How to decide

  • Ask your processor which agent routes it supports and which shopping surfaces each one serves.
  • Supporting one route is enough for most checks. You do not need every protocol.
  • Treat per-request payments for content or an API as a separate decision from shopping checkout.

Where this shows up

  • Self-check question 15Has anyone in your business looked at agent payment approaches such as x402, ACP, UCP or MPP, even just to decide not yet?
  • Self-check question 14Has your payments or fraud team agreed how to treat a purchase or booking that an AI agent starts for a customer?
  • The ecommerce guideShopping surfaces, default-on channels, and the split between Amazon and Shopify over Meta's Muse.
  • The financial services guideComparison and quote apps inside ChatGPT that hand off to the firm's own site.

Sources

  1. Microsoft Advertising: Copilot Checkout and Brand Agents (Jan 2026) (about.ads.microsoft.com/en/blog/post/january-2026/conversations-that-convert-copilot-checkout-and-brand-agents), read 4 Nov 2026.
  2. x402 (x402.org), read 4 Nov 2026.
  3. Ora llms.txt (ora.ai/llms.txt), read 4 Nov 2026.
  4. Scorecard methodology: the crawl of 4 Nov 2026 (amireadyforagents.com/scorecards/methodology), read 4 Nov 2026.
  5. AgentReady.org guide (agentready.org), read 4 Nov 2026. Vendor claim.
  6. Meta: Introducing Muse (8 Sep 2026) (about.fb.com/news/2026/09/introducing-muse-personal-ai-agent), read 4 Nov 2026. Vendor claim.
  7. Sector scorecards dataset, edition 4 Nov 2026 (amireadyforagents.com/scorecards), read 4 Nov 2026.

Last reviewed