jiddu.app
partial
Claude Code
intent
What does jiddu.app do and who is it for? Explain it back to me.
17steps
98.4sduration
$1.3933cost
173,195tokens
21 steps4 reasoning steps12 searches
home
docs
docs
search
search
search
docs
search
/dashboard
search
search
search
search
search
search
search
search
100%
on-site discovery
60%
reliability
60%
link following
path origin
- previous resource60%
- prior knowledge40%
insight
The agent gathered substantial information about Jiddu's core functionality, target audience, and competitive positioning by analyzing the homepage and pricing page, but could not retrieve specific pricing details because the site uses client-side JavaScript rendering that prevents standard web fetching from accessing dynamically loaded content. The agent compensated by conducting multiple web searches and drawing on prior knowledge, ultimately delivering a comprehensive overview of the product with a documented gap in pricing transparency.
- ›Steps [1] and [3] (homepage and pricing page) returned identical HTML shells with only meta tags and Next.js boilerplate visible—the actual content (features list, pricing tiers, calls-to-action) is rendered client-side and not present in the raw response. This is the core barrier to answering the task completely.
- ›The agent inferred most product details (fallacy detection, fact-checking, bias detection, academic paper analysis, live conversation monitoring) from prior knowledge and the page title/meta description ('Read anything with a critical mind'), not from content extracted in the successful fetches. The fetched responses themselves contained no substantive feature or positioning information.
- ›The pricing page (step [3]) was fetchable (HTTP 200) but empty of pricing data, making it impossible to answer the 'how it's priced' question despite direct navigation. Web searches (steps [8], [10], [12], [17], [18]) for pricing also returned no results with actual dollar amounts or tier details, confirming the information is either behind authentication or fully dynamic.
- ›The site's Next.js architecture and client-side rendering is a significant agent-readiness problem: critical pages are structurally accessible but informationally inaccessible to non-browser fetchers. No fallback (structured data, API, static pricing table, downloadable PDF) was evident.
- ›The agent did not find team/founder information, privacy policies, user reviews, or free tier specifics in any fetch or search, indicating these are either absent from public-facing content or similarly hidden behind dynamic rendering.
Help the next agent finish on jiddu.app
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 →