What you can conclude
- OAI-AdsBot requested the recorded page.
- You can review paths, timing, and HTTP outcomes.
- OpenAI publishes a crawler-specific IP source.
Keep OpenAI advertising crawler requests in their own operational view instead of grouping them with training or search activity.
OAI-AdsBot is an OpenAI crawler associated with advertising systems rather than model training or search indexing.
Talivia keeps OAI-AdsBot in the Other purpose group so its requests do not get interpreted as training, search, or user-triggered answer fetches.
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-AdsBot/1.0; +https://openai.com/adsbotTalivia looks for the stable OAI-AdsBot token in the normalized User-Agent.
User-agent: OAI-AdsBot
Allow: /
# To block instead:
# Disallow: /Use robots.txt to express an allow or block preference for this crawler.
When the integration supplies a source IP from a trusted network boundary, Talivia can compare it with provider-published ranges.
View official sourceTurn on collection in website settings.
Send the minimal event from trusted server code or middleware.
Review pages, statuses, trends, and verification confidence.
Talivia first matches the OAI-AdsBot User-Agent token. When a trusted source IP matches provider-published ranges, the request can receive stronger verification confidence.
Add a rule for OAI-AdsBot in robots.txt and check the provider’s official documentation for behavior. robots.txt expresses crawl preferences; it is not access control or identity verification.
Talivia stores the hostname, sanitized path, method, User-Agent, optional status, classification, and verification result. It does not store page bodies, cookies, authorization headers, query strings, or raw IP addresses.
Start recording real requests with server-side tracking.
Add your website