institute.aero
success
Claude Code
intent

What does institute.aero do and who is it for? Explain it back to me.

10steps
71.6sduration
$0.4822cost
52,898tokens
12 steps2 reasoning steps3 searches
home
home
/en/services
docs
search
search
search
docs
institute.home
/en
80%
answer from your site
43%
answer efficiency
67%
followed site links
answer sources
  • from this site80%
  • from agent knowledge20%
url discovery
  • given in the task14%
  • followed a link57%
  • found via web search29%
insight

Agent successfully assembled a coherent explanation of institute.aero's mission, audience, and donation model by fetching the Polish foundation's homepage and English-language landing page. The site published most core positioning directly, but lacked service details, discrete pricing, case studies, and competitive comparisons—gaps the agent identified transparently rather than filling with unsupported claims.

  • ›Steps [1] and [10] (homepage fetches in Polish and English) were the primary content sources; they directly supplied the foundation's self-description, service areas, target segments, and donation tiers. No external fetches or searches were cited in the final answer, indicating the site's own pages contained the needed substance.
  • ›The agent correctly distinguished between the Polish foundation (institute.aero) and unrelated organizations surfaced by generic aviation searches (steps [5]–[7], ASI-Institute, AIAA, Lukasiewicz ILOT). This required following domain-specific links and using narrow searches; the site itself was not discoverable via broad aviation terms.
  • ›Pricing was transparently published on the English landing page ([10]) in a non-traditional form (donation tiers, tax-deductibility)—fully fetchable and not hidden. The agent accurately reported it without speculation.
  • ›The agent explicitly called out what it could NOT find: no discrete service pricing, case studies, governance details, or competitor comparisons. These absences were site gaps, not research failures; the agent did not fill them with model memory.
  • ›The site required the agent to piece together its positioning from general sections rather than navigate to a dedicated 'services' or 'about' page; attempts to fetch institute.aero/en/services and institute.aero/pricing both returned 404, forcing reliance on homepage content.

See every agent that visits institute.aero

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 →