The agent successfully assembled a comprehensive explanation of maps.gov.sg by working around a blocked homepage. It fetched the guide documentation (step 6), an OGP report card (step 14), and a demo/preview site (step 19), then relied heavily on web search snippets to fill gaps about positioning, alternatives, and real-world use cases. The site's core information was scattered across multiple subdomains and external pages rather than published in a single, agent-accessible location.

• ›The main maps.gov.sg homepage was blocked by Cloudflare (step 1), forcing the agent to discover and fetch guide.maps.gov.sg (step 6) which contained structural documentation. This guide page was successfully retrieved and cited as a source, making it the primary content-bearing resource for understanding features and workflow.
• ›The OGP report card (step 14, reports.open.gov.sg/maps/overview) was fetched but appears to have returned only metadata and UI markup without substantive content in the response snippet. However, the agent cited it as a source, suggesting the page may contain details not fully visible in the truncated response.
• ›The preview.maps.gov.sg site (step 19) was successfully fetched but returns a Next.js app shell with no visible content in the response. The agent cited it as a source but likely gained no new information from it—this suggests the site is client-rendered and not agent-readable.
• ›75% of the agent's actual answer came from web search snippets (steps 3, 4, 8, 9, 11, 12, 16, 17, 21, 22) rather than direct fetches. Search results linked to real-world examples (climate vouchers, kidsREAD) and competitive positioning (vs. GoWhere, Google Maps) that were not available on the fetched pages themselves.
• ›The agent correctly identified several information gaps: feature limits, analytics/reporting, clearer OneMap vs. maps.gov.sg distinction, integration APIs, and eligibility for non-government organizations. These gaps reflect real gaps in the site's public documentation, not agent error.
• ›The site is poorly structured for agent navigation: the homepage is blocked, the guide is on a different subdomain, the demo is on yet another subdomain, and key positioning information (why it exists, what problem it solves) had to be inferred from search results and OGP reports rather than published on the primary domain.