inled.es
success
Claude Code
intent

What does inled.es do and who is it for? Explain it back to me.

15steps
71.9sduration
$0.8229cost
199,803tokens
26 steps11 reasoning steps5 searches
home
office.home
start.home
/apps/seafari
/apps/droidtux
/apps/codexbar-gnome
/apps/ai-exporter
search
edge.home
/bastion
search
/inledgroup
search
search
search
80%
on-site discovery
100%
reliability
70%
link following
path origin
  • previous resource70%
  • web search20%
  • prior knowledge10%
insight

The agent successfully assembled a comprehensive overview of Inled Group by visiting their product landing pages and main site directly. The site is moderately navigable — product pages exist and are discoverable, but the company's business model, funding, team, and long-term sustainability are opaque or absent entirely. The agent had to piece together the story from individual product descriptions and fill gaps with external context (prior knowledge and web search) since the site does not publish a unified positioning statement or business model documentation.

  • ›Each product page (office.inled.es, start.inled.es, edge.inled.es, seafari, droidtux, etc.) returned structured metadata (title, description, price fields set to '0') that clearly communicated what the product does and that it is free, but these pages are siloed — there is no unified 'what is Inled' page that explains the company's vision, business model, or product ecosystem.
  • ›The site does not publish explicit business model, funding, team, or sustainability information anywhere the agent could fetch. The agent had to rely on inferences (all products marked price: '0', GitHub repository presence, no sponsorship/donation links found) and external web search to speculate about how they sustain themselves.
  • ›Individual product pages are well-optimized for discoverability (clear titles, descriptions, and feature headlines), but lack depth — DroidTux, for example, returned minimal setup or usage documentation. The site is agent-readable at the discovery level but thin on operational detail.
  • ›The agent successfully cited 9 fetches as sources, all of which were directly accessed product or company pages. No routing/search steps were cited, indicating the site's structure allowed direct navigation once URLs were guessed or inferred. The 70% fetch sourcing from previous artifacts suggests the agent had prior knowledge of Inled's product URLs.
  • ›Mixed-language pages (some Spanish, some English) and unclear maintenance status (e.g., Bastion Browser marked archived) created friction in understanding the full scope and health of the portfolio.

See every agent that visits inled.es

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 →