quitory.app
partial
Claude Code
intent

What does quitory.app do and who is it for? Explain it back to me.

18steps
106.4sduration
$1.4054cost
240,352tokens
24 steps6 reasoning steps11 searches
home
docs
/features
docs
search
search
search
search
home
search
search
/sites/redxcdgpx90dbdo…
/sites/redxcdgpx90dbdo…
search
search
search
search
search
100%
on-site discovery
57%
reliability
86%
link following
path origin
  • previous resource86%
  • prior knowledge14%
insight

The agent gathered substantial information about Quitory's core purpose, target audience, and differentiation from alternatives by extracting content from the homepage and Framer search index, but was unable to locate complete pricing information despite multiple search and fetch attempts. The site's lack of traditional navigation pages (pricing, features, about all returned 404s) forced the agent to rely on the homepage and search index fragments, making pricing discovery incomplete and platform availability ambiguous.

  • ›Steps [1] and [11] (homepage fetches) returned the meta description and core positioning: Quitory is a craving-intercept tool for quitting vaping/ZYN/smoking with a free SOS tool, trigger tracking, and a sci-fi narrative wrapper. This formed the foundation of the 'What it Does' section.
  • ›Steps [14] and [16] (Framer search index JSON) contained indexed page titles and descriptions including references to CBT/WHO guidance and a '365-day mission arc' that implied paid content, but the actual pricing details were cut off or not fully populated in the accessible JSON.
  • ›The site's navigation structure is minimal or client-side-only: direct URL guesses to /pricing, /features, and /about all returned 404s, indicating the site is a single-page Framer app with routing not exposed via traditional URLs. The agent had to work around this by parsing Framer's internal search index instead of following discoverable links.
  • ›Web searches [6–22] were routing-only (they returned app store results for competitors, not Quitory itself), suggesting Quitory has limited public search presence and is either very new or not yet indexed in major app marketplaces. The agent could not confirm iOS/Android availability.
  • ›The homepage meta description was the primary content-bearing artifact; it explicitly named the three use cases (vaping, ZYN, smoking) and the SOS tool, making it agent-ready. However, pricing and platform details were not surfaced anywhere accessible, indicating either incomplete site content or a deliberate choice to gate that information.
  • ›The agent successfully synthesized differentiation (craving intercept vs. tracker, CBT/WHO backing, no shame on slip) from homepage copy and search index fragments, demonstrating the site does position its value proposition clearly — but only in those two places.

Help the next agent finish on quitory.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 →