What is Andibot?
Andibot gathers web content for Andi, a conversational AI search assistant that returns summaries and sources. Unlike a transaction agent, its recorded purpose is to make pages available to a search experience.
A request may retrieve text that Andi can use when answering a question or preparing a sourced result. The available operator material does not document Andibot's crawl schedule, whether a particular fetch is query-time or pre-indexing work, or how long retrieved content remains in Andi's systems. Those details should not be guessed from one log entry.
Access can affect visibility inside Andi because the service needs readable source material to summarize or cite a page. Allowing the bot is not a promise of inclusion, ranking, or citation. Andi still decides which sources fit a user's query.
No evidence in this bot connects Andibot to model training. It should be classified as AI search retrieval, not as a training crawler. A site can therefore make a separate access decision for Andibot without assuming the same choice applies to bots that collect training data.
The stable token is Andibot, but the entry's verification status is unverifiable. There are no recorded operator IP ranges, Web Bot Auth keys, or Cloudflare identity details. A matching User-Agent header is useful for traffic grouping, though it cannot prove that Andi sent the request.
the directory records robots.txt support as true. Because public operator documentation for this exact token is limited, confirm that observed requests stop or change after a rule update. Keep confidential content behind authentication regardless of the robots setting.
