here-be-dragons.ai
partial
Claude Code
intent

What does here-be-dragons.ai do and who is it for? Explain it back to me.

18steps
84.9sduration
$1.1206cost
212,137tokens
26 steps8 reasoning steps9 searches
home
/mission
docs
/work
/transparency
/contact
search
/login
search
search
search
/api
search
search
search
docs
search
search
100%
on-site discovery
78%
reliability
67%
link following
path origin
  • previous resource67%
  • prior knowledge22%
  • other11%
insight

The agent could not fully satisfy the task due to client-side rendering and member-only access barriers. It assembled a partial understanding from web search results and prior knowledge, identifying the organization as a new Austrian nonprofit focused on responsible AI, but could not access or retrieve public pricing, complete service details, or meaningful differentiation from alternatives. The site's navigation structure was discoverable, but substantive content remained behind authentication.

  • ›Steps [1]–[6] and [9] returned only HTML shells with JavaScript placeholders—no rendered content about mission, work, pricing, or membership structure. All pages were 200 OK but functionally empty to the agent.
  • ›Step [11] (search result snippet) and step [24] (LinkedIn link) provided the only usable facts: organization name, Austrian nonprofit status (Verein für verantwortungsvolle Mensch-Maschine-Zukünfte), location (Dornbirn), and founding date (July 6, 2026). These came from search metadata and prior knowledge, not from the site's own publicly rendered content.
  • ›The agent correctly identified that core content (Work, Mission, About pages) exists but would not load, and that membership-gated 'Dragonbook' feature prevents outsider visibility into services, pricing, and audience targeting. No public pricing, tier structure, or service catalog was published in any fetchable format.
  • ›Site design choice: membership-first model with client-side rendering means discovery-layer content (differentiation, value prop, pricing) is not machine-readable or statically published. The agent had to rely on inferences and web search rather than primary sources.
  • ›Agent attempted multiple strategies (direct fetch, search with site: operator, filetype query, API endpoint guess) but exhausted all accessible routes. The site is not agent-ready for the discovery-evaluation task without either static documentation or an accessible content API.

Help the next agent finish on here-be-dragons.ai

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 →