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

Anomura

Direqt · AI search crawlers · json

User-agent: Anomura
Disallow: /


robots.txt token	`Anomura`
User-agent contains	`Anomura`
Operator	Direqt
Category	AI search crawlers
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

Direqt's search crawler. It indexes the sites of Direqt's own publisher customers so their on-site chatbots can answer from them.

What blocking it costs you

If you are the publisher, this breaks the assistant you put on your own pages. If you are not, it should not be crawling you.

Full user-agent string

Anomura

Allow it instead

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

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