Stripe Agentic Commerce vs Coinbase x402

Cart

1. ai-native userMy agent can create and update a cart or order draft through a documented protocol call

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialclaimed7/10

   Stripe's ACP-style custom checkout documents an explicit reverse-API contract where sellers implement create/update/confirm endpoints and sessions move through documented statuses (incomplete | ready_for_payment | requires_escalation | processing | completed | canceled), directly matching cart/order-draft creation and update via a documented protocol call; the embedded OCA flow also covers 'cart management' end-to-end. However this is gated behind private preview, US-only availability, and a waitlist, with no independent/hands-on evidence of a successful cart-update call in the pack. Missing for 10: independent/hands-on verification of a live create/update call succeeding, and confirmation the feature is generally available rather than waitlisted preview.

   • [claimed-docs] “The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and th…”
   • [claimed-docs] “For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “Stripe's agentic-commerce hub is explicitly chat-native: "Buyers can browse products, get personalized recommendations, and complete purchas…”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   x402 documents per-request HTTP 402 payment flows (quote price, sign payment, verify, settle) but nothing in the evidence describes a cart or order-draft object that an agent can create/update via a protocol call — the protocol is stateless pay-per-request, not cart/order management, and even the 'merchant checkout' integration mention (doc-13) only says agents can 'authorize payment sessions,' not manage draft orders. Missing for 10: any documented cart/order object, create/update API or protocol verbs, and evidence of persisted order state across calls.

   • [claimed-docs] “x402-enable a merchant checkout built on Payment Acceptance so agents can authorize payment sessions directly.”
   • [claimed-docs] “"x402 is an open standard for adding per-request payments to HTTP, so APIs and services can charge without checkout pages, subscriptions, or…”

   proof ↗⚑ flag

Checkout

1. ai-native userMy agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed8/10

   Stripe documents the full end-to-end agent checkout: sellers publish catalogs via ACS, agents complete checkout via ACP/UCP or embedded flows, shared payment tokens serve as delegated payment credentials with scoped usage limits, and completion is confirmed via checkout.session.completed events with agent attribution; runtime probes confirm the MCP server, Link CLI, and MPP infra are live. missing for 10: independent hands-on end-to-end purchase report (community evidence is speculative/skeptical, not a confirmed successful transaction), and several flows (ACS custom checkout, OCA embedding) remain private-preview/waitlisted rather than generally available.

   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and th…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”
   • [claimed-docs] “For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management…”
   • [claimed-docs] “Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases.”
   • [probe] “PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and p…”

   proof ↗⚑ flag

   Coinbase x402~partialprobed7/10

   Docs describe a complete flow — an agent hitting a 402 response, resolving payment terms, signing with an agentic wallet/account (delegated credential), the CDP Facilitator verifying and settling onchain, and the resource server returning the confirmed resource — and probes confirm the discovery and facilitator endpoints behave live as documented. However this is a per-request HTTP payment handshake rather than a traditional multi-step 'checkout session', and there is no independent/hands-on trace of an agent completing a full purchase (discovery→credential→confirmed order) end-to-end; community commentary even flags unresolved trust gaps in confirming delivered work post-payment. Missing for 10: independent third-party demonstration of a full agent purchase transcript, and clarity on session-like continuity versus single-request settlement.

   • [claimed-docs] “"x402 is an open standard for adding per-request payments to HTTP, so APIs and services can charge without checkout pages, subscriptions, or…”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [claimed-docs] “Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is the source of US…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the hosted CDP facilitator auth-gates as documented — a keyless GET to https://api.cdp.coinbase.com/pla…”
   • [community] “We run 124 x402 endpoints at httpay.xyz and the 'verify work was done' problem is real — especially for compute-heavy tasks like image gener…”

   proof ↗⚑ flag

Embedded surfaces

1. merchantBuyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialclaimed5/10

   Stripe's ACP/ACS clearly enables in-chat browsing and checkout, with concrete evidence tied to ChatGPT (OpenAI co-developed ACP, 'first AI platform to implement ACP with ChatGPT', and merchant onboarding/CSV catalog/checkout-session flows), plus SPT tokenization and human-approval gates. However, evidence names only ChatGPT as a live surface — there is no documentation or proof of live integration with Claude, Gemini, or Copilot — and the embedded/agent-as-intermediary checkout mode is explicitly gated as 'private preview' and limited to 'US, Canada, and select European countries,' with ChatGPT participation requiring an application rather than being open by default. Community threads raise trust/incentive concerns but don't concretely contradict that checkout works for ChatGPT. missing for 10: evidence of live checkout support in Claude/Gemini/Copilot, and proof the private-preview gating has lifted to general availability.

   • [claimed-docs] “Stripe's agentic-commerce hub is explicitly chat-native: "Buyers can browse products, get personalized recommendations, and complete purchas…”
   • [claimed-docs] “"ACP is open source and community-designed under the Apache 2.0 license. Businesses can implement the specification to transact with any AI …”
   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   x402 documents agent-to-agent/API payment infrastructure (MCP-compatible tool-call discovery, AWS Bedrock AgentCore, Agentic Wallets) but there is no evidence of integration with named consumer chat/assistant surfaces like ChatGPT, Claude, Gemini, or Copilot enabling buyers to complete purchases inside those chat UIs. The protocol targets machine-to-machine settlement, not consumer chat checkout flows in these specific products.

   • [claimed-docs] “Give an AgentCore agent access to x402 services through an AWS Payment Manager and Coinbase CDP connector.”
   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”

   proof ↗⚑ flag

Protocol conformance

1. developerBuild against a versioned commerce protocol with a published schema and conformance or validation tooling

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialprobed6/10

   Stripe documents an open, community-governed protocol (ACP, Apache 2.0, published spec at agenticcommerce.dev) and, for the sibling Machine Payments Protocol, an explicit conformance CLI ('mppx validate' tests discovery, challenge formats, error handling, and the full payment flow) plus a public spec site (mpp.dev) confirmed live by probe. However, there's no evidence of a formally versioned schema (e.g., semver, changelog) for ACP itself, no OpenAPI/JSON schema found (probe explicitly 404s for openapi.json/swagger.json), and no ACP-specific validator analogous to mppx validate — conformance tooling is documented only for MPP, not the core commerce checkout protocol. missing for 10: versioned ACP schema/spec artifact, ACP-specific conformance/validation tool, published machine-readable OpenAPI schema.

   • [claimed-docs] “"ACP is open source and community-designed under the Apache 2.0 license. Businesses can implement the specification to transact with any AI …”
   • [claimed-docs] “MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and T…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Coinbase x402~partialprobed5/10

   x402 is documented as a versioned protocol under open Linux Foundation governance (v2 support tables, TSC oversight, npm package with SLSA provenance) and has clear spec docs (how-it-works, facilitator support tables), but there is no published formal schema (e.g., JSON Schema/OpenAPI) or explicit conformance/validation test suite in evidence — the openapi probe returned 404s and no conformance-testing tool is mentioned. missing for 10: published machine-readable schema (OpenAPI/JSON Schema), an official conformance or validation test suite/tool, and independent confirmation of protocol versioning practices beyond npm version numbers.

   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”
   • [claimed-docs] “Governance: "x402 was originally incubated at Coinbase." — then the "x402 Foundation launched under the Linux Foundation" and "Coinbase comp…”
   • [claimed-docs] “Named governance seats on x402.org: "The x402 Governing Board is responsible for marketing, business oversight, and budget decisions for the…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the hosted CDP facilitator auth-gates as documented — a keyless GET to https://api.cdp.coinbase.com/pla…”

   proof ↗⚑ flag

Agent search

1. ai-native userMy agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required

   weight 3 · round to Coinbase x402
   Stripe Agentic Commerce~partialclaimed4/10

   Stripe does expose some keyless/self-service discovery paths — the Link CLI lets an agent 'Search products and complete payments with UCP' using a customer-controlled wallet with self-service credentials (no merchant partnership needed on the buyer side), and Stripe Directory helps agents find external providers. But the flagship agentic-commerce discovery/checkout path (ACS/OCA) explicitly requires a private, seller-initiated relationship — 'Only a seller can initiate an OCA request' and 'An OCA is a required connection between your agent and a seller that enables agentic commerce flows' — and is gated as 'private preview' in limited geographies, meaning broad cross-merchant search without any partnership is not generally available. missing for 10: universal, partnership-free product search across arbitrary merchants (most flows require seller-approved OCA or private-preview access), independent/hands-on confirmation that Link CLI's UCP search actually returns cross-merchant results without any seller-side integration.

   • [claimed-docs] “"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to compl…”
   • [claimed-docs] “Stripe Directory helps developers and AI agents find the best external providers for a task and follow the best supported path to provision …”
   • [claimed-docs] “For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management…”
   • [claimed-docs] “Stripe's agentic-commerce hub is explicitly chat-native: "Buyers can browse products, get personalized recommendations, and complete purchas…”

   proof ↗⚑ flag

   Coinbase x402✓fullprobed9/10

   The x402 Bazaar provides a public, keyless discovery API and MCP-tool-call interface for agents to search payable services across merchants without any partnership or API key, and a live runtime probe confirms the keyless GET returned real payable-service listings exactly as documented. Docs also detail self-service alternative (CDP API key) and automatic listing without registration, and community sources corroborate agents using x402 to discover/pay for services without prior accounts. Missing for 10: independent third-party evaluation of discovery relevance/quality beyond Coinbase's own docs and the single runtime probe.

   • [claimed-docs] “When you build with the CDP SDK's x402 building blocks, x402 Bazaar support is enabled automatically. There is no registration form or separ…”
   • [claimed-docs] “Bazaar discovery is public. You do not need a CDP API key to use the discovery APIs or the corresponding TypeScript SDK functions.”
   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [claimed-docs] “"Getting discovered makes your endpoint available to tens of thousands of agents through CDP APIs, the Bazaar MCP server, and Amazon Bedrock…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”
   • [community] “It's a great way for developers or ai agents to test drive an API without creating an account and getting an API key from the api provider. …”

   proof ↗⚑ flag

Machine readable offers

1. developerRead machine-readable offer data — price, availability, variants, checkout links — for any listed product or service

   weight 2 · round to Coinbase x402
   Stripe Agentic Commerce~partialclaimed6/10

   Stripe documents a seller-side catalog feed (CSV) containing product/variant rows with price and availability fields, plus checkout completion via shared payment tokens and delegated checkout webhooks, and agent-builder docs describe 'product feed ingestion' so agents can present offers and checkout. However, the mechanism is a seller-pushed feed into Stripe's index rather than a documented universal read/query API that any developer/agent can call to fetch offer data for an arbitrary listed product, and it's gated behind private preview, onboarding agreements (OCA), and US/Canada/EU-only availability. Missing for 10: a documented public read/query endpoint or protocol response schema for agents to pull offer data on demand, and independent/hands-on confirmation of catalog read access working end-to-end.

   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management…”
   • [claimed-docs] “The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and th…”
   • [claimed-docs] “Stripe's agentic-commerce hub is explicitly chat-native: "Buyers can browse products, get personalized recommendations, and complete purchas…”

   proof ↗⚑ flag

   Coinbase x402~partialprobed7/10

   The x402 Bazaar discovery API/SDK returns machine-readable listings for payable services — price (USDC amount), network/asset/scheme, timeout, and a resource endpoint that itself acts as the 'checkout' call — and this was independently confirmed live via a keyless GET returning real listings (probe-rt-1), matching docs on public discovery with no API key needed (docs-6, supp-5, supp-6). Availability is implicit (30-day settlement pruning keeps the catalog live) but the docs never explicitly frame data as 'variants' or provide a distinct 'checkout link' field beyond the resource URL itself. Missing for 10: explicit variant/option metadata in listings, an explicit checkout-link field distinct from the resource endpoint, and independent (non-Coinbase) confirmation of listing completeness/accuracy.

   • [claimed-docs] “When you build with the CDP SDK's x402 building blocks, x402 Bazaar support is enabled automatically. There is no registration form or separ…”
   • [claimed-docs] “Bazaar discovery is public. You do not need a CDP API key to use the discovery APIs or the corresponding TypeScript SDK functions.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [claimed-docs] “"Getting discovered makes your endpoint available to tens of thousands of agents through CDP APIs, the Bazaar MCP server, and Amazon Bedrock…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”

   proof ↗⚑ flag

Merchant feeds

1. merchantPublish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullclaimed9/10

   Stripe documents a concrete, detailed catalog-publishing mechanism for merchants: a CSV feed format uploaded via the v2 Product Catalog Import API to a presigned URL, with defined cadence (daily product data, 15-min inventory/pricing), explicit replace-mode deletion semantics, import-result webhooks with per-row error reporting, and required restricted-key permissions — all under the self-serve ACS onboarding flow described in the for-sellers docs. This directly matches the story of publishing a catalog into agent surfaces via a documented feed/import API, going well beyond a vague claim into an operational spec merchants can implement against. missing for 10: independent/hands-on merchant confirmation of the import pipeline working end-to-end, and the feature is still gated to private preview / limited geographies (US, Canada, select European countries) rather than universally GA.

   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration.”
   • [claimed-docs] “It lets you share product, price, and availability information with agents while minimizing changes to your existing commerce systems.”
   • [claimed-docs] “Stripe's agentic-commerce hub is explicitly chat-native: "Buyers can browse products, get personalized recommendations, and complete purchas…”

   proof ↗⚑ flag

   Coinbase x402~partialprobed6/10

   x402 Bazaar auto-lists any x402-enabled endpoint into a discoverable catalog (23,000+ resources) accessible via API, TypeScript SDK, or MCP tool calls, with no registration form needed once payment settles — this functions as a merchant discovery feed for agents. However, it is not a true 'catalog/import API' in the product-catalog sense: listing requires actually running a live payable endpoint and a successful settled payment (not a bulk import of a product list), items expire after 30 days without settlement, and there's no support for describing multiple SKUs/services or rich product metadata beyond price/asset/network. Missing for 10: a genuine bulk catalog-import or feed format for multiple products/services at once, richer product metadata (descriptions, categories) beyond payment terms, and independent hands-on confirmation that discovery surfaces reliably drive agent traffic to listed merchants.

   • [claimed-docs] “When you build with the CDP SDK's x402 building blocks, x402 Bazaar support is enabled automatically. There is no registration form or separ…”
   • [claimed-docs] “Bazaar discovery is public. You do not need a CDP API key to use the discovery APIs or the corresponding TypeScript SDK functions.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [claimed-docs] “"Getting discovered makes your endpoint available to tens of thousands of agents through CDP APIs, the Bazaar MCP server, and Amazon Bedrock…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”

   proof ↗⚑ flag

Service discovery

1. ai-native userMy agent can discover payable services and APIs through a published directory or discovery index

   weight 2 · round to Coinbase x402
   Stripe Agentic Commerce✓fullprobed7/10

   Stripe publishes a live, machine-readable discovery surface: the 'Stripe Directory' explicitly helps 'developers and AI agents find the best external providers for a task and follow the best supported path to provision or use them' (docs-13), backed by a probed live well-known skills/services index (stripe-ac-probe-rt-3) and the open mpp.dev spec index for machine-payable APIs (stripe-ac-probe-rt-2), plus per-endpoint discovery via HTTP 402 challenges (docs-9/18/19). Missing for 10: concrete evidence that the Directory itself indexes specifically 'payable' services/APIs (vs. general providers) and an end-to-end example of an agent using the directory to find and pay for a service.

   • [claimed-docs] “Stripe Directory helps developers and AI agents find the best external providers for a task and follow the best supported path to provision …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.str…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the …”
   • [claimed-docs] “x402 is a protocol for internet payments... your server returns an HTTP 402 response with payment details, including a Stripe deposit addres…”
   • [claimed-docs] “Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid …”

   proof ↗⚑ flag

   Coinbase x402✓fullprobed9/10

   The x402 Bazaar is a documented, keyless, public discovery index (23,000+ resources) that agents can query via search API, TypeScript SDK, or MCP tool calls, and a runtime probe confirmed live discovery results without an API key. missing for 10: independent (non-Coinbase) hands-on confirmation of agents successfully using the discovery index end-to-end in production beyond the single runtime probe.

   • [claimed-docs] “When you build with the CDP SDK's x402 building blocks, x402 Bazaar support is enabled automatically. There is no registration form or separ…”
   • [claimed-docs] “Bazaar discovery is public. You do not need a CDP API key to use the discovery APIs or the corresponding TypeScript SDK functions.”
   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [claimed-docs] “"Getting discovered makes your endpoint available to tens of thousands of agents through CDP APIs, the Bazaar MCP server, and Amazon Bedrock…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed9/10

   Stripe confirms a live llms.txt (HTTP 200 probe) and extensive agent-oriented markdown docs (.md endpoints, skills.json well-known catalog, MCP server, link-cli --llms-full), all directly consumable by an agent pointed at these URLs. missing for 10: independent third-party confirmation that agents actually consume/parse these files effectively in the wild beyond Stripe's own probes.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/agentic-commerce.md # Agentic commerce Sell through agents, or embed commerce into your …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.str…”
   • [claimed-docs] “Install instructions that help AI agents create more accurate Stripe integrations.”
   • [claimed-docs] “"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to compl…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Coinbase x402✓fullprobed8/10

   Probes confirm a live llms.txt at docs.cdp.coinbase.com/llms.txt (200) and per-page .md docs (e.g. x402/welcome.md) that explicitly point agents to the llms.txt index, plus docs explicitly describe agent/MCP-oriented discovery flows. missing for 10: no independent third-party report of an agent actually consuming llms.txt to complete a task, and no OpenAPI spec (404s) as a complementary machine-readable format.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cdp.coinbase.com/llms.txt # Coinbase Developer Documentation - [Docs (537 pages)](https://docs.cdp…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.cdp.coinbase.com/x402/welcome.md > ## Documentation Index > Fetch the complete documentation index a…”
   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialclaimed5/10

   Stripe ships CLI/API primitives that could run headlessly — anonymous CI sandbox creation via `stripe sandbox create` (no account registration), an `mppx validate` conformance CLI for automated end-to-end testing of MPP integrations, and REST/MCP APIs that are inherently non-interactive. However, the core agentic-commerce and Link CLI wallet flows are explicitly gated by mandatory human approval ("Stripe requires human confirmation before it takes certain stripe_api_write actions"; "Customers approve each request on the Link website or in the mobile app"), which blocks fully unattended CI automation of actual payment execution. Missing for 10: explicit CI/pipeline documentation or examples, a documented way to bypass/automate the human-approval step for testing, and evidence of headless operation for the core checkout/SPT flows rather than just sandbox/dev tooling.

   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
   • [claimed-docs] “MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and T…”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”
   • [claimed-docs] “"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to compl…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed4/10

   x402 is an HTTP-based payment protocol designed to be invoked programmatically by servers/agents (e.g., 'agent purchasing a tool call mid-task', SDK-based integration, MCP tool-call discovery), which implies it can run in automated/headless contexts like CI, but there is no explicit evidence of a CLI, CI pipeline example, or headless automation harness/test suite. missing for 10: explicit CI/headless automation examples, a documented CLI, non-interactive test/dev workflow guidance, and independent confirmation of running x402 flows unattended in build pipelines.

   • [claimed-docs] “an agent purchasing a tool call mid-task”
   • [claimed-docs] “AI agent pays instantly with stablecoins No signups or approvals required”
   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [claimed-docs] “Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is the source of US…”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed9/10

   Stripe documents and runtime-verifies a first-party hosted MCP server (mcp.stripe.com) with clear auth (OAuth 401 challenge observed live) and documented tools for AI agents to interact with the Stripe API, plus human-approval gating for sensitive actions. This is corroborated by both docs and a runtime probe confirming the endpoint is live and gated exactly as documented. Missing for 10: independent third-party (non-Stripe) hands-on report of connecting an agent to the MCP server in production use.

   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed6/10

   Docs explicitly describe an official 'Bazaar MCP server' letting MCP-compatible agents discover payment-gated x402 services via tool calls, which is a genuine first-party MCP server integration for the agentic discovery flow. However, the MCP server appears scoped to discovery only (finding payable resources), not the full pay/settle transaction flow, and there's no independent/hands-on corroboration of the MCP server itself (only docs mention it). Missing for 10: evidence that payment execution (not just discovery) can be driven through the MCP server, and independent/community verification of the MCP server working end-to-end.

   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [claimed-docs] “"Getting discovered makes your endpoint available to tens of thousands of agents through CDP APIs, the Bazaar MCP server, and Amazon Bedrock…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed8/10

   Stripe ships the official Link CLI (@stripe/link-cli, published on npm and confirmed live in a runtime probe, v0.19.2) for agent wallet access, plus the Stripe CLI for sandbox provisioning and mppx CLI for MPP conformance testing, all documented and agent-legible (--llms-full docs). missing for 10: no independent/community hands-on review of the CLI's usability, and multiple overlapping CLIs (stripe, link-cli, mppx) rather than one unified official CLI.

   • [claimed-docs] “Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to comple…”
   • [github] “The CLI can produce one of three credential types: A virtual card (PAN)... A Link Pay Token (LPT)... A Shared Payment Token (SPT)”
   • [claimed-docs] “"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to compl…”
   • [probe] “official CLI documented at https://docs.stripe.com/agentic-commerce/link-cli”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and p…”
   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
   • [claimed-docs] “MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and T…”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   No evidence pack item mentions an official CLI tool for x402; the documentation focuses on SDKs, facilitator APIs, MCP integration, and discovery, but nothing describes a CLI product. missing for 10: any mention of an x402 CLI, its commands, or install instructions.

   ⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed9/10

   Stripe publishes extensive, concrete public API documentation for agentic commerce — ACS seller/agent endpoints, shared payment tokens, machine payments (MPP/x402), a hosted MCP server, and a CLI — all with runtime-verified live endpoints (401-gated MCP server, live mppx package, live skills.json, live link-cli npm package), giving AI-native users clear documented ways to drive the product programmatically. Missing for 10: a discoverable formal OpenAPI/swagger schema (probe-3 shows all candidate spec URLs 404) and independent third-party hands-on API integration reports beyond Stripe's own docs.

   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [probe] “PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.str…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and p…”
   • [claimed-docs] “The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and th…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Coinbase x402~partialprobed6/10

   x402 exposes a documented HTTP-based protocol (402 flow, discovery APIs, facilitator endpoints) that AI agents can drive programmatically, with runtime probes confirming the discovery endpoint is live and keyless and the facilitator auth-gates as documented. However this is a payment/discovery protocol, not a general product API — there's no OpenAPI spec (probe-3 shows 404s across candidate paths), and full programmatic control (e.g., managing wallets, settlement, compliance rules) still routes through CDP SDKs rather than a single unified public API surface. missing for 10: a formal OpenAPI/swagger spec, independent hands-on confirmation of the full request/pay/retry loop beyond discovery, and evidence of broader API coverage beyond payments/discovery.

   • [claimed-docs] “Add one line of code to require payment for each incoming request. If a request arrives without payment, the server responds with HTTP 402, …”
   • [claimed-docs] “Bazaar discovery is public. You do not need a CDP API key to use the discovery APIs or the corresponding TypeScript SDK functions.”
   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the hosted CDP facilitator auth-gates as documented — a keyless GET to https://api.cdp.coinbase.com/pla…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
   • [claimed-docs] “"x402 is an open standard for adding per-request payments to HTTP, so APIs and services can charge without checkout pages, subscriptions, or…”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullclaimed8/10

   Stripe documents Restricted API Keys (RAKs) as 'the recommended type of key for API keys you give to AI agents' with granular permission scoping, plus scoped Shared Payment Tokens with currency/amount/expiration limits and revocation, and MCP server actions gated by human approval tokens — together giving strong least-privilege credentialing for agents. missing for 10: independent/hands-on verification of RAK permission granularity in practice, and no evidence of automated credential rotation or audit-logging specifics for agent-issued keys.

   • [claimed-docs] “RAKs are the recommended type of key for API keys you give to AI agents.”
   • [claimed-docs] “Stripe recommends always using RAKs instead of unrestricted secret keys, especially when giving a key to an AI agent. Use RAK permissions to…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”
   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed4/10

   x402 replaces API keys with pay-per-request payments rather than issuing scoped API credentials, so there's no OAuth-style scope/permission system; however, 'Agentic accounts'/'Agentic Wallet' let a user give an agent a wallet to autonomously pay for services, and batch-settlement escrow includes cryptographically signed spending limits and defined refund/withdrawal semantics, which functions as a loose least-privilege spend-limit mechanism for the agent's payment authority. Missing for 10: explicit API-credential scoping (read/write/resource-level permissions), granular per-service access control beyond payment limits, and independent confirmation that these spend-limit controls are enforced in practice.

   • [claimed-docs] “Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is the source of US…”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”
   • [claimed-docs] “The batch-settlement scheme targets high-frequency agent loops: "Batch settlement lets agents perform thousands of granular interactions whi…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed9/10

   Stripe ships extensive official SDK/CLI/protocol tooling for AI-native builders: a hosted MCP server (docs + runtime probe confirming live OAuth-gated endpoint), Link CLI published on npm with runtime verification, agent skills catalog served at a well-known JSON endpoint, restricted API keys guidance for agents, MPP/x402 machine-payment protocols with open spec and mppx conformance CLI, and one-prompt agent build flows. This is corroborated by independent runtime probes (npm resolution, live endpoint checks), not just vendor docs. missing for 10: no independent third-party developer testimonial/case study of building against these SDKs (only Stripe-run runtime probes and docs), and ACP/MCP write actions still require human approval gating rather than fully autonomous agent operation.

   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [claimed-docs] “Install instructions that help AI agents create more accurate Stripe integrations.”
   • [claimed-docs] “RAKs are the recommended type of key for API keys you give to AI agents.”
   • [claimed-docs] “Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to comple…”
   • [github] “The CLI can produce one of three credential types: A virtual card (PAN)... A Link Pay Token (LPT)... A Shared Payment Token (SPT)”
   • [probe] “PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.str…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and p…”
   • [claimed-docs] “MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and T…”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”

   proof ↗⚑ flag

   Coinbase x402~partialprobed6/10

   Docs reference SDK building blocks (CDP SDK's x402 building blocks, TypeScript SDK discovery functions, npm package x402 confirmed live at v1.2.0 with SLSA provenance) and MCP/AgentCore integrations, showing real SDK-based build paths for AI agents. However, evidence lacks concrete SDK code samples, comprehensive language coverage, or independent developer corroboration beyond one HN comment expressing intent to try it with FastAPI. missing for 10: actual SDK code examples/API reference beyond npm existence, multi-language SDK coverage evidence, independent hands-on developer reports of building with the SDK successfully.

   • [claimed-docs] “When you build with the CDP SDK's x402 building blocks, x402 Bazaar support is enabled automatically. There is no registration form or separ…”
   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the hosted CDP facilitator auth-gates as documented — a keyless GET to https://api.cdp.coinbase.com/pla…”
   • [community] “this looks great, gonna look into writing something to use with fastapi”

   proof ↗⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Stripe Agentic Commerce~partialclaimed5/10

   Machine payments (x402, MPP) let agents transact programmatically without a human in the loop for each call, and SPTs allow scoped, usage-limited autonomous spending — supporting some background automation. However, the same evidence pack documents pervasive human-approval gates for higher-value or write actions ('Stripe requires human confirmation before it takes certain stripe_api_write actions' and 'Customers approve each request on the Link website or in the mobile app'), which directly limits true unattended background autonomy for most commerce flows. Missing for 10: a documented persistent/scheduled automation or workflow feature that runs entirely without any human approval step across the product's full scope, and independent evidence of such automations running successfully unattended.

   • [claimed-docs] “"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid…”
   • [claimed-docs] “MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and T…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”
   • [claimed-docs] “"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to compl…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed5/10

   x402 enables agent wallets to autonomously discover and pay for services mid-task (agentic accounts, Bazaar discovery, MCP tool-call discovery, batch settlement for high-frequency loops), which supports background autonomous payment automations, but the product itself is a payment protocol/infrastructure layer, not a scheduler or automation orchestrator — there's no evidence of triggers, cron-like scheduling, or persistent background task management outside of payment transactions. missing for 10: evidence of actual task/workflow scheduling or orchestration beyond payment execution, independent hands-on validation of autonomous background operation over time, and details on error handling/retry logic for unattended long-running agent loops.

   • [claimed-docs] “Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is the source of US…”
   • [claimed-docs] “Let an MCP-compatible agent discover services with tool calls.”
   • [claimed-docs] “an agent purchasing a tool call mid-task”
   • [claimed-docs] “The x402 protocol is introducing batch settlement, enabling agents to transact at extremely low latency and fractions of a cent.”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”
   • [claimed-docs] “The batch-settlement scheme targets high-frequency agent loops: "Batch settlement lets agents perform thousands of granular interactions whi…”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialprobed4/10

   Evidence shows agent-facing tooling that lets an AI actually exercise the API — a sandbox CLI that provisions working keys ("stripe sandbox create --help"), an MCP server exposing callable API tools, and a machine-readable skills/llms.txt catalog — but nothing in the pack describes a classic interactive API reference page with inline runnable code examples; the docs are plain markdown (per the .md probes) and the openapi.json/swagger.json spec paths all 404. missing for 10: a documented interactive reference UI (e.g. try-it/run-in-browser code samples), an OpenAPI/Swagger spec for the agentic-commerce endpoints, independent confirmation that examples execute against live data.

   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe’s kno…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the machine-readable skills catalog is live at the documented keyless well-known URL — https://docs.str…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/agentic-commerce.md # Agentic commerce Sell through agents, or embed commerce into your …”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   The evidence pack shows extensive text documentation but no mention of an interactive API reference or runnable examples; a probe explicitly found no OpenAPI/Swagger spec at any candidate path (404s), indicating no interactive reference tooling is exposed.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Stripe Agentic Commerce—none0/10

   The evidence pack shows a direct probe for an OpenAPI/Swagger spec at all standard locations (openapi.json, swagger.json, etc.) returning 404 across the board, and no other citation surfaces a downloadable machine-readable API spec for the Agentic Commerce endpoints. While Stripe ships llms.txt, a skills.json index, and an MCP server, none of these constitute a downloadable OpenAPI/equivalent spec for the story as written.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   A direct probe for OpenAPI/swagger specs at all standard paths on the CDP docs site returned 404s, and no other evidence pack item points to a downloadable machine-readable API spec; the docs only offer markdown/llms.txt style documentation, not an OpenAPI equivalent.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullclaimed7/10

   Stripe explicitly documents a sandbox provisioning flow for coding agents: 'run stripe sandbox create --help to provision an anonymous Stripe sandbox with working API keys. No account registration required,' which directly satisfies testing without touching production data. Missing for 10: independent/hands-on confirmation that agentic-commerce-specific flows (ACS, SPTs, machine payments) work in this sandbox, and documentation on how test-mode agent transactions differ from production before going live.

   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed3/10

   The only sandbox-relevant evidence is a passing mention that the facilitator's supported-network table includes Base Sepolia (a public testnet) alongside mainnet networks, implying developers could test payments without real funds — but there is no dedicated 'sandbox mode', test facilitator, or explicit developer guidance for testing against non-production data. missing for 10: explicit sandbox/testnet documentation or tutorial, dedicated test facilitator or test-mode API keys, guidance on faucet/test USDC usage, and any community/hands-on confirmation of a working testnet flow.

   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Stripe Agentic Commerce—none0/10

   The evidence pack covers extensive agentic-commerce features (SPTs, MCP, MPP, Link CLI, ACP) but contains no documentation of API version strings, an upgrade/versioning scheme, or a deprecation policy for these agentic-commerce endpoints — several features are explicitly flagged as 'private preview' or waitlisted rather than versioned/stable, but no deprecation policy is cited anywhere.

   • [claimed-docs] “Stripe's agentic-commerce hub is explicitly chat-native: "Buyers can browse products, get personalized recommendations, and complete purchas…”
   • [claimed-docs] “For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management…”
   • [claimed-docs] “The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and th…”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   The evidence pack shows a 'v2' support table for the facilitator API but nowhere documents an API versioning scheme, backward-compatibility guarantees, or a deprecation policy for x402 endpoints/SDKs; no changelog, sunset timeline, or version-support-window language appears anywhere in the docs or probes.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Coinbase x402
   Stripe Agentic Commerce~partialclaimed5/10

   Stripe provides some bulk-like primitives — sellers can upload a whole product catalog via CSV feed (up to 4GB) and 'bulk fulfill orders' via the List CheckoutSessions endpoint — but these are seller-side backend operations, not an AI-native user-facing bulk operation across many purchases/items in one agent action. There's no evidence of an agent being able to, e.g., issue one command to buy/refund/manage many items or transactions at once as an end-user capability. missing for 10: agent-facing bulk purchase/checkout across many items in one call, bulk SPT/token operations, batch API endpoints exposed to AI agents beyond seller catalog upload and fulfillment listing, independent hands-on confirmation of bulk agent workflows.

   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed7/10

   x402's batch-settlement scheme is documented specifically to let agents perform 'thousands of granular interactions' bundled into a single onchain settlement, which is the protocol's version of bulk/batch operations across many payment items (vouchers redeemed together). This is first-party documented with mechanics (escrow, cryptographic vouchers, refund semantics) but there is no independent or hands-on verification that this batching works at scale in production, and no evidence of bulk operations outside the payment-settlement context (e.g., bulk discovery or bulk resource management). Missing for 10: third-party/hands-on confirmation of batch settlement at scale, and evidence of bulk operations beyond payment batching.

   • [claimed-docs] “Charge however you price. Fixed-price, usage-based, and batched payments through the exact, upto, and batch-settlement schemes.”
   • [claimed-docs] “The x402 protocol is introducing batch settlement, enabling agents to transact at extremely low latency and fractions of a cent.”
   • [claimed-docs] “The batch-settlement scheme targets high-frequency agent loops: "Batch settlement lets agents perform thousands of granular interactions whi…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Coinbase x402
   Stripe Agentic Commerce—none0/10

   Evidence shows Stripe emits webhooks (checkout.session.completed, SPT state-transition events, import success/failure events) that developers can build on, but there is no documented feature letting an AI-native user define custom rules/conditions that automatically trigger actions on events — in fact, agent write-actions via MCP explicitly require human approval before execution, the opposite of automatic rule-triggered action.

   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed4/10

   x402 has some built-in event→action automation (a 402 response auto-triggers a client to sign and retry with payment; unpaid resources are auto-removed from the Bazaar after 30 days without settlement), but there is no evidence of a general rules engine where an AI-native user can define arbitrary custom triggers/conditions and actions — the automation is hardwired protocol behavior, not user-configurable rule authoring. missing for 10: a rule-definition interface or config, support for arbitrary event types beyond payment/settlement, user-set conditional logic (if/then) beyond the protocol's fixed retry-and-settle flow.

   • [claimed-docs] “Add one line of code to require payment for each incoming request. If a request arrives without payment, the server responds with HTTP 402, …”
   • [claimed-docs] “"Getting discovered makes your endpoint available to tens of thousands of agents through CDP APIs, the Bazaar MCP server, and Amazon Bedrock…”
   • [claimed-docs] “The x402 protocol is introducing batch settlement, enabling agents to transact at extremely low latency and fractions of a cent.”
   • [claimed-docs] “The batch-settlement scheme targets high-frequency agent loops: "Batch settlement lets agents perform thousands of granular interactions whi…”

   proof ↗⚑ flag

Fees transparency

1. merchantThe fees for agent-originated transactions are published — I can price agentic channels without asking sales

   weight 2 · round to Coinbase x402
   Stripe Agentic Commerce✓fullcommunity7/10

   Stripe explicitly publishes the flat card-processing rates (2.9%+30¢ domestic, plus documented adders for manual entry/international/currency conversion) and states these standard rates are what agent-originated orders inherit, with 'no separate agentic-channel fee schedule disclosed' — meaning a merchant can price ACS-driven sales from the public pricing page without a sales call. Missing for 10: no dedicated line-item fee schedule specifically labeled for agent/ACS transactions (only an inference that standard rates apply), and no clarity on whether third-party platform fees (e.g., ChatGPT's own merchant commission referenced in community discussion) stack on top for ACP-routed orders.

   • [claimed-docs] “stripe.com/pricing publishes the flat rates that agent-driven orders inherit, with no separate agentic-channel fee schedule disclosed: Stand…”
   • [community] “"Merchants pay a small fee on completed purchases, but the service is free for users, doesn't affect their prices, and doesn't influence Cha…”

   proof ↗⚑ flag

   Coinbase x402✓fullclaimed8/10

   Coinbase publishes a concrete, self-serve fee schedule for the CDP Facilitator (first 1,000 onchain transactions/month free, then $0.001 per additional transaction, verification always free, batch settlement amortizing costs further), letting a merchant price agentic payment flows without contacting sales. Missing for 10: independent/third-party verification of real-world billed fees, and any published fee variance across supported networks (Base, Polygon, Arbitrum, Solana) beyond the flat headline rate.

   • [claimed-docs] “Free to start, inexpensive to scale. The first 1,000 onchain Facilitator transactions each month are free, then each additional onchain tran…”
   • [claimed-docs] “Facilitator fees, verbatim: "Free to start, inexpensive to scale." — "The first 1,000 onchain Facilitator transactions each month are free",…”
   • [claimed-docs] “Built-in screening. OFAC and Know Your Transaction (KYT) checks identify and decline payments involving sanctioned or high-risk addresses.”

   proof ↗⚑ flag

Payouts

1. merchantAgent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel

   weight 1 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullclaimed8/10

   Agent-originated orders flow through standard Stripe primitives - checkout.session.completed events, Dashboard transaction tagging/filtering by agent, an agent_details field, bulk fulfillment, and standard Refunds API - with pricing docs confirming no separate agentic fee schedule and machine payments explicitly stating settlement/reporting 'work the same as any other payment in Stripe'. missing for 10: independent/third-party confirmation that reconciliation works in practice, and removal of the 'Private preview' gate on agent_details

   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”
   • [claimed-docs] “"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid…”
   • [claimed-docs] “stripe.com/pricing publishes the flat rates that agent-driven orders inherit, with no separate agentic-channel fee schedule disclosed: Stand…”
   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”

   proof ↗⚑ flag

   Coinbase x402~partialcommunity5/10

   Docs confirm the CDP Facilitator validates and settles payments onchain and 'reports the result to your resource server,' and sellers can receive to custodial or self-custody wallets, giving a baseline settlement/reporting hook comparable to other channels. However there's no documented merchant-facing statement/ledger/dashboard, refund/chargeback handling, or tax/accounting reconciliation tooling, and community reports (comm-10) note real-world friction around verifying settlement timing for variable-length agent tasks. Missing for 10: dedicated payout statements or ledger exports, refund/dispute reconciliation flow, and independent confirmation that merchants can reconcile x402 settlements against traditional accounting systems.

   • [claimed-docs] “The CDP Facilitator handles that work as a hosted service: it validates signed payments, screens transactions, submits settlement onchain, a…”
   • [claimed-docs] “Sellers receive at any address they control — including CDP custodial wallets, Coinbase Business, Prime, or a self-custody wallet”
   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”
   • [claimed-docs] “Facilitator fees, verbatim: "Free to start, inexpensive to scale." — "The first 1,000 onchain Facilitator transactions each month are free",…”
   • [community] “We run 124 x402 endpoints at httpay.xyz and the 'verify work was done' problem is real — especially for compute-heavy tasks like image gener…”

   proof ↗⚑ flag

Attribution analytics

1. merchantOrders are attributed to the originating agent and I can report on or filter transactions by agent

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullclaimed8/10

   Stripe's seller docs explicitly state that agent-driven orders generate a unique checkout.session.completed event, appear on the Dashboard Transactions page 'tagged with the originating agent,' and merchants 'can filter transactions by agent names,' with a documented agent_details field and bulk-fulfillment support via the CheckoutSessions API. Missing for 10: independent/hands-on confirmation of the attribution UI in practice, and the agent_details field is noted as Private preview rather than GA.

   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   The evidence pack covers payment settlement, discovery (Bazaar), wallets, screening, and fees, but nowhere describes agent-identity attribution on orders or a merchant-facing report/filter-by-agent capability. No dashboard, transaction log, or agent-ID field is documented.

   ⚑ flag

Onboarding to agents

1. merchantI have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint

   weight 3 · round to Coinbase x402
   Stripe Agentic Commerce~partialclaimed7/10

   Stripe documents a genuine self-serve merchant path: onboard as a seller in the Dashboard, review and accept per-agent terms, publish a CSV product catalog via presigned-URL API, and receive human-approval-gated agent orders tagged in the Transactions page. However this is explicitly gated - Agentic Commerce Suite is private preview and restricted to US, Canada, and select European countries, and the custom ACP-style integration explicitly requires joining a waitlist rather than pure self-serve enablement. Missing for 10: evidence of unrestricted GA availability outside private preview, and a self-serve (non-waitlist) path for the custom checkout-endpoint integration.

   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”
   • [claimed-docs] “The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and th…”
   • [claimed-docs] “Stripe's agentic-commerce hub is explicitly chat-native: "Buyers can browse products, get personalized recommendations, and complete purchas…”

   proof ↗⚑ flag

   Coinbase x402✓fullprobed8/10

   Docs give a concrete self-serve merchant path: add one line of code (or use CDP SDK x402 building blocks) to require payment, receive at any wallet address (custodial, self-custody, Business, Prime), and Bazaar discovery/listing happens automatically with no registration form or API call once payments settle — confirmed live via runtime probe of the discovery endpoint. missing for 10: no independent hands-on merchant onboarding report/case study corroborating the frictionless claim beyond docs+probe, and no explicit merchant-facing 'agreement' or ToS acceptance step is documented.

   • [claimed-docs] “Add one line of code to require payment for each incoming request. If a request arrives without payment, the server responds with HTTP 402, …”
   • [claimed-docs] “Sellers receive at any address they control — including CDP custodial wallets, Coinbase Business, Prime, or a self-custody wallet”
   • [claimed-docs] “When you build with the CDP SDK's x402 building blocks, x402 Bazaar support is enabled automatically. There is no registration form or separ…”
   • [claimed-docs] “Bazaar discovery is public. You do not need a CDP API key to use the discovery APIs or the corresponding TypeScript SDK functions.”
   • [claimed-docs] “Payable-service discovery is open: "The x402 Bazaar is a catalog of payment-gated services discovered by the CDP Facilitator." and "Bazaar d…”
   • [claimed-docs] “"Getting discovered makes your endpoint available to tens of thousands of agents through CDP APIs, the Bazaar MCP server, and Amazon Bedrock…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”

   proof ↗⚑ flag

Traffic controls

1. merchantRate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialclaimed5/10

   Merchants get agent-level allow/deny control via OCA consent ("Find the agent you want to sell through and review its terms", approval requests, and either party can terminate an OCA at any time) plus per-agent order attribution/filtering in the Dashboard, but there is no documented rate-limiting mechanism for specific agents or platforms. missing for 10: explicit per-agent or per-platform rate-limit/throttling controls, granular allow/deny at the platform (vs individual agent) level, and any dashboard UI for setting quotas.

   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management…”
   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   The evidence shows built-in OFAC/KYT screening for sanctioned addresses and general facilitator validation, but nothing about merchants configuring per-agent or per-platform allow/deny lists or rate limits. Access control in the docs is limited to compliance screening, not merchant-defined agent-level policies.

   • [claimed-docs] “Built-in screening. OFAC and Know Your Transaction (KYT) checks identify and decline payments involving sanctioned or high-risk addresses.”
   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”

   proof ↗⚑ flag

1. ai-native userRead the product's source under an open license

   weight 2 · round to Coinbase x402
   Stripe Agentic Commerce~partialprobed4/10

   The core Agentic Commerce Suite (checkout backend, SPT infrastructure, MCP server) is proprietary Stripe infrastructure with no published source, but the Agentic Commerce Protocol is explicitly 'open source and community-designed under the Apache 2.0 license,' and the Link CLI client has a public GitHub repo (stripe/link-cli). This gives an AI-native user real, licensed source to read for parts of the ecosystem, but not for the product's core commerce/payment engine. Missing for 10: open-licensed source for the actual ACS backend/checkout service, MCP server implementation, and MPP/x402 server-side code — only the protocol spec and a thin CLI client are open.

   • [claimed-docs] “"ACP is open source and community-designed under the Apache 2.0 license. Businesses can implement the specification to transact with any AI …”
   • [github] “The CLI can produce one of three credential types: A virtual card (PAN)... A Link Pay Token (LPT)... A Shared Payment Token (SPT)”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and p…”

   proof ↗⚑ flag

   Coinbase x402~partialprobed5/10

   The evidence shows x402 was contributed to the Linux Foundation and is now developed under 'open, vendor-neutral governance' with public docs and an npm-published SDK (v1.2.0) with SLSA provenance, implying source availability, but no citation ever names a specific open-source license (MIT/Apache/etc.) or points to a public repository. Missing for 10: explicit license text/repo citation, confirmation of source-code (not just protocol spec) openness, and independent verification that the code itself (not just governance) is freely licensed.

   • [claimed-docs] “Governance: "x402 was originally incubated at Coinbase." — then the "x402 Foundation launched under the Linux Foundation" and "Coinbase comp…”
   • [claimed-docs] “Named governance seats on x402.org: "The x402 Governing Board is responsible for marketing, business oversight, and budget decisions for the…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the hosted CDP facilitator auth-gates as documented — a keyless GET to https://api.cdp.coinbase.com/pla…”
   • [community] “The Linux Foundation... today announced it is launching the x402 Foundation with the contribution of the x402 protocol from Coinbase... It s…”

   proof ↗⚑ flag

Delegated credentials

1. ai-native userHand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed8/10

   Stripe ships exactly this: Shared Payment Tokens grant sellers scoped access with explicit usage_limits (currency, max_amount, expires_at), merchant/seller scoping, and revocation, and Link CLI issues one-time-use virtual cards/LPTs/SPTs to agents rather than raw PANs, with human approval gates on spend. This is corroborated by docs, GitHub source, and live npm/runtime probes. missing for 10: independent hands-on third-party audit of the credential-scoping mechanics (only vendor docs + probes, no external security review), and broader geographic/GA availability (features are private preview / US-Canada-EU only).

   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [github] “The CLI can produce one of three credential types: A virtual card (PAN)... A Link Pay Token (LPT)... A Shared Payment Token (SPT)”
   • [claimed-docs] “"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to compl…”
   • [claimed-docs] “Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to comple…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and p…”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed5/10

   x402 lets an agent's wallet make cryptographically signed, per-request payments with authorized-but-not-exceeded amounts (the 'upto' scheme) and batch-settlement vouchers where 'limits are cryptographically signed' and buyers retain 'refund and withdrawal semantics' — functioning like a scoped, capped credential rather than a raw card number. However, there is no documented mechanism for setting an explicit expiry window or restricting a credential to specific merchants; the wallet/agentic account simply holds USDC and signs payments to whatever service it calls. Missing for 10: explicit credential expiry configuration, merchant/service allow-listing, and a unified 'issue a scoped credential' UX rather than per-request signing.

   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”
   • [claimed-docs] “The batch-settlement scheme targets high-frequency agent loops: "Batch settlement lets agents perform thousands of granular interactions whi…”
   • [claimed-docs] “Charge however you price. Fixed-price, usage-based, and batched payments through the exact, upto, and batch-settlement schemes.”
   • [claimed-docs] “Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is the source of US…”

   proof ↗⚑ flag

Machine payments

1. developerMonetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed9/10

   Stripe explicitly documents HTTP 402 machine payments (x402 and MPP) letting agents pay per API call with no checkout UI, backed by a runtime probe confirming the MPP spec and mppx SDK are live, plus a conformance CLI (mppx validate) and one-prompt build path. missing for 10: independent/hands-on developer report of a working 402 integration beyond Stripe's own docs and probes.

   • [claimed-docs] “Machine payments let agents pay for APIs and services programmatically.”
   • [claimed-docs] “x402 is a protocol for internet payments... your server returns an HTTP 402 response with payment details, including a Stripe deposit addres…”
   • [claimed-docs] “"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid…”
   • [claimed-docs] “MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and T…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the …”

   proof ↗⚑ flag

   Coinbase x402✓fullprobed8/10

   x402 directly implements HTTP 402-based per-request payments with a one-line integration, hosted facilitator for verification/settlement, fixed/usage/batch pricing schemes, and agent-to-agent payment flows with no checkout UI, corroborated by runtime probes showing live discovery and facilitator endpoints and community reports of real deployments (httpay.xyz, Apiosk). missing for 10: independent hands-on verification of the exact developer 'one-line' integration experience beyond docs, and clearer resolution of community concerns about KYC/AML friction potentially affecting the 'no checkout UI' promise.

   • [claimed-docs] “Add one line of code to require payment for each incoming request. If a request arrives without payment, the server responds with HTTP 402, …”
   • [claimed-docs] “The CDP Facilitator handles that work as a hosted service: it validates signed payments, screens transactions, submits settlement onchain, a…”
   • [claimed-docs] “Charge however you price. Fixed-price, usage-based, and batched payments through the exact, upto, and batch-settlement schemes.”
   • [claimed-docs] “"x402 is an open standard for adding per-request payments to HTTP, so APIs and services can charge without checkout pages, subscriptions, or…”
   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the hosted CDP facilitator auth-gates as documented — a keyless GET to https://api.cdp.coinbase.com/pla…”
   • [community] “We run 124 x402 endpoints at httpay.xyz and the 'verify work was done' problem is real — especially for compute-heavy tasks like image gener…”
   • [community] “Apiosk approaches it from the server side: a gateway that enforces per-request x402 payments so API providers can monetize without accounts …”

   proof ↗⚑ flag

Settlement rails

1. developerSettle agent-initiated payments in stablecoins over documented rails

   weight 2 · round to Coinbase x402
   Stripe Agentic Commerce~partialprobed6/10

   Stripe explicitly documents stablecoin-denominated agent payments over documented rails (MPP on Tempo/USDC.e and Solana/USDC, x402 on Base/USDC) with published minimums (0.01 USDC) and geographic scope, and a runtime probe confirms the MPP spec and mppx SDK are live. However, the same docs state payments 'settle in fiat' into the Stripe balance rather than being settled to the developer in stablecoins, so the 'settle in stablecoins' half of the story is not actually delivered — it's stablecoin-denominated payment collection with fiat settlement. Missing for 10: actual stablecoin-denominated settlement (not fiat conversion), independent/hands-on developer corroboration beyond Stripe's own docs.

   • [claimed-docs] “"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid…”
   • [claimed-docs] “x402 is a protocol for internet payments... your server returns an HTTP 402 response with payment details, including a Stripe deposit addres…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the …”
   • [claimed-docs] “You can build an API that uses MPP with a single prompt to your coding agent”

   proof ↗⚑ flag

   Coinbase x402✓fullprobed9/10

   x402 is purpose-built for agent-initiated stablecoin (USDC/ERC-20/SPL) payments over a documented HTTP 402 protocol, with a hosted CDP Facilitator that verifies, screens (OFAC/KYT), and settles onchain across Base, Solana, Polygon, Arbitrum and World, and agent wallet integrations (Agentic Accounts, AgentCore, MCP) for autonomous payment flows. Runtime probes confirm the discovery API is live and keyless and the facilitator auth-gates as documented, and community hands-on reports (124 live x402 endpoints, HN builders using it with FastAPI) corroborate real-world settlement usage. missing for 10: independent large-scale audit of settlement finality/reliability, and resolution of the community-flagged 'verify work was done before settling' friction reported by production operators.

   • [claimed-docs] “The CDP Facilitator handles that work as a hosted service: it validates signed payments, screens transactions, submits settlement onchain, a…”
   • [claimed-docs] “Built-in screening. OFAC and Know Your Transaction (KYT) checks identify and decline payments involving sanctioned or high-risk addresses.”
   • [claimed-docs] “Accept ERC-20 tokens on supported EVM networks and SPL tokens on Solana.”
   • [claimed-docs] “Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is the source of US…”
   • [claimed-docs] “"x402 is an open standard for adding per-request payments to HTTP, so APIs and services can charge without checkout pages, subscriptions, or…”
   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the hosted CDP facilitator auth-gates as documented — a keyless GET to https://api.cdp.coinbase.com/pla…”
   • [community] “The protocol is pretty simple. Make a request and get back payment headers. Sign the data, with the proper amounts. The signed transaction i…”
   • [community] “We run 124 x402 endpoints at httpay.xyz and the 'verify work was done' problem is real — especially for compute-heavy tasks like image gener…”

   proof ↗⚑ flag

Wallets

1. ai-native userProvision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed8/10

   Link CLI documents a customer-controlled wallet from which the agent retrieves one-time-use payment credentials, with balance/transaction visibility ('reads transaction history, balances, and account details') and human approval on every spend via the Link app/website, and is confirmed live on npm by runtime probe. missing for 10: independent/hands-on user reports of actually funding and using the wallet end-to-end (only vendor docs and a package-registry probe, no third-party usage account).

   • [claimed-docs] “Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to comple…”
   • [claimed-docs] “Your agent reads transaction history, balances, and account details from connected bank accounts and credit cards.”
   • [claimed-docs] “"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to compl…”
   • [github] “The CLI can produce one of three credential types: A virtual card (PAN)... A Link Pay Token (LPT)... A Shared Payment Token (SPT)”
   • [github] “A virtual card (PAN) for use with a standard web checkout form. The issued card works anywhere, and is not restricted to Link-enabled seller…”
   • [claimed-docs] “Customers approve each request on the Link website or in the mobile app.”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and p…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed5/10

   Coinbase's Agentic Accounts docs explicitly describe giving an agent a CDP wallet that holds USDC and pays for x402 services, and note the account is user/organization-controlled via a Coinbase account or wallet — directly matching the 'agent holds/spends' and 'user-controlled' parts of the story. However, there is no documentation describing an explicit funding flow or a balance-visibility dashboard/API for monitoring the agent's wallet spend, which is a core part of the story. missing for 10: explicit funding mechanism for the agent wallet, balance/spend visibility UI or API for the controlling user.

   • [claimed-docs] “Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is the source of US…”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”

   proof ↗⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe Agentic Commerce—none0/10

   The evidence pack covers token/authorization revocation (SPT revocation, OCA termination) and human-approval gates for payment actions, but nothing about user-controlled data retention policies, data export, or deletion of stored personal/transaction data. Privacy-posture around retention/deletion is a fair question for a payments platform handling PII and financial data, but no documentation addresses it.

   ⚑ flag

   Coinbase x402—none0/10

   The evidence pack covers payment mechanics, facilitator screening, discovery, and governance, but nothing addresses user-controlled data retention or deletion policies for transaction/KYT data collected by the CDP Facilitator. Given onchain settlement is inherently immutable and off-chain screening data governance is unaddressed, there is no evidence of any retention/deletion controls for AI-native users.

   ⚑ flag

Ecosystem adoption

1. developerAt least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration

   weight 2 · round to Coinbase x402
   Stripe Agentic Commerce~partialprobed6/10

   Stripe documents ACP as "open source and community-designed under the Apache 2.0 license" co-developed with OpenAI (who implemented it in ChatGPT as "the first AI platform"), and MPP as an open protocol "co-authored by Stripe and Tempo," with x402/network-token integrations naming Mastercard's Agent Pay and Visa's Intelligent Commerce as third-party implementers. Independent runtime probes confirm mpp.dev is a separate, non-Stripe-branded spec site with governance and SDK on public npm, supporting genuine multi-party involvement rather than a private integration. Missing for 10: independent (non-Stripe-authored) case studies or hands-on reports of a third seller/agent platform beyond OpenAI/Tempo actually running the protocol in production, and clearer separation of protocol governance from Stripe's own docs.

   • [claimed-docs] “"ACP is open source and community-designed under the Apache 2.0 license. Businesses can implement the specification to transact with any AI …”
   • [claimed-docs] “MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and T…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the …”
   • [claimed-docs] “The ACP-style custom integration has sellers "implement a reverse API that defines the requests Stripe sends to your commerce backend and th…”

   proof ↗⚑ flag

   Coinbase x402✓fullcommunity8/10

   x402 was contributed to the vendor-neutral Linux Foundation x402 Foundation, with 40+ member organizations (AWS, American Express, Cloudflare, Google, Mastercard, Shopify, Stripe, Visa, Solana Foundation, etc.) and a named Governing Board/Technical Steering Committee independent of Coinbase, plus independent implementations like httpay.xyz and Apiosk running their own x402 endpoints/gateways. This is clear evidence of multiple independent parties beyond Coinbase implementing and governing the protocol, though community commentary notes Coinbase/US firms still dominate influence. Missing for 10: deeper technical detail on independent (non-Coinbase) facilitator implementations or interoperability testing between competing implementations, and stronger independent audit of the foundation's actual decentralization in practice.

   • [claimed-docs] “Governance: "x402 was originally incubated at Coinbase." — then the "x402 Foundation launched under the Linux Foundation" and "Coinbase comp…”
   • [claimed-docs] “Named governance seats on x402.org: "The x402 Governing Board is responsible for marketing, business oversight, and budget decisions for the…”
   • [community] “The Linux Foundation... today announced it is launching the x402 Foundation with the contribution of the x402 protocol from Coinbase... It s…”
   • [community] “We run 124 x402 endpoints at httpay.xyz and the 'verify work was done' problem is real — especially for compute-heavy tasks like image gener…”
   • [community] “Apiosk approaches it from the server side: a gateway that enforces per-request x402 payments so API providers can monetize without accounts …”
   • [community] “It's worth noting that this protocol is primarily supported by Coinbase today -- You'd be using USDC on the Base network (Layer 2 on top of …”

   proof ↗⚑ flag

Spec publication

1. developerThe commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything

   weight 3 · round drawn
   Stripe Agentic Commerce✓fullprobed8/10

   Stripe explicitly documents that the Agentic Commerce Protocol (ACP) it speaks is "open source and community-designed under the Apache 2.0 license" and that "businesses can implement the specification to transact with any AI agent or payment processor" with no signup required to read or implement it — only optional ChatGPT marketplace participation needs an application, which is a separate distribution channel, not the spec itself. This is corroborated by similar open-protocol framing for MPP ("an open protocol... co-authored by Stripe and Tempo", live spec at mpp.dev) and x402, and a runtime probe confirms the MPP spec is publicly fetchable without auth. Missing for 10: explicit version-numbering/changelog evidence for the spec, and independent (non-Stripe) confirmation that implementers never need a signed agreement to build against the published spec.

   • [claimed-docs] “"ACP is open source and community-designed under the Apache 2.0 license. Businesses can implement the specification to transact with any AI …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Machine Payments Protocol is published in the open — https://mpp.dev/ answers a plain GET with the …”
   • [claimed-docs] “MPP "is an open protocol that lets agents pay for your APIs and services programmatically without a checkout UI, co-authored by Stripe and T…”
   • [claimed-docs] “x402 is a protocol for internet payments... your server returns an HTTP 402 response with payment details, including a Stripe deposit addres…”

   proof ↗⚑ flag

   Coinbase x402✓fullprobed8/10

   x402 is documented as an open, versioned protocol now governed by the vendor-neutral x402 Foundation under the Linux Foundation, with a public spec site (x402.org), published governance/TSC structure, and no signup, API key, or account required to read the spec or implement the handshake (docs, discovery APIs, and npm SDK are all keyless per probes). Community evidence corroborates that it's self-hostable on any chain/token and not gated behind Coinbase agreements, though some skepticism exists about de facto Coinbase influence. Missing for 10: an explicit versioned spec document/changelog (e.g., semver spec repo) directly cited, and stronger independent confirmation that implementers never need to sign any agreement with Coinbase or the Foundation.

   • [claimed-docs] “Governance: "x402 was originally incubated at Coinbase." — then the "x402 Foundation launched under the Linux Foundation" and "Coinbase comp…”
   • [claimed-docs] “Named governance seats on x402.org: "The x402 Governing Board is responsible for marketing, business oversight, and budget decisions for the…”
   • [community] “The Linux Foundation... today announced it is launching the x402 Foundation with the contribution of the x402 protocol from Coinbase... It s…”
   • [community] “It's worth noting that this protocol is primarily supported by Coinbase today -- You'd be using USDC on the Base network (Layer 2 on top of …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the x402 Bazaar discovery index is keyless by design and live — a plain GET to https://api.cdp.coinbase…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the hosted CDP facilitator auth-gates as documented — a keyless GET to https://api.cdp.coinbase.com/pla…”
   • [claimed-docs] “Bazaar discovery is public. You do not need a CDP API key to use the discovery APIs or the corresponding TypeScript SDK functions.”

   proof ↗⚑ flag

Disputes

1. developerDisputes and chargebacks on agent transactions can be handled via API — evidence submission, status, outcomes

   weight 2 · round drawn
   Stripe Agentic Commerce—none0/10

   The evidence pack documents refunds via the standard Refunds API/Dashboard for machine payments, and general agent-approval workflows for actions like refunds, but contains no mention of a disputes/chargebacks API, evidence submission, dispute status tracking, or outcome reporting for agent-initiated transactions specifically.

   ⚑ flag

   Coinbase x402—none0/10

   No evidence describes a dispute/chargeback API, evidence-submission workflow, or outcome/status tracking; x402 payments settle irreversibly onchain via the Facilitator, and community comments even flag 'verify work was done' as an unresolved trust problem with no built-in resolution mechanism. Missing for 10: any dispute-filing API, evidence submission, adjudication process, or chargeback/refund status endpoint.

   • [community] “We run 124 x402 endpoints at httpay.xyz and the 'verify work was done' problem is real — especially for compute-heavy tasks like image gener…”
   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”
   • [claimed-docs] “The batch-settlement scheme targets high-frequency agent loops: "Batch settlement lets agents perform thousands of granular interactions whi…”

   proof ↗⚑ flag

Refunds

1. developerRefunds on agent-placed orders can be initiated and tracked programmatically

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialclaimed5/10

   Evidence shows refunds are available through Stripe's standard Refunds API/Dashboard (inherited by agent-driven orders) and that the Stripe MCP server explicitly supports refunds as a stripe_api_write action, gated by human approval before an agent can execute or retry it. However, there's no agent-specific refund tracking mechanism (e.g., dedicated refund status webhooks tied to agent_details, or refund reporting in the agent-tagged Transactions view) beyond the standard Stripe rails. Missing for 10: dedicated refund tracking/webhooks scoped to agent orders, explicit API examples for programmatic refund initiation on SPT-based orders, and independent/hands-on confirmation of the refund flow working end-to-end.

   • [claimed-docs] “"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid…”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”
   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”

   proof ↗⚑ flag

   Coinbase x402~partialclaimed3/10

   The only refund-relevant evidence is a single line about the batch-settlement scheme stating that 'buyers retain defined refund and withdrawal semantics,' but this is not elaborated into an actual API, dashboard, or programmatic tracking mechanism, and no other docs address refunds/disputes for standard (non-batch) x402 payments. missing for 10: a documented refund API or endpoint, dispute-resolution workflow, refund status tracking, and coverage for non-batch payment flows.

   • [claimed-docs] “The batch-settlement scheme targets high-frequency agent loops: "Batch settlement lets agents perform thousands of granular interactions whi…”

   proof ↗⚑ flag

Agent identity

1. merchantAgents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialclaimed6/10

   Stripe's ACS onboarding shows a real per-agent registration/approval flow ('review its terms' and 'send the agent an approval request that the agent must accept') and an OCA connection that both parties must confirm before commerce flows, plus order-level attribution ('tagged with the originating agent', filterable by agent name) and scoped, revocable SPT grants — all of which let a merchant distinguish known, approved agents from anonymous traffic. However there is no documented cryptographic signature scheme, public agent identity registry, or explicit trust-tier/reputation system merchants can query independently of the approval workflow. Missing for 10: cryptographic agent signatures/verifiable credentials, a public or queryable trust-tier/reputation system, and independent (non-vendor) evidence that merchants can reliably detect spoofed or unregistered agent traffic.

   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”
   • [claimed-docs] “For agent builders, the embedded mode manages "the full checkout lifecycle through Stripe, including product feed ingestion, cart management…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “RAKs are the recommended type of key for API keys you give to AI agents.”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   x402 verifies and screens the *payment* (signed payment proof, OFAC/KYT checks on wallet addresses) but has no mechanism for merchants to identify or tier *agents* themselves — no registered agent profiles, agent-level signatures/identity credentials, or trust tiers are described; the protocol is explicitly designed for signup-free, pseudonymous access ('No signups or approvals required'), the opposite of verifiable agent identity.

   • [claimed-docs] “AI agent pays instantly with stablecoins No signups or approvals required”
   • [claimed-docs] “The hosted CDP Facilitator "validates signed payments, screens transactions, submits settlement onchain, and reports the result to your reso…”
   • [claimed-docs] “Built-in screening. OFAC and Know Your Transaction (KYT) checks identify and decline payments involving sanctioned or high-risk addresses.”

   proof ↗⚑ flag

Human oversight

1. ai-native userSensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves

   weight 3 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce✓fullprobed8/10

   Stripe documents multiple concrete consent gates before money moves: MCP requires explicit human 'Approve' confirmation with an approval token before write actions like refunds/outbound payments (expiring in 24h), Link CLI requires the customer to 'approve each request on the Link website or in the mobile app' before releasing one-time-use credentials, and Shared Payment Tokens carry issuer-set usage_limits (currency, max_amount, expiration) plus revocation and a documented state machine with webhooks. Runtime probes corroborate the MCP OAuth-gated approval flow and the live Link CLI package. missing for 10: independent/hands-on evidence of the approval UX actually blocking a real transaction end-to-end (only docs/runtime probes, no third-party test), and no evidence of a 'signed mandate' artifact akin to AP2's cryptographic mandates.

   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”
   • [claimed-docs] “"Link CLI gives your agent access to a wallet that your customer controls. Your agent can retrieve one-time-use payment credentials to compl…”
   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Stripe's hosted MCP server is live and gated exactly as documented — a keyless JSON-RPC initialize POST…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Link CLI — the agent-wallet client documented for retrieving one-time-use payment credentials and p…”
   • [claimed-docs] “Customers approve each request on the Link website or in the mobile app.”

   proof ↗⚑ flag

   Coinbase x402—none0/10

   x402's own documentation frames the protocol as removing friction rather than adding human oversight — 'AI agent pays instantly with stablecoins, No signups or approvals required' (docs-17) — and the signing step in the handshake is the agent's wallet cryptographically authorizing payment (supp-1, comm-7), not a documented user-facing confirmation, mandate, or per-purchase consent screen. Compliance checks (OFAC/KYT) screen counterparties for sanctions risk, not spending authorization by the user, so there is no evidence of the confirmation/consent mechanism the story requires.

   • [claimed-docs] “AI agent pays instantly with stablecoins No signups or approvals required”
   • [claimed-docs] “"x402 is an open standard for adding per-request payments to HTTP, so APIs and services can charge without checkout pages, subscriptions, or…”
   • [community] “The protocol is pretty simple. Make a request and get back payment headers. Sign the data, with the proper amounts. The signed transaction i…”
   • [claimed-docs] “Built-in screening. OFAC and Know Your Transaction (KYT) checks identify and decline payments involving sanctioned or high-risk addresses.”

   proof ↗⚑ flag

Liability

1. merchantThe fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk

   weight 2 · round drawn
   Stripe Agentic Commerce—none0/10

   The evidence pack covers SPT scoping/revocation, checkout session lifecycle, human-approval gates for refunds, and network Agent Pay/Intelligent Commerce token programs, but nowhere states explicit fraud-liability or chargeback-allocation rules (e.g., who bears loss on a disputed agent-initiated charge, liability-shift terms, or chargeback responsibility between merchant/agent/Stripe). This is a fair question for a payments platform (trust-safety axis clearly applies), but no documentation in the pack addresses it.

   ⚑ flag

   Coinbase x402—none0/10

   Evidence covers OFAC/KYT screening for sanctioned addresses and onchain settlement finality, but nowhere documents fraud liability allocation, chargeback rules, or who bears risk for disputed/unauthorized agent-initiated transactions. Community comments even flag unresolved 'verify work was done' and settlement trust problems, but no merchant-facing liability/dispute-resolution policy is cited.

   • [claimed-docs] “Built-in screening. OFAC and Know Your Transaction (KYT) checks identify and decline payments involving sanctioned or high-risk addresses.”
   • [community] “We run 124 x402 endpoints at httpay.xyz and the 'verify work was done' problem is real — especially for compute-heavy tasks like image gener…”

   proof ↗⚑ flag

Spend controls

1. ai-native userSet per-agent spend caps and usage limits and revoke an agent's payment authority instantly

   weight 2 · round to Stripe Agentic Commerce
   Stripe Agentic Commerce~partialclaimed7/10

   Shared Payment Tokens explicitly support per-token usage_limits (currency, max_amount, expiration) and can be revoked at any time so sellers can't use them ('Sellers can't create a payment with a revoked SPT'), and Restricted API Keys (RAKs) let a developer scope what an agent's key can do, while MCP write actions require human approval tokens that expire in 24h. However, these are per-token/per-key controls rather than a single unified 'per-agent' spend-cap dashboard, and there's no evidence of one-click instant revocation of an agent's entire payment authority across all rails (card, machine payments, x402, Link wallet) at once. missing for 10: a unified per-agent spend-cap/limit management UI or API (vs. per-SPT/per-key limits), evidence of instantly revoking ALL of an agent's payment methods/authority in one action, and independent/hands-on confirmation that revocation works as documented in production.

   • [claimed-docs] “"Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases." The issuing agent mu…”
   • [claimed-docs] “RAKs are the recommended type of key for API keys you give to AI agents.”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”
   • [claimed-docs] “Shared payment tokens (SPTs) grant sellers scoped access to customers’ payment methods for agent-initiated purchases.”

   proof ↗⚑ flag

   Coinbase x402~partialcommunity3/10

   x402 documents per-transaction spend limits via the 'upto' authorize-and-settle scheme and batch-settlement's cryptographically signed voucher limits/escrow, and agentic accounts let an agent hold a funding source — but there is no documented mechanism to set a persistent per-agent spend cap/usage quota across sessions or to instantly revoke an agent's payment authority; a community commenter even suggests pairing x402 with a third-party 'budget SDK' for spending ceilings, implying it's not native. missing for 10: native per-agent spend-cap configuration, usage-limit dashboards, and an instant revocation/kill-switch mechanism for agent payment authority.

   • [claimed-docs] “Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is the source of US…”
   • [claimed-docs] “Agent wallets: "Agentic accounts let an AI agent hold funds and act through a Coinbase account or wallet. For an x402 buyer, the account is …”
   • [claimed-docs] “The batch-settlement scheme targets high-frequency agent loops: "Batch settlement lets agents perform thousands of granular interactions whi…”
   • [community] “Apiosk approaches it from the server side: a gateway that enforces per-request x402 payments so API providers can monetize without accounts …”

   proof ↗⚑ flag