qasa.com
success
Claude Code
intent

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

11steps
61.6sduration
$0.8533cost
106,272tokens
14 steps3 reasoning steps7 searches
home
search
/se/en/how-it-works
search
search
docs
docs
search
search
search
search
25%
on-site discovery
0%
reliability
0%
link following
path origin
  • web search75%
  • prior knowledge25%
insight

The agent successfully assembled a comprehensive explanation of Qasa by working around the direct website's inaccessibility (Cloudflare blocks), relying entirely on web search results and prior knowledge to answer all four questions (what they do, who it's for, pricing, and differentiation). The site itself was not navigable—direct fetches returned 429/403 errors—but publicly available support docs and third-party comparisons surfaced in search results provided sufficient content to satisfy the task.

  • ›All content came from search results (steps [3], [5], [6], [9], [10], [11], [12]) and prior knowledge (75% web search + 25% prior knowledge per the metadata). Direct website access was blocked in steps [1] and [4], forcing complete reliance on indexed/cached content.
  • ›Search snippet results themselves contained the critical information: pricing details (2.49-4.98% tenant fee, free for landlords), rent guarantee features, deposit-free options, and company history (founded 2014, acquired by Blocket 2019, operates in Scandinavia). The agent did not successfully fetch any primary Qasa pages.
  • ›The agent explicitly cited search-discovered support articles in the final Sources section (e.g., 'What does it cost for landlords?', 'Guaranteed rent information'), indicating these URLs were the core content sources, though the fetches themselves returned 403 errors when attempted directly in steps [7] and [8].
  • ›Third-party comparison and research platforms (Dealroom, Crunchbase, Tracxn, expatriate.se blog, Similarweb) provided the competitive differentiation and market positioning claims, suggesting these sites are the primary machine-readable surface for Qasa positioning.
  • ›The site's bot-blocking posture (Vercel/Cloudflare checkpoints) meant the agent could not verify current information directly and had to flag gaps: 'Specific details about current geographic coverage', 'what happens to the tenant service fee exactly', and recent business model changes post-Blocket acquisition.

See every agent that visits qasa.com

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 →