ChatGPT-User
OpenAI · User-requested fetches
What OpenAI says it does
“certain user actions in ChatGPT and Custom GPTs”
The facts
| Operator | OpenAI |
| robots.txt token | ChatGPT-User |
| Appears in access logs | Yes |
| User-agent string | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/bot |
| robots.txt | May not honor robots.txt. OpenAI states robots.txt rules may not apply to it because the fetches are initiated by a user, not a crawl schedule. |
| IP list | https://openai.com/chatgpt-user.json |
| Documentation | https://developers.openai.com/api/docs/bots, read 4 Aug 2026 |
Allow or block it in robots.txt
To block ChatGPT-User entirely:
User-agent: ChatGPT-User Disallow: /
To allow it everywhere:
User-agent: ChatGPT-User Allow: /
OpenAI's stated position: may not honor robots.txt. OpenAI states robots.txt rules may not apply to it because the fetches are initiated by a user, not a crawl schedule. Blocking it reliably means blocking at the server, not in robots.txt.
Verify a request is really ChatGPT-User
Match the requesting IP against the published list.
A hit from ChatGPT-User means a person asked ChatGPT something and it opened this page to answer. That is exactly the event AI visibility tools try to measure.
Observed on this property
| First seen here | 5 Aug 2026 |
| Most recent | 21 Sep 2026 |
| Requests, last 30 days | 432 |
| Requests, all time | 823 |
| robots.txt fetches | 1 |
Most requested paths:
/(229)/tool/rankshift/(12)/fetch/(11)/tool/profound/(10)/.env(8)/a-z/(6)/best-aeo-tools/(6)/proxy/(5)
Also run by OpenAI
- GPTBot | Trains AI models
- OAI-SearchBot | AI search index