vaultgymnastics.com
partial
Claude Code
intent

What does vaultgymnastics.com do and who is it for? Explain it back to me.

26steps
101.2sduration
$1.4803cost
384,112tokens
39 steps13 reasoning steps11 searches
home
docs
home
/features
docs
/gyms
/for-gyms
/gyms
/software
search
/camps
search
search
search
docs
search
search
docs
search
search
/meets
/scores
/contact
search
search
search
93%
on-site discovery
60%
reliability
40%
link following
path origin
  • previous resource40%
  • web search7%
  • prior knowledge53%
insight

The agent assembled a partial but coherent picture of Vault Gymnastics by fetching the homepage and key section pages (/about, /gyms, /meets, /scores, /camps), discovering that it is a platform connecting gyms, meets, scores, and camps for youth gymnastics. However, the task was only partially satisfied: the agent could not find pricing information (all pricing-related pages returned 404s), could not articulate a clear business model, and could not meaningfully differentiate Vault from competitors based on site-accessible content. The site's heavy JavaScript rendering, sparse HTML, and lack of blog/resource/contact pages made it difficult to extract detailed feature specs or positioning without relying on prior knowledge and web search.

  • ›Steps [1], [5], [7], [15], [16], [17] returned successful 200 responses but with truncated HTML responses (4400+ chars truncated), indicating the agent could not fully parse the rendered page content—a byproduct of the site's Next.js architecture and client-side rendering.
  • ›The agent discovered the four main pillars (Gyms, Meets, Scores, Camps) by guessing conventional URL patterns (/gyms, /meets, /scores, /camps), not by following explicit site navigation—suggesting the homepage and nav structure did not clearly expose these sections in a machine-readable way.
  • ›Critical gaps were deliberately unavailable on the site: /pricing, /features, /blog, /contact, and /for-gyms all returned 404s. The agent had to rely on web search and prior knowledge to fill in information about competitors (iClassPro, Jackrabbit, Waresport, MeetScoresOnline) and Vault's market positioning.
  • ›Step [25] (Waresport blog) was fetched but its content was also truncated; it was not cited in the final response, indicating the agent could not extract useful competitor comparison details from it.
  • ›The agent's final answer heavily acknowledged what it *could not find*—pricing, monetization model, detailed feature specs, and differentiation—rather than presenting a comprehensive picture. This transparency reflects the site's poor agent-readiness for discovery-evaluation tasks.
  • ›The site metadata and page titles (visible in step [1] header) hinted at the four pillars ('Vault Gymnastics: Gyms, Meets, Scores & Camps'), but the agent had to infer and verify each section by direct URL guessing rather than following documented navigation.

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