---
schema_version: "newruntime-reader-dossiers-v1"
type: "reader_dossier"
slug: "chatgpt-user"
kind: "ai_answer"
operator: "OpenAI"
researched_at: "2026-10-23"
confidence: "high"
json_url: "https://newruntime.com/readers/chatgpt-user.json"
canonical_url: "https://newruntime.com/readers/chatgpt-user/"
---

# ChatGPT-User

> Fetches web pages for user-initiated actions in ChatGPT, Custom GPTs and GPT Actions; not an automatic crawler and not used to decide Search eligibility.

## Dossier

- Kind: AI search & answer engines
- Operator: OpenAI (https://openai.com/)
- Documentation: https://developers.openai.com/api/docs/bots
- robots.txt tokens: ChatGPT-User
- Feeds: live answer fetch
- Respects robots.txt: Partly, per its documentation. Docs: because actions are user-initiated, robots.txt rules may not apply.
- Verification: Published IP ranges (https://openai.com/chatgpt-user.json)
- Labels matched in our logs: chatgpt-user

## Why it matters to New Runtime (our interpretation)

Each hit is a live ChatGPT user (or agent) asking about something New Runtime covered — the closest thing to a real machine-mediated reader.

## Observed behaviour

- Baseline 2026-10-23 (93-day window): 812 requests on 78 days; first seen 2026-07-23, last seen 2026-10-23; Regular.
- Reading mix (crawler journeys): 22 content reads, 1 feed or discovery reads, 0 machine-consumption reads; 22 unique materials.
- Identity check: verified 70, claimed unverified 1 requests.
- Live numbers: https://newruntime.com/bot-traffic-history.json and https://newruntime.com/crawler-journeys.json

## Sources

- https://developers.openai.com/api/docs/bots

Identity: A family name is what a client claims in its user agent. It is verified only when its request came from the operator's published IP ranges or passed forward-confirmed reverse DNS, as reported per family in /crawler-journeys.json. Anyone can claim any name.

All dossiers: https://newruntime.com/readers.md