tryiris.ai
success
Claude Code
intent

What does tryiris.ai do and who is it for? Explain it back to me.

11steps
64.1sduration
$0.6919cost
116,355tokens
13 steps2 reasoning steps4 searches
home
docs
docs
/features
/why-iris
search
search
docs
/post/iris-and-lumens-…
search
search
71%
on-site discovery
57%
reliability
57%
link following
path origin
  • previous resource57%
  • web search29%
  • prior knowledge14%
insight

The agent satisfied the core task by assembling a comprehensive explanation of Iris from the homepage, pricing page, blog, and external sources discovered via web search. The site's own pages provided what, who, and pricing information directly; competitive differentiation and details about deployment options required external research and informed inference, revealing gaps in the site's self-documentation. The site is moderately agent-navigable for basic facts but sparse on technical depth and comparative positioning.

  • ›Step [0] (homepage) and step [2] (pricing page) were the only two successful direct fetches from tryiris.ai itself and provided the core product positioning ('400+ PTZ camera models', 'browser-based control', 'unified dashboard') and pricing structure ('per-studio' subscription tiers). Both were well-formed and information-rich.
  • ›Steps [3], [4], [5] all returned 404s (/features, /about, /why-iris), indicating the site has a shallow navigable structure—the agent had to guess at standard page patterns rather than following published navigation. This forced reliance on homepage content and external discovery.
  • ›Steps [8], [9], [10], [11] relied on web search to fill gaps: the agent found a blog, a partnership post, external press coverage (Church Production Magazine, TV Tech, Audinate press release), and third-party sources. The final response cites all of these external sources prominently, indicating the site itself was insufficient for answering 'how it's different from alternatives' and 'recent company context' (Audinate acquisition).
  • ›The agent explicitly flagged missing content: no searchable camera model list, no direct competitor comparison, sparse deployment architecture docs, unclear cloud-vs-on-prem options. These gaps are acknowledged in the final response and represent sections the site should surface but does not.
  • ›Pricing data was cleanly presented on the dedicated /pricing page, but the agent had to infer context (e.g., what 'cloud bandwidth' means in practice) from the page alone—no FAQ or comparison matrix disambiguated pricing tiers.

Help the next agent finish on tryiris.ai

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 →