gonet.at
success
Claude Code
intent

What does gonet.at do and who is it for? Explain it back to me.

20steps
70.7sduration
$0.9058cost
311,151tokens
21 steps1 reasoning step4 searches
home
home
/devices
/devices
/europe-travel
search
/packages
docs
docs
docs
/faq
/faq
search
/api
search
/review/gonet.at
search
/shop
/buy
/contact
94%
on-site discovery
63%
reliability
50%
link following
path origin
  • previous resource50%
  • web search6%
  • prior knowledge44%
insight

The agent partially satisfied the task by assembling a high-level overview of GoNet from fragmented homepage and structural pages, but worked around significant gaps in pricing transparency and feature depth. The site's heavy reliance on dynamic content loading, Arabic-first design, and absence of traditional pricing/shop pages made it difficult to extract concrete details — the agent filled these gaps with reasonable inferences and prior knowledge rather than discovered facts.

  • ›Content-bearing fetches returned only generic marketing copy and navigation structure (homepage, about, FAQ, devices page, regional travel bundles) — no explicit pricing tables, feature matrices, or plan details were machine-readable in the HTML responses.
  • ›The agent had to reverse-engineer pricing from a single search result URL (gonet.at/esim/sudan?lang=en showing $18.76) rather than from a published pricing page; /pricing, /packages, /shop, and /buy all returned 404s, suggesting the site may use a single-page app or checkout flow not exposed to web crawlers.
  • ›Site defaults to Arabic (lang=ar) with RTL rendering, then serves English via query parameter — this language-switching architecture is navigable but requires prior knowledge to discover English content; there is no language selector visible in fetched HTML.
  • ›The agent found no structured data (schema.org, JSON-LD) or agent-facing documentation in fetches; claims about 'lifetime validity,' 'unlimited data,' and '5 plan tiers' were inferred from marketing headlines and product page names (/Europe-Travel, regional eSIM pages) rather than explicit feature documentation.
  • ›Web search results (steps 9, 11, 14, 18) were routers that confirmed GoNet exists and provided context (Trustpilot link, competitor comparisons) but did not yield additional first-party GoNet pricing or feature details — the agent cited sources that it could not actually fetch due to access blocks (Trustpilot returned 403).
  • ›No FAQ, blog post, or help article within the fetches explained pricing model, plan tiers, data allowances, or competitive differentiation in machine-readable form; the final answer relies heavily on reasonable extrapolation and comparison-by-absence to competitors.

Help the next agent finish on gonet.at

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 →