curl -s https://www.pathwren.workers.dev/crawler/quillbot.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

QuillBot

QuillBot · AI training crawlers · json

User-agent: QuillBot
Disallow: /


robots.txt token	`QuillBot`
User-agent contains	`QuillBot`
Operator	QuillBot
Category	AI training crawlers
robots.txt	operator publishes no robots.txt statement
Verify by	no published verification method

What it is

Operated by QuillBot as part of its writing, paraphrasing and AI-detection products. The dataset also records a second token, quillbot.com, for the same operator.

What blocking it costs you

Exclusion from QuillBot's corpus. No compliance statement is published, so the rule is a request.

Full user-agent string

QuillBot

Allow it instead

User-agent: QuillBot
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=quillbot&s=client-dossiers'

/tools/verification-methods?crawler=quillbot
How do I prove a request really is QuillBot? 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://quillbot.com
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-ai-training · block-all-ai · maximum-ai-visibility