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

QualifiedBot

Qualified · AI search crawlers · json

User-agent: QualifiedBot
Disallow: /


robots.txt token	`QualifiedBot`
User-agent contains	`QualifiedBot`
Operator	Qualified
Category	AI search crawlers
robots.txt	operator publishes no robots.txt statement
Verify by	no published verification method

What it is

Analyses a customer's website so Qualified's AI sales chatbots can answer questions about it in context.

What blocking it costs you

A chatbot on a site that licensed the product loses context. If that site is yours, this block is self-inflicted.

Full user-agent string

QualifiedBot

Allow it instead

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

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