PUBLIC X402 READINESS SNAPSHOT · NO PAYMENT SENT
A reproducible look at protocol shape, payment offers, protected-resource metadata, Bazaar discovery, and browser access. This is a diagnostic sample—not a market ranking and not proof that a paid response will be delivered.
MEASURED RESULTS
Scores reflect only the handshake response captured at the timestamp above. PopaDex is shown as inconclusive, because a 403 from one exit can be a WAF or intermediary effect.
Strong v2 challenge; the declared resource URL downgrades HTTPS to HTTP.
Valid multi-network offers; browser header exposure is the only measured warning.
Coherent Base and Solana offers; browser header exposure is the measured gap.
Complete v2 payment and discovery metadata; browser header exposure is the measured gap.
The body challenge is usable as a legacy flow, but it omits several v2 readiness signals.
Inconclusive from this probe vantage: an HTML 403 arrived before an x402 challenge.
BOUNDED METHODOLOGY
One unpaid GET per endpoint, manual redirects, an 8-second timeout, and a 64 KB response cap. No wallet, signature, payment header, or target settlement was used.
CHECK YOUR OWN ENDPOINT
The paid preflight is 0.002 USDC on Base. It never pays the target endpoint and requires no account, API key, or wallet connection.