Rank #5 of 7 in Agentic Commerce

Coinbase x402
Coinbase, Inc. (protocol stewarded by the x402 Foundation, a Linux Foundation project) · commercial
Access
Install
npm install x402-fetchTry itExperimental
See what an agent can do with Coinbase x402 before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources # the x402 Bazaar, keyless by designrecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agent checkout — stories about agent checkout in this arenaAgent checkoutevidence →
Stories about agent checkout in this arena
Agent discovery — stories about agent discovery in this arenaAgent discoveryevidence →
Stories about agent discovery in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Fees economics — stories about fees economics in this arenaFees economicsevidence →
Stories about fees economics in this arena
Merchant enablement — stories about merchant enablement in this arenaMerchant enablementevidence →
Stories about merchant enablement in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Order lifecycle — stories about order lifecycle in this arenaOrder lifecycleevidence →
Stories about order lifecycle in this arena
n/a
Payment credentials — stories about payment credentials in this arenaPayment credentialsevidence →
Stories about payment credentials in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Protocol openness — stories about protocol openness in this arenaProtocol opennessevidence →
Stories about protocol openness in this arena
Refunds disputes — stories about refunds disputes in this arenaRefunds disputesevidence →
Stories about refunds disputes in this arena
Trust safety — stories about trust safety in this arenaTrust safetyevidence →
Stories about trust safety in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 13 free · 0 paid · 0 enterprise · 16 not stated in evidence
Follow the green: where the map greys out is where Coinbase x402 stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent checkout — stories about agent checkout in this arenaAgent checkout
Stories about agent checkout in this arena
My agent can create and update a cart or order draft through a documented protocol call
—0/10
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
~7/10
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)
—0/10
Build against a versioned commerce protocol with a published schema and conformance or validation tooling
~5/10
Agent discovery — stories about agent discovery in this arenaAgent discovery
Stories about agent discovery in this arena
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required
✓9/10
Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service
~7/10
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell
~6/10
My agent can discover payable services and APIs through a published directory or discovery index
✓9/10
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~6/10
unlocks → Machine-readable spec · Versioning policy · Official CLI · My agent can create and update a cart or order draft through a documented protocol call · Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)
Subscribe to events via webhooks
n/an/a
Build against official SDKs
~6/10
Issue scoped/least-privilege API credentials for an agent
~4/10
Connect an agent via an official MCP server
~6/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~3/10
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
n/an/a
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Fees economics — stories about fees economics in this arenaFees economics
Stories about fees economics in this arena
Merchant enablement — stories about merchant enablement in this arenaMerchant enablement
Stories about merchant enablement in this arena
Orders are attributed to the originating agent and I can report on or filter transactions by agent
—–
I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint
✓8/10
Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout
—0/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle
Stories about order lifecycle in this arena
Payment credentials — stories about payment credentials in this arenaPayment credentials
Stories about payment credentials in this arena
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
~5/10
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
✓8/10
Settle agent-initiated payments in stablecoins over documented rails
✓9/10
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility
~5/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Protocol openness — stories about protocol openness in this arenaProtocol openness
Stories about protocol openness in this arena
Refunds disputes — stories about refunds disputes in this arenaRefunds disputes
Stories about refunds disputes in this arena
Trust safety — stories about trust safety in this arenaTrust safety
Stories about trust safety in this arena
Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots
—0/10
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
—0/10
The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk
—0/10
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
~3/10
Sorted by importance (agentic first) (high → low) · 56/56 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partialfree | 6/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partialfree | 6/10 | Tprobed⚿ | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | fullfree | 8/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partialfree | 6/10 | Tprobed⚿ | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 3/10 | Cclaimed | |
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required C Agent search | ai-native user | Agent discovery — stories about agent discovery in this arenaAgent discovery | 3 | fullfree | 9/10 | Tprobed | |
I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint C Onboarding to agents | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 3 | fullfree | 8/10 | Tprobed | |
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI C Machine payments | developer | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | full | 8/10 | Tprobed⚿ | |
The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything C Spec publication | developer | Protocol openness — stories about protocol openness in this arenaProtocol openness | 3 | fullfree | 8/10 | Tprobed⚿ | |
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order C Checkout | ai-native user | Agent checkout — stories about agent checkout in this arenaAgent checkout | 3 | partial | 7/10 | Tprobed⚿ | |
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell C Merchant feeds | merchant | Agent discovery — stories about agent discovery in this arenaAgent discovery | 3 | partialfree | 6/10 | Tprobed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 6/10 | Tprobed⚿ | |
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number C Delegated credentials | ai-native user | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | partial | 5/10 | Cclaimed | |
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility C Wallets | ai-native user | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | partial | 5/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 4/10 | Cclaimed | |
Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots C Agent identity | merchant | Trust safety — stories about trust safety in this arenaTrust safety | 3 | none | 0/10 | ||
My agent can create and update a cart or order draft through a documented protocol call C Cart | ai-native user | Agent checkout — stories about agent checkout in this arenaAgent checkout | 3 | none | 0/10 | ||
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves C Human oversight | ai-native user | Trust safety — stories about trust safety in this arenaTrust safety | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
My agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically C Order events | developer | Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle | 3 | n/a | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
My agent can discover payable services and APIs through a published directory or discovery index C Service discovery | ai-native user | Agent discovery — stories about agent discovery in this arenaAgent discovery | 2 | fullfree | 9/10 | Tprobed | |
Settle agent-initiated payments in stablecoins over documented rails C Settlement rails | developer | Payment credentials — stories about payment credentials in this arenaPayment credentials | 2 | full | 9/10 | Tprobed⚿ | |
At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration C Ecosystem adoption | developer | Protocol openness — stories about protocol openness in this arenaProtocol openness | 2 | full | 8/10 | Xcommunity | |
The fees for agent-originated transactions are published — I can price agentic channels without asking sales C Fees transparency | merchant | Fees economics — stories about fees economics in this arenaFees economics | 2 | fullfree | 8/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 7/10 | Cclaimed | |
Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service C Machine readable offers | developer | Agent discovery — stories about agent discovery in this arenaAgent discovery | 2 | partialfree | 7/10 | Tprobed | |
Build against a versioned commerce protocol with a published schema and conformance or validation tooling C Protocol conformance | developer | Agent checkout — stories about agent checkout in this arenaAgent checkout | 2 | partialfree | 5/10 | Tprobed⚿ | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed⚿ | |
Refunds on agent-placed orders can be initiated and tracked programmatically C Refunds | developer | Refunds disputes — stories about refunds disputes in this arenaRefunds disputes | 2 | partial | 3/10 | Cclaimed | |
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly G Spend controls | ai-native user | Trust safety — stories about trust safety in this arenaTrust safety | 2 | partial | 3/10 | Xcommunity | |
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers) C Embedded surfaces | merchant | Agent checkout — stories about agent checkout in this arenaAgent checkout | 2 | none | 0/10 | ||
Disputes and chargebacks on agent transactions can be handled via API — evidence submission, status, outcomes C Disputes | developer | Refunds disputes — stories about refunds disputes in this arenaRefunds disputes | 2 | none | 0/10 | ||
Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout C Traffic controls | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 2 | none | 0/10 | ||
The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk C Liability | merchant | Trust safety — stories about trust safety in this arenaTrust safety | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
My agent can query the status and tracking of an order it placed, after the purchase C Post purchase status | ai-native user | Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle | 2 | n/a | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Orders are attributed to the originating agent and I can report on or filter transactions by agent C Attribution analytics | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel C Payouts | merchant | Fees economics — stories about fees economics in this arenaFees economics | 1 | partialfree | 5/10 | Xcommunity | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 34 stories with headroom
What would move Coinbase x402’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agent checkout — stories about agent checkout in this arenaMy agent can create and update a cart or order draft through a documented protocol call
nonemoves PA Scoreimpact 30
Missing: any documented cart/order object, create/update API or protocol verbs, and evidence of persisted order state across calls.
Trust safety — stories about trust safety in this arenaAgents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots
nonemoves PA Scoreimpact 30
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.
Trust safety — stories about trust safety in this arenaSensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
nonemoves PA Scoreimpact 30
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.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
Missing: any mention of an x402 CLI, its commands, or install instructions.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
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.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
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.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
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.
Trust safety — stories about trust safety in this arenaThe fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk
nonemoves PA Scoreimpact 20
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.
Showing the top 8 of 34 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 29 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
X402 docs28 stories
- My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
- Build against a versioned commerce protocol with a published schema and conformance or validation tooling
- My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required
- Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service
- Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell
- My agent can discover payable services and APIs through a published directory or discovery index
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- The fees for agent-originated transactions are published — I can price agentic channels without asking sales
- Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel
- I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint
- Read the product's source under an open license
- Self-host the core product
- Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
- Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
- Settle agent-initiated payments in stablecoins over documented rails
- Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility
- At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration
- The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything
- Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
Hacker News11 stories
- My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
- My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required
- Build against official SDKs
- Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel
- Read the product's source under an open license
- Self-host the core product
- Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
- Settle agent-initiated payments in stablecoins over documented rails
- At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration
- The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything
- Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
X402 batch settlement docs7 stories
- Issue scoped/least-privilege API credentials for an agent
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
- Refunds on agent-placed orders can be initiated and tracked programmatically
- Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
x402.org5 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Define rules that trigger actions automatically on events
- I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint
- Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
Leadership docs4 stories
- Build against a versioned commerce protocol with a published schema and conformance or validation tooling
- Read the product's source under an open license
- At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration
- The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything
OpenAPI spec2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources # the x402 Bazaar, keyless by designreproduced$ curl -s https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources # the x402 Bazaar, [redacted]less by design
{"items":[{"accepts":[{"amount":"3000","asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","currency":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","extra":{"credentialTypes":["authorization"],"name":"USD Coin","version":"2"},"maxAmountRequired":"3000","maxTimeoutSeconds":3600,"network":"eip155:8453
$curl -si https://api.cdp.coinbase.com/platform/v2/x402/supported # the hosted facilitator, auth-gatedreproduced$ curl -si https://api.cdp.coinbase.com/platform/v2/x402/supported # the hosted facilitator, auth-gated HTTP/2 401 Unauthorized
$npm view x402 version # the protocol SDK, on the public registryreproduced$ npm view x402 version # the protocol SDK, on the public registry x402 version: 1.2.0
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
9 of 13 testable claims verified · 0 contradicted → integrity 69/100
20 distinct capability claims found in Coinbase x402’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
9
Verified
4
Unverified
0
Contradicted
16
Undersold
Verified (13)
“Servers can require payment per request by returning HTTP 402 until the client attaches proof of payment”
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UIfullproof ↗
“A hosted CDP Facilitator validates signed payments, screens them, settles onchain, and reports results back to the seller's server”
Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channelpartialproof ↗
“Building with the CDP SDK's x402 blocks automatically lists the service in x402 Bazaar with no separate registration step”
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sellpartialproof ↗
“Bazaar discovery APIs and SDK functions are public and usable without a CDP API key”
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership requiredfullproof ↗
“Payments can be made in any ERC-20 token on supported EVM networks or SPL tokens on Solana”
Settle agent-initiated payments in stablecoins over documented railsfullproof ↗
“Merchant checkouts built on Payment Acceptance can be x402-enabled so agents authorize payment sessions directly”
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed orderpartialproof ↗
“MCP-compatible agents can discover x402-payable services through tool calls”
My agent can discover payable services and APIs through a published directory or discovery indexfullproof ↗
“Batch settlement lets agents transact at very low latency and fractions of a cent per interaction”
Settle agent-initiated payments in stablecoins over documented railsfullproof ↗
“Bazaar lets buyers search payable services by intent with network, asset, scheme, and price filters, ranked results”
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership requiredfullproof ↗
“Bazaar lets buyers search payable services by intent with network, asset, scheme, and price filters, ranked results”
My agent can discover payable services and APIs through a published directory or discovery indexfullproof ↗
“Listed endpoints reach agents via CDP APIs, Bazaar MCP server, and Bedrock AgentCore; delisted after 30 days with no settlement”
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sellpartialproof ↗
“x402 protocol governance moved to vendor-neutral Linux Foundation stewardship with 40 launch member organizations”
At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integrationfullproof ↗
“A named Governing Board and Technical Steering Committee oversee business and technical direction of the published x402 spec”
The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anythingfullproof ↗
Unverified (5)
“Buyers or agents pay from a Coinbase-provided agentic wallet or another compatible signer holding USDC”
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibilitypartialproof ↗
“Facilitator is free for the first 1,000 onchain transactions per month, then $0.001 each, with payment verification always free”
The fees for agent-originated transactions are published — I can price agentic channels without asking salesfullproof ↗
“Agentic accounts let an AI agent hold and spend USDC directly through a Coinbase account or wallet to pay for services”
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibilitypartialproof ↗
“MCP-compatible agents can discover x402-payable services through tool calls”
“Batch settlement uses cryptographic vouchers per interaction with escrowed funds and defined buyer refund/withdrawal rights”
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card numberpartialproof ↗
Undersold (16)
Build against a versioned commerce protocol with a published schema and conformance or validation toolingpartialproof ↗
Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or servicepartialproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIpartialproof ↗
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpointfullproof ↗
Read the product's source under an open licensepartialproof ↗
Refunds on agent-placed orders can be initiated and tracked programmaticallypartialproof ↗
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantlypartialproof ↗
Claims outside our story set (4)
Real capability claims found in Coinbase x402’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Sellers can receive payments at any wallet they control, including CDP custodial, Coinbase Business/Prime, or self-custody wallets”
source ↗“Built-in OFAC and Know-Your-Transaction screening automatically declines payments from sanctioned or high-risk addresses”
source ↗“Sellers can price with fixed, usage-based (up-to), or batch-settlement payment schemes”
source ↗“An AWS Payment Manager plus CDP connector gives Bedrock AgentCore agents access to x402-payable services”
source ↗
Business model
The protocol is open and free to implement; Coinbase's hosted CDP facilitator includes 1,000 onchain settlements per month free, then $0.001 per onchain transaction — payment verification is always free.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents