Andibot — Andi Search's crawler
Andibot is the crawler token associated with Andi, an AI-based answer search engine. The token is catalogued in independent crawler directories and observed in logs. Andi publishes limited official operator documentation, so this entry identifies Andibot by token and flags unverifiable specifics rather than inventing IP ranges or behaviour.
What this means
Andibot is the crawler token associated with Andi, a search product that returns AI-generated answers rather than a list of links. The token appears in independent crawler directories and in operator logs, which is how it is catalogued.
Andi provides limited formal operator documentation compared with larger vendors, so this entry identifies Andibot by its token without asserting specifics it does not publish. That is why the status is partially verified.
How Andibot identifies itself
Andibot uses the robots.txt user-agent token Andibot, the stable identifier to match on. We do not assert an exact full user-agent string, version number, or IP range, because those are not published in verifiable operator material — and inventing them is not allowed.
Because a user-agent token can be copied and no official IP range is published for verification, treat Andibot identification as a claim. Classify by token and apply policy conservatively where authenticity matters.
- robots.txt token: Andibot (catalogued in crawler directories)
- Associated with Andi, an AI answer search engine
- No published IP ranges — token identification only
robots.txt considerations
To request that Andibot stay out, if it honours robots.txt:
User-agent: Andibot Disallow: /
Compliance can only be confirmed by observing whether disallowed paths stop being fetched. robots.txt is a request to compliant crawlers, not an access boundary.
How it appears in analytics and logs
A request carrying the Andibot token is Andi's crawler fetching a URL to support its AI answer search — a bot event, not a human visit. With limited official docs, treat the token as identification rather than full proof.
Diagnostic use case
Identify the Andibot token in logs and set robots.txt policy for Andi's crawler, treating unpublished specifics as not verified.
What WebmasterID can help detect
WebmasterID classifies the Andibot token server-side as an AI crawler and shows its activity on the bot-intelligence surface, so its coverage is visible without log parsing.
Common mistakes
- Asserting Andibot's IP ranges or exact UA string — they are not published.
- Assuming robots.txt compliance without observing behaviour.
- Counting Andibot crawl hits as human traffic.
Privacy and accuracy notes
Detection uses only the request user-agent token. No human identity is involved. WebmasterID records the crawl as a bot event, separate from human analytics.
Related pages
- YouBot — You.com crawler
YouBot is the crawler operated by You.com to support its search and AI assistant. Its robots.txt token is YouBot. Public documentation is limited in places, so specifics that cannot be confidently sourced are marked partially verified rather than guessed.
- Monitoring for new AI crawlers
New AI crawlers appear regularly, often with tokens you have never seen. Monitoring for them means surfacing unfamiliar bot-like user agents, checking each against the operator's documentation before deciding policy, and resisting both reflexive blocking and reflexive trust. The aim is a deliberate, sourced decision for each new token rather than a static, stale allow/block list.
- AI training crawlers vs AI search crawlers
Within a single AI vendor, training and search are usually handled by separate crawlers with separate robots.txt tokens. OpenAI's GPTBot crawls for training while OAI-SearchBot supports search features. Treating them as one control leads to policy mistakes.
- AI search analytics
See which AI answer engines reach your site, recorded server-side.
Sources and verification notes
- Dark Visitors — AI crawler directory (Andibot)Third-party directory cataloguing the Andibot token; official operator docs are limited.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.