alpius.studio
success
Claude Code
intent
What does alpius.studio do and who is it for? Explain it back to me.
5steps
39.9sduration
$0.2459cost
22,230tokens
8 steps3 reasoning steps
home
home
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 task20%
- followed a link80%
insight
The agent successfully gathered what Alpius.studio does, who it serves, and how it differs from alternatives, but hit a wall on pricing transparency and technical specifics. The site is moderately navigable for portfolio review but deliberately opaque on pricing and methodological details, forcing the agent to assemble conclusions from fragmented marketing copy and work backward from absence.
- ›All fetches returned the same homepage URL (typed from memory, not surfaced by site navigation); the agent made no progress following internal links. The trajectory shows 5 tool_call steps, all targeting alpius.studio/ with identical HTTP 200 responses, suggesting either shallow site structure or that the agent was re-fetching the same page rather than exploring deeper.
- ›Pricing information is genuinely absent from the site—step [3] explicitly confirms 'no pricing information is listed' and directs to email contact. This is a real gap, not an agent failure, and the final response correctly flags this as a constraint on the buyer's decision process.
- ›The site publishes no technical documentation of tools, AI techniques, or case studies. The agent's 'Confusing or Missing Elements' section (drawn from model memory applied to site absence) correctly identifies that differentiators are positioning-driven rather than substantively explained—e.g., 'scalable pipelines' is asserted but never defined with examples or metrics.
- ›The agent's final response accurately reflects site content where it exists (portfolio categories, end-to-end approach, social proof) but acknowledges gaps (Higgsfield role unexplained, no tool/model specifics, no ROI data) by calling them out rather than filling them from model memory. This is appropriate boundary-setting.
- ›The site is not agent-optimized for this task: no pricing page, no FAQ, no structured comparison, no embedded metadata. The agent reconstructed the answer from repeated fetches of the same homepage and then filled in analytical gaps (competitive positioning, absence of case studies) via reasoning, not retrieval.
See every agent that visits alpius.studio
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 →