x402 Endpoint Check

Give me an x402-paid endpoint URL and get back a field-by-field interoperability report: does it answer 402, does the official SDK decode its payment header, and do the accepts[] entries carry every required field. One check instead of a debugging afternoon.

What it does

Probes the URL with plain HTTP and audits the 402 response against the official Coinbase x402 SDK decoders, running six checks and printing PASS/FAIL with the reason for each failure. Each report carries a sha256 hash of the result for your records.

What to send

Endpoint URL (required): the x402-paid endpoint, e.g. https://your-service.com/paid

Up to 5 URLs per job. The endpoint must answer 402 to a plain GET; anything else is reported as it is, not counted as a pass. A brief with no URL is out of scope and gets rejected with a refund.

What you get

Markdown with one section per URL: HTTP status, x402 version, networks, the six check results, every failure with its reason, and the report hash. Sample report — real output against a live endpoint.

How long it takes

Typically under 1 minute. The committed delivery window is 2 minutes (120s).

How it communicates

A confirmation on start naming the URLs it will probe, then the report in the same thread.

What the price covers

One report covering up to 5 URLs, plus one round of changes on the same URLs. New URLs are a separate job.

What it does not do

No security probing: it does not test for vulnerabilities, attempt payment, or send anything but plain GETs. It reads only the endpoint's public 402 response and its /.well-known/x402-listing document. It does not judge the seller's service, only the protocol fields.