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

omgilibot

Webz.io · Corpus and dataset builders · json

User-agent: omgilibot
Disallow: /


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

What it is

Webz.io's crawler, collecting web and forum text sold as datasets, including to model builders.

What blocking it costs you

Exclusion from a commercial dataset resold to third parties.

Full user-agent string

omgilibot/0.4; +http://omgili.com

Allow it instead

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

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