mylittlebun.com
success
Claude Code
intent
What does mylittlebun.com do and who is it for? Explain it back to me.
21steps
100.0sduration
$1.2388cost
296,921tokens
35 steps14 reasoning steps10 searches
home
docs
/en
search
search
search
sitemap
/en/create
/en/digital-vs-paper-g…
/en/long-distance-gend…
search
/fr/create
/how-it-works
robots.txt
/en/faq
search
search
search
search
search
search
100%
on-site discovery
73%
reliability
64%
link following
path origin
- previous resource64%
- prior knowledge36%
insight
The agent partially satisfied the task by assembling an explanation of My Little Bun's core offering (digital gender reveal scratch cards, free, interactive, shareable via link), target audience, and positioning against alternatives. However, the site's heavy client-side rendering prevented the agent from accessing detailed pricing tiers, feature breakdowns, company info, or business sustainability details—gaps the agent explicitly called out. The agent had to rely on URL structure hints (sitemap, robots.txt) and guesswork rather than published documentation.
- ›The sitemap [12] confirmed the site's URL structure (/en/create, blog posts on digital vs. paper reveals, long-distance reveals) but returned no human-readable content; all pages were Next.js skeletons with JavaScript-rendered bodies that the agent could not parse.
- ›The agent inferred the product's existence and purpose entirely from URL slugs and headings it guessed from prior knowledge (e.g., /en/create, /en/digital-vs-paper-gender-reveal-scratch-cards) rather than from fetched HTML content, which suggests the site does not publish machine-readable positioning or feature lists in its HTML.
- ›Web searches [7, 9, 10, 19, 24, 26, 28, 29, 31, 33] returned no direct mentions of My Little Bun, no reviews, no Product Hunt launch, no Reddit/Twitter presence—indicating either a very new or very niche product with minimal online footprint. The agent had to synthesize its answer from inferred URLs and generic knowledge of the gender reveal category.
- ›The agent could not access FAQ, pricing page, terms, privacy policy, or about pages—critical business details—because either the site does not publish them or they are fully client-rendered and not indexable. This left gaps on link persistence, revenue model, data handling, and company identity.
- ›The free pricing claim appears to be inferred from repeated URL slug patterns (e.g., 'Free, no app, no account needed') rather than from fetched content, suggesting the agent may be assembling text from prior knowledge of competitors or the site's marketing copy rather than from the actual HTML responses.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →