Agent Commerce Index

Where AI agents can safely find places to spend.

A source-backed, conservative directory for agentic commerce. It separates protocol signals from live purchase permission, then adds risk labels so agents and builders can route spend with human approval.

16Initial entries across protocols, platforms, and merchant signals.
3Protocol families tracked separately: ACP, UCP, and MCP.
0Entries treated as permission for autonomous spend without user approval.

Methodology

Source-backed, not hype-backed.

The goal is not to claim that every listed store is ready for every agent. The goal is to map public readiness signals and keep operational risk obvious.

Protocol signals are separate.

Stripe ACP, UCP, and MCP solve related but different problems. A store can appear in one ecosystem without exposing a universal agent checkout endpoint.

ACPUCPMCP

Spend requires controls.

Every listed commerce path should use user consent, spend caps, and a confirmation step before purchase. MCP access is not payment authorization.

Human approvalSpend caps

Risk is editorial.

Risk ratings consider ticket size, returns, inventory, shipping complexity, API blast radius, and whether spend can scale without friction.

LowMediumHigh

Agent Commerce Protocols

ACP, UCP, and MCP are not the same thing.

This distinction matters for builders. Checkout protocol support, tool protocol support, and merchant participation each imply different security work.

Stripe ACP

Stripe describes ACP as a way for AI agents to manage checkout flows between buyers and sellers, including shared payment-token handoff where configured.

CheckoutPayments

UCP

UCP positions itself as a commerce lifecycle protocol for discovery, checkout, identity linking, and order management across platforms and merchants.

DiscoveryOrder

MCP

MCP connects AI applications to external tools, resources, and workflows. It can power commerce tools, but it does not automatically approve purchases.

ToolsContext

Source-Backed Agent-Ready Stores

Initial trusted list.

These entries are seeded from public Stripe and UCP signals. They are candidates for agent routing, not blanket authorization.

Etsy

Marketplace signal through Stripe ACP and the UCP ecosystem. Useful for discovery-heavy purchases with many seller-specific constraints.

Confirm seller terms, shipping, personalization, and return policy before purchase.

Medium risk

URBN

Stripe announcement names URBN, including Anthropologie, Free People, and Urban Outfitters, as using Agentic Commerce Suite.

Require size, color, variant, and return-window confirmation.

Medium risk

Revolve

Fashion retailer listed in Stripe's Agentic Commerce Suite announcement.

Best for user-approved repeat-style flows, not blind autonomous checkout.

Medium risk

Abt Electronics

Electronics retailer listed in Stripe's Agentic Commerce Suite announcement.

Require model number, warranty, delivery, and return checks.

Medium risk

Wayfair, Target, Walmart

UCP names these retailers in its co-developed/adopted ecosystem list.

Use as ecosystem signals; verify individual live workflows before routing purchases.

Medium risk

Coach, Kate Spade, Halara, Nectar, Ashley Furniture

Additional merchants named in Stripe's public Agentic Commerce Suite announcement.

Higher-friction categories need explicit user review for fit, shipping, financing, and returns.

Medium risk

Autonomous Shopping Safety Ratings

Agent-to-merchant needs guardrails.

The page is intentionally conservative. A useful agent commerce index should reduce accidental spend, not encourage it.

Warning: enabling autonomous purchases carries financial risk. Always set spend limits on wallets, tokens, API keys, cards, and cloud accounts. This directory is informational and does not replace merchant terms, legal review, fraud controls, or user consent.

Agent-readable endpoint

Use the JSON index.

https://oceanbennett.com/agent-commerce.json

Versioned JSON for agents, crawlers, and developers building commerce-routing tools.

Open JSON

Submit

Want to be indexed?

Send a public source URL, protocol support, auth model, payment flow, refund policy, and recommended spend limits.

Submit a merchant signal