The agent successfully assembled a comprehensive explanation of Lusha by relying entirely on web search results and prior knowledge, since direct website access was blocked by Cloudflare. It retrieved accurate information about Lusha's core function (B2B contact database with buying signals), pricing structure (credit-based), target users (SMB revenue teams), and competitive differentiation (AI agent integration via MCP). The site's marketing pages and documentation are inaccessible to automated agents, forcing the agent to reconstruct the narrative from third-party sources and cached knowledge rather than primary sources.

• ›All eight content-bearing steps were web searches ([3], [4], [8], [9], [10], [11], [12], [13]), not direct Lusha.com fetches—the homepage, pricing page, and about page all returned 403 Cloudflare blocks. The agent pivoted entirely to search results, which contained aggregated/summarized information rather than canonical product documentation.
• ›Search results from third-party review and comparison sites (salesmotion.io, amplemarket.com, millionphones.com, pipeline.zoominfo.com, g2.com, tracxn.com) provided the actual content: pricing tiers, credit costs, database size, signal categories, and competitive positioning. These were cited extensively in the final response's source list.
• ›The agent encountered deliberate inconsistencies in sourced data (database size ranging 280M–300M+, customer counts varying, MCP timeline ambiguity), flagging these directly in the 'What Was Confusing' section—demonstrating transparency about fragmentation caused by secondary sourcing and outdated/inconsistent marketing claims across Lusha's own blog and third-party sites.
• ›Lusha's primary web properties are effectively invisible to non-browser agents: Cloudflare anti-bot protection blocks structured data retrieval, so the agent cannot access official pricing documentation, product pages, or company information directly. This forces reliance on third-party interpretation and cached knowledge.
• ›The agent successfully inferred Lusha's positioning and differentiators (MCP with Claude, SMB-friendly pricing, buying signals) from scattered blog posts and comparison content, but lacked access to official product roadmaps, exact seat/credit limits on tiers, or verified ROI metrics—gaps the agent acknowledged.
• ›All eight cited sources are external summaries, reviews, or comparison sites, not Lusha.com pages. The only Lusha.com URLs cited are blog posts embedded in search results, never the main product pages. This indicates Lusha.com is optimized for human browsing and SEO but not for agent-readable primary source access.