---
schema_version: "newruntime-reader-dossiers-v1"
type: "reader_dossier"
slug: "keenablebot"
kind: "ai_answer"
operator: "Keenable"
researched_at: "2026-10-23"
confidence: "high"
json_url: "https://newruntime.com/readers/keenablebot.json"
canonical_url: "https://newruntime.com/readers/keenablebot/"
---

# KeenableBot

> Builds and maintains the Keenable search index, which answers queries from AI agents and applications and cites source pages with links. A separate Keenable-User agent fetches single pages on behalf of a person or their agent.

## Dossier

- Kind: AI search & answer engines
- Operator: Keenable (https://keenable.ai/)
- Documentation: https://app.keenable.ai/bot
- robots.txt tokens: KeenableBot, Keenable-User
- Feeds: search index
- Respects robots.txt: Yes, per its documentation. Docs: follows RFC 9309; a group naming its token overrides '*'; honors noindex/nofollow/none in meta robots and X-Robots-Tag.
- Verification: Published IP ranges (https://app.keenable.ai/bot/keenablebot.json)
- Labels matched in our logs: keenablebot

## Why it matters to New Runtime (our interpretation)

Indexing by a search engine built for AI agents means our pages can be cited in agent and app answers served through Keenable.

## Observed behaviour

- Baseline 2026-10-23 (93-day window): 252 requests on 20 days; first seen 2026-09-23, last seen 2026-10-23; Regular.
- Live numbers: https://newruntime.com/bot-traffic-history.json and https://newruntime.com/crawler-journeys.json

## Sources

- https://app.keenable.ai/bot

Identity: A family name is what a client claims in its user agent. It is verified only when its request came from the operator's published IP ranges or passed forward-confirmed reverse DNS, as reported per family in /crawler-journeys.json. Anyone can claim any name.

All dossiers: https://newruntime.com/readers.md