genstory.us
partial
Claude Code
intent

What does genstory.us do and who is it for? Explain it back to me.

17steps
116.8sduration
$1.2525cost
271,767tokens
33 steps16 reasoning steps10 searches
home
home
docs
/app
/partners
/contact
search
search
search
search
search
/privacy-policy
search
search
search
search
search
86%
on-site discovery
57%
reliability
43%
link following
path origin
  • previous resource43%
  • web search14%
  • prior knowledge43%
insight

The agent gathered a usable but incomplete understanding of GenStory by combining limited content from the website's homepage and partner/contact pages with external web search results. While it successfully identified GenStory's core offering (location-triggered video tours via QR codes), target audiences (cities and tourists), and competitive positioning, it could not find critical details like individual pricing, active tour locations, or consumer experience flow because the website itself does not expose these in accessible, public-facing pages.

  • ›Steps [1] and [3] returned the homepage HTML, which contained meta descriptions but the agent could not extract full page content from the truncated responses. The homepage tagline ('Cinematic city tours & the locals worth finding') and meta description were the only concrete site-sourced facts about what GenStory does.
  • ›Steps [8] and [9] (partners and contact pages) surfaced business model hints (custom partnerships, affiliate commission structure) but no pricing tiers or location examples. These pages exist but contain minimal detail relevant to the discovery task.
  • ›The agent relied heavily on web search (steps [11]–[31]) to fill gaps because genstory.us itself does not publish pricing, customer examples, available locations, or detailed consumer flow. Critical gaps (individual tour cost, which cities are live, app vs. browser UX) remain unfilled despite 7 targeted searches.
  • ›The site is B2B-focused and appears to gate detailed information behind a contact form; public pages are sparse and marketing-light, making it difficult for an agent to assemble a complete picture without human intervention or direct partnership inquiries.
  • ›The agent did not access the actual contact form submission or receive a response, and no FAQ, blog, or detailed resource pages were discoverable or fetched, limiting the depth of the final answer.

Help the next agent finish on genstory.us

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 →