Coinbase x402 vs Skyfire

Cart

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

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

   Skyfire—none0/10

   Skyfire's documented protocol (tokens, kya/pay/kya-pay, MCP tools like find-sellers/create-*-token) covers identity verification and payment authorization/settlement, but there is no documented call for creating or updating a cart or order draft — order/cart state is left to the seller's own system, not exposed via Skyfire's API or MCP server.

   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “Create an MCP Server Resource that explains which token types are required (`kya`, `pay`, and/or `kya-pay`), how tokens must be passed (the …”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”
   • [claimed-docs] “Skyfire gives agents verified identity and payment credentials — "No 403 errors, captchas or blocked checkouts. Authenticated access and pay…”

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

   Skyfire✓fullprobed8/10

   Skyfire documents the full agent-checkout loop: MCP tools let an agent discover sellers, create kya/pay/kya-pay tokens (delegated payment+identity credential), and sellers charge the token post-delivery with funds moved between wallets, completing a confirmed order/settlement. missing for 10: independent/hands-on end-to-end transaction proof (evidence is vendor docs plus a narrow auth-only runtime probe, not a full live purchase trace) and no example of an explicit 'confirmed order' object/receipt returned to the buyer.

   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “Sellers can use a `kya-pay` token to enable a guest checkout experience for buyer agents.”
   • [claimed-docs] “Skyfire gives agents verified identity and payment credentials — "No 403 errors, captchas or blocked checkouts. Authenticated access and pay…”
   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/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 drawn
   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

   Skyfire—none0/10

   Skyfire's evidence documents a generic agent-to-agent payment/identity protocol (tokens, MCP server for 'find-sellers' and token creation) but nowhere mentions ChatGPT, Claude, Gemini, Copilot or any named chat/assistant surface, nor any commerce-in-chat integration or app-store listing. The MCP server is a generic protocol endpoint, not documented evidence of embedding within these specific consumer assistant surfaces.

   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”
   • [claimed-docs] “Create an MCP Server Resource that explains which token types are required (`kya`, `pay`, and/or `kya-pay`), how tokens must be passed (the …”

   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

   Skyfire~partialprobed4/10

   Skyfire points to an external 'open' KYAPay protocol (KYAPay.org) with JWT-based tokens that all Skyfire tokens conform to, giving a nominal published spec, but the evidence pack shows no OpenAPI/schema file for Skyfire's own API (all standard OpenAPI paths 404) and no conformance/validation tooling (test suites, schema validators, certification) is documented anywhere. Missing for 10: a published machine-readable schema for the Skyfire API itself, explicit protocol versioning, and any conformance/validation tooling a developer could run against.

   • [claimed-docs] “"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens ar…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”
   • [claimed-docs] “Create an MCP Server Resource that explains which token types are required (`kya`, `pay`, and/or `kya-pay`), how tokens must be passed (the …”

   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

   Skyfire~partialprobed5/10

   Skyfire's MCP server exposes a 'find-sellers' tool for programmatic discovery, but access requires a self-service API key scoped to a registered agent (not fully keyless) and seller listings are approval-gated by Skyfire rather than an open, permissionless catalog; runtime probe confirms endpoints are key-gated. missing for 10: evidence of true keyless/anonymous discovery, breadth/independence of merchant catalog, and independent corroboration of discovery quality beyond Skyfire's own docs.

   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”
   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api…”

   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

   Skyfire~partialprobed3/10

   Skyfire's MCP server exposes a 'find-sellers' tool for service discovery, and seller service creation includes a 'pricing' field (skyfire-docs-3, skyfire-docs-6, skyfire-supp-9), suggesting some machine-readable service metadata exists. However, there is no documented schema showing availability, variants, or checkout links returned to a developer/agent, and no OpenAPI spec was found (skyfire-probe-2) to confirm structured offer data beyond pricing and identity requirements. Missing for 10: documented availability/variant fields, explicit checkout-link data, and a public API schema showing full offer payloads.

   • [claimed-docs] “Click Create Service and provide details like: name, type, pricing, identity requirements, etc. Submit for approval.”
   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”

   proof ↗⚑ flag

Merchant feeds

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

   weight 3 · round to Coinbase x402
   Coinbase x402~partialprobed6/10

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

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

   proof ↗⚑ flag

   Skyfire~partialclaimed5/10

   Skyfire lets a seller register services via 'Create Service' (name, type, pricing, identity requirements) and then makes them discoverable to agents through the MCP server's 'find-sellers' tool, which is a real agent-discovery surface. But this is a one-at-a-time, approval-gated dashboard/API flow rather than a documented bulk catalog feed or import API for a full product/service catalog. missing for 10: a bulk catalog feed/import API (e.g., CSV/JSON catalog upload), documentation on how multiple SKUs or listings map to discovery, and evidence of independent merchant usage confirming catalog visibility in agent surfaces.

   • [claimed-docs] “Click Create Service and provide details like: name, type, pricing, identity requirements, etc. Submit for approval.”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”
   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”

   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

   Skyfire~partialclaimed6/10

   Skyfire's MCP server exposes a 'find-sellers' tool that lets an agent query for payable services/sellers programmatically, and sellers register services through an approval-gated catalog, giving agents a discovery mechanism (skyfire-docs-6, skyfire-supp-9, skyfire-docs-3). However, there's no evidence of a publicly browsable directory/index outside the MCP tool call, nor documentation of how the directory is structured, filtered, or how comprehensive/curated it is. Missing for 10: a documented public directory/catalog UI or API endpoint separate from the MCP tool, details on search/filter capabilities, and independent confirmation of discovery breadth.

   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”
   • [claimed-docs] “Click Create Service and provide details like: name, type, pricing, identity requirements, etc. Submit for approval.”
   • [claimed-docs] “Create an MCP Server Resource that explains which token types are required (`kya`, `pay`, and/or `kya-pay`), how tokens must be passed (the …”

   proof ↗⚑ flag

Agent access

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

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

   Skyfire✓fullprobed8/10

   Skyfire's docs site serves a working llms.txt (HTTP 200, agent-oriented summary) confirmed by both a probe and a runtime check, and its full docs are structured as agent-consumable markdown (.md endpoints throughout). This directly satisfies pointing an agent at llms.txt/agent-oriented docs. Missing for 10: no independent third-party report of an agent successfully consuming llms.txt end-to-end, and no OpenAPI spec (all candidate paths 404) which would further strengthen machine-readability.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.skyfire.xyz/llms.txt # Skyfire Developer Portal Documentation > Skyfire is the open identity and p…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”

   proof ↗⚑ flag

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

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

   Skyfire~partialprobed6/10

   Skyfire is API-first: agents authenticate via scoped API keys (no interactive login) and all core operations (token creation, introspection, charging) are REST endpoints, confirmed live and key-gated by a runtime probe, plus an MCP server for programmatic agent workflows. However, there's no explicit CI/CD example, headless setup guide, or CLI/SDK documentation showing automation-pipeline usage. missing for 10: explicit CI/headless usage guide, CLI or SDK tooling, and independent confirmation of non-interactive automation beyond API-key auth.

   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”
   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”
   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api…”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”

   proof ↗⚑ flag

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

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

   Skyfire✓fullclaimed8/10

   Skyfire documents an official hosted MCP server (https://mcp.skyfire.xyz/mcp, plus sandbox) with documented tools (find-sellers, create-kya-token, create-pay-token, create-kya-payment-token) and auth via API key header, letting agents connect and execute commerce workflows. missing for 10: independent/third-party corroboration of the MCP server working in practice, and no public OpenAPI/schema for deeper verification.

   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “Create an MCP Server Resource that explains which token types are required (`kya`, `pay`, and/or `kya-pay`), how tokens must be passed (the …”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”

   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

   Skyfire—none0/10

   Skyfire's docs describe REST APIs, MCP server integration, and a dashboard/Playground, but no evidence pack item mentions an official CLI tool for developers or agents. Missing for 10: any documented CLI binary, npm/pip package, or command-line reference.

   ⚑ flag

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

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

   Skyfire✓fullprobed8/10

   Skyfire ships a documented public REST API (tokens, introspect, charge-token) gated by per-agent API keys, confirmed live via runtime probe returning a structured auth error rather than a 404, plus llms.txt-served docs. Missing for 10: a published OpenAPI/swagger spec (probe found all candidate spec URLs 404) and independent third-party corroboration beyond vendor docs/probes.

   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”
   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.skyfire.xyz/llms.txt # Skyfire Developer Portal Documentation > Skyfire is the open identity and p…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”

   proof ↗⚑ flag

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

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

   Skyfire~partialclaimed6/10

   Skyfire API keys are scoped per-agent (Buyer/Seller) and pay tokens carry committed amounts with hard balance ceilings, and KYA-gated tokens enforce identity requirements, which together give agent-level least-privilege credentials. However, this is scoped to payment/identity tokens rather than granular API permission scopes (e.g., no fine-grained action/resource-level scoping or role-based permission sets), and there is no documented per-token revocation API. missing for 10: fine-grained permission/action scoping beyond agent+amount+identity, documented revocation controls, independent/hands-on verification of scoping enforcement.

   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”
   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “"Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agen…”
   • [claimed-docs] “Revocation is bounded by design: deactivating an account does not void already-issued pay/kya-pay tokens — "New token creation stops at deac…”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”

   proof ↗⚑ flag

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

   Skyfire—none0/10

   Evidence shows Skyfire has REST API reference docs, a Playground, and an MCP server for agent integration, but nowhere does it mention or link to an official language SDK (e.g., Python/JS client library). The openapi.json probe even returned 404, undermining any inference of auto-generated SDK tooling.

   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”

   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

   Skyfire~partialclaimed5/10

   Skyfire's MCP server lets an agent autonomously discover sellers, mint kya/pay tokens, and execute commerce transactions without human-in-the-loop approval up to committed token limits (skyfire-docs-6, skyfire-supp-9, skyfire-supp-4), which supports autonomous background operation for agent commerce specifically. But Skyfire is a payment/identity layer, not a general automation/orchestration platform — there's no documented scheduler, trigger system, or persistent background-job mechanism for setting up broader autonomous workflows beyond commerce transactions. missing for 10: evidence of a scheduling/trigger system, persistent background job execution beyond per-call MCP invocations, and support for non-commerce automation tasks.

   • [claimed-docs] “Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic co…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”
   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Skyfire gives agents verified identity and payment credentials — "No 403 errors, captchas or blocked checkouts. Authenticated access and pay…”

   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

   Skyfire—none0/10

   The evidence shows Skyfire has structured reference docs (charge-token, introspect-token, etc.) but the openapi probe found no machine-readable spec (404s on all candidate paths), and there is no mention of an interactive console, 'try it' feature, or runnable code examples anywhere in the pack — only static markdown-style API reference pages.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”
   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”

   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

   Skyfire—none0/10

   The docs contain structured API reference pages (e.g., charge-token, introspect-token) suggesting an underlying spec, but a direct probe for machine-readable OpenAPI/Swagger files at all standard locations returned 404 for every candidate path, and no evidence shows a downloadable spec file or link.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”
   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”

   proof ↗⚑ flag

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

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

   Skyfire~partialclaimed5/10

   The MCP server docs explicitly reference a separate sandbox endpoint (mcp-sandbox.skyfire.xyz) distinct from the production mcp.skyfire.xyz, showing a dedicated test environment exists. However, there's no broader documentation of a sandbox for the core token/payment APIs, wallets, or KYA flows outside the MCP context, and no detail on how sandbox data is isolated from production. Missing for 10: dedicated sandbox docs for REST/token APIs beyond MCP, explicit guidance on test credentials/test wallets, independent confirmation the sandbox fully mirrors production without touching real funds.

   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”

   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

   Skyfire—none0/10

   While the API path shows a v1 prefix (skyfire-probe-rt-1) and an OpenAPI spec probe returned 404s (skyfire-probe-2), there is no documentation of a versioning scheme, deprecation timeline, or migration policy anywhere in the evidence pack. Missing for 10: any deprecation policy page, versioning changelog, or migration guide.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api…”

   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

   Skyfire—none0/10

   Skyfire's documented API is single-item/token-centric (create one token, charge one token, introspect one token) with no documented batch or bulk endpoints for processing many items in one call. No evidence of any bulk-operation capability across tokens, sellers, or charges.

   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”

   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

   Skyfire—none0/10

   Evidence shows sellers set their own service pricing when configuring a service, but there is no published fee schedule for Skyfire's own transaction/take-rate fees on agent-originated payments — nothing lets a merchant price agentic channels without contacting sales.

   • [claimed-docs] “Click Create Service and provide details like: name, type, pricing, identity requirements, etc. Submit for approval.”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”

   proof ↗⚑ flag

Payouts

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

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

   Skyfire~partialclaimed5/10

   Skyfire documents the settlement mechanics merchants need — charge-token API, committed/ceiling amounts, multi-charge until balance exhausted, defined settlement windows (up to 51 hours), and overcharge rejection (402) — which supports reconciliation of individual transactions. However, there is no documented merchant-facing payout flow (e.g., withdrawal to bank/external accounts), no statement/reporting/export API, and no mention of standard accounting artifacts (invoices, ledgers, CSV/webhook reporting) that would let a merchant reconcile against other channels. missing for 10: documented payout/withdrawal mechanism to real-world funds, merchant reporting/statement or export API, reconciliation tooling or ledger export, independent confirmation of reporting flows.

   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “Revocation is bounded by design: deactivating an account does not void already-issued pay/kya-pay tokens — "New token creation stops at deac…”
   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Skyfire gives agents verified identity and payment credentials — "No 403 errors, captchas or blocked checkouts. Authenticated access and pay…”

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

   Skyfire~partialclaimed5/10

   Skyfire ties every transaction to a specific Buyer Agent via KYA identity tokens and per-agent API keys, so orders are technically attributable to the originating agent (skyfire-docs-1, skyfire-supp-2, skyfire-supp-7), and introspect/charge-token APIs let a seller programmatically check token/agent status (skyfire-docs-4, skyfire-docs-5). However, there is no evidence of a merchant-facing report or dashboard view that lets a merchant filter/aggregate transactions by agent — only a general 'Agent Dashboard' for key management is mentioned. Missing for 10: documented merchant reporting/analytics UI or API for filtering transactions by agent, evidence of aggregate order-to-agent attribution reporting.

   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”
   • [claimed-docs] “"Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agen…”
   • [claimed-docs] “Cardholder consent bounds card spending: "The agent/agent platform can never spend more than the cardholder approved." — an authorization co…”
   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”

   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

   Skyfire~partialclaimed7/10

   Skyfire documents a concrete merchant-facing path: create a Seller Agent, generate a scoped API key, click 'Create Service' with pricing/identity requirements, and use the Charge Token API to collect payment — all via the Agent Dashboard (skyfire-docs-3, skyfire-supp-8, skyfire-docs-4). However, service creation is explicitly 'Submit for approval,' meaning it's gated rather than a pure self-serve flip-a-switch flow. Missing for 10: confirmation of approval turnaround/criteria, an explicit merchant agreement/ToS signing step, and independent verification that the approval process is lightweight rather than a manual sales gate.

   • [claimed-docs] “Click Create Service and provide details like: name, type, pricing, identity requirements, etc. Submit for approval.”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”
   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”

   proof ↗⚑ flag

Traffic controls

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

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

   Skyfire~partialclaimed4/10

   Skyfire lets sellers set per-service identity requirements (KYA verification levels) that gate token creation and thus checkout access, and its payment-card flow lets a merchant's bot manager identify and allow known agents rather than block them — giving coarse allow/deny-by-identity control. However there is no documented rate-limiting feature, no explicit deny-list or per-agent/platform blocking mechanism, and no console for merchants to enumerate specific agents/platforms to throttle or reject. Missing for 10: rate-limiting controls, explicit allow/deny list management UI/API, granular per-agent-platform policy enforcement beyond identity-level gating.

   • [claimed-docs] “"Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agen…”
   • [claimed-docs] “The site, or the bot manager in front of it, can then identify the agent/agent platform and allow it through rather than block it.”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”

   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

   Skyfire—none0/10

   Evidence shows Skyfire is a closed, key-gated commercial API/platform (identity+payments infrastructure) with only a published token spec (KYAPay) being open, not the product's own source code; no repo, license, or open-source claim appears anywhere in the pack.

   • [probe] “PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api…”
   • [claimed-docs] “"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens ar…”

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

   Skyfire✓fullclaimed8/10

   Skyfire issues scoped pay/kya-pay tokens with committed amount ceilings, expiry windows (10s-24h plus grace period), and merchant/identity-requirement gating rather than raw card numbers, all documented via API and MCP server tooling. Missing for 10: independent third-party/hands-on corroboration beyond vendor docs, and explicit merchant-restriction scoping details (evidence shows identity/amount/time limits clearly but merchant-lock-in specifics are thinner).

   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “Revocation is bounded by design: deactivating an account does not void already-issued pay/kya-pay tokens — "New token creation stops at deac…”
   • [claimed-docs] “"Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agen…”
   • [claimed-docs] “On signup, your Buyer Agent is created automatically, along with a pre-funded wallet so you can start using paid services right away.”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”

   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

   Skyfire~partialclaimed7/10

   Skyfire lets sellers register a service, gate access with kya/pay tokens, and charge per call via the Charge Token API after delivery — with no checkout UI, matching most of the story's intent, and the docs explicitly note overcharges are rejected with an HTTP 402 PAYMENT_ERROR. However, the evidence shows Skyfire's core mechanism is its own token/JWT (KYAPay) issuance-and-charge flow rather than a standard HTTP 402 challenge-response loop as the primary payment protocol. Missing for 10: explicit documentation that HTTP 402 is used as the initial payment-required response/handshake (not just an overcharge error code), and independent confirmation of the 402-based flow in production use.

   • [claimed-docs] “Click Create Service and provide details like: name, type, pricing, identity requirements, etc. Submit for approval.”
   • [claimed-docs] “Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect…”
   • [claimed-docs] “Skyfire gives agents verified identity and payment credentials — "No 403 errors, captchas or blocked checkouts. Authenticated access and pay…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”

   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

   Skyfire~partialclaimed3/10

   Skyfire documents thorough payment settlement rails — wallets, pay/kya-pay tokens, committed amounts, charge-token API, settlement timing windows, and open KYAPay token spec — but none of the evidence explicitly states that settlement occurs in stablecoins or names any specific blockchain/stablecoin rail. Missing for 10: explicit stablecoin currency mention, underlying blockchain/rail specification, and confirmation that wallet balances/settlement are denominated in a stablecoin rather than fiat/credit abstraction.

   • [claimed-docs] “Skyfire gives agents verified identity and payment credentials — "No 403 errors, captchas or blocked checkouts. Authenticated access and pay…”
   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “On signup, your Buyer Agent is created automatically, along with a pre-funded wallet so you can start using paid services right away.”
   • [claimed-docs] “"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens ar…”

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

   Skyfire✓fullclaimed7/10

   Docs describe a Buyer Agent wallet auto-created and pre-funded on signup, scoped per-agent via API keys that the user controls, with committed-amount enforcement against the wallet balance and an introspect-token API to check remaining balance. This covers user-provisioned/funded/controlled wallet plus balance visibility, but missing for 10: dashboard UI screenshots showing balance, explicit mechanism for manually topping up/funding beyond initial pre-fund, and independent/hands-on corroboration.

   • [claimed-docs] “On signup, your Buyer Agent is created automatically, along with a pre-funded wallet so you can start using paid services right away.”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”
   • [claimed-docs] “Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”
   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”

   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

   Skyfire—none0/10

   Skyfire's docs describe identity verification (KYA), token issuance/expiry, and payment settlement, but nothing in the evidence pack addresses user-controlled data retention policies or deletion of stored identity/verification/payment data. Given Skyfire handles real-world identity data via KYA, this is a fair privacy axis to expect, but no retention or deletion controls are documented.

   ⚑ 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

   Skyfire—none0/10

   Skyfire claims tokens conform to an 'open KYAPay protocol' hosted at KYAPay.org, but every operational piece — charging, wallets, settlement, MCP server, verification — runs exclusively through Skyfire's own APIs and infrastructure per the evidence pack. There is no mention of any independent vendor, competitor, or third party implementing the protocol or running their own compatible service/settlement layer.

   • [claimed-docs] “"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens ar…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflo…”

   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

   Skyfire~partialprobed4/10

   Skyfire claims tokens conform to "the open KYAPay protocol, an industry specification for identity-linked payment credentials" (referencing KYAPay.org), suggesting a published spec exists, but the evidence pack itself notes that charging, wallets, and settlement all run through Skyfire's own gated APIs, and every other capability (creating tokens, MCP server, seller services) requires an API key and account signup — no evidence of a version number, a standalone spec document, or an implementation path that doesn't require signing up with Skyfire. missing for 10: a link to a versioned KYAPay spec document, confirmation it can be implemented independently of Skyfire's account/API-key system, and independent corroboration of the spec's openness.

   • [claimed-docs] “"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens ar…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.x…”
   • [probe] “PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api…”
   • [claimed-docs] “Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single…”

   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

   Skyfire—none0/10

   The evidence pack documents token creation, charging, introspection, settlement timing, and revocation limits, but nowhere describes a dispute or chargeback mechanism — no evidence-submission endpoint, dispute status API, or outcome reporting is mentioned. Payment guarantees are described as ceiling-bound token commitments rather than a dispute-resolution workflow, so this applicable axis has no supporting evidence.

   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “Revocation is bounded by design: deactivating an account does not void already-issued pay/kya-pay tokens — "New token creation stops at deac…”

   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

   Skyfire—none0/10

   The evidence pack covers token creation, charging, settlement, and revocation bounds in detail, but nowhere documents a refund API, refund initiation flow, or refund status/tracking endpoint. Since Skyfire is a payments platform, refunds are a plausible feature, but no evidence of programmatic refund support exists — missing for 10: any refund/dispute API reference, refund status tracking, or documented refund workflow.

   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “Revocation is bounded by design: deactivating an account does not void already-issued pay/kya-pay tokens — "New token creation stops at deac…”
   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”

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

   Skyfire✓fullclaimed8/10

   Skyfire's KYA/KYA-Pay tokens give merchants a verifiable, signed identity credential (JWT) per agent, with optional real-world identity attachment and hard gating ('token creation fails and the transaction does not proceed' if verification level is insufficient), plus per-agent scoped API keys and a documented merchant/bot-manager flow to identify and admit agent traffic instead of blocking it. This directly addresses distinguishing trusted, verified agent traffic from anonymous bots via a signature-based, tiered identity system. Missing for 10: independent/third-party corroboration of real-world merchant adoption or trust-tier enforcement outside Skyfire's own docs, and no public API schema (openapi probes 404) to verify signature/verification details externally.

   • [claimed-docs] “Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agent…”
   • [claimed-docs] “"Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agen…”
   • [claimed-docs] “"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens ar…”
   • [claimed-docs] “Cardholder consent bounds card spending: "The agent/agent platform can never spend more than the cardholder approved." — an authorization co…”
   • [claimed-docs] “The site, or the bot manager in front of it, can then identify the agent/agent platform and allow it through rather than block it.”
   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”

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

   Skyfire~partialclaimed5/10

   Skyfire's pay/kya-pay tokens are signed JWT 'mandates' that commit a specific spending ceiling at creation time, and that ceiling is a hard cap enforced by the buyer's wallet balance and cardholder consent ('agent can never spend more than the cardholder approved'), giving a documented, auditable authorization trail per token. However, the evidence shows token creation is an agent/API-driven action, not a human-facing confirmation prompt or explicit per-purchase human sign-off — there's no documented UI step where a person approves each individual transaction before it fires, only the pre-set balance/identity gating. Missing for 10: an explicit human-in-the-loop confirmation/approval UI or workflow per purchase, and documentation of configurable spend policies beyond wallet pre-funding and KYA identity requirements.

   • [claimed-docs] “"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens ar…”
   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Cardholder consent bounds card spending: "The agent/agent platform can never spend more than the cardholder approved." — an authorization co…”
   • [claimed-docs] “"Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agen…”
   • [claimed-docs] “On signup, your Buyer Agent is created automatically, along with a pre-funded wallet so you can start using paid services right away.”

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

   Skyfire~partialclaimed6/10

   Skyfire's docs explicitly allocate payment risk: sellers are guaranteed payment up to a token's committed amount and 'do not carry buyer non-payment risk' (skyfire-supp-4), overcharges are rejected, and even after account deactivation in-flight tokens are still honored so sellers get paid (skyfire-supp-6). Card-based flows also state the agent can never exceed cardholder-approved amounts and purchases are never anonymous to the merchant (skyfire-supp-7). However, there is no dedicated chargeback/dispute-resolution policy, no explicit statement of who bears fraud losses when credentials are stolen or a buyer disputes via their bank, and no formal merchant-facing liability/ToS document. Missing for 10: explicit chargeback/dispute process, stolen-credential fraud liability terms, formal merchant liability agreement or ToS reference.

   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Revocation is bounded by design: deactivating an account does not void already-issued pay/kya-pay tokens — "New token creation stops at deac…”
   • [claimed-docs] “Cardholder consent bounds card spending: "The agent/agent platform can never spend more than the cardholder approved." — an authorization co…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”

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

   Skyfire~partialclaimed4/10

   Skyfire supports per-agent scoping and spend caps: keys are scoped to a single agent, and pay tokens carry a committed amount ceiling that bounds spend and rejects overcharges. However, the docs explicitly state there is no per-token revocation API and that deactivating an account does not void already-issued tokens — in-flight tokens remain chargeable until expiry plus a 24-hour grace window — directly contradicting 'instant' revocation of payment authority. missing for 10: a documented instant per-agent/per-token revocation mechanism, independent or hands-on confirmation of revocation behavior, and granular usage-limit controls beyond token amount/expiry.

   • [claimed-docs] “Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation re…”
   • [claimed-docs] “Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued…”
   • [claimed-docs] “Revocation is bounded by design: deactivating an account does not void already-issued pay/kya-pay tokens — "New token creation stops at deac…”
   • [claimed-docs] “API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”

   proof ↗⚑ flag