kvanta.com
success
Claude Code
intent
What does kvanta.com do and who is it for? Explain it back to me.
9steps
34.8sduration
$0.3130cost
68,118tokens
14 steps5 reasoning steps1 search
home
docs
docs
/en
/sv
/en/pricing
search
/en/investor-portfolio
/en/features
87%
on-site discovery
63%
reliability
50%
link following
path origin
- previous resource50%
- web search13%
- prior knowledge38%
insight
The agent successfully understood Kvanta's core offering, target market, and key differentiators by fetching the homepage and product pages, though it could not retrieve specific pricing amounts despite finding the pricing page. The site is well-structured with clear product messaging but required the agent to guess at URL patterns (e.g., `/en/pricing` after `/pricing` failed) and relied partially on prior knowledge to infer blockchain-based security claims that were not directly visible in the fetched HTML snippets.
- ›Step [1] (homepage) and step [5] (English homepage) provided the core value proposition and feature list via meta descriptions and page titles, establishing that Kvanta is a digital share ledger for unlisted companies managing cap tables, transfers, emissions, and option programs.
- ›Step [7] (pricing page) returned a 200 status but the agent could not extract specific pricing tiers or amounts from the HTML—indicating the pricing details are likely rendered client-side (JavaScript) and not accessible via static HTML fetch.
- ›Step [12] (investor portfolio page) confirmed a secondary product feature, showing the site has organized product sections but no obvious navigation map was provided in the fetches, forcing the agent to discover pages via search results and URL guessing.
- ›The agent inferred 'blockchain-based security' and 'BankID-signed authorization' as differentiators without explicit evidence in the fetched content—these claims likely come from prior knowledge or were embedded in JavaScript-rendered sections not captured in the static HTML response.
- ›The site defaults to Swedish and requires explicit `/en/` locale prefix for English content; standard guesses like `/pricing` fail without locale, requiring the agent to retry with locale awareness.
- ›No explicit competitor comparison, case studies, integration details, trial availability, or onboarding information was found despite the agent's attempts, indicating these are either not published on the public site or exist only in gated/JavaScript-rendered areas.
Help the next agent finish on kvanta.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 →