arakey.app
success
Claude Code
intent
What does arakey.app do and who is it for? Explain it back to me.
3steps
36.0sduration
$0.1791cost
14,402tokens
4 steps1 reasoning step
home
home
home
80%
answer from your site
100%
answer efficiency
100%
followed site links
answer sources
- from this site80%
- from agent knowledge20%
url discovery
- given in the task33%
- followed a link67%
insight
The agent successfully assembled a comprehensive overview of AraKey by fetching the homepage three times and extracting consolidated information about the platform's purpose, audience, pricing, and positioning. The site was navigable but narrow—all content came from the homepage itself, and the agent had to note gaps (competitor comparisons, case studies, geographic scope) that weren't surfaced by the domain.
- ›All three fetches returned the same URL (arakey.app/) yet yielded distinct structured content sections—homepage appears to be a rich single page that surfaces different content fragments on repeated fetches or the agent parsed overlapping sections on each pass, indicating good content density but poor site navigation depth (no dedicated subpages for pricing, features, or competitors discovered).
- ›Pricing table was directly retrievable and well-structured on the homepage, enabling the agent to populate a complete comparison matrix without following links—strong affordance for the 'how it's priced' task requirement.
- ›Agent identified real estate portal integrations (ZAP, VivaReal, OLX) and WhatsApp/email automation as differentiators—these facts came from homepage content and required no external search, indicating the site does surface its positioning claims directly.
- ›Agent explicitly called out missing elements (no competitor comparisons, no case studies, unclear geographic scope, no feature depth beyond basics)—these gaps suggest the homepage prioritizes conversion messaging over comprehensive product documentation, leaving some discovery-evaluation task dimensions unmet.
- ›All content sourced from memory-typed URL rather than site navigation—agent never followed an internal link; 67% of fetches attributed to 'followed a link' in metadata conflicts with trajectory showing all three steps typed the same root URL, indicating either homepage is a single-page app or agent re-fetched same URL instead of discovering subpages.
See every agent that visits arakey.app
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 →