Stripe Agentic Commerce vs Crossmint

Cart

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

   weight 3 · round to Crossmint
   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

   Crossmint✓fullprobed8/10

   Crossmint's Agent Checkouts API is a documented protocol call that lets an agent submit a product URL and spending cap to create an order/checkout, and runtime probing confirms the endpoint is live and agent-scoped (requiring ServerKeyAgent auth). The lifecycle supports polling for status updates, which functions as order-draft state updates, and agent cards similarly document order-intent creation/tracking (total, reserved, spent, available). missing for 10: no explicit 'update cart' verb or partial-order-edit API, no OpenAPI/schema confirmation (openapi.json probes 404), and no independent third-party corroboration beyond first-party docs and the vendor's own runtime probe.

   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”

   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 drawn
   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

   Crossmint✓fullprobed8/10

   Crossmint's Agent Checkouts API lets an agent be handed a product URL and spending cap and complete checkout on the user's behalf, with delegated payment credentials (agent cards/order intents or delegated wallet signer permissions) and a poll-driven order lifecycle to confirm terminal state; runtime probe confirms the endpoint is live and enforces agent-scoped auth. missing for 10: independent/third-party confirmation of a fully completed order in production (docs note no staging/test environment and no webhooks in v1, so end-to-end success is self-reported), and no public case study of a real merchant purchase completing.

   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”

   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

   Crossmint~partialclaimed3/10

   Crossmint documents generic agent-payment infrastructure (Agent Cards, Agent Wallets, Agent Checkouts) that lets any AI agent buy from merchants via API, which could theoretically be wired into chat surfaces, but there is no evidence of concrete integration or partnership with ChatGPT, Claude, Gemini, Copilot or similar assistant surfaces. Missing for 10: named integrations/plugins with specific chat/assistant platforms, evidence of buyers actually completing purchases inside those surfaces, and any merchant-facing onboarding flow tied to those platforms.

   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   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

   Crossmint—none0/10

   Crossmint documents payment flows (x402, MPP, agent checkouts) but there is no evidence of a versioned commerce protocol with a published schema or conformance/validation tooling — probes for OpenAPI/swagger specs all 404'd, and the live agent-checkouts endpoint is explicitly path-versioned as '/api/unstable/', signaling the opposite of a stable published protocol.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   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 Stripe Agentic Commerce
   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

   Crossmint—none0/10

   Crossmint's agent products (Agent Cards, Agent Wallets, Agent Checkouts) are all payment/execution infrastructure that require the agent to already have a specific product URL or merchant endpoint — 'hand it a product URL and a spending cap' — none of the evidence describes a search or product-discovery API across merchants. There is no documented catalog search, product query, or merchant-discovery endpoint; discovery is assumed to happen elsewhere before Crossmint is invoked.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”

   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 Stripe Agentic Commerce
   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

   Crossmint—none0/10

   Crossmint's docs describe agent checkout as handing it a merchant product URL and letting Crossmint execute the purchase, but nowhere is there evidence that Crossmint itself exposes machine-readable offer data (price, availability, variants, checkout links) for developers to read — it's a payment/checkout executor, not a product-data or listing API. Missing for 10: any API/schema returning structured product price/availability/variant data, any catalog or listing endpoint, any documentation of reading offer metadata rather than just completing a purchase given a URL.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”

   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 Stripe Agentic Commerce
   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

   Crossmint—none0/10

   The evidence covers Crossmint's payment rails (cards, wallets, x402, MPP, checkouts) but nothing describes a published directory or discovery index of payable services/APIs that an agent could browse or query; llms.txt is a docs-crawling aid, not a service discovery index. This is a fair axis for an agent-payments platform, but no capability is evidenced.

   ⚑ flag

Agent access

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

   weight 2 · round drawn
   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

   Crossmint✓fullprobed9/10

   Crossmint serves a live llms.txt (confirmed by direct probe returning HTTP 200 with agent-oriented content) and every docs page is also available as markdown via the same URL + .md suffix, directly matching the story of pointing an agent at llms.txt or agent-oriented docs. Missing for 10: no independent third-party report of an agent successfully consuming these docs end-to-end, and no OpenAPI spec (all candidates 404) to complement the llms.txt for structured agent consumption.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.crossmint.com/llms.txt # Crossmint > Crossmint is a blockchain infrastructure platform for develop…”
   • [probe] “PROBE runtime (recorded 2026-09-14): docs.crossmint.com serves llms.txt keylessly — '# Crossmint... checkout for onchain and physical-world …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   proof ↗⚑ flag

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

   weight 2 · round to Crossmint
   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

   Crossmint~partialprobed6/10

   Crossmint's core products are REST/headless APIs (explicit 'headless checkout API', agent checkouts API, wallet API) designed for programmatic, UI-less automation, and probes confirm keyless API-key-based auth suitable for scripted/CI calls. However there is no explicit documentation of CI pipeline usage, SDK examples for automated test suites, or non-interactive auth setup, and agent-checkouts testing is noted as production-only with no staging environment, complicating CI use. Missing for 10: documented CI/automation examples, staging/sandbox support for safe automated testing, and explicit non-interactive credential provisioning guidance.

   • [claimed-docs] “Crossmint's headless checkout API is a set of REST APIs that allow you to integrate credit card and cross-chain crypto payments inside your …”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “Crossmint offers secure, programmable smart wallet infrastructure through a single API that is configurable for any use case”

   proof ↗⚑ flag

3. 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

   Crossmint✓fullprobed8/10

   Crossmint exposes a documented REST API surface (wallets, agent cards, agent checkouts, payment flows) with quickstarts and runtime probes confirming the endpoints are live and API-key/agent-key authenticated, and llms.txt/markdown docs are served for machine consumption. The main gap is the absence of a discoverable formal OpenAPI/Swagger spec (probe-2 shows all standard OpenAPI paths 404), so full machine-readable API introspection isn't confirmed. Missing for 10: a published OpenAPI/Swagger schema, independent third-party confirmation of API robustness beyond Crossmint's own docs.

   • [claimed-docs] “Crossmint offers secure, programmable smart wallet infrastructure through a single API that is configurable for any use case”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.crossmint.com/llms.txt # Crossmint > Crossmint is a blockchain infrastructure platform for develop…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [probe] “PROBE runtime (recorded 2026-09-14): docs.crossmint.com serves llms.txt keylessly — '# Crossmint... checkout for onchain and physical-world …”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”

   proof ↗⚑ flag

4. 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

   Crossmint✓fullprobed7/10

   Crossmint documents explicit least-privilege delegation for agents: user-owned wallets grant an agent a bound signer key with a spend cap, allowed counterparties, and a time window, all enforced onchain and revocable at any time; agent cards similarly use order-intent 'fixed allowance' credentials with amount/expiration limits and network-level enforcement. A runtime probe further shows an agent-specific credential type (ServerKeyAgent) is live on the Agent Checkouts API, confirming agent-scoped API keys exist in practice, not just in docs. Missing for 10: independent/third-party corroboration of these scoping guarantees, and clearer documentation of general-purpose (non-payment) API key scoping/role management beyond the wallet/card/checkout domain.

   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”

   proof ↗⚑ flag

5. 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

   Crossmint~partialprobed5/10

   Crossmint's docs show a single REST API accessed via quickstarts (agent checkouts, cards, stablecoin wallets) and protocol-specific clients like @x402/core and mppx, implying SDK-style tooling, but no evidence names an official multi-language SDK package (e.g., npm/pip installable Crossmint SDK) and the OpenAPI probe found no published spec, undercutting a clean 'official SDK' story. missing for 10: explicit official SDK package names/install instructions, multi-language SDK coverage, and a discoverable OpenAPI/schema reference.

   • [claimed-docs] “Create a user-owned smart wallet, authorize an agent as a delegated signer, and send USDXM on Base Sepolia.”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”
   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   proof ↗⚑ flag

6. ai-native userSubscribe to events via webhooks

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

   Multiple agentic-commerce flows emit dedicated webhooks that a developer/agent-builder can subscribe to: order completion (`checkout.session.completed` tagged with agent), catalog import status (`v2.commerce.product_catalog.imports.*`), OCA embedded checkout completion (`delegated_checkout.requested_session.completed`), and SPT state transitions (`shared_payment.issued_token.used`, etc.), all part of Stripe's standard event/webhook infrastructure applied to agentic commerce. Missing for 10: explicit doc snippet on creating/registering a webhook endpoint for these events and independent hands-on confirmation of subscription setup.

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

   proof ↗⚑ flag

   Crossmint—none0/10

   The only explicit evidence about webhooks states the opposite of the story: Agent Checkouts documentation says 'no webhooks in v1' and requires polling until a terminal state is reached, with no other evidence pack item describing a webhook subscription mechanism anywhere in Crossmint's API.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   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

   Crossmint~partialclaimed5/10

   Crossmint lets agents transact autonomously once delegated: onchain-enforced spend limits, counterparties, and time windows mean the agent acts 'with no user prompt per action' and checkouts/x402/MPP payments proceed without human intervention ([crossmint-supp-4], [crossmint-supp-6], [crossmint-supp-7]). However this is scoped strictly to payment/checkout automation, not a general-purpose background job/workflow scheduler, and agent checkouts require manual polling with no webhooks or staging ('no webhooks in v1', 'no staging environment') ([crossmint-supp-7]). Missing for 10: general-purpose automation/scheduling framework beyond payments, webhook/event-driven triggers, and evidence of autonomous background operation outside the payment domain.

   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”

   proof ↗⚑ flag

2. ai-native userOperate the product with natural-language commands

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

   Stripe's agentic-commerce stack is built around natural-language-driven flows: buyers can browse, get recommendations, and 'complete purchases without leaving the conversation,' Link CLI supports natural queries like 'Buy me this book from Stripe Press' and 'What did I spend on dining this month?', and the MCP server/skills let AI agents interact with the API conversationally. However, this is fundamentally an API/protocol/SDK product for developers and agent-builders, not an end-user interface itself — the 'natural language' surface is provided by the calling LLM/agent (ChatGPT, etc.), and most interactions (SPT issuance, key management, catalog feeds, checkout hooks) are structured API/CLI calls rather than NL commands to Stripe itself. Missing for 10: evidence of Stripe's own product surface directly accepting free-form natural-language commands (as opposed to relying on a third-party agent/LLM to translate NL into API calls), and independent hands-on confirmation that the documented NL examples work end-to-end in production rather than as illustrative docs snippets.

   • [claimed-docs] “Buyers can browse products, get personalized recommendations, and complete purchases without leaving the conversation.”
   • [claimed-docs] ““Buy me this book from Stripe Press””
   • [claimed-docs] ““What did I spend on dining this month?””
   • [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] “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.”
   • [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

   Crossmint—none0/10

   Crossmint's evidence describes REST APIs, SDKs, and agent-delegated payment flows (cards, wallets, checkouts, x402/MPP), but nothing shows a natural-language command interface for the human/AI-native user to directly operate Crossmint itself — no chat UI, NL-to-API translation layer, or documented conversational control surface. The axis is fair to ask of a product marketed as 'payment infrastructure for AI agents,' but no such capability is evidenced.

   • [claimed-docs] “Crossmint offers secure, programmable smart wallet infrastructure through a single API that is configurable for any use case”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   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

   Crossmint—none0/10

   The evidence shows only markdown-based docs and an llms.txt feed; explicit probes for an OpenAPI/Swagger spec (openapi.json, swagger.json, etc.) all returned 404, and no evidence mentions an interactive API console, sandbox, or runnable code examples.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.crossmint.com/llms.txt # Crossmint > Crossmint is a blockchain infrastructure platform for develop…”
   • [probe] “PROBE runtime (recorded 2026-09-14): docs.crossmint.com serves llms.txt keylessly — '# Crossmint... checkout for onchain and physical-world …”

   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

   Crossmint—none0/10

   A direct probe found no OpenAPI/Swagger spec at any standard path (all 404s), and while an llms.txt/markdown docs format exists, that is not a machine-readable API spec. missing for 10: an OpenAPI/Swagger JSON or YAML spec, any documented spec download link, or equivalent machine-readable API schema.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.crossmint.com/llms.txt # Crossmint > Crossmint is a blockchain infrastructure platform for develop…”

   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

   Crossmint~partialclaimed4/10

   Crossmint documents genuine testnet sandboxes for some flows (e.g., the stablecoin wallet quickstart runs on Base Sepolia, crossmint-docs-3), but for Agent Checkouts the docs explicitly state 'there is no staging environment for it' and testing is production-only (crossmint-supp-7). So sandboxed testing exists for part of the agent stack but is explicitly absent for another major agent capability. missing for 10: a unified sandbox/staging environment across all agent products (cards, checkouts, wallets), independent confirmation of testnet behavior beyond docs, and any sandbox coverage for Agent Cards/Checkouts specifically.

   • [claimed-docs] “Create a user-owned smart wallet, authorize an agent as a delegated signer, and send USDXM on Base Sepolia.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   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

   Crossmint—none0/10

   No evidence pack item documents API versioning conventions or a deprecation policy; the only version-related signal is an endpoint path containing 'unstable' (crossmint-probe-rt-1), which if anything suggests unversioned/experimental APIs rather than a documented deprecation policy.

   ⚑ flag

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

   weight 2 · round to Stripe Agentic Commerce
   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

   Crossmint—none0/10

   The evidence pack covers single-item agent payment flows (cards, wallets, checkouts, x402/MPP) and mentions managing funds 'at scale' in passing, but there is no documented batch/bulk API, bulk wallet creation, or multi-item transaction endpoint that would let a user perform operations across many items at once.

   • [claimed-docs] “Secure, programmable wallets to manage and move company funds at scale.”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

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

   weight 3 · round to Crossmint
   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

   Crossmint~partialclaimed4/10

   Crossmint lets users define scoped rules (spend caps, counterparty allow-lists, time windows) that once set let an agent act autonomously without per-action prompts, and states 'Transaction rules enforced onchain' — a form of automatic rule-based action. However this is closer to pre-authorized permission bounds than true event-triggered automation, and the docs explicitly note agent checkouts have 'no webhooks in v1', meaning event-driven triggering isn't supported there. Missing for 10: an explicit rules/automation engine that fires actions on arbitrary external or on-chain events, webhook/event-subscription support, and independent confirmation of automated rule execution beyond spend-limit enforcement.

   • [claimed-docs] “Transaction rules enforced onchain”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   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 Stripe Agentic Commerce
   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

   Crossmint—none0/10

   Crossmint publishes general wallet MAU overage pricing and checkout fee tiers, but the evidence pack explicitly states 'No agent-card- or agent-checkout-specific price is published on the pricing page' (crossmint-supp-9), meaning a merchant cannot price the agent-specific channels (Agent Cards, Agent Checkouts) without contacting sales.

   • [claimed-docs] “Published pricing: wallets are "Free 1,000 Monthly Active Wallets" then "Overages start at $0.05 per MAU. Volume discounts available."; onra…”

   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

   Crossmint~partialclaimed3/10

   Evidence shows transaction-lifecycle tracking (order intents track total/reserved/spent/available amounts) and a documented authorization-hold/capture and dispute-management model for card checkout, which are reconciliation-adjacent, plus tiered per-transaction pricing. But there is no documented merchant payout schedule, settlement-to-bank-account flow, transaction reporting dashboard, or export/reconciliation tooling specific to agent-originated payments, and the agent-checkouts flow explicitly lacks webhooks ('no webhooks in v1' — poll until terminal state), undermining real-time reconciliation. Missing for 10: merchant payout/settlement documentation, reporting/dashboard or export tools, reconciliation-specific guidance for agent transactions, and webhook-based confirmation.

   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”
   • [claimed-docs] “Published pricing: wallets are "Free 1,000 Monthly Active Wallets" then "Overages start at $0.05 per MAU. Volume discounts available."; onra…”

   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

   Crossmint—none0/10

   The evidence describes agent payment mechanisms (cards, wallets, checkouts, spending rules) but contains no mention of merchant-facing reporting, dashboards, or transaction filtering by originating agent — the core of this story. Order intents and delegated signers are documented for controlling agent spend, not for merchant attribution/reporting.

   ⚑ 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 Stripe Agentic Commerce
   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

   Crossmint—none0/10

   Evidence covers agent-side integrations (agent wallets, agent cards, x402/MPP payment flows, agent checkouts) but nothing documents a merchant-facing onboarding step — no setting to enable, agreement to sign, or endpoint-publishing guide aimed at merchants who want to accept agent traffic. The 'buy from any merchant' framing implies merchants need no explicit action, but this is never documented as a self-serve merchant enablement path.

   ⚑ 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

   Crossmint—none0/10

   The evidence details user-side and agent-side spending controls (spend caps, counterparties, time windows, order intents) but nothing about merchants controlling which agents/agent platforms may access their catalog or checkout, nor any rate-limiting/allow-deny mechanism exposed to merchants. Crossmint's agent-checkout flow treats the merchant as an arbitrary third-party target ('buy from any merchant'), not as a Crossmint customer configuring agent access policies.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

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

   Stripe's docs show an extensive API surface for agentic commerce (Product Catalog Import API, Checkout Sessions, Shared Payment Tokens, MCP server exposing Stripe API tools, restricted API keys, CLI/sandbox tooling) letting agents perform most seller/agent/consumer actions programmatically, with the MCP server explicitly wrapping the API. However evidence also documents real UI/human dependencies: seller onboarding is described as 'Dashboard self-serve', and Stripe's own MCP server 'requires human confirmation' via a Dashboard approval URL before certain writes (refunds, outbound payments), meaning not all actions can be completed purely via API without a human UI step. Missing for 10: evidence that seller onboarding and gated write actions (refunds, payouts) can be fully completed via API without a Dashboard/human approval step, and independent confirmation of full UI/API feature parity.

   • [claimed-docs] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”
   • [claimed-docs] “Dashboard-side agent actions carry a documented human approval gate: "To prevent agents from making mistakes, Stripe requires human confirma…”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [claimed-docs] “RAKs are the recommended type of key for API keys you give to AI agents.”
   • [claimed-docs] “Agent orders flow through standard Stripe rails with per-agent attribution: "Stripe sends `checkout.session.completed` after the agent compl…”

   proof ↗⚑ flag

   Crossmint~partialprobed6/10

   Crossmint is built API-first — wallets, agent cards, agent checkouts, and headless checkout are all exposed as REST APIs, with headless checkout explicitly positioned as the API-only alternative to Crossmint's embedded iframe UI, giving 'full control of the user experience' (crossmint-docs-1, crossmint-docs-7, crossmint-docs-8, crossmint-supp-1). However, there's no explicit claim or evidence of full UI/API feature parity across the whole platform, and the probe found no discoverable OpenAPI spec (404s on all candidate paths), suggesting some API surface may be undocumented or incomplete relative to the dashboard. Missing for 10: an explicit parity statement or audit showing every dashboard/UI action (account/team management, dispute handling, analytics) has an API equivalent, and a published OpenAPI spec confirming full API surface.

   • [claimed-docs] “Crossmint offers secure, programmable smart wallet infrastructure through a single API that is configurable for any use case”
   • [claimed-docs] “Crossmint's headless checkout API is a set of REST APIs that allow you to integrate credit card and cross-chain crypto payments inside your …”
   • [claimed-docs] “Embedded iframe with customizable UI.”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

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

   The evidence pack covers agentic checkout, payment tokens, MCP tools, machine payments, and wallet CLIs, but contains no mention of a data export feature, open-format data portability, or account/data offboarding process for merchants or AI agents using the platform.

   ⚑ flag

   Crossmint—none0/10

   The evidence pack covers Crossmint's wallet, checkout, and agent-payment APIs in depth, but nothing addresses data export, open-format portability, or account/data takeout for users leaving the platform. Missing for 10: any documented data export feature, open-format (e.g., CSV/JSON) export tooling, or explicit portability/exit guarantees for user data.

   ⚑ flag

Order events

1. developerMy agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically

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

   Stripe documents at least one lifecycle push event for agent orders — checkout.session.completed fires when an agent completes an order, tagged with agent attribution and filterable in the Dashboard — plus a delegated_checkout.requested_session.completed webhook for embedded checkout completion, and separate webhooks exist for catalog-import and SPT-token state changes. However, there is no documented event set covering the full requested lifecycle (created, updated, fulfilled, canceled) for orders themselves; canceled/fulfilled-specific webhooks aren't shown, and bulk fulfillment is presented as a pull (List CheckoutSessions) rather than a push mechanism. Missing for 10: explicit order.created/updated/canceled webhook events, a documented order-events reference, and independent/hands-on confirmation of subscription reliability.

   • [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] “Merchant onboarding is Dashboard self-serve — "Use Agentic Commerce Suite (ACS) to start selling through agents with a single integration", …”

   proof ↗⚑ flag

   Crossmint—none0/10

   Crossmint's own docs explicitly state agent checkouts have 'no webhooks in v1' and require polling until a terminal state is reached, meaning there is no programmatic push-based subscription to order lifecycle events (created/updated/fulfilled/canceled). No other product area (wallets, cards) documents webhook/event subscription either.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

Post purchase status

1. ai-native userMy agent can query the status and tracking of an order it placed, after the purchase

   weight 2 · round to Crossmint
   Stripe Agentic Commerce—none0/10

   Evidence covers checkout completion, order attribution in the Stripe Dashboard, and bulk fulfillment tools for sellers, but nothing shows an agent being able to query order status or shipping/tracking information after a purchase is placed — no order-status API, webhook, or tool is documented for the agent side post-purchase.

   • [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…”

   proof ↗⚑ flag

   Crossmint~partialclaimed6/10

   Docs explicitly describe agent checkouts as poll-driven — 'no webhooks in v1... you poll until it reaches a terminal state' — and order intents/rails each carry their own status, so an agent can query order status after purchase via polling. However, this is documented only for the Agent Checkouts flow (not agent cards or wallet payments), lacks any true package/shipment tracking detail, and has no independent or hands-on corroboration beyond first-party docs. Missing for 10: shipment/delivery tracking detail, webhook or push-based status updates, and third-party verification of the polling flow actually working in production.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “An order intent can have multiple rails, each with its own status, credential formats, and verification.”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”

   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 Crossmint
   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

   Crossmint✓fullprobed9/10

   Crossmint's Agent Cards give agents a one-time card number, expiration, and CVC scoped by an order intent with amount, description, merchant lock, and expiration — never exposing the real card number — enforced via Visa/Mastercard network rails (crossmint-supp-2, crossmint-supp-3, crossmint-supp-8). This is corroborated by a live runtime probe showing the agent-scoped checkout endpoint requiring agent-specific credentials (crossmint-probe-rt-1). Missing for 10: independent third-party (non-vendor) verification of the card-scoping behavior in production beyond the docs and single runtime probe.

   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Credentials are one-time and network-verified: minting returns "the secure one-time card number, expiration, and CVC", and verification is a…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “Give agents permission to pay with a user's card using Crossmint's Agentic Payments API.”

   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

   Crossmint—none0/10

   All Crossmint evidence describes agents/wallets *paying* x402 or MPP-protected endpoints (client/payer side) — e.g. crossmint-supp-6 and crossmint-supp-5 explain how a Crossmint wallet reads a 402 challenge and retries with payment proof. There is no evidence of tooling for a developer to stand up their own API/service that returns HTTP 402 challenges and receives/settles per-call agent payments (the monetization/merchant side of x402). Missing for 10: any docs or API for creating/serving a 402-gated endpoint, receiving settlement, or configuring per-call pricing as a service provider — evidence only covers the consuming side.

   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”
   • [claimed-docs] “This guide shows how to pay x402-protected endpoints using a Crossmint wallet.”
   • [claimed-docs] “This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet.”

   proof ↗⚑ flag

Settlement rails

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

   weight 2 · round to Crossmint
   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

   Crossmint✓fullprobed8/10

   Crossmint documents stablecoin settlement for agent payments via user-owned wallets with delegated signer permissions (USDXM/USDC), and explicit rails including x402 and MPP protocols with runtime-verified endpoint behavior, giving strong first-party and probe corroboration of documented stablecoin rails. missing for 10: independent (non-vendor) real-world case studies of production stablecoin settlement volume, and confirmation the x402/MPP flows work beyond testnet/Base Sepolia examples.

   • [claimed-docs] “Create a user-owned smart wallet, authorize an agent as a delegated signer, and send USDXM on Base Sepolia.”
   • [claimed-docs] “This guide shows how to pay x402-protected endpoints using a Crossmint wallet.”
   • [claimed-docs] “This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet.”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”
   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”

   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

   Crossmint~partialclaimed7/10

   Crossmint's Agent Wallets docs show a user-owned, non-custodial wallet that a user funds and controls, with the agent authorized as a scoped, revocable delegated signer (spend cap, counterparties, time window) enforced onchain, and a working stablecoin-wallet quickstart (crossmint-docs-3, crossmint-supp-4, crossmint-supp-5). However, the evidence never explicitly documents a balance-visibility feature (e.g., a balance/dashboard API for the funding user) — missing for 10: explicit balance-check/visibility API or UI evidence, independent/hands-on corroboration of the wallet flow.

   • [claimed-docs] “Create a user-owned smart wallet, authorize an agent as a delegated signer, and send USDXM on Base Sepolia.”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”
   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”

   proof ↗⚑ 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 Stripe Agentic Commerce
   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

   Crossmint—none0/10

   Evidence describes Crossmint as a single-vendor proprietary API/platform (wallets, checkout, agent cards) — even where it interoperates with external protocols like x402 or MPP, those are third-party specs Crossmint merely consumes, not evidence that independent parties implement Crossmint's own protocol/platform. No evidence pack item shows any other company or independent implementer building a competing or parallel implementation of Crossmint's infrastructure.

   ⚑ 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 to Stripe Agentic Commerce
   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

   Crossmint—none0/10

   Crossmint documents its own REST/agent APIs (cards, wallets, checkouts) but the evidence shows no open, versioned specification of its own commerce protocol — the OpenAPI/swagger probe returned 404 on all candidate paths, and no spec repository or versioning scheme is mentioned. While Crossmint implements external protocols like x402 and MPP, it does not publish its own commerce protocol as an open spec.

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

   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

   Crossmint—none0/10

   The only relevant evidence states that Crossmint itself absorbs dispute risk and manages chargebacks directly with the bank on the user's behalf (crossmint-supp-10), which is for the general Checkout product, not agent-specific. There is no documentation of any developer-facing API for submitting dispute evidence, checking dispute status, or retrieving outcomes. Missing for 10: any dispute-management API endpoints, evidence-submission workflow, or status/outcome reporting for agent transactions.

   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”

   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

   Crossmint—none0/10

   Evidence covers dispute/chargeback risk absorption for general card Checkout (crossmint-supp-10), but this describes Crossmint handling bank disputes, not a developer-facing refund API for initiating/tracking refunds on agent-placed orders. No refund endpoint, refund object, or tracking mechanism is documented anywhere for Agent Cards, Agent Wallets, or Agent Checkouts. Missing for 10: any refund API/endpoint, refund status tracking, and agent-order-specific refund workflow documentation.

   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”

   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

   Crossmint~partialprobed5/10

   Crossmint's agent stack does embed verifiable-identity mechanisms — onchain delegated signer keys with scoped, revocable permissions (crossmint-supp-4), card-network verified 'Agent Cards' secured by Visa VIC/Mastercard Agent Pay (crossmint-supp-1, -3), and a distinct 'ServerKeyAgent' credential type confirmed live at the Agent Checkouts endpoint (crossmint-probe-rt-1). These give merchants some cryptographic/network-level basis to distinguish agent-initiated, permissioned transactions from anonymous traffic. However, there is no documented merchant-facing registry, trust-tier system, or API for merchants to look up/verify an agent's identity or reputation directly — the verification lives inside Crossmint/card-network infrastructure rather than being exposed as a merchant-consumable signal. Missing for 10: an explicit merchant-facing agent identity/reputation lookup or trust-tier classification, and independent confirmation that merchants can actually distinguish trust levels using this data.

   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “Credentials are one-time and network-verified: minting returns "the secure one-time card number, expiration, and CVC", and verification is a…”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”

   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

   Crossmint~partialclaimed6/10

   Crossmint documents strong pre-authorized consent mechanisms — user-signed onchain delegation with spend caps, counterparties, and time windows, plus order-intent 'agent cards' with fixed allowances and expiration — enforced without a per-purchase prompt, and revocable at any time. However, the story asks for documented approval INCLUDING per-purchase consent or signed mandate at time of spend, and Crossmint's model explicitly favors upfront scoped delegation with 'no user prompt per action' rather than a per-transaction confirmation step; this is a deliberate design tradeoff, not a failure, so it's partial rather than disputed. missing for 10: evidence of an optional per-purchase confirmation/step-up flow, independent/hands-on verification of the delegation and revocation actually working in production, and clarity on how disputes/approval work for agent checkouts specifically (dispute coverage is only confirmed for general checkout, not agent checkouts).

   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”

   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 to Crossmint
   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

   Crossmint~partialclaimed4/10

   Crossmint documents dispute handling for its general Checkout product (Crossmint absorbs card dispute risk via authorization holds, per crossmint-supp-10) and describes spend caps/order-intent controls for agent cards and wallets, but explicitly notes this chargeback/liability coverage is not specific to agent-initiated transactions. There is no dedicated documentation defining fraud/liability/chargeback allocation rules for agent checkouts or agent-card/agent-wallet flows. missing for 10: explicit agent-transaction-specific liability/chargeback policy, merchant-facing dispute-resolution terms for agent checkouts, and clarity on who bears risk when an agent-initiated purchase is fraudulent or disputed.

   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   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 Crossmint
   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

   Crossmint✓fullprobed8/10

   Crossmint documents onchain-enforced per-agent spend caps, allowed counterparties, and time windows for agent wallets, plus order-intent allowances with amount/expiration for agent cards, and explicitly states permissions are revocable at any time by the user. This is corroborated by detailed docs on delegation mechanics and a runtime probe confirming agent-scoped auth is live in production. Missing for 10: independent (non-vendor) confirmation that revocation is instantaneous in practice, and no evidence of a unified dashboard/UI for setting caps or revoking across all three agent products (cards, wallets, checkouts) in one place.

   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”

   proof ↗⚑ flag