x402 conformance status: agent402.tools
agent402.tools reads WEAK 21/23 on the scheduled run of 2026-10-27T02:33:32.169Z (checker inventory 1.9.0). Checked, never certified: this page states below what the checks do not cover. It is rebuilt after every scheduled run; if no run has happened for 26 hours (the daily run plus two hours of grace; 48 hours until 2026-10-10, which let one whole missed run pass unseen) the image reads STALE rather than repeating an old word.
Operate this endpoint? The fix for every adverse row above is on the board's detail column and in the check's own detail text, free. If you would rather fix it before the next run reads it, there is a private operator audit, $99: the same battery run privately, a fix list in the order the money leaks, re-tests until it passes for 30 days, and nothing published without your word. The fee buys the work, never the verdict; a paid audit never changes this badge.
POST https://agent402.tools/api/search — WEAK 21/23 checks
| verdict | check | detail |
|---|---|---|
| PASS | client_fingerprint_parity | all 5 probed User-Agents get the same 402 as the baseline (a User-Agent comparison from one network seat, not a client fingerprint) |
| PASS | discovery_docs_parity | /.well-known/x402, /openapi.json, /llms.txt answer 200 to the default client and to Python-urllib/3.12 and libwww-perl/6.68 alike |
| PASS | body_envelope_complete | body carries x402Version + resource beside `accepts` |
| PASS | accepts0_payable | accepts[0] is exact/eip155:8453 — payable by a client that takes the first option |
| WEAK | accepts_all_executable | 2/16 advertised option(s) cannot be executed by a standard x402 client (upto/eip155:8453: scheme "upto" is not an x402 scheme; exact/algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=: network "algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=" is not a CAIP-2 id (a v2 body owes CAIP-2)) — accepts[] is the machine-executable list, not a menu of routes the operator will honour; move non-x402 routes to another key |
| PASS | header_body_agree | header and body advertise the same payment options |
| WEAK | plaintext_envelope_refused | plaintext redirects 301 to https://agent402.tools/api/search, but 301 lets a client drop the body and re-issue a paying POST as GET — 308 preserves the method |
| PASS | no_payment | 402 Payment required |
| PASS | header_not_base64_json | 402 payment_required |
| PASS | garbage_payload | 402 payment_required |
| PASS | bad_signature | 402 payment_required |
| PASS | wrong_signer | 402 payment_required |
| PASS | wrong_amount_underpay | 402 payment_required |
| PASS | wrong_destination | 402 payment_required |
| PASS | expired_authorization | 402 payment_required |
| PASS | not_yet_valid | 402 payment_required |
| PASS | wrong_chain_domain | 402 payment_required |
| PASS | payTo_not_zero_address | payTo 0xaBF4FAbd… |
| PASS | asset_contract_exists | asset has contract code |
| PASS | asset_supports_eip3009 | authorizationState() answers — EIP-3009 present |
| PASS | payTo_not_blacklisted | isBlacklisted(payTo) is false |
| PASS | asset_is_canonical | asset is canonical USDC on base |
| PASS | payTo_account_type | payTo is a contract — it receives ERC-20 fine, but whether funds are sweepable depends on its code (not verifiable read-only) |
Verdict changes on record
What this does not cover
The checker tests spec-normative x402 requirements on the rejection path (the 402, its payment terms, the receiving rail's on-chain liveness, client-fingerprint parity, plaintext exposure) and performs no live paid settlement. A clean verdict is necessary, not sufficient: a door that accepts a payment and then fails to deliver is outside its reach. Nothing here says anything about the endpoint's security, its operator, or the quality of what it sells. Method, scope and selection rules: monitor page; the check inventory is published and versioned.
Embed this badge
Embedding is the operator's choice; the image is free, never for sale, and rebuilt daily. Serve it from here (do not copy the file) so it can go STALE honestly. The image is served with a 30-minute cache at the origin and at the CDN edge (edge rule added 2026-09-11), so a badge can lag the board by 30 minutes and no more. Markdown:
[](https://coppice-ai.com/badge/agent402.tools.html)HTML:
<a href="https://coppice-ai.com/badge/agent402.tools.html"><img src="https://coppice-ai.com/badge/agent402.tools.svg" alt="x402 conformance status for agent402.tools" height="20"></a>