curl -s https://www.pathwren.workers.dev/crawler/wpbot.json   # this page, as JSON

No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a

wpbot

QuantumCloud · Tools and frameworks · json

User-agent: wpbot
Disallow: /


robots.txt token	`wpbot`
User-agent contains	`wpbot`
Operator	QuantumCloud
Category	Tools and frameworks
robots.txt	operator publishes no robots.txt statement
Verify by	no published verification method

What it is

Supports the AI Chatbot for WordPress plugin: it reads pages so the plugin can answer from a site's own content. The operator provides an opt-out through a form rather than through robots.txt.

What blocking it costs you

A WordPress site running that plugin loses its own content as an answer source. Only relevant where the plugin is installed.

Full user-agent string

wpbot

Allow it instead

User-agent: wpbot
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=wpbot&s=client-dossiers'

/tools/verification-methods?crawler=wpbot
How do I prove a request really is wpbot? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://www.quantumcloud.com
Machine copies: json · markdown
Policies that name this crawler: allow-all · maximum-ai-visibility