zavu.dev
success
Claude Code
intent

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

6steps
37.0sduration
$0.3575cost
43,434tokens
11 steps5 reasoning steps2 searches
home
docs
docs
search
docs
search
75%
on-site discovery
100%
reliability
50%
link following
path origin
  • previous resource50%
  • web search25%
  • prior knowledge25%
insight

The agent successfully assembled a comprehensive explanation of Zavu by combining fetches from the main site, pricing page, and documentation with web search results. However, the site's JavaScript-heavy architecture meant the agent could not directly extract complete details from page content and had to rely heavily on search snippets and prior knowledge to fill gaps, leaving some specifics (exact pricing tiers, agent runtime features, carrier-specific costs) only partially clarified.

  • ›Steps [1], [3], [4] returned HTML that was too JavaScript-rendered to be fully parsed; the agent could not extract structured content directly from these fetches, forcing reliance on search results and prior knowledge for core details.
  • ›Steps [6] and [9] (web searches) were the primary content-bearing sources, providing search snippet previews and URLs to comparison pages (vs. OpenAI, MessageBird) that the agent cited explicitly; the search results bridged gaps the direct fetches could not fill.
  • ›Step [8] (docs.zavu.dev/introduction) was fetched but appears not to have yielded usable content; no specific information from this fetch appears in the final answer, suggesting the documentation page also relies heavily on client-side rendering.
  • ›The agent successfully identified core positioning (unified API, multi-channel messaging, AI-focused) and pricing model (MAU-based, starting $20–25/month) but acknowledged three specific areas it could not confirm: exact pricing tier details, agent runtime capabilities, and country-specific carrier costs.
  • ›The site publishes comparison pages (vs. competitors) and pricing pages, but these are not directly machine-readable without JavaScript execution; the agent had to infer differentiation from search snippets rather than canonical product comparison tables.

Help the next agent finish on zavu.dev

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 →