agent-readiness-gtm-ai.zoominfo-workers.workers.dev
success
Claude Code
intent

What does agent-readiness-gtm-ai.zoominfo-workers.workers.dev do and who is it for? Explain it back to me.

7steps
34.5sduration
$0.1904cost
56,506tokens
10 steps3 reasoning steps
home
docs
.well-known/agent-card
.well-known/agent-skills
llms.txt
llms-full.txt
docs
100%
on-site discovery
100%
reliability
71%
link following
path origin
  • previous resource71%
  • prior knowledge29%
insight

The agent successfully assembled a comprehensive explanation of GTM AI's purpose, audience, pricing model, and differentiation by combining structured metadata from well-known artifact endpoints with full-text documentation. The site was highly agent-navigable—it published machine-readable agent-card and skills index files, llms.txt summaries, and a full content dump, allowing the agent to build a complete picture without guessing. However, the agent had to work around gaps: explicit competitor comparisons, per-tool credit costs, and free-tier usage limits were not published in accessible form.

  • ›Step [5] (agent-card.json) and step [6] (skills index) provided structured, machine-readable metadata that immediately answered 'what do they do' and 'who it's for' — this is strong agent-readiness for identity layer.
  • ›Step [7] (llms.txt) and step [8] (llms-full.txt) delivered prose documentation including pricing model, capabilities, and developer resources all in one fetch — the site explicitly published this for AI discoverability.
  • ›The agent correctly inferred pricing from llms.txt ('pay-as-you-go, consumption-based, free tier with credits') but acknowledged that 'exact credit costs for each tool aren't published on the pricing page' — the site lacked granular per-tool pricing in a structured format.
  • ›Competitor differentiation was entirely missing from the site's published content; the agent had to note 'the site doesn't explicitly compare itself to competitors' rather than retrieve a comparison. This is a positioning gap, not a site navigation failure.
  • ›The agent used 71% prior knowledge and 29% prior knowledge, fetching only 5 of 8 tool calls as content-bearing — suggesting the site had some routing or navigation gaps that forced reliance on guessed URLs (/.well-known endpoints, /llms.txt, /llms-full.txt) rather than discovered links.
  • ›No explicit CTA, sign-up flow, or pricing page with actionable next steps was retrieved — the agent accessed docs and metadata but not a conversion or onboarding surface.

See every agent that visits agent-readiness-gtm-ai.zoominfo-workers.workers.dev

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 →