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

img2dataset

LAION / img2dataset · Corpus and dataset builders · json

User-agent: img2dataset
Disallow: /


robots.txt token	`img2dataset`
User-agent contains	`img2dataset`
Operator	LAION / img2dataset
Category	Corpus and dataset builders
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

The tool used to turn image-URL lists such as LAION's into downloaded training sets. It is run by whoever is building a dataset, not by a single operator.

What blocking it costs you

Your images are skipped when someone materialises an image-text dataset that references them.

Full user-agent string

img2dataset

Allow it instead

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

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