ora
fenra.is
partial
Claude Code
intent

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

19steps
84.1sduration
$1.3768cost
225,289tokens
31 steps12 reasoning steps10 searches
home
search
docs
docs
search
/store/apps/details
search
docs.home
search
search
search
search
search
search
/en
/demo
/contact
search
home
67%
on-site discovery
44%
reliability
33%
link following
path origin
  • previous resource33%
  • web search33%
  • prior knowledge33%
insight

The agent gathered a partial understanding of Fenra by assembling fragments from the Icelandic homepage metadata, a Google Play Store listing, and a separate fenra.world site, but could not access pricing, detailed features, or comparative positioning because the main site is a JavaScript SPA with no statically rendered content and no English-language marketing pages. The site itself proved largely opaque to machine crawling; the agent relied heavily on prior knowledge and guesswork to construct an answer.

  • Step [1] (fenra.is/) returned only HTML metadata in Icelandic (title: 'Fenra. - Gæðastjórnun og verkstaðsskráning fyrir íslensk byggingarteymi'; meta description: managing projects, logbooks, time tracking, drawings, documents, quality systems, building manual). This was the only direct content from the actual domain; the agent extracted the core feature list and target market from this single source.
  • Step [10] (Google Play Store) was the most useful external source but returned truncated HTML; the agent could not extract pricing, reviews, or detailed feature descriptions from the fetch. The agent cited this as a source but admitted it did not resolve pricing or comparison questions.
  • Step [29] (fenra.world) returned a Squarespace landing page (truncated in response). It was a different domain entirely, suggesting a separate brand or product line, and did not clarify the relationship to fenra.is. The agent did not cite this in the final response, indicating it was not content-bearing.
  • The site is a single-page JavaScript application that returns the same HTML shell for most paths (all 404 attempts like /pricing, /about, /en, /demo, /contact returned identical HTML to the homepage). This architecture makes it impossible for an agent to discover pricing, company information, or detailed feature pages without executing JavaScript or being logged in.
  • No structured data (Schema.org, JSON-LD), public API documentation, or robots.txt hints were present. The agent had to rely on web search to find the Google Play listing, which was the only external reference point; the site itself contains no outbound links or SEO metadata to guide discovery.
  • All search queries for pricing, comparisons, and detailed feature descriptions returned generic construction software results, not Fenra-specific content. The site has minimal public presence and no indexed marketing pages in English, suggesting it is a hyper-local product for the Icelandic market with limited discoverability.
  • The agent's final answer repeatedly flags gaps ('⚠️ I couldn't find pricing information', 'I couldn't find explicit comparisons') and recommends direct contact with the company, indicating the site fails to publish decision-critical information in a machine-readable or web-accessible form.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →