jundiworks.com
partial
Claude Code
intent
What does jundiworks.com do and who is it for? Explain it back to me.
16steps
68.8sduration
$0.8461cost
245,144tokens
26 steps10 reasoning steps5 searches
home
/birth
search
docs
docs
/faq
/chart
/teaching
/natal
/natal
search
search
/profile
search
/astro
search
100%
on-site discovery
73%
reliability
73%
link following
path origin
- previous resource73%
- prior knowledge27%
insight
The agent explored jundiworks.com and assembled a partial understanding of what the platform does (Bazi/Chinese astrology chart reading with educational features), who it's for (Chinese-speaking astrology users), and its design philosophy, but could not locate pricing information despite multiple attempts. The site lacks standard business pages (pricing, about, FAQ all returned 404), forcing the agent to infer most positioning from navigable pages and prior knowledge rather than published documentation.
- ›Steps [1], [3], [10], [11], [12], [14], [19], [22] returned HTML scaffolds for pages like /natal, /chart, /teaching, /profile, /astro, but all responses were truncated (4400+ chars cut off), meaning the agent never received full page content that would contain pricing, feature details, or call-to-action elements.
- ›The agent discovered site structure and purpose through navigation links and prior knowledge inferred from Chinese domain language ('灵图计划', 'Inner Contour Project', Bazi references), not from published metadata or structured data—no SEO tags, schema markup, or machine-readable pricing were apparent in the truncated responses.
- ›Standard SaaS discovery pages (/pricing, /about, /faq) returned 404 errors [steps 6, 7, 8], indicating the site either has a minimalist architecture or uses a single-page app that returns different content client-side. The agent could not retrieve pricing, company background, or alternative comparison from any page.
- ›Web searches [4, 16, 17, 20, 24] were unproductive—they either matched the wrong domain (justworks.com payroll), returned generic astrology competitors, or found only the homepage reference. No third-party pricing aggregators, reviews, or documentation indexed the service.
- ›The agent relied heavily on prior knowledge (27% of fetch sourcing) and previous artifacts (73%) to construct its answer, indicating the website itself published minimal actionable content in fetched form—the user flow appears to require account creation or birth chart entry to access pricing.
Help the next agent finish on jundiworks.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 →