x402 Doctor

Reviewed Jan 1, 2000.

• tools: 3 tools scanned
• metadata: scanned

No findings.

Tools (3)

• probe_x402_endpoint

  Probe an x402 seller endpoint and report what it observes about it. Performs the handshake a paying client would: GET with no X-PAYMENT header, then checks the 402 challenge against 16 rules. Every finding says whether the rule comes from the x402 spec or from an observed facilitator rejection. Reports status "healthy" (nothing to report), "advisories" (only warn/info findings — the endpoint works), "defects_found" (at least one error-severity finding), "not_x402" or "unreachable".

• explain_defect

  Full explanation of one rule by id — what it checks, why it matters, how to fix it, and where the rule came from. Use when you want the reasoning without re-probing.

• list_checks

  The whole rule table. Knowing what was NOT checked is part of knowing what a clean result means.