Index / ARD publishers / www.pathwren.workers.dev

www.pathwren.workers.dev

www.pathwren.workers.dev publishes an Agentic Resource Discovery manifest at /.well-known/ard.json, declaring what an AI agent can call on this domain. Everything below is read from that file. First seen by our crawler on 01 September 2026.

17declared resources
17with a callable endpoint
17answering of 17 checked
44verified tools

Declared resource	Type
AI Crawler Index — A2A agentanswers in 138ms A2A (Agent2Agent) v1.0 agent, JSON-RPC 2.0 over POST, seven read-only skills about web crawlers and AI user agents: classify_user_agent, lookup_crawler, list_crawlers, generate_robots_txt, is_verified_crawler_ip, whats_changed and changes_since — the last o... endpoint: `https://www.pathwren.workers.dev/c/ard/.well-known/agent-card.json` identifier: `urn:air:www.pathwren.workers.dev:agent:ai-crawler-index` published to be found for: which bot is this user-agent string · is this IP really GPTBot or is something spoofing it · write me a robots.txt that blocks AI training crawlers but keeps searc · what does blocking ClaudeBot actually cost me a2a crawlers user-agent robots.txt bot-detection	application/a2a-agent-card+json
Agent Discovery Doctor — AI Crawler Indexanswers in 212ms A2A v1.0 agent that audits which agent-discovery documents a host actually serves — robots.txt, llms.txt, openapi.json, the .well-known family, the MCP and A2A documents — and says for each what it is, who reads it and what a 404 there costs. It also valida... endpoint: `https://www.pathwren.workers.dev/c/ard/a2a/doctor/.well-known/agent-card.json` identifier: `urn:air:www.pathwren.workers.dev:agent:doctor` published to be found for: which agent discovery files does my domain serve · do I need an llms.txt and what goes in it · validate my A2A agent card against the spec · check my .well-known files for AI agents a2a doctor crawlers agents	application/a2a-agent-card+json
Crawler IP Verifier — AI Crawler Indexanswers in 321ms A2A v1.0 agent that checks crawler IP addresses against the ranges the operators themselves publish: up to 500 addresses per call with the matching prefix, source and mirror time for each, CIDR containment lookups both ways, paste-ready allowlists for nginx... endpoint: `https://www.pathwren.workers.dev/c/ard/a2a/netcheck/.well-known/agent-card.json` identifier: `urn:air:www.pathwren.workers.dev:agent:netcheck` published to be found for: verify a list of IP addresses against published crawler ranges · is this IP really Googlebot or is something spoofing it · generate an nginx allowlist of AI crawler IP ranges · which operator owns this CIDR block a2a netcheck crawlers agents	application/a2a-agent-card+json
Crawler Log Triage — AI Crawler Indexanswers in 95ms A2A v1.0 agent that turns pasted access-log lines into who crawled you: every line classified by operator and category, a rollup with hits and bytes per operator, the lines whose user-agent claims an operator from an address outside every range that operato... endpoint: `https://www.pathwren.workers.dev/c/ard/a2a/triage/.well-known/agent-card.json` identifier: `urn:air:www.pathwren.workers.dev:agent:triage` published to be found for: which AI bots are in my access log · is something impersonating Googlebot in my logs · summarise my crawler traffic by operator · make a robots.txt from what actually crawled my site a2a triage crawlers agents	application/a2a-agent-card+json
Discovery and Auth-Posture Probe — AI Crawler Indexanswers in 116ms A2A v1.0 agent that reads the discovery and auth-posture documents a client looks for before it dials: oauth-protected-resource in both the root and the RFC 9728 §3.1 insertion form, oauth-authorization-server, .well-known/mcp, .well-known/mcp.json, /mcp.js... endpoint: `https://www.pathwren.workers.dev/c/ard/a2a/discovery/.well-known/agent-card.json` identifier: `urn:air:www.pathwren.workers.dev:agent:discovery` published to be found for: which discovery documents does my agent host serve · do I publish oauth-protected-resource in the RFC 9728 insertion form · is my .well-known/mcp.json actually valid JSON or a soft 404 · what does an MCP client read before it dials my endpoint a2a discovery crawlers agents	application/a2a-agent-card+json
MCP Endpoint Conformance — AI Crawler Indexanswers in 124ms A2A v1.0 agent that lints an MCP endpoint you name: initialize and version negotiation including a repeated byte-identical handshake, JSON-Schema validation of every tool the endpoint advertises, and JSON-RPC error conformance for the five malformed request... endpoint: `https://www.pathwren.workers.dev/c/ard/a2a/lint/.well-known/agent-card.json` identifier: `urn:air:www.pathwren.workers.dev:agent:lint` published to be found for: does my MCP server negotiate the protocol version correctly · check my MCP endpoint's tool schemas for JSON-Schema faults · does my MCP server return -32601 or an HTML 500 for an unknown method · is my MCP handshake idempotent a2a lint crawlers agents	application/a2a-agent-card+json
MCP Endpoint Score Card — AI Crawler Indexanswers in 113ms A2A v1.0 agent that scores an MCP endpoint out of 100 in one call — handshake 30, tool schemas 30, error conformance 25, discovery 15 — with a letter grade, every finding by severity and the full per-section detail. Built to be called from a monitor: stable... endpoint: `https://www.pathwren.workers.dev/c/ard/a2a/score/.well-known/agent-card.json` identifier: `urn:air:www.pathwren.workers.dev:agent:score` published to be found for: score my MCP endpoint out of 100 · grade an MCP server for spec conformance · give me one alertable number for my MCP endpoint's health · what is wrong with my MCP server and how bad is it a2a score crawlers agents	application/a2a-agent-card+json
robots.txt Policy Lint — AI Crawler Indexanswers in 149ms A2A v1.0 agent that reads a robots.txt you paste and says what it actually does: RFC 9309 lint with the errors that silently change meaning, whether a named crawler may fetch a named path and which rule decided it, an audit of which AI crawlers the file rea... endpoint: `https://www.pathwren.workers.dev/c/ard/a2a/robots/.well-known/agent-card.json` identifier: `urn:air:www.pathwren.workers.dev:agent:robots` published to be found for: check my robots.txt for mistakes · does my robots.txt actually block GPTBot · is this path allowed for this crawler by my robots.txt · what changed in effect between these two robots.txt files a2a robots crawlers agents	application/a2a-agent-card+json
agent-discovery-doctoranswers in 106ms7 verified tools MCP server at www.pathwren.workers.dev, verified by introspection: 7 tools exposed. endpoint: `https://www.pathwren.workers.dev/c/neuronto-com/mcp/doctor` identifier: `urn:air:www.pathwren.workers.dev:mcp:agent-discovery-doctor`	application/mcp-server-card+json
ai-crawler-indexanswers in 61ms9 verified tools Five remote MCP servers (Streamable HTTP, JSON-RPC 2.0, no auth) on one host. The endpoint to connect to is POST https://www.pathwren.workers.dev/c/ard/mcp — this URL is the server card that describes it, not the endpoint. /mcp identifies one crawler at a t... endpoint: `https://www.pathwren.workers.dev/c/neuronto-com/mcp` identifier: `urn:air:www.pathwren.workers.dev:mcp:ai-crawler-index` published to be found for: connect an MCP server that identifies web crawlers · triage an access log and tell me which AI bots hit my site · check which agent discovery files my domain serves mcp crawlers log-analysis discovery	application/mcp-server-card+json
crawler-ip-verifieranswers in 111ms7 verified tools MCP server at www.pathwren.workers.dev, verified by introspection: 7 tools exposed. endpoint: `https://www.pathwren.workers.dev/c/neuronto-com/mcp/netcheck` identifier: `urn:air:www.pathwren.workers.dev:mcp:crawler-ip-verifier`	application/mcp-server-card+json
crawler-log-triageanswers in 72ms7 verified tools MCP server at www.pathwren.workers.dev, verified by introspection: 7 tools exposed. endpoint: `https://www.pathwren.workers.dev/c/neuronto-com/mcp/triage` identifier: `urn:air:www.pathwren.workers.dev:mcp:crawler-log-triage`	application/mcp-server-card+json
mcp-endpoint-lintanswers in 203ms7 verified tools MCP server at www.pathwren.workers.dev, verified by introspection: 7 tools exposed. endpoint: `https://www.pathwren.workers.dev/c/neuronto-com/mcp/lint` identifier: `urn:air:www.pathwren.workers.dev:mcp:mcp-endpoint-lint`	application/mcp-server-card+json
robots-policy-lintanswers in 169ms7 verified tools MCP server at www.pathwren.workers.dev, verified by introspection: 7 tools exposed. endpoint: `https://www.pathwren.workers.dev/c/neuronto-com/mcp/robots` identifier: `urn:air:www.pathwren.workers.dev:mcp:robots-policy-lint`	application/mcp-server-card+json
AI Crawler Index — HTTP API and datasetanswers in 199ms The same index as plain HTTP: OpenAPI 3.1 over read-only JSON and CSV endpoints — every crawler record, per-operator IP ranges mirrored from the operator's own published file, ready-made robots.txt policies, and a changelog of what moved. No key and no rate... endpoint: `https://www.pathwren.workers.dev/c/ard/openapi.json` identifier: `urn:air:www.pathwren.workers.dev:api:crawler-index` published to be found for: download a JSON list of AI crawler user agents · where can I get published IP ranges for AI bots · csv of crawlers by category and operator api openapi dataset crawlers ip-ranges	application/json
AI Crawler Index — since-cursor changes feedanswers in 71ms A since-cursor feed over the whole index: every operator IP-range list that gained or lost prefixes, every upstream that failed or recovered, and every crawler record added or edited. Send the `cursor` from your last response back as `since` and you get onl... endpoint: `https://www.pathwren.workers.dev/c/ard/changes.json?since=0` identifier: `urn:air:www.pathwren.workers.dev:feed:changes` published to be found for: how do I keep a copy of the AI crawler list up to date · did any AI crawler IP ranges change since yesterday · subscribe to changes in crawler user agents and robots tokens · which crawler IP-range endpoints are failing right now changes feed cursor crawlers ip-ranges monitoring	application/json
AI Crawler Index — x402 payment-discovery documentanswers in 201ms The host's x402 payment-discovery document, and a negative answer served as data rather than as a 404: x402Version 2 with an EMPTY `accepts` array, `configured: false`, `reason: no_paid_resources`, `implemented: false`, `payTo: null`. Nothing on this host i... endpoint: `https://www.pathwren.workers.dev/c/ard/.well-known/x402` identifier: `urn:air:www.pathwren.workers.dev:payment:x402-discovery` published to be found for: does this host charge for anything before I call it · what does an empty x402 accepts array mean · is /.well-known/x402 part of the x402 specification · which endpoints here require payment and which are free x402 payments discovery well-known free	application/json

Source: https://www.pathwren.workers.dev/.well-known/ard.json, this publisher's own file. Identifiers are reproduced exactly as published. Of the resources listed, 17 have been probed for reachability. "Answers" and "no response" describe only whether an endpoint replied when last probed: services go down and come back, and an entry is demoted rather than removed. None of this is a trust, quality or safety rating.

Search this publisher's resources alongside every other indexed resource at https://neuronto.com/search, or connect an agent to https://neuronto.com/mcp. If this is your domain, the free console shows what a registry sees when it reads your manifest.