The agent successfully compiled a comprehensive explanation of Buildkite by relying primarily on web search results and third-party pricing/comparison sites rather than Buildkite's own website. The buildkite.com domain itself returned JavaScript-heavy pages that could not be parsed for content, forcing the agent to assemble its answer from external sources (CICDCost, CICDCalculator, TechnologyMatch, Spacelift, Bunnyshell, Enlyft, 6sense, and TechTarget). Despite this friction, the agent delivered a detailed, accurate overview of Buildkite's positioning, pricing model, target audience, and differentiation—though gaps remain around hosted agent pricing and feature tier specifics that would require direct site navigation or sales contact.

• ›Buildkite's own website (steps 1–4) returned only boilerplate HTML with JavaScript initialization code, rendering its pages unreadable to the agent. The site appears to be a client-side rendered SPA, making its content opaque to static fetches.
• ›Steps 6, 12, 13 (web searches) were content-bearing: search snippets and linked third-party comparison/pricing sites (Spacelift, TechnologyMatch, Bunnyshell) provided direct information about Buildkite's features, competitive positioning, and customer base without requiring page fetch.
• ›Steps 10–11 (CICDCost and CICDCalculator pages) returned JavaScript bundles with no visible pricing data in the HTML; the agent did not cite these as sources, indicating they were routing-only or unhelpful despite 200 status codes.
• ›The agent explicitly noted in its final response that Buildkite's public pricing page does not clearly itemize feature breakdowns by plan tier, and that hosted agent pricing was not publicly documented—indicating the site publishes incomplete product information.
• ›The agent had to rely on prior knowledge (~50%) and web search (~50%) to synthesize the answer; nearly zero content came directly from buildkite.com itself, demonstrating poor site surface area for agent discovery and identity extraction.