getaster.co
success
Claude Code
intent
What does getaster.co do and who is it for? Explain it back to me.
5steps
51.8sduration
$0.3521cost
22,929tokens
7 steps2 reasoning steps1 search
home
home
home
home
search
67%
answer from your site
100%
answer efficiency
100%
followed site links
answer sources
- from this site67%
- from search results17%
- from agent knowledge17%
url discovery
- given in the task25%
- followed a link75%
insight
The agent successfully synthesized Aster's positioning, pricing, and core features from the site's homepage (fetched multiple times), then augmented with third-party competitor research to contextualize differentiation. The site was minimally navigable—all content came from the homepage; no internal links were followed, and the agent had to infer gaps (team, privacy details, comparative positioning) from absence rather than discovery.
- ›All site content originated from repeated homepage fetches (steps [1–4] retrieved the same URL three times), indicating the site lacks internal navigation or deep pages; the agent accessed only one page from the target domain.
- ›Steps [1–4] are duplicative fetches of the same URL, suggesting the agent was cycling through cached or identical responses rather than following links—75% of URLs were claimed to be 'followed from a fetched page,' but no child links appear in the trajectory, indicating heavy reliance on model memory to reconstruct answers from a single source.
- ›Pricing, features, and audience data were present on the homepage but fragmented across multiple fetch responses; the agent reassembled them into coherent sections, a sign the site publishes information but not in a single consolidated resource.
- ›The site provided no team, founding, privacy, or competitive comparison data; the agent filled this gap by conducting an external web search (step [5]) and citing third-party sources in the final response, signaling the site's incompleteness for a full evaluation task.
- ›Portuguese-language content mixed with English on the homepage was noted in the final response, but no language-selection mechanism or localization path was mentioned, indicating limited site discoverability for non-Portuguese speakers or agent language negotiation.
See every agent that visits getaster.co
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 →