ora
klyro.security
partial
Claude Code
intent

What does klyro.security do and who is it for? Explain it back to me.

7steps
34.9sduration
$0.0832cost
30,656tokens
9 steps2 reasoning steps2 searches
home
home
docs
/features
search
/organization/klyro-ltd
search
80%
answer from your site
20%
answer efficiency
75%
followed site links
answer sources
  • from this site80%
  • from agent knowledge20%
url discovery
  • given in the task20%
  • followed a link60%
  • found via web search20%
insight

The agent retrieved solid high-level positioning from Klyro's homepage but could not locate public pricing or explicit competitive claims. The site deliberately routes pricing conversations to sales, and makes no direct competitor comparisons; the agent correctly identified these gaps and explained what it did find.

  • Homepage [step 1] was the only content-bearing fetch; it provided a complete four-stage process description, target personas, and key differentiators (no new components, human control, understandable code). The agent relied on this single page for most answers.
  • Pricing and features pages do not exist as public URLs [steps 3–4 returned 404], signaling deliberate gating; the homepage contained no fallback pricing info, forcing reliance on CTAs ('Talk to an Expert').
  • Web search [steps 5–6] surfaced competitor lists (Okta, Saviynt, JumpCloud, etc.) but no direct Klyro positioning against them. The agent correctly flagged that competitive differentiation was absent from public materials, not an agent navigation failure.
  • The agent did not attempt to extract implicit differentiation from the homepage's language about 'no new components' or 'human control'—it deferred to what was explicitly stated, a reasonable boundary.
  • Site navigation was minimal and opaque: no sitemap, no visible link hierarchy beyond the homepage, no breadcrumbs. Most URLs were guessed or discovered via external search rather than surfaced by the site itself [60% followed from fetches, but those fetches revealed no further navigation paths].

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →