promptkit.app
success
Claude Code
intent

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

6steps
34.8sduration
$0.2813cost
54,908tokens
10 steps4 reasoning steps1 search
home
docs
/features
search
/us/app/promptkit-ai-h…
/detail/promptkit/iiab…
60%
on-site discovery
60%
reliability
40%
link following
path origin
  • previous resource40%
  • web search40%
  • prior knowledge20%
insight

The agent successfully assembled a comprehensive overview of PromptKit by working around an inaccessible main website — the homepage and routing pages (pricing, features) all returned 404s or generic 400-char truncations. Instead, the agent relied on web search to discover App Store and Chrome Web Store listings, which contained the bulk of actionable product information. The site's own domain proved largely non-navigable for machine extraction, forcing the agent to triangulate understanding from third-party app storefronts.

  • ›The main website (promptkit.app/) returned HTML but was truncated in the fetch response and did not expose the information needed to answer any of the four task requirements (what it does, who it's for, pricing, differentiation). Attempts to navigate to /pricing and /features returned 404 errors, indicating either missing routes or a single-page app that serves all content from root.
  • ›Step [6] (web search) was the critical pivot: it surfaced App Store and Chrome Web Store links that actually contained structured product metadata, pricing tiers, category tags, user reviews, and platform availability — information the official site did not expose in a machine-readable form.
  • ›Steps [7] and [8] (App Store and Chrome Web Store) provided the foundation for the final answer: app descriptions, feature lists, subscription pricing ($19/month on iOS), multi-platform support, and category positioning. These third-party storefronts were the only sources that yielded complete, parseable product information.
  • ›The agent had to invoke prior knowledge and inference to fill gaps: explicitly noting that pricing structure was unclear, that the site lacked a visible pricing page, and that subscription vs. one-time purchase models were ambiguous across platforms. The final response lists this as a 'confusing' finding.
  • ›Site agent-readiness is low: no dedicated pricing page, no features page, homepage does not appear to expose product details in a way that survived the fetch. The agent succeeded despite the site, not because of it.

See every agent that visits promptkit.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 →