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

Scrapy

Scrapy project · Tools and frameworks · json

User-agent: Scrapy
Disallow: /


robots.txt token	`Scrapy`
User-agent contains	`Scrapy`
Operator	Scrapy project
Category	Tools and frameworks
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

Not an operator: the default user-agent of the most common Python crawling framework. Anyone can be behind it. Modern Scrapy obeys robots.txt by default, which is why the default UA is still worth a rule.

What blocking it costs you

You block a very large tail of unattributed one-off crawlers, and also every well-behaved researcher who did not change the default.

Full user-agent string

Scrapy/2.11.0 (+https://scrapy.org)

Allow it instead

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

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