illumi.one
success
Claude Code
intent

What does illumi.one do and who is it for? Explain it back to me.

5steps
28.8sduration
$0.2532cost
45,491tokens
8 steps3 reasoning steps1 search
home
docs
docs
search
/illumi-review
75%
on-site discovery
50%
reliability
50%
link following
path origin
  • previous resource50%
  • web search25%
  • prior knowledge25%
insight

The agent partially satisfied the task by assembling a coherent explanation of illumi.one from two homepage fetches (main page and pricing page), but relied heavily on inference and prior knowledge to fill gaps the site itself did not explicitly address. The site provided basic positioning and pricing tiers but lacked competitive comparisons, feature details, use-case specifics, and team/plan scoping information that would have enabled a more confident and complete answer.

  • ›Step [1] (homepage) returned the site's tagline ('AI visual workspace that takes you from thinking to delivery') and likely navigation/hero content; step [2] (pricing page) returned the three-tier pricing table ($0 Free, $25/mo Pro, $20/mo annual). These two fetches contained the core factual anchors for the final response.
  • ›The agent had to infer most positioning details (vs. Miro, Figma, Notion, ChatGPT) without explicit competitor comparisons on the site. The final response's differentiators section is assembled reasoning, not extracted from page content—a significant knowledge gap the agent itself flagged ('Limited public information on competitors').
  • ›The site does not publish structured details on: which AI models are included per plan, storage/workspace limits, team size caps, per-user vs. per-workspace pricing, export capabilities, or API access. The agent explicitly called out these missing details, indicating the site forces visitors to either contact sales or make assumptions.
  • ›The 404 on /about (step [3]) suggests limited public company/team information, further narrowing what the site surface-exposes about positioning and intent.
  • ›The web search (step [5]) did not yield usable alternatives comparison content (one result was a 410 removal page; others were unrelated mobile app reviews), so the agent relied on domain knowledge and inference rather than third-party validation.

Help the next agent finish on illumi.one

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 →