uely.ch
success
Claude Code
intent

What does uely.ch do and who is it for? Explain it back to me.

11steps
38.6sduration
$0.0817cost
92,881tokens
17 steps6 reasoning steps1 search
home
/en
docs
docs
llms.txt
/preise
/funktionen
/ueber-uns
/uely-vs-barto
search
docs
100%
on-site discovery
80%
reliability
70%
link following
path origin
  • previous resource70%
  • prior knowledge30%
insight

The agent assembled a reasonably complete overview of Uely-3000 by combining direct fetches from the homepage, the llms.txt artifact, and multiple pages from get.uely.ch and docs.uely.ch. However, the site's information architecture forced the agent to work around incomplete or inaccessible content: pricing specifics remain vague, feature details were not fully retrieved, and the agent had to rely on prior knowledge and inferred connections to construct a coherent narrative. The site publishes its core positioning well (AI workspace + Swiss farm marketplace), but details on pricing tiers, competitive positioning, and operational mechanics are fragmented across multiple subdomains and behind pages that were fetched but not fully readable.

  • ›Step [7] (llms.txt) was the critical discovery resource — it clearly articulated the dual mission (workspace + marketplace), target audience, and tech stack, and the agent cited it explicitly. This artifact is agent-friendly and functioned as a north star.
  • ›Pricing information exists (step [10], get.uely.ch/preise) but the response was truncated; the agent could not extract the actual tier table and had to note only that 'pricing page exists' and 'starts at 20 CHF/month' without full detail. This is a content accessibility gap, not a discovery gap.
  • ›The agent discovered comparison content (step [15], uely-vs-barto) and feature lists (step [11]) but neither was fully readable from the trajectory; the agent had to assemble positioning from fragments and logical inference rather than from a single, complete positioning document.
  • ›The site has a three-subdomain structure (uely.ch, get.uely.ch, docs.uely.ch) with incomplete internal linking; the agent had to guess and infer URLs rather than follow breadcrumbs, indicating weak internal navigation for agent discovery.
  • ›The English-language homepage (step [3]) was available but the agent's richer findings came from German-language pages (preise, funktionen, ueber-uns), suggesting content depth varies by language.
  • ›Documentation (step [14], docs.uely.ch/en/geld/gebuehren) was fetched and cited but the agent notes it could not fully access payment mechanics, indicating either truncation or complex page structure that resisted machine reading.

Help the next agent finish on uely.ch

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 →