ayanworks.com
success
Claude Code
intent

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

18steps
75.1sduration
$1.0163cost
77,385tokens
26 steps8 reasoning steps8 searches
home
docs
docs
search
search
/about-us
home
home
search
search
/products
/sovio
search
/products
search
/services
search
search
80%
on-site discovery
50%
reliability
20%
link following
path origin
  • previous resource20%
  • web search20%
  • prior knowledge60%
insight

The agent assembled a comprehensive explanation of AyanWorks by combining successful fetches of the company's main pages with web search results, but had to work around the absence of public pricing information and incomplete feature differentiation on the site itself. Direct fetches of the homepage, products page, and services page yielded metadata and partial content, while search-backed discovery was needed to validate product names (CREDEBL, Sovio) and real-world deployments; the site's inaccessibility on first attempt forced reliance on search routing. The final answer is substantially complete on *what* they do and *who* it's for, but pricing and competitive differentiation remain fragmentary due to site gaps.

  • ›Step [8] (about-us) and [14] (homepage) returned only metadata and truncated HTML; full page content was not accessible in fetched responses, forcing the agent to rely on search result snippets and prior knowledge to synthesize understanding.
  • ›Step [16] (products page) confirmed the two product lines (CREDEBL and Sovio) exist but returned truncated content—no pricing tiers, feature matrices, or deployment models were exposed in the actual fetch response.
  • ›Step [17] (services page) redirected to the homepage, suggesting poor internal navigation or URL structure; the agent had to guess this route and recover from it.
  • ›Steps [1], [2], [3], [9], [10] all failed with fetch errors on direct guesses (/, /pricing, /about, /products, /sovio), indicating the site either has strict access controls, uses client-side rendering that breaks plain fetches, or uses inconsistent URL routing—the agent succeeded only by finding working URLs via search results.
  • ›Real-world deployment information (Bhutan, Papua New Guinea) and competitive context were obtained from search results [20], not from site content; the site does not expose case studies or market positioning in a machine-readable form.
  • ›Step [21] (CREDEBL.id) was successfully fetched but returned Next.js boilerplate markup with no meaningful content in the response snippet; the separate product domain is inaccessible to content extraction.
  • ›The agent explicitly flagged pricing as a 'MAJOR GAP'—this is a critical discovery-layer and payments-layer miss on the site's part; no public pricing exists, requiring direct contact.
  • ›The site's positioning is clear at the metadata level (meta descriptions, OG tags) but product differentiation (CREDEBL vs. Sovio) is left implicit; the agent had to infer from context that one is open-source and one is commercial.

Help the next agent finish on ayanworks.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 →
© 2026 era labs