x402 (Coinbase protocol)
x402.org · Agent-Commerce Infrastructure modeIntegrated
Overall = mean of Interrupt Score 86 and Machine-Readability 92 → 89 / 100. The badge is set by the Interrupt Score alone — how scoring works.
Confidence: Verified (Probed) (0.95) — A live Tier-2 agent session completed the flow end to end.
The operator (or its agent's wallet) retains custody directly — no intermediary ever holds funds.
Machine-Readability Score
Four check groups, equal weight: machine interfaces (OpenAPI, MCP server, llms.txt), browsing efficiency, element discoverability, and discovery/agent access (retrieval-bot robots.txt access, sitemap, schema.org). Each check is tagged with how strong the real-world evidence is that it changes agent behavior — proven, plausible, or emerging — grades are honesty labels, they never weight the score. A separate signal about ease of integration — it never enters the Interrupt Score or badge above.
Findings
How scoring works →Interrupt tier: Low-Interrupt — derived from 2 findings; interrupt score 86 / 100. It alone drives the badge above; the headline Overall score blends it 50/50 with Machine-Readability.
Every tool starts at 100. Each interrupt found subtracts a penalty of base weight × timing × hardness × evidence — the multiplier values below come from the same rubric tables the score is computed with, so the arithmetic in this matrix reproduces the number exactly.
| Interrupt found | Base weight | × Timing | × Hardness | × Evidence | = Penalty |
|---|---|---|---|---|---|
| Starting score | 100 | ||||
| Identity / KYC verificationAccount verification (KYC / OTP)Acquiring USDC via an on-ramp requires KYC (documents, wait period). | 6 | ×1one-time setup | ×2.5hard | ×0.8Tier 1 (unauth probe) | −12 |
| Crypto wallet / key-custody setupPayment setupPrivate key generation/custody setup for the wallet. | 3 | ×1one-time setup | ×1soft | ×0.8Tier 1 (unauth probe) | −2.4 |
| Total penalty | −14.4 | ||||
| Interrupt Score = 100 − 14.4 = 85.6 → rounds to 86 | 86 | ||||
Checked — nothing found
A check only turns green when a probe tier capable of detecting that interrupt actually ran and found nothing. Not tested ≠ clean.
- CAPTCHA / bot-challengeNone found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt)
- Email OTP verificationNone found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt)
- SMS / phone OTP verificationNone found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt)
- Mandatory phone verification callNone found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt)
- Mailed physical code (postal)None found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt)
- “Contact sales” wall (no self-serve path)None found — checked at Tier 1 (unauth probe)
- Manual approval queueNone found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt)
- Mandatory redirect to vendor’s own siteNone found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt)
- SSO-only signup, no API-key issuanceNone found — checked at Tier 1 (unauth probe)
- Rate-limit-triggered manual reviewNone found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt)
- One-time account / payment-method provisioningNone found — checked at Tier 1 (unauth probe)
Not yet tested
- ToS clause banning automated/bot accessNo probe tier that can detect this has run yet — unknown, not clean
Agent-ready alternatives
Other Agent-Commerce Infrastructure tools in the same mode (integrated), ranked by Overall LLM-Friendliness — comparable to this listing because they share its usage mode.