minimal.apply.agency
success
Claude Code
intent
What does minimal.apply.agency do and who is it for? Explain it back to me.
16steps
52.0sduration
$0.5902cost
177,185tokens
24 steps8 reasoning steps2 searches
home
home
/ydelser/portaler-og-s…
/ydelser/ai-der-kan-ha…
/priser
sitemap
sitemap
/om
/ydelser/drift-og-vide…
/ydelser
search
/cases/brunata
/cases
search
llms.txt
/om/nyheder
100%
on-site discovery
93%
reliability
86%
link following
path origin
- previous resource86%
- prior knowledge14%
insight
The agent successfully gathered enough information to explain Apply's core offerings, target audience, and positioning, but had to work around a significant gap: pricing information is not published on the site. The agent assembled its answer primarily from service pages, case studies, the llms.txt file, and the about page—all directly fetched and content-bearing. The site is moderately navigable for discovery but incomplete for commerce/pricing visibility.
- ›Steps [5], [6], [12], [13] returned service descriptions that form the backbone of the answer ('Portaler & Selvbetjening', 'AI, der kan handle', 'Drift & Videreudvikling'). These pages are sparse but sufficient for understanding the three service pillars.
- ›Step [21] (llms.txt) was the single most agent-ready resource—it condensed the company mission, legal details, and service offerings in machine-readable form and was explicitly cited as a reference.
- ›Step [11] (about page) and step [15] (case study: Brunata) provided qualitative positioning ('Rar, Dygtig, Flittig') and concrete examples of client work, which the agent used to explain differentiation.
- ›Pricing is completely absent: step [7] (guessed /priser) returned 404, and the agent found no alternative pricing page in the sitemap or elsewhere. The agent had to explicitly call this out as missing rather than answer from the site.
- ›The site is Danish-first: 86% of fetches came from prior knowledge (direct URL guessing based on common patterns) rather than discovered navigation. The agent did not find an English version link or language switcher mentioned in the returned HTML snippets.
- ›The agent did not need to search the web to answer the task—both web searches (steps [16], [19]) returned unrelated results and were not cited in the final response, indicating the site's own content was sufficient for the discovery-evaluation intent.
Help the next agent finish on minimal.apply.agency
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 →