# Thinkbot

> Collects pages for analysis of how sites are adopting AI and automation. The ai.robots.txt dataset records the operator as not respecting robots.txt.

| field | value |
|---|---|
| operator | Thinkbot |
| category | Corpus and dataset builders |
| robots.txt token | `Thinkbot` |
| user-agent contains | `Thinkbot` |
| robots.txt | compliance disputed |
| verify by | no published verification method |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://www.thinkbot.agency |
| last reviewed | 2026-09-14 |

## What blocking it costs you

Exclusion from a market-research dataset. Expect to enforce this at the edge rather than in robots.txt.

## Full user-agent string

```
Thinkbot
```

## Block it

```
User-agent: Thinkbot
Disallow: /
```

## Allow it

```
User-agent: Thinkbot
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 Thinkbot?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=thinkbot&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/thinkbot.json · index: https://www.pathwren.workers.dev/llms.txt