The agent could not access marriott.com directly due to security restrictions, so it assembled an explanation entirely from web search results and prior knowledge. Despite this limitation, it delivered a substantive answer covering what Marriott does, pricing, target audience, competitive positioning, and explicitly flagged gaps in its knowledge (live UI features, redemption mechanics, corporate booking flows). The site's bot protection rendered it non-navigable for the agent, forcing a workaround via search-sourced third-party summaries and help articles.

• ›Steps [8–12] were all web searches that returned third-party summaries (The Points Guy, NerdWallet, hotel comparison blogs) and Marriott help articles. None were direct fetches of marriott.com's own pages.
• ›The agent successfully guessed that marriott.com is a hotel booking platform but could not verify current UI, live deal promotions, redemption calculators, or corporate booking workflows by exploring the live site; it had to infer from search results and prior knowledge.
• ›The agent's final response explicitly cited 10 sources, all from search results [8–12]. No direct website fetches were content-bearing; the site itself was architecturally or policy-blocked from agent access.
• ›Key gaps the agent flagged (points valuation clarity, corporate group booking handling, brand comparison tools, mobile app differences) reflect genuine unknowns that direct site exploration might have answered but searches could not fully address.
• ›The site's hosting/CDN configuration (Akamai, 403 errors on homepage, 404s on guessed internal paths) indicates deliberate bot exclusion, making it highly agent-hostile despite being a major e-commerce platform.