aresto.ai
partial
Claude Code
intent
What does aresto.ai do and who is it for? Explain it back to me.
14steps
58.3sduration
$0.8476cost
142,190tokens
23 steps9 reasoning steps6 searches
home
docs
/arestotile-app
/aresto-os
/device
docs
/preorder
search
search
/device
search
search
search
search
100%
on-site discovery
88%
reliability
88%
link following
path origin
- previous resource88%
- prior knowledge13%
insight
The agent successfully identified Aresto's core value proposition—a hardware-based personal AI computer with local inference and autonomous agents—but could not complete the task fully due to missing pricing information. The site's dynamic JavaScript-heavy architecture and lack of a public pricing page made critical details inaccessible despite thorough exploration of device, OS, app, about, and preorder pages.
- ›Steps [1], [4], [5], [6], [8], [9] each returned valid HTML pages that the agent extracted positioning, product features (14-inch device, Aresto OS, 50 pre-configured agents, AMD Ryzen AI processor, local inference, messaging integrations), and business model (no-subscription, one-time purchase) from. The agent correctly cited these pages in its Sources section.
- ›The site does not publish pricing on any standard location (/pricing returned 404 at step [3]). The agent had to acknowledge this gap explicitly in its final response ('I could not find the actual device price anywhere') rather than inferring from fetched content—a key signal that the site does not expose this critical evaluation factor.
- ›The site's heavy reliance on client-side rendering (Next.js with truncated responses showing <4400 characters of boilerplate HTML across multiple fetches) severely limits machine readability. The agent could not extract detailed agent specifications, timeline clarity, or competitive positioning statements—all present in the UI but not accessible through standard web fetching. The agent worked around this by assembling a coherent narrative from partial content and making one explicit disclosure about unavailable information (pricing).
- ›The agent's discovery path relied primarily on prior knowledge (13% per metadata) and prior artifact context (88%) rather than web search, indicating the site's public SEO/indexing presence is weak for comparative queries ('Aresto vs ChatGPT' searches returned unrelated results).
- ›The agent correctly identified the product's differentiation (hardware-first, local processing, agents with persistent state, one-time purchase vs. subscription) from fragments across multiple pages, showing the core positioning IS present—but scattered and not consolidated in a comparison or executive summary.
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 →