Coinbase x402 vs Crossmint

Cart

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

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

   Crossmint✓fullprobed8/10

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

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

   proof ↗⚑ flag

Checkout

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

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

   Crossmint✓fullprobed8/10

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

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

   proof ↗⚑ flag

Embedded surfaces

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

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

   Crossmint~partialclaimed3/10

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

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

   proof ↗⚑ flag

Protocol conformance

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Agent search

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

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

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

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

   proof ↗⚑ flag

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Machine readable offers

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

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

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

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

   proof ↗⚑ flag

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Service discovery

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

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

   Crossmint—none0/10

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

   ⚑ flag

Agent access

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

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

   Crossmint✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

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

   Crossmint~partialprobed6/10

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

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

   proof ↗⚑ flag

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

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

   Crossmint✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

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

   Crossmint✓fullprobed7/10

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

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

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

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

   Crossmint~partialprobed5/10

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

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

   proof ↗⚑ flag

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

   Crossmint~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

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

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

   Crossmint~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

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

   Crossmint—none0/10

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

   ⚑ flag

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

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

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

   Crossmint~partialclaimed4/10

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

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

   proof ↗⚑ flag

Fees transparency

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Payouts

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

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

   Crossmint~partialclaimed3/10

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

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

   proof ↗⚑ flag

Attribution analytics

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

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

   Crossmint—none0/10

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

   ⚑ flag

Onboarding to agents

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

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

   Crossmint—none0/10

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

   ⚑ flag

Traffic controls

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Delegated credentials

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

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

   Crossmint✓fullprobed9/10

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

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

   proof ↗⚑ flag

Machine payments

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Settlement rails

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

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

   Crossmint✓fullprobed8/10

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

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

   proof ↗⚑ flag

Wallets

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

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

   Crossmint~partialclaimed7/10

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

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

   proof ↗⚑ flag

Ecosystem adoption

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

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

   Crossmint—none0/10

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

   ⚑ flag

Spec publication

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Disputes

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Refunds

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

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

   Crossmint—none0/10

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

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

   proof ↗⚑ flag

Agent identity

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

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

   Crossmint~partialprobed5/10

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

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

   proof ↗⚑ flag

Human oversight

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

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

   Crossmint~partialclaimed6/10

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

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

   proof ↗⚑ flag

Liability

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

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

   Crossmint~partialclaimed4/10

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

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

   proof ↗⚑ flag

Spend controls

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

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

   Crossmint✓fullprobed8/10

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

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

   proof ↗⚑ flag