x402 Doctor — agent-tools.cloud

Why is my x402 endpoint broken? Checks the whole payment flow an agent would hit (402 challenge, networks, payTo and amount, Solana settlement, Bazaar/OpenAPI discovery, MCP) and returns a fix per problem. Free quick check; full diagnosis $0.01.

Paid verification

How it works

No sponsored paid call yet.

Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.

Quality grade

How grading works

A 70.8 / 100

Availability 20.0 / 20

Endpoint responded (HTTP 402)

Payability 15.0 / 15

✓ Answers a real HTTP 402 challenge
✓ Publishes a /.well-known/x402 descriptor
✓ Payment address on record
✓ Settlement network declared
✓ Price declared

Demand 12.6 / 35

41 distinct payers, 278 USDC transfers in the last 30 days; the wallet is shared by 5 listings, so each is credited 1/5

Performance 10.0 / 10

Last probe answered in 181 ms (full marks at 200 ms or less)

Readiness 13.2 / 15

Agent readiness 88/100

Owner verified 0.0 / 5

Nobody has claimed this listing yet

Endpoint last checked 19 h ago. On-chain activity last read 3 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here A, 70.8/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements	10/10	Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge	25/25	Paid endpoint answers with an HTTP 402 challenge (181 ms).
x402 version	n/a	x402 version not observed yet.
Signed descriptor	n/a	No x402 standard defines a signed descriptor.
Uptime (30 days)	15/15	32/32 probes succeeded over 30 days (100%).
Resource declaration	10/10	Declares 6 paid resource(s).
Verified identity	5/10	Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags	1/5	not seen in a source for over 30 days; declares x402.
Security declaration	n/a	Payment is the access control for an x402 resource.

Applicable criteria total 75 points, scaled to 100.

Responsiveness: Responsive (181 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest, catalog_listing. Qualifies the payment claim; adds no points.

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 80% of peers; This listing 88 · peer median 78
Latency: Faster than 57% of peers; This listing 181 ms · peer median 205 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags −4 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days; declares x402.

How many agent tools actually work · All statistics

Paid endpoints

6 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

GET https://x402-doctor.fizzl.eu/api/v1/diagnose

Why is an x402 endpoint broken? Every check (402 challenge, payment options, discovery, settlement) with pass/warn/fail and a fix hint.

GET https://x402-doctor.fizzl.eu/api/v1/preflight

Is this x402 endpoint safe to pay? go / caution / no_go with the recommended payment option and the reasons. Never pays the endpoint.

GET https://x402-doctor.fizzl.eu/api/v1/preflight/batch

The pre-payment check for up to 10 x402 endpoints in one call: go / caution / no_go per endpoint.

GET https://x402-doctor.fizzl.eu/api/v1/preflight/deep

Before an expensive call: the pre-payment check plus the full diagnosis, the daily history and the seller's other endpoints.

GET https://x402-doctor.fizzl.eu/api/v1/fix

Diagnoses an x402 endpoint, then returns per problem the concrete code change for your stack, filled in with your own values.

GET https://x402-doctor.fizzl.eu/api/v1/delivery-check

Did the seller deliver after payment? Doctor buys the endpoint once (if it costs at most $0.10) and reports status, response and settlement.

How to call

cURL · x402-fetch / x402-axios will auto-handle 402

curl -sS -i -X GET https://x402-doctor.fizzl.eu/api/v1/diagnose  # expect HTTP 402 Payment Required (about 0.001 USDC/call)

/.well-known/x402.json

https://x402-doctor.fizzl.eu/.well-known/x402

Listed in

Directories this entry was found in.

submission since 2026-09-28 mcp since 2026-10-08 x402 since 2026-10-08 x402scan since 2026-10-13 a2a since 2026-11-04