kitbase.dev
success
Claude Code
intent

What does kitbase.dev do and who is it for? Explain it back to me.

26steps
123.5sduration
$1.5135cost
344,792tokens
40 steps14 reasoning steps9 searches
home
docs
.well-known
/why-kitbase
/ai-visibility
docs.home
search
search
/web-analytics
search
search
search
/event-tracking
/bot-analytics
/backlinks
/scr2em/kitbase-sdk
search
search
/use-cases
search
/glossary
search
/bot-analytics.md
/web-analytics.md
/ai-visibility.md
/index.md
100%
on-site discovery
100%
reliability
94%
link following
path origin
  • previous resource94%
  • prior knowledge6%
insight

The agent successfully understood Kitbase's core offerings, pricing, and positioning by retrieving markdown versions of key product pages after initial HTML fetches proved truncated. The site is well-organized with clear product pages, but the agent had to work around JavaScript-rendered pages and web search results pointing to unrelated products (scale model databases, creator platforms) — the markdown artifacts proved far more agent-readable than the rendered HTML.

  • ›Steps [32, 33, 35, 36, 38] all returned markdown source files (.md) with complete, untruncated content; these directly answered all four questions (what, who, pricing, differentiation). The agent explicitly cited these as sources.
  • ›Initial HTML fetches [1, 3, 4, 5, 11, 17, 18, 20, 27, 30] returned truncated responses (marked '[truncated, 4400 more chars]'), making them unsuitable for content extraction. The agent recovered by guessing .md file paths, a reliable pattern but not discoverable from the site's navigation.
  • ›Web search steps [8, 10, 13, 14, 16, 21, 24, 26, 29] were routing-only; they returned results for unrelated products (ConvertKit, scale model databases, competitor analytics tools) and did not contribute to the final answer. The agent correctly deprioritized these.
  • ›The site's JavaScript rendering (Astro framework, visible in HTML head) blocked server-side extraction of rendered content, but markdown artifacts were published as static files, making the site partially agent-ready if the agent knows to probe for .md versions.
  • ›Pricing, feature set, and competitive positioning are all clearly documented in the markdown files; no information had to be inferred or assembled from fragments. However, the agent noted gaps: backlinks feature under-explained, AI credits system opaque, enterprise pricing custom/hidden, and '#1 platform' claim unvalidated against market evidence.

See every agent that visits kitbase.dev

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →