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

AI2Bot

Allen Institute for AI · Corpus and dataset builders · json

User-agent: AI2Bot
Disallow: /


robots.txt token	`AI2Bot`
User-agent contains	`AI2Bot`
Operator	Allen Institute for AI
Category	Corpus and dataset builders
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

The Allen Institute's crawler, gathering pages for open research corpora such as Dolma that underpin fully open models like OLMo.

What blocking it costs you

Excluded from open research datasets. Worth a deliberate decision: this is the category where 'blocking AI' also blocks the open, auditable end of it.

Full user-agent string

Mozilla/5.0 (compatible) AI2Bot (+https://www.allenai.org/crawler)

Allow it instead

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

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