Assistant fetchers
KlaviyoAIBot is a bot operated by Klaviyo that fetches single pages on demand for an AI assistant. KlaviyoAIBot is Klaviyo's web crawler that fetches publicly available pages from domains explicitly connected to user accounts to power the Kai Customer Agent feature. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Request says
"KlaviyoAIBot"
Checked against
Nothing published
Live check
No operator check exists for KlaviyoAIBot. This still shows what the address really is.
Reference
| User agent | KlaviyoAIBotToken only: match on the substring. |
|---|---|
| Operator | Klaviyo |
| Purpose | Assistant fetchers |
| Respects robots.txt | Honourssource |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Indexes based on 'change signals' and user configuration. |
| Robots.txt tokens | KlaviyoAIBot |
| Operator documentation | None published |
KlaviyoAIBot is Klaviyo's web crawler that fetches publicly available pages from domains explicitly connected to user accounts to power the Kai Customer Agent feature. Th…
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: KlaviyoAIBot
Disallow: /User-agent: KlaviyoAIBot
Allow: /User-agent: KlaviyoAIBot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking KlaviyoAIBot means a person who asks about one of your URLs gets an error instead of a summary. That is a support and reputation trade-off, not a training one.
Build a file for every crawlerFAQ
KlaviyoAIBot is a bot operated by Klaviyo that fetches single pages on demand for an AI assistant. KlaviyoAIBot is Klaviyo's web crawler that fetches publicly available pages from domains explicitly connected to user accounts to power the Kai Customer Agent feature. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Yes. The operator documents that KlaviyoAIBot reads robots.txt and follows Disallow rules for its own token. Rules take effect on the next fetch of the file, which can be hours or days after you publish them.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the KlaviyoAIBot token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking KlaviyoAIBot means a person who asks about one of your URLs gets an error instead of a summary. That is a support and reputation trade-off, not a training one.