pilotprotocol.network
success
Claude Code
intent
What does pilotprotocol.network do and who is it for? Explain it back to me.
6steps
53.3sduration
$0.0648cost
27,927tokens
7 steps1 reasoning step
home
home
/plans
home
docs
docs
83%
answer from your site
83%
answer efficiency
100%
followed site links
answer sources
- from this site83%
- from agent knowledge17%
url discovery
- given in the task17%
- followed a link83%
insight
The agent successfully assembled a coherent explanation of Pilot Protocol's purpose, audience, and positioning from the site's homepage, plans page, about page, and documentation hub. The site is reasonably navigable but deliberately vague on competitive positioning and pricing details, forcing the agent to acknowledge gaps rather than fill them with external knowledge.
- ›Steps [0] and [1] retrieved the same homepage URL twice (typed from memory), suggesting the agent re-verified content rather than relying on a single parse—both pulls supplied complementary framing (features vs. audience/pricing context), indicating the homepage is information-rich but not strictly structured.
- ›Step [2] (pricing page) published three tier names and free-tier details but explicitly withheld paid pricing, citing 'contact sales'—the site's architecture openly gates commercial information rather than hiding it, making this a deliberate friction point rather than a navigation failure.
- ›Step [4] (about page) revealed founder/company name and mission but provided no competitive comparison, positioning analysis, or market context—the site avoids comparative language by design, so the agent correctly labeled this as missing rather than inferring alternatives.
- ›Step [5] (docs page) was the only step that explicitly mentioned alternative platforms (MCP, A2A, ACP) and positioned them as 'potentially complementary,' but did not explain the functional or market differences—the agent had to note this as incomplete competitive intelligence.
- ›The agent grounded its 'confusing or missing' section entirely on absences it observed (no published pricing, no use cases, no real examples, no learning-curve guidance), avoiding claims unsupported by the fetches, demonstrating disciplined adherence to the trajectory.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →