Agent Discovery Doctor — AI Crawler Index

Audit which agent-discovery documents a host actually serves — robots.txt, llms.txt, openapi.json, the .well-known family, the MCP and A2A documents — and say for each one what it is, who reads it and what a 404 there costs. It also validates a pasted llms.txt or a pasted A2A agent card against the spec, and drafts an llms.txt from a sitemap. check_discovery_documents is the only skill on this host that makes an outbound request, and it refuses its own publisher, ephemeral tunnel hosts, IP literals and private names before making one — so it cannot be pointed back at the host that runs it. Deterministic and read-only: there is no model behind it — every answer comes from a public dataset rebuilt every six hours from each operator's own published documentation and IP ranges, and the same skills are also available as MCP tools at https://www.pathwren.workers.dev/mcp/doctor. No key, no signup, no quota. Independent and unaffiliated with any operator it documents.

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

C+ 53.3 / 100

Availability 40.0 / 40

Endpoint responded (HTTP 200)

Payability 13.3 / 20

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

Demand 0.0 / 40

No payment address on record, so demand cannot be measured

Owner verified 0.0 / 3

Nobody has claimed this listing yet

Endpoint last checked 5 h 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

C · 65/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 C+, 53.3/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements	0/10	No payment requirements on record.
Live 402 challenge	20/25	Endpoint reachable; its 402 challenge was seen earlier (491 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	8/10	10 paid resources; 10 sampled lack a description.
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 (491 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. 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. Display only: search order uses the quality grade.

Compared with peers

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

Readiness: Higher than 24% of peers; This listing 65 · peer median 78
Latency: Faster than 19% of peers; This listing 491 ms · peer median 205 ms

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

Valid payment requirements −10 — Return complete payment requirements in the 402 challenge.
Now: No payment requirements on record.
Live 402 challenge −5 — Answer the paid path with a valid 402 challenge.
Now: Endpoint reachable; its 402 challenge was seen earlier (491 ms).
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.

How many agent tools actually work · All statistics

Paid endpoints

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

https://www.pathwren.workers.dev/mcp

https://www.pathwren.workers.dev/mcp/triage

https://www.pathwren.workers.dev/mcp/doctor

https://www.pathwren.workers.dev/a2a

https://www.pathwren.workers.dev/data/agents.json

https://www.pathwren.workers.dev/documents.json

https://www.pathwren.workers.dev/ip-ranges/all.json

https://www.pathwren.workers.dev/openapi.json

https://www.pathwren.workers.dev/stats.json

https://www.pathwren.workers.dev/llms.txt

How to call

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

curl -sS -i -X GET https://www.pathwren.workers.dev/a2a/doctor  # expect HTTP 402 Payment Required (price advertised in the 402 response)

/.well-known/x402.json

https://www.pathwren.workers.dev/.well-known/x402

Listed in

Directories this entry was found in.

a2a since 2026-09-01