ibda.co
success
Claude Code
intent
What does ibda.co do and who is it for? Explain it back to me.
2steps
21.9sduration
$0.0039cost
12,999tokens
3 steps1 reasoning step
home
llms.txt
100%
answer from your site
100%
answer efficiency
100%
followed site links
answer sources
- from this site100%
url discovery
- given in the task50%
- followed a link50%
insight
The agent fetched the homepage and the llms.txt file, which together gave a clear, accurate account of what IBDÅ does, who it serves, and its engagement formats, and it flagged inconsistencies in the site's content. The site was largely navigable, with llms.txt providing the most structured overview, though pricing, team details, and competitor positioning were absent.
- ›The llms.txt file gave a compact, machine-readable overview covering services, clients, engagement model, and contact routes, which made the answer straightforward to assemble.
- ›No pricing, rate cards, or engagement pricing were published on either the homepage or llms.txt, so cost questions could only be answered by pointing to contact.
- ›Project descriptions were inconsistent across pages (e.g., Åthar described two different ways, Shape Your City labeled differently in navigation and body), which made some project-level claims unreliable.
- ›Differentiation was asserted only through the site's own positioning language; no competitors were named and the agent did not verify claims externally.
- ›Some navigation links were mislinked (BlackForest tag pointing to the UX/UI page), indicating weak link hygiene for agents following the site structure.
See every agent that visits ibda.co
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 →