The agent worked around direct website access barriers (Vercel security blocks) to assemble a comprehensive overview of lhowsam.com using web search results and GitHub repository data. The site was not directly navigable due to HTTP 429 errors, forcing heavy reliance on search engine snippets and external sources (GitHub, LinkedIn, Wiza profiles). The agent successfully answered the core task—what the site is, who it's for, pricing, and how it differs—but had to infer most content from second-hand sources rather than reading the actual website.

• ›All direct fetches of lhowsam.com returned HTTP 429 (Vercel security checkpoints), preventing content retrieval. The agent pivoted entirely to web search and GitHub.
• ›Web search results [3, 7, 8, 11, 12, 13, 14] provided URL snippets and metadata (titles, breadcrumbs) but no full page content—the agent had to infer what the site contains from result titles ('About', 'Projects', 'Blog') and search query patterns.
• ›The GitHub repository [9] was the only directly readable source, confirming the tech stack (Next.js, Vercel) but not the site's actual content or positioning.
• ›The agent correctly identified the site as a personal portfolio/blog and inferred Luke Howsam's expertise and projects from search result titles and URL patterns, but explicitly noted it could not verify current details, update frequency, or contact information due to access barriers.
• ›The site publishes no structured metadata (schema, llms.txt, or API docs) that would allow agents to discover content programmatically; search results were the only discovery mechanism.