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

aiHitBot

aiHit · Corpus and dataset builders · json

User-agent: aiHitBot
Disallow: /


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

What it is

aiHit's automated collector, building a company dataset from public company websites.

What blocking it costs you

Your company record in a B2B dataset goes stale. Documented as respecting robots.txt, so the rule works.

Full user-agent string

aiHitBot

Allow it instead

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

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