# QualifiedBot

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

| field | value |
|---|---|
| operator | Qualified |
| category | AI search crawlers |
| robots.txt token | `QualifiedBot` |
| user-agent contains | `QualifiedBot` |
| robots.txt | operator publishes no robots.txt statement |
| verify by | no published verification method |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://www.qualified.com |
| last reviewed | 2026-09-14 |

## 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
```

## Block it

```
User-agent: QualifiedBot
Disallow: /
```

## Allow it

```
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.

- **How do I prove a request really is QualifiedBot?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=qualifiedbot&s=client-dossiers'`  
  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.

JSON: https://www.pathwren.workers.dev/crawler/qualifiedbot.json · index: https://www.pathwren.workers.dev/llms.txt