Coinbase x402 vs Visa Intelligent Commerce

Cart

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

   weight 3 · round to Visa Intelligent Commerce
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed6/10

   Visa's REST APIs document creating a purchase-intent (POST /acp/v1/instructions) with mandate fields (amount, merchant, description) that functions like an order/cart draft, and revocation of that intent is documented as a follow-on call — but there is no explicit 'update/modify draft' endpoint, only initiate and cancel actions on the instruction/mandate object. Missing for 10: a documented update/modify-in-place endpoint for an existing cart/order object, and clearer mapping of Visa's 'instruction' concept to a literal cart/order draft rather than a payment-intent mandate.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “Capture consumer consent, set spending limits, and manage mandates for agent-initiated payments.”

   proof ↗⚑ flag

Checkout

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

   weight 3 · round to Visa Intelligent Commerce
   Coinbase x402~partialprobed7/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullclaimed8/10

   Visa's docs describe the full agent-checkout pipeline with concrete REST endpoints: card enrollment/tokenization (POST /acp/v1/tokens), a purchase-intent mandate with spend caps and expiry (POST /acp/v1/instructions), scoped delegated credential retrieval tied to merchant/amount (POST /acp/v1/instructions/{id}/credentials), passkey-based instruction authentication, and authorization-time enforcement plus payment outcome confirmation — covering checkout session, delegated credential, and confirmed order end-to-end. Missing for 10: independent/hands-on evidence of a completed real-world transaction (all evidence is first-party docs) and the product page's own maturity caveat that it is 'in the process of development and deployment'.

   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “Confirm payment outcomes and trigger post-purchase actions in real-time.”
   • [claimed-docs] “Controls to ensure that the agent’s purchasing actions and the related authorizations align with the user’s authenticated instruction”

   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 Visa Intelligent Commerce
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialprobed5/10

   Visa Intelligent Commerce provides the underlying payment rails for agent-initiated purchases (tokenization, mandate/consent controls, passkey step-up auth, Trusted Agent Protocol, and an MCP server for developers to plug into agentic experiences), which is the necessary plumbing for buyers to check out via AI agents. However, the evidence never names or demonstrates live integration with specific chat/assistant surfaces like ChatGPT, Claude, Gemini, or Copilot — it's generic 'agent' infrastructure plus a community-noted MCP server, with the core product itself flagged as still 'in the process of development and deployment.' Missing for 10: explicit evidence of shipped integrations or launch partnerships with ChatGPT/Claude/Gemini/Copilot, and independent confirmation that merchants can actually complete checkout flows inside those named surfaces today.

   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”
   • [claimed-docs] “the toolkit helps developers and non-technical users to work with AI agents using plain language — no coding required.”
   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [probe] “PROBE runtime (recorded 2026-09-14): Visa's developer gateway is live and credential-gated exactly as documented — a keyless GET to https://…”

   proof ↗⚑ flag

Protocol conformance

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

   weight 2 · round drawn
   Coinbase x402~partialprobed5/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed5/10

   Visa publishes detailed REST API docs (endpoints, required fields, sample payloads) for Intelligent Commerce and a public spec with reference implementation for the Trusted Agent Protocol (RFC 9421 signatures, JWKS verification), plus a sandbox for testing. However, there's no evidence of a single unified 'commerce protocol' with an explicit version number, a published machine-readable schema (e.g. OpenAPI/JSON Schema spec file), or dedicated conformance/validation tooling beyond the sandbox and a reference implementation repo. missing for 10: explicit protocol versioning scheme, downloadable/published schema (OpenAPI or similar), dedicated conformance-test suite or validator tool, independent developer corroboration of building against the spec.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “The Trusted Agent Protocol's agent recognition signature is HTTP Message Signatures "defined by RCF 9421" (typo in original), "aligned with …”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”
   • [claimed-docs] “Merchant-side onboarding starts with a self-serve "Intelligent Commerce Sandbox Sign up" form (Organization ID, company, contact details, te…”
   • [claimed-docs] “including the cryptographic standards (RFC9421), required message signature fields, and the process for validating an agent's intent.”

   proof ↗⚑ flag

Service discovery

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

   weight 2 · round to Coinbase x402
   Coinbase x402✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialprobed5/10

   Visa provides discovery surfaces for its own developer APIs — an official MCP server (visa-intelligent-commerce-docs-8, probe-2), a public npm package (visa-ic-probe-rt-2), and a machine-readable llms.txt index (visa-intelligent-commerce-probe-1) — which let an agent discover and call its payment/commerce endpoints. However this is discovery of Visa's own API surface, not a broader directory/index of third-party payable services or merchants that an agent could browse; the TAP agent-registry is for verifying agent identity, not for service discovery. Missing for 10: a published directory/marketplace of payable third-party services, evidence of cross-vendor service discovery, independent confirmation the MCP/llms.txt are used for live service discovery rather than just docs.

   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.visaacceptance.com/llms.txt # VisaAcceptance Developer Center > This developer documentation …”
   • [probe] “official MCP server documented at https://github.com/visaacceptance/agent-toolkit”
   • [probe] “PROBE runtime (recorded 2026-09-14): Visa's developer gateway is live and credential-gated exactly as documented — a keyless GET to https://…”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Visa Intelligent Commerce
   Coinbase x402✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullprobed9/10

   A probe confirms llms.txt returns HTTP 200 with structured content at developer.visaacceptance.com/llms.txt, and Visa also publishes an official MCP server (agent-toolkit) confirmed live on npm, giving agents both a machine-readable docs entry point and a programmatic tool interface. Missing for 10: independent third-party confirmation that agents actually consume llms.txt successfully in practice beyond the HTTP probe.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.visaacceptance.com/llms.txt # VisaAcceptance Developer Center > This developer documentation …”
   • [probe] “official MCP server documented at https://github.com/visaacceptance/agent-toolkit”
   • [probe] “PROBE runtime (recorded 2026-09-14): Visa's developer gateway is live and credential-gated exactly as documented — a keyless GET to https://…”
   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”
   • [claimed-docs] “It offers a specialized set of tools designed to help you manage invoices, create payment links, and perform other Visa Acceptance-related o…”

   proof ↗⚑ flag

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

   weight 2 · round to Visa Intelligent Commerce
   Coinbase x402~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialprobed6/10

   The product is fundamentally API/protocol-driven (REST endpoints for tokens, instructions, credentials) with a published MCP server and npm-distributed agent-toolkit, plus a self-serve sandbox for test transactions — all of which are inherently headless and scriptable without a UI. However, there is no explicit documentation or example of CI/CD pipeline integration, automated test harnesses, or non-interactive credential/authentication flows (since the design requires passkey/step-up human authentication at key points), which limits true unattended automation. Missing for 10: explicit CI/CD pipeline examples, documentation on running fully unattended (given passkey step-up requirements), automated test suite integration guidance.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”
   • [probe] “official MCP server documented at https://github.com/visaacceptance/agent-toolkit”
   • [probe] “PROBE runtime (recorded 2026-09-14): Visa's developer gateway is live and credential-gated exactly as documented — a keyless GET to https://…”
   • [claimed-docs] “Merchant-side onboarding starts with a self-serve "Intelligent Commerce Sandbox Sign up" form (Organization ID, company, contact details, te…”

   proof ↗⚑ flag

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

   weight 3 · round to Visa Intelligent Commerce
   Coinbase x402~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullprobed7/10

   Visa explicitly ships an official MCP server (visaacceptance/agent-toolkit, published on npm as @visaacceptance/mcp) that lets developers/agents connect to Visa Intelligent Commerce APIs for payment-enabled operations like invoices and payment links, corroborated by a runtime probe confirming the npm package exists with Visa-staff maintainers. Missing for 10: independent hands-on usage reports/reviews of the MCP server beyond Visa's own announcement and npm registry check, and more detail on the full tool surface exposed via MCP.

   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”
   • [claimed-docs] “the toolkit helps developers and non-technical users to work with AI agents using plain language — no coding required.”
   • [claimed-docs] “It offers a specialized set of tools designed to help you manage invoices, create payment links, and perform other Visa Acceptance-related o…”
   • [probe] “official MCP server documented at https://github.com/visaacceptance/agent-toolkit”
   • [probe] “PROBE runtime (recorded 2026-09-14): Visa's developer gateway is live and credential-gated exactly as documented — a keyless GET to https://…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Coinbase x402—none0/10

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

   ⚑ flag

   Visa Intelligent Commerce—none0/10

   Evidence shows an MCP server and an npm-published 'agent-toolkit' with tool bindings, but nothing describes an official CLI binary or command-line interface for AI-native users to interact with Visa Intelligent Commerce.

   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”
   • [claimed-docs] “It offers a specialized set of tools designed to help you manage invoices, create payment links, and perform other Visa Acceptance-related o…”
   • [probe] “official MCP server documented at https://github.com/visaacceptance/agent-toolkit”
   • [probe] “PROBE runtime (recorded 2026-09-14): Visa's developer gateway is live and credential-gated exactly as documented — a keyless GET to https://…”

   proof ↗⚑ flag

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

   weight 3 · round to Visa Intelligent Commerce
   Coinbase x402~partialprobed6/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullprobed8/10

   Visa publishes a documented REST API (POST /acp/v1/instructions, /acp/v1/tokens, /acp/v1/instructions/{id}/credentials) with field-level specs, sandbox sign-up, and an official MCP server/agent-toolkit for AI-native access, corroborated by npm registry presence and a live gateway probe. missing for 10: independent third-party developer confirmation of building against the API and broader SDK/language coverage beyond the documented endpoints.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”
   • [probe] “official MCP server documented at https://github.com/visaacceptance/agent-toolkit”
   • [probe] “PROBE runtime (recorded 2026-09-14): Visa's developer gateway is live and credential-gated exactly as documented — a keyless GET to https://…”
   • [claimed-docs] “Merchant-side onboarding starts with a self-serve "Intelligent Commerce Sandbox Sign up" form (Organization ID, company, contact details, te…”

   proof ↗⚑ flag

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

   weight 2 · round to Visa Intelligent Commerce
   Coinbase x402~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialcommunity7/10

   Visa Intelligent Commerce issues agent-specific payment tokens/credentials scoped by merchant name, amount, and decline thresholds via mandates, gated behind passkey-authenticated user instructions (visa-ic-supp-1, visa-ic-supp-3, visa-ic-supp-5, visa-ic-supp-2). This is a concrete least-privilege credential model for payments, but it is payment-specific rather than a general API-credential scoping mechanism, and the platform page itself carries a maturity caveat ('in the process of development and deployment') plus community skepticism that standardized agent identity/permission scoping is still immature (visa-intelligent-commerce-comm-1). Missing for 10: evidence of granular scoping beyond amount/merchant (e.g., category-level or time-window least privilege), independent/production validation of the scoping enforcement, and confirmation the maturity caveat has been resolved.

   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [community] “The Visa/Mastercard announcements are interesting but feel premature. The missing piece is standardized agent identity and capability declar…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Visa Intelligent Commerce
   Coinbase x402~partialprobed6/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullprobed8/10

   Visa documents official REST APIs (with concrete endpoints for enrollment, credential retrieval, purchase-intent mandates), an official MCP server (published on npm as @visaacceptance/mcp with a GitHub repo), and an open-source Trusted Agent Protocol reference implementation, giving AI-native developers multiple official SDK/tooling surfaces to build against. Missing for 10: dedicated language-specific SDKs (Python/Node/Java client libraries) beyond the MCP/toolkit and REST docs, and independent third-party corroboration of SDK developer experience.

   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”
   • [claimed-docs] “It offers a specialized set of tools designed to help you manage invoices, create payment links, and perform other Visa Acceptance-related o…”
   • [probe] “official MCP server documented at https://github.com/visaacceptance/agent-toolkit”
   • [probe] “PROBE runtime (recorded 2026-09-14): Visa's developer gateway is live and credential-gated exactly as documented — a keyless GET to https://…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Coinbase x402~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed5/10

   Visa Intelligent Commerce provides the payment-authorization infrastructure (mandates, spend caps, tokens, passkey-anchored consent) that enables agents to transact autonomously within user-set limits, and the purchase-intent mandate mechanism (decline thresholds, effectiveUntilTime) supports background/recurring authorization without per-transaction human sign-off. However, this is a payments-rail product, not an automation/scheduling platform — there's no evidence of the product itself offering a UI or API for users to configure recurring/background 'automations' (e.g., scheduled tasks, triggers, workflows) beyond the payment-instruction mandate; that capability lives in whatever agent/orchestrator integrates with Visa's APIs. missing for 10: first-party evidence of an automation/scheduling interface for background-running tasks, independent hands-on confirmation of autonomous mandate execution in production, and clarity on how recurring (not just one-off) purchase intents are managed.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “Capture consumer consent, set spending limits, and manage mandates for agent-initiated payments.”
   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce—none0/10

   Evidence shows detailed REST endpoint documentation with sample JSON payloads (mandates, enroll-card, retrieve-credentials) and a separate sandbox signup form for sending test transactions, but nothing describes an interactive API reference (e.g., a Swagger/Postman-style 'try it' console) where examples can be run directly from the docs page. missing for 10: an interactive/try-it-now console embedded in API docs, evidence of one-click runnable code samples, any UI screenshot or independent report of in-docs execution.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “Merchant-side onboarding starts with a self-serve "Intelligent Commerce Sandbox Sign up" form (Organization ID, company, contact details, te…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.visaacceptance.com/llms.txt # VisaAcceptance Developer Center > This developer documentation …”

   proof ↗⚑ flag

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

   weight 2 · round to Visa Intelligent Commerce
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialprobed6/10

   Visa documents concrete REST endpoints (e.g., POST /acp/v1/instructions, /acp/v1/tokens, /acp/v1/instructions/{id}/credentials) with detailed field-level specs, an MCP server, and an llms.txt-served developer portal, indicating machine-readable interfaces exist, but no evidence explicitly confirms a downloadable OpenAPI/Swagger spec file. missing for 10: an explicit OpenAPI/Swagger JSON or YAML artifact, a documented download link or spec generation endpoint, independent confirmation the spec is machine-parseable rather than just REST prose docs.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.visaacceptance.com/llms.txt # VisaAcceptance Developer Center > This developer documentation …”
   • [claimed-docs] “Developers can now connect to Visa Intelligent Commerce APIs through the MCP Server, making it faster and easier for builders to bring intel…”

   proof ↗⚑ flag

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

   weight 1 · round to Visa Intelligent Commerce
   Coinbase x402~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullclaimed8/10

   Visa documents a dedicated sandbox: a self-serve 'Intelligent Commerce Sandbox Sign up' form that lets developers 'send test transactions,' separate test endpoints (https://apitest.visaacceptance.com vs production https://api.visaacceptance.com), and explicit fee terms stating 'Free to use in Sandbox. Contact Visa for fees in Production.' This directly satisfies testing without touching production data or paying production fees. Missing for 10: independent/hands-on confirmation that the sandbox behaves as documented (no third-party report of actually using it), and no detail on sandbox data reset/isolation guarantees.

   • [claimed-docs] “Merchant-side onboarding starts with a self-serve "Intelligent Commerce Sandbox Sign up" form (Organization ID, company, contact details, te…”
   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”

   proof ↗⚑ flag

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

   weight 2 · round to Visa Intelligent Commerce
   Coinbase x402—none0/10

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

   ⚑ flag

   Visa Intelligent Commerce~partialclaimed3/10

   API endpoints show explicit versioning (e.g., POST /acp/v1/instructions, /acp/v1/tokens) indicating a versioning scheme, but no evidence anywhere in the pack documents a deprecation policy, sunset timeline, or version-lifecycle commitment for these APIs. missing for 10: documented deprecation/versioning policy, migration guidance between versions, changelog or version-lifecycle commitments.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase x402
   Coinbase x402~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce—none0/10

   The evidence describes per-transaction flows (single card enrollment, single purchase-intent mandate, single credential retrieval, single invoice/payment link creation) with no mention of batch or bulk APIs for processing many items/transactions at once. While bulk operations are a plausible axis for a commerce/payments platform, there is no documentation of batch enrollment, bulk credential issuance, or multi-item transaction processing.

   • [claimed-docs] “It offers a specialized set of tools designed to help you manage invoices, create payment links, and perform other Visa Acceptance-related o…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”

   proof ↗⚑ flag

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

   weight 3 · round to Visa Intelligent Commerce
   Coinbase x402~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed5/10

   Visa Intelligent Commerce lets users set mandate-based rules such as decline thresholds, expiry times, and consumer prompts that constrain agent-initiated purchases, and documents automatic post-purchase actions triggered on payment confirmation events. This is rule-based automation but scoped narrowly to payment authorization and consent, not a general event-trigger-action framework a user can freely define. missing for 10: broader event types beyond payment confirmation, arbitrary custom action definitions beyond spend caps and expiry, independent evidence of the rule engine executing complex conditional logic

   • [claimed-docs] “Confirm payment outcomes and trigger post-purchase actions in real-time.”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”

   proof ↗⚑ flag

Fees transparency

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

   weight 2 · round to Coinbase x402
   Coinbase x402✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce—none0/10

   Visa's own documentation states fees are 'Free to use in Sandbox. Contact Visa for fees in Production' — meaning production pricing is explicitly not published and requires contacting Visa directly, the opposite of the story's ask for a self-serve published rate card.

   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”

   proof ↗⚑ flag

Payouts

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

   weight 1 · round to Coinbase x402
   Coinbase x402~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed4/10

   Visa Intelligent Commerce documents authorization, tokenization, mandates, and dispute-relevant 'commerce signals' capture, and notes settlement/IOU concepts in TAP, but there is no documented merchant payout/settlement schedule, reconciliation file/report format, or statement-level breakdown distinguishing agent-originated transactions from other channels — it's treated as a standard card-rail authorization with evidence signals for disputes, not a distinct reconciliable payout flow. missing for 10: documented payout/settlement cadence, merchant reconciliation reports or statement descriptors specific to agent transactions, dispute/chargeback API (vs. just evidence capture), independent merchant confirmation of reconciling agent payments like other channels.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “TAP's signed Agentic Payment Container adapts to the merchant's rail: for guest-checkout key entry it carries a credential hash — "If the ha…”
   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”

   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 Visa Intelligent Commerce
   Coinbase x402—none0/10

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

   ⚑ flag

   Visa Intelligent Commerce~partialclaimed4/10

   Visa Intelligent Commerce provides agent-scoped tokens, TAP signatures identifying an agent per interaction, and commerce-signal capture for dispute resolution, which implies some technical basis for attributing a transaction to an agent, but there is no documented merchant-facing reporting/dashboard feature or API to filter or report transactions specifically by agent identity. missing for 10: a merchant reporting/analytics dashboard or API endpoint that lets merchants filter/query transactions by agent identifier, explicit documentation of agent-ID fields surfaced in settlement/reporting data, and independent evidence merchants actually use this for reporting.

   • [claimed-docs] “The Trusted Agent Protocol's agent recognition signature is HTTP Message Signatures "defined by RCF 9421" (typo in original), "aligned with …”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”
   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”
   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”

   proof ↗⚑ flag

Onboarding to agents

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

   weight 3 · round to Coinbase x402
   Coinbase x402✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed7/10

   Visa documents a genuine self-serve onboarding flow: a public 'Intelligent Commerce Sandbox Sign up' form with terms acceptance that immediately unlocks test transactions (visa-ic-supp-10), plus an open, publishable Trusted Agent Protocol reference implementation merchants can deploy to declare/verify agent traffic (visa-ic-supp-9, visa-intelligent-commerce-gh-1/2). However, production enablement is explicitly gated — 'Contact Visa for fees in Production' (visa-ic-supp-8) — meaning the fully self-serve path only covers sandbox/dev, not live acceptance. Missing for 10: a documented self-serve production activation step (no sales contact), and independent merchant confirmation that the sandbox-to-production path works without manual Visa involvement.

   • [claimed-docs] “Merchant-side onboarding starts with a self-serve "Intelligent Commerce Sandbox Sign up" form (Organization ID, company, contact details, te…”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”
   • [github] “By presenting a secure digital signature with every interaction, a merchant can verify that an agent is legitimate and has the user's permis…”
   • [github] “This allows you to confidently welcome agent-driven commerce while protecting your site from harmful bots.”
   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”

   proof ↗⚑ flag

Traffic controls

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

   weight 2 · round to Visa Intelligent Commerce
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed5/10

   Trusted Agent Protocol gives merchants a way to cryptographically verify agent legitimacy, distinguish credentialed agents from anonymous bots via an agent-registry, and reject stale/replayed signed requests, which supports an allow/deny posture at checkout. However there is no documented merchant-facing control for rate-limiting specific agents or blocking by agent platform/brand — the evidence is about identity verification and anti-bot protection, not policy-based throttling or platform-level allow/deny lists. missing for 10: explicit rate-limiting mechanism, per-platform allow/deny configuration UI or API, documented throttling/quota controls.

   • [github] “By presenting a secure digital signature with every interaction, a merchant can verify that an agent is legitimate and has the user's permis…”
   • [github] “This allows you to confidently welcome agent-driven commerce while protecting your site from harmful bots.”
   • [claimed-docs] “The Trusted Agent Protocol's agent recognition signature is HTTP Message Signatures "defined by RCF 9421" (typo in original), "aligned with …”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase x402
   Coinbase x402~partialprobed5/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialprobed4/10

   Visa Intelligent Commerce itself (the core enrollment/token/mandate platform) is a closed, proprietary financial service with no source release, but the related Trusted Agent Protocol spec and reference implementation, plus the agent-toolkit, are published openly on GitHub with a runnable sample ecosystem (agent-registry, cdn-proxy, merchant-backend, tap-agent). This only covers peripheral protocol/toolkit components, not the core Intelligent Commerce platform's own source. Missing for 10: an explicit open-source license grant for the core Intelligent Commerce platform itself, not just the TAP spec/toolkit sidecars.

   • [probe] “PROBE runtime (recorded 2026-09-14): the Trusted Agent Protocol is published in the open — https://raw.githubusercontent.com/visa/trusted-ag…”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”
   • [github] “By presenting a secure digital signature with every interaction, a merchant can verify that an agent is legitimate and has the user's permis…”
   • [claimed-docs] “It offers a specialized set of tools designed to help you manage invoices, create payment links, and perform other Visa Acceptance-related o…”

   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 Visa Intelligent Commerce
   Coinbase x402~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullclaimed9/10

   Extensive first-party docs describe exactly this: agent-specific pass-through payment tokens, purchase-intent mandates with declineThreshold amount/currency and effectiveUntilTime expiry, and credential retrieval requests scoped to a specific merchantName/merchant descriptor and amount — all gated behind passkey-authenticated user instructions. This directly matches 'scoped, limited-use credential with amount limits, expiry, merchant restrictions instead of raw card number.' missing for 10: independent third-party (non-Visa) hands-on confirmation that these scoped credentials work end-to-end in production rather than sandbox, since the product itself carries a documented maturity caveat.

   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”

   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 Coinbase x402
   Coinbase x402✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed5/10

   Visa's Trusted Agent Protocol spec explicitly describes an HTTP 402 flow where a merchant/service returns a 402 with a 'payment IOU,' and after verifying the signed agent payload, 'the Merchant can grant access with the expectation that the funds will be available when settlement occurs' — a genuine machine-payable, checkout-less mechanism (visa-ic-supp-7, visa-ic-supp-6). However, all documentation and the reference implementation (agent-registry, cdn-proxy, merchant-backend) frame this around e-commerce/merchant checkout rather than generic API/service monetization or per-call billing, and there's no dedicated guide for developers wanting to gate an arbitrary API endpoint this way. Missing for 10: explicit API-monetization framing/tutorial, per-call billing/metering support, and independent/hands-on evidence of the 402 flow being used outside merchant checkout scenarios.

   • [claimed-docs] “TAP's signed Agentic Payment Container adapts to the merchant's rail: for guest-checkout key entry it carries a credential hash — "If the ha…”
   • [claimed-docs] “The Trusted Agent Protocol's agent recognition signature is HTTP Message Signatures "defined by RCF 9421" (typo in original), "aligned with …”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”
   • [github] “Securely receive key information needed for checkout via query parameters. This can include, as consented by the consumer, verifiable consum…”

   proof ↗⚑ flag

Settlement rails

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

   weight 2 · round to Coinbase x402
   Coinbase x402✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce—none0/10

   All evidence describes Visa Intelligent Commerce's card-network rails (tokenized cards, network tokens, VisaNet authorization, passkey-anchored mandates) — there is no mention anywhere of stablecoin settlement, crypto rails, or any non-card settlement currency. The axis applies to a payments product but no evidence supports stablecoin settlement specifically.

   • [claimed-docs] “Secure retrieval and management of network tokens, supporting seamless agentic commerce across multiple payment networks.”
   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”

   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 drawn
   Coinbase x402~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed5/10

   Visa IC lets a consumer enroll/tokenize their card for agent use, set decline-threshold spend limits via mandates, and authenticate/control every agent payment instruction via Passkey — covering 'funded and controlled by me' reasonably well (visa-ic-supp-1, visa-ic-supp-2, visa-ic-supp-3, visa-ic-supp-4). But this is card-linkage/tokenization infrastructure, not a stored-value 'wallet' with its own balance, and there is no evidence of a balance-visibility feature for the end user or agent. Missing for 10: an actual funded wallet construct (vs. tokenized card-on-file), explicit balance-visibility UI/API, and independent confirmation beyond Visa's own docs.

   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Capture consumer consent, set spending limits, and manage mandates for agent-initiated payments.”

   proof ↗⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Coinbase x402—none0/10

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

   ⚑ flag

   Visa Intelligent Commerce—none0/10

   Visa Intelligent Commerce documents consent capture, mandates, spend caps, and even cancellation of a purchase intent, but none of the evidence addresses a user's ability to control data retention periods or request deletion of stored consumer data, tokens, or consent records. Revocation of a 'purchase intent' (visa-ic-supp-3) is a transactional control, not a data-retention/deletion mechanism, so the specific privacy-posture story is unaddressed.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “Capture consumer consent, set spending limits, and manage mandates for agent-initiated payments.”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”

   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 Coinbase x402
   Coinbase x402✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce—none0/10

   All evidence is first-party Visa documentation, GitHub repos owned by Visa, and Visa's own MCP/agent-toolkit; none names a second independent implementer (merchant platform, other network, AI vendor, etc.) building on the protocol. Community commentary even frames the initiative as still 'premature' with no adoption signals cited, so there's no evidence of an ecosystem beyond the vendor.

   • [community] “The Visa/Mastercard announcements are interesting but feel premature. The missing piece is standardized agent identity and capability declar…”
   • [community] “The Visa/Mastercard moves are interesting but I'd bet the real unlock is when businesses start issuing agent-specific cards with embedded po…”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Trusted Agent Protocol is published in the open — https://raw.githubusercontent.com/visa/trusted-ag…”

   proof ↗⚑ flag

Spec publication

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

   weight 3 · round to Coinbase x402
   Coinbase x402✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialprobed5/10

   Visa's Trusted Agent Protocol (TAP) is published openly on GitHub with a runnable reference implementation and keyless README access, satisfying 'read without signing' for that layer (visa-ic-probe-rt-1, visa-ic-supp-9, visa-ic-supp-6). However, the core Intelligent Commerce payment protocol (ACP instructions, tokens, credentials) requires a sandbox sign-up form with terms acceptance and 'Contact Visa for fees in Production' for real use, meaning the actual commerce protocol is gated behind registration/agreements, not a freely implementable open spec (visa-ic-supp-10, visa-ic-supp-8). Missing for 10: a single unified, explicitly versioned spec document covering the full commerce protocol (not just TAP) that can be implemented end-to-end without any sandbox registration or production agreement.

   • [probe] “PROBE runtime (recorded 2026-09-14): the Trusted Agent Protocol is published in the open — https://raw.githubusercontent.com/visa/trusted-ag…”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”
   • [claimed-docs] “The Trusted Agent Protocol's agent recognition signature is HTTP Message Signatures "defined by RCF 9421" (typo in original), "aligned with …”
   • [claimed-docs] “Merchant-side onboarding starts with a self-serve "Intelligent Commerce Sandbox Sign up" form (Organization ID, company, contact details, te…”
   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”

   proof ↗⚑ flag

Disputes

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

   weight 2 · round drawn
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce—none0/10

   Evidence explicitly states Visa's docs stop at collecting 'commerce signals' to aid dispute resolution, not a dedicated dispute/chargeback API with evidence submission, status, or outcome endpoints (visa-ic-supp-8). No other citation shows any dispute-specific API surface.

   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”

   proof ↗⚑ flag

Refunds

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

   weight 2 · round to Coinbase x402
   Coinbase x402~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce—none0/10

   Evidence explicitly states Visa Intelligent Commerce docs 'stop at evidence capture, not a dispute API' — there's only an optional 'policies.refundPolicy' metadata field attached to a credential request and generic 'commerce signals' for dispute resolution, not a programmatic refund initiation/tracking endpoint or status API for agent-placed orders.

   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”

   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 Visa Intelligent Commerce
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullprobed8/10

   Visa's Trusted Agent Protocol gives merchants a concrete verifiable-identity mechanism: RFC9421 HTTP message signatures tagged 'agent-browser-auth'/'agent-payer-auth', anti-replay nonces/timestamps, verification against Visa's public JWKS, and an open reference implementation that includes an 'agent-registry' component explicitly described as letting merchants 'instantly distinguish a legitimate, credentialed agent from an anonymous bot' and confirm it acts on behalf of an authenticated user. This is corroborated by a runtime probe showing the spec and reference repo are live and publicly accessible, going beyond marketing copy. Missing for 10: independent/production adoption evidence beyond Visa's own repo and probes, and clearer merchant-facing tooling for classifying agents into explicit 'trust tiers' rather than a binary signed/unsigned check.

   • [github] “By presenting a secure digital signature with every interaction, a merchant can verify that an agent is legitimate and has the user's permis…”
   • [github] “This allows you to confidently welcome agent-driven commerce while protecting your site from harmful bots.”
   • [claimed-docs] “including the cryptographic standards (RFC9421), required message signature fields, and the process for validating an agent's intent.”
   • [claimed-docs] “The Trusted Agent Protocol's agent recognition signature is HTTP Message Signatures "defined by RCF 9421" (typo in original), "aligned with …”
   • [claimed-docs] “TAP's signed Agentic Payment Container adapts to the merchant's rail: for guest-checkout key entry it carries a credential hash — "If the ha…”
   • [claimed-docs] “The TAP spec is public with a runnable reference implementation: "Establishing a universal standard of trust between AI agents and merchants…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Trusted Agent Protocol is published in the open — https://raw.githubusercontent.com/visa/trusted-ag…”

   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 Visa Intelligent Commerce
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce✓fullclaimed8/10

   Visa Intelligent Commerce documents passkey-anchored authentication of payment instructions, per-purchase mandates with declineThreshold caps and consumerPrompt confirmation text, credential requests scoped to specific merchant/amount, and a Trusted Agent Protocol signature scheme validating agent intent before authorization — collectively a documented consent/mandate flow gating money movement. missing for 10: independent hands-on verification that the consent/mandate flow works end-to-end in production (product still carries a 'in process of development and deployment' caveat) and no third-party audit of the passkey step-up UX.

   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “"Your agents can enroll a customer's card for tokenization during the customer's account registration or when the customer begins a new purc…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “The Trusted Agent Protocol's agent recognition signature is HTTP Message Signatures "defined by RCF 9421" (typo in original), "aligned with …”
   • [claimed-docs] “Controls to ensure that the agent’s purchasing actions and the related authorizations align with the user’s authenticated instruction”
   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”

   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 Visa Intelligent Commerce
   Coinbase x402—none0/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed3/10

   Docs describe extensive fraud-prevention plumbing (passkey authentication, mandates, TAP signatures) but the only mention of chargebacks/disputes explicitly stops at 'commerce signals... allow for quick resolution of most disputes' rather than a documented liability-shift or chargeback-allocation policy, and explicitly notes there is no dispute API. Missing for 10: explicit statement of who bears fraud/chargeback liability (merchant vs. issuer vs. cardholder) for agent-initiated transactions, documented dispute resolution process/API, and any liability-shift terms analogous to EMV rules.

   • [claimed-docs] “Fees, verbatim from FEES & TERMS: "Free to use in Sandbox. Contact Visa for fees in Production." On refunds/disputes the docs stop at eviden…”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “The Trusted Agent Protocol's agent recognition signature is HTTP Message Signatures "defined by RCF 9421" (typo in original), "aligned with …”

   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 Visa Intelligent Commerce
   Coinbase x402~partialcommunity3/10

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

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

   proof ↗⚑ flag

   Visa Intelligent Commerce~partialclaimed7/10

   Docs show concrete mandate mechanics — declineThreshold spend caps, effectiveUntilTime, and a documented 'cancel a purchase intent' revocation path — plus passkey-gated instruction authentication and per-request credential scoping to merchant/amount, which together implement caps and a revocation-like control. However, evidence covers per-purchase-intent caps/cancellation rather than a persistent 'agent-wide spend cap + instant kill-switch' dashboard, and the product itself is flagged as still 'in the process of development and deployment.' Missing for 10: consumer-facing UI/API for setting ongoing per-agent usage limits (not just per-transaction mandates), explicit 'revoke all future authority instantly' mechanism beyond canceling a single intent, and independent/hands-on confirmation of revocation latency.

   • [claimed-docs] “Spend caps live in the purchase-intent mandate: Initiate a Purchase Intent (POST /acp/v1/instructions) exists "to verify that your agent is …”
   • [claimed-docs] “Human approval is passkey-anchored end to end: provisioning includes "step up verification of the cardholder as well as setting up a Passkey…”
   • [claimed-docs] “Agent-scoped credentials are the core primitive: "Provisioning and life cycle management of agent-specific payment tokens that can be used b…”
   • [claimed-docs] “Credentials are scoped to an authenticated instruction: retrieval is POST /acp/v1/instructions/{instructionID}/credentials, and the request …”
   • [claimed-docs] “Capture consumer consent, set spending limits, and manage mandates for agent-initiated payments.”

   proof ↗⚑ flag