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

omgili

Webz.io · Corpus and dataset builders · json

User-agent: omgili
Disallow: /


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

What it is

The older robots token for the same Webz.io collection, still honoured and still worth listing.

What blocking it costs you

Same as omgilibot.

Full user-agent string

omgili/0.5 +http://omgili.com

Allow it instead

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

/tools/verification-methods?crawler=omgili
How do I prove a request really is omgili? 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