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

Crawl4AI

Crawl4AI project · Tools and frameworks · json

User-agent: Crawl4AI
Disallow: /


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

What it is

An open-source LLM-oriented crawler and scraper library, run by whoever installs it. Like Scrapy, the default user-agent identifies the software and says nothing about who is behind the request.

What blocking it costs you

You block a library, not an operator: the rule catches a researcher and a bulk scraper equally, and anyone who edits one config line is not caught at all.

Full user-agent string

Crawl4AI

Allow it instead

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

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