curl -s https://www.pathwren.workers.dev/crawler/klaviyoaibot.json # this page, as JSON
No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a
Klaviyo · AI search crawlers · json
User-agent: KlaviyoAIBot Disallow: /
| robots.txt token | KlaviyoAIBot |
| User-agent contains | KlaviyoAIBot |
| Operator | Klaviyo |
| Category | AI search crawlers |
| robots.txt | obeys robots.txt (documented) |
| Verify by | no published verification method |
Fetches pages from domains a Klaviyo customer has explicitly connected to their own account, to power Klaviyo's Kai customer agent. It is scoped to connected domains rather than the open web.
If the connected domain is yours, blocking this breaks the agent you configured. If it is not, this bot should not be reaching you at all.
KlaviyoAIBot
User-agent: KlaviyoAIBot Allow: /
A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.
curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=klaviyoaibot&s=client-dossiers'
/tools/verification-methods?crawler=klaviyoaibotEvery parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.
Operator documentation: https://help.klaviyo.com/hc/en-us/articles/40496146232219
Machine copies: json ·
markdown
Policies that name this crawler:
allow-all · block-all-ai · allow-ai-search-only · maximum-ai-visibility