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

ChatGPT Agent

OpenAI · User-triggered fetchers · json

User-agent: ChatGPT-User
Disallow: /


robots.txt token	`ChatGPT-User`
User-agent contains	`ChatGPT Agent`
Operator	OpenAI
Category	User-triggered fetchers
robots.txt	obeys robots.txt (documented)
Verify by	published IP ranges
Published ranges	213 IPv4 + 0 IPv6 · json · source

What it is

ChatGPT's agent mode driving a real browser: it navigates and interacts with sites to finish a multi-step task a user gave it. OpenAI governs it with the ChatGPT-User token and the ChatGPT-User prefix list rather than a token of its own, so the robots rule and the address check are the same ones.

What blocking it costs you

Agentic tasks a user asked for — booking, comparing, filling a form on your site — fail. This is the fetch that ends in a transaction, so it is the most expensive user-triggered block on this list.

Full user-agent string

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/bot

Allow it instead

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

/tools/verification-methods?crawler=chatgpt-agent
How do I prove a request really is ChatGPT-User? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.
/tools/verify-crawler?ip=104.208.184.192&ua=ChatGPT-User
Is 104.208.184.192 really ChatGPT-User? That address checked against every prefix this host mirrors. 104.208.184.192 is the first address of 104.208.184.192/28, one of the ranges listed on this page — so the link is a worked example that returns a match. Swap in an address from your own log.

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://platform.openai.com/docs/bots
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-all-ai · allow-ai-search-only · maximum-ai-visibility