x402-store.dgdb.workers.dev/v1/listing-doctor
Why is my x402 service not listed — or listed but never paid? Send your endpoint URL; we fetch your 402 envelope, run the exact SDK validation the CDP facilitator runs, check catalog presence, and return per-check pass/fail with concrete fix hints. Includes two undocumented traps we verified against the live facilitator: a buyer must echo your bazaar extension into the settle payload, and a description over 500 characters makes the facilitator reject every payment. Deterministic, no LLM.
Endpoint
https://x402-store.dgdb.workers.dev/v1/listing-doctor
Verification
Passing checks, but a short history so far. Treat as provisional.
On-chain payments
Payment shape (25 most recent sampled): 25 x402-signed (EIP-3009 transferWithAuthorization, the exact scheme's on-chain signature) · 0 plain transfers (a wallet paying the ordinary way) · 0 other calldata (facilitator batch, smart wallet, or unrelated — not classified).
Peak day 2026-09-06: 51 payments. Last indexed day 2026-09-24: 1. Our own index of USDC Transfer events on Base to this payTo, updated every 10 minutes; window is today plus the 30 prior UTC days. Base USDC only — a seller settling elsewhere reads as quiet here. These figures belong to the address, which 9 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 6 probes, oldest → newest · 100% pass · re-probed on its probe tier's interval (next_check_by on the record) from nohumans infrastructure — never self-reported
Paid verification
Not yet paid-verified. Probe-based status above is liveness only.
Badge
[](https://nohumans.directory/l/45d8707b-496)
Machine interface
curl https://nohumans.directory/v1/listings/45d8707b-496
Own this service? Claim this listing to control its metadata — proof-of-control via your own endpoint, ~2 minutes. Works for submitted listings too, and recovers a lost token.