kinly.dk
success
Claude Code
intent

What does kinly.dk do and who is it for? Explain it back to me.

12steps
33.9sduration
$0.3162cost
100,312tokens
18 steps6 reasoning steps
home
docs
docs
/features
llms.txt
/om-os
/ydelser
/projekter
/cms
/seo
/projects
/portfolio
100%
on-site discovery
58%
reliability
75%
link following
path origin
  • previous resource75%
  • prior knowledge25%
insight

The agent successfully gathered comprehensive information about Kinly by discovering and parsing the llms.txt file, which contained structured, machine-readable details about the company's services, pricing, and positioning. The site's navigation structure required guessing Danish URL paths (/om-os, /ydelser, /projekter, /cms, /seo) rather than relying on visible site navigation, but the llms.txt artifact provided a complete reference that enabled the agent to validate those paths and answer all core questions about what Kinly does, who they serve, how they price, and what differentiates them.

  • ›Step [7] (llms.txt) was the primary content source—it explicitly listed Kinly's positioning ('lille dansk webbureau'), target verticals ('salon og skønhed, restaurant og café'), and clarified which Kinly this was (distinguishing kinly.dk from kinly.com and kinly.org.uk). This single file answered ~70% of the task directly.
  • ›Steps [11–16] fetched Danish-language pages (/om-os, /ydelser, /projekter, /cms, /seo) but were rendered as React/Next.js HTML bundles with truncated content, revealing no usable text in the trajectory. The agent relied on these being reachable (200 status) to validate the structure mentioned in llms.txt, but did not actually extract content from them—they served as route confirmation rather than content sources.
  • ›The site does not expose pricing, service details, or company information in conventional navigation or English-language pages; the agent discovered these only through prior knowledge of llms.txt convention and by successfully guessing Danish URL slugs. The site is not naturally navigable for English-speaking agents or those without structured metadata discovery.
  • ›The agent's final answer included specific pricing tiers (3,997 DKK, 4,997 DKK, etc.) and feature details (Next.js, TypeScript, Tailwind, 'Panelet' CMS) that appear verbatim in the llms.txt response at step [7], confirming that file as the authoritative source for the domain's positioning and commercial model.
  • ›Attempted common routes like /pricing, /about, /features, /projects, /portfolio all returned 404s, indicating no conventional English-language discovery surface; the site is effectively opaque without either Danish language skills or knowledge that llms.txt exists.

See every agent that visits kinly.dk

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 →