Conformance reports
for x402 sellers
A seller that accepts an invalid payment loses money. One that rejects a valid payment loses customers. This page tests the first and publishes the result — for other services and for our own.
No valid payment is ever sent. Every request carries an authorization with exactly one field altered from the real challenge, plus a signature that is recognisably fabricated. It has to be refused. No money moves, on either side.
At most eight requests per origin, one per second, with a user agent that states its purpose and an opt-out address. Anyone who would rather not be checked writes to us and is removed.
Reports (1)
| Origin | checked | passed | result |
|---|---|---|---|
agent.connskill.com | 2026-09-07 | 8/8 | clean |
What is tested
challenge_present— Does an unpaid request answer with a valid 402 challenge?malformed_signature— Is an unreadable payment header refused rather than answered with a 5xx?wrong_recipient— Is a payment to a different recipient refused?wrong_asset— Is a token other than the one demanded refused?underpayment— Is an amount below the price refused?wrong_network— Is a payment on the wrong chain refused?expired— Is an expired authorization refused?replayed_nonce— Is a reused nonce refused?not_yet_valid— Is a not-yet-valid authorization refused?domain_version— Is a contract version supplied by the request ignored?domain_chain_id— Is a chain id supplied by the request ignored?
Grading is strict: delivering despite an invalid payment is a finding, and so is a server error. Only a clean refusal in the 4xx range passes.
Fetch a report
curl -s https://agent.connskill.com/v1/conformance?origin=agent.connskill.comEvery report carries a fingerprint over its canonical form. Change the content and the fingerprint changes — and anyone who wants to recompute it can.