owlish.bot
success
Claude Code
intent

What does owlish.bot do and who is it for? Explain it back to me.

10steps
45.2sduration
$0.4255cost
124,744tokens
12 steps2 reasoning steps1 search
home
docs
docs
.well-known
/features
docs
docs
search
docs
/index.md
89%
on-site discovery
89%
reliability
78%
link following
path origin
  • previous resource78%
  • web search11%
  • prior knowledge11%
insight

The agent successfully understood and explained Owlish by assembling information from the homepage, pricing page, documentation, and a competitive comparison blog post. The site surfaced most of what was needed directly, though the agent had to piece together details from multiple pages and flag several operational ambiguities (skills roadmap, multi-agent routing, knowledge sync behavior) that the site left unexplained.

  • ›Step [1] (homepage) and [10] (index.md) provided the core positioning and feature list; step [9] (pricing.md) delivered exact pricing tiers and add-on costs in structured form, making pricing fully machine-readable.
  • ›Step [8] (competitive blog post) was critical for the 'how it's different' section — Owlish self-authored comparisons to Intercom, Zendesk, Tidio, and Help Scout, which the agent correctly surfaced. This is unusual: the site outsourced differentiation to its own blog rather than embedding a comparison table on the product page.
  • ›The site published pricing and core product description in both HTML and Markdown (.md) artifact forms, making it agent-friendly; however, operational details (skills roadmap, multi-agent routing logic, KB sync frequency semantics) were either absent or scattered, forcing the agent to flag confusion rather than invent answers.
  • ›The agent attempted /features (404), which suggests the site does not expose a dedicated features page — capabilities are spread across homepage, docs, and pricing; this fragmentation is a minor navigability gap.

See every agent that visits owlish.bot

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 →