Skip to content
ProductArena

Agentic Commerce Arena

Agentic Commerce arenaBuyer checklist

Every requirement we judge agentic commerce products against, as a ready-to-send RFP checklist — with each item's priority, why it matters, and how the top-ranked products score on it today.

56 requirements · 13 themes · verdicts for 7 products · updated 2026-09-15 · priorities mirror the story weights our scoring uses (methodology)

Procurement report →
Show the markdown export
# Agentic Commerce — buyer checklist (RFP)

Derived from ProductArena's evidence-graded user-story taxonomy for Agentic Commerce: 56 judged requirements. Priorities mirror story weights (3 = must-have, 2 = should-have, 1 = nice-to-have).

## Agent checkout

- [ ] **[must-have]** My agent can create and update a cart or order draft through a documented protocol call
- [ ] **[must-have]** My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
- [ ] **[should-have]** Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)
- [ ] **[should-have]** Build against a versioned commerce protocol with a published schema and conformance or validation tooling

## Agent discovery

- [ ] **[must-have]** My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required
- [ ] **[must-have]** Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell
- [ ] **[should-have]** Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service
- [ ] **[should-have]** My agent can discover payable services and APIs through a published directory or discovery index

## Agenticness

- [ ] **[must-have]** Plug MCP servers into this product so it can use their tools
- [ ] **[must-have]** Connect an agent via an official MCP server
- [ ] **[must-have]** Drive the product through a documented public API
- [ ] **[must-have]** Delegate tasks to a built-in AI assistant inside the product
- [ ] **[should-have]** Point an agent at llms.txt or agent-oriented docs
- [ ] **[should-have]** Run the product headlessly / in CI for automation
- [ ] **[should-have]** Use an official CLI
- [ ] **[should-have]** Issue scoped/least-privilege API credentials for an agent
- [ ] **[should-have]** Build against official SDKs
- [ ] **[should-have]** Subscribe to events via webhooks
- [ ] **[should-have]** Get AI-generated insights and suggestions from my data inside the product
- [ ] **[should-have]** Set up automations that run autonomously in the background
- [ ] **[should-have]** Operate the product with natural-language commands
- [ ] **[should-have]** Explore an interactive API reference with runnable examples
- [ ] **[should-have]** Download a machine-readable API spec (OpenAPI or equivalent)
- [ ] **[should-have]** Rely on versioned APIs with a documented deprecation policy
- [ ] **[nice-to-have]** Test against a sandbox environment without touching production data

## Automation depth

- [ ] **[must-have]** Define rules that trigger actions automatically on events
- [ ] **[should-have]** Perform bulk operations across many items at once
- [ ] **[should-have]** Schedule recurring jobs or workflows
- [ ] **[nice-to-have]** Version, review, and roll back my automations

## Fees economics

- [ ] **[should-have]** The fees for agent-originated transactions are published — I can price agentic channels without asking sales
- [ ] **[nice-to-have]** Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel

## Merchant enablement

- [ ] **[must-have]** I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint
- [ ] **[should-have]** Orders are attributed to the originating agent and I can report on or filter transactions by agent
- [ ] **[should-have]** Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout

## Openness

- [ ] **[must-have]** Export all of my data in open formats and leave
- [ ] **[must-have]** Self-host the core product
- [ ] **[should-have]** Do everything through the API that I can do in the UI
- [ ] **[should-have]** Read the product's source under an open license

## Order lifecycle

- [ ] **[must-have]** My agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically
- [ ] **[should-have]** My agent can query the status and tracking of an order it placed, after the purchase

## Payment credentials

- [ ] **[must-have]** Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
- [ ] **[must-have]** Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
- [ ] **[must-have]** Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility
- [ ] **[should-have]** Settle agent-initiated payments in stablecoins over documented rails

## Privacy posture

- [ ] **[must-have]** Prevent my data from being used to train AI models
- [ ] **[should-have]** Choose where my data is stored (region/residency)
- [ ] **[should-have]** Control data retention and deletion
- [ ] **[should-have]** Opt out of telemetry and usage tracking

## Protocol openness

- [ ] **[must-have]** The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything
- [ ] **[should-have]** At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration

## Refunds disputes

- [ ] **[should-have]** Disputes and chargebacks on agent transactions can be handled via API — evidence submission, status, outcomes
- [ ] **[should-have]** Refunds on agent-placed orders can be initiated and tracked programmatically

## Trust safety

- [ ] **[must-have]** Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots
- [ ] **[must-have]** Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
- [ ] **[should-have]** The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk
- [ ] **[should-have]** Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly

---

Source: https://ultrametric.ai/productarena/arena/agentic-commerce (evidence-graded verdicts for 7 products) · methodology: https://ultrametric.ai/productarena/methodology

Chips show the top 5 ranked products' current verdict on each requirement — ✓ full · ~ partial · ! disputed · — none · n/a not applicable.

Agent checkout — stories about agent checkout in this arenaAgent checkout· 4 items

Stories about agent checkout in this arena

Agent discovery — stories about agent discovery in this arenaAgent discovery· 4 items

Stories about agent discovery in this arena

Agenticness — how well agents can access and operate the productAgenticness· 17 items

How well agents can access and operate the product

Automation depth — how much of the product can run unattendedAutomation depth· 4 items

How much of the product can run unattended

Fees economics — stories about fees economics in this arenaFees economics· 2 items

Stories about fees economics in this arena

Merchant enablement — stories about merchant enablement in this arenaMerchant enablement· 3 items

Stories about merchant enablement in this arena

Openness — open source, data portability, and self-hosting storiesOpenness· 4 items

Open source, data portability, and self-hosting stories

Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle· 2 items

Stories about order lifecycle in this arena

Payment credentials — stories about payment credentials in this arenaPayment credentials· 4 items

Stories about payment credentials in this arena

Privacy posture — data-handling and privacy storiesPrivacy posture· 4 items

Data-handling and privacy stories

Protocol openness — stories about protocol openness in this arenaProtocol openness· 2 items

Stories about protocol openness in this arena

Refunds disputes — stories about refunds disputes in this arenaRefunds disputes· 2 items

Stories about refunds disputes in this arena

Trust safety — stories about trust safety in this arenaTrust safety· 4 items

Stories about trust safety in this arena

Full evidence behind every verdict lives on the arena page and each product page — chips above deep-link straight to the judged story.