The agent assembled a comprehensive overview of Schedulist by working around an inaccessible website. The schedulist.app domain is a React SPA that does not render static content, making direct page fetches unhelpful; the agent instead relied on web search results and app store pages to answer the task. The final response covers what Schedulist does, target users, pricing, and competitive differentiation—all sourced from third-party platforms and search results rather than from the official site itself.

• ›Direct fetches of schedulist.app (steps [0]–[3]) returned only HTML boilerplate with no content—the site is a client-side React app that requires JavaScript rendering. The agent correctly identified this limitation and pivoted to search.
• ›All substantive content came from external sources: web searches (steps [5], [6], [7], [8], [11], [12]) and the Apple App Store (step [10]). The agent cited five sources in its final response; step [10] (App Store) was the only first-party destination successfully fetched.
• ›The agent inferred feature details, pricing ($3.99/month or $41.99/year), and competitive positioning from search snippets and app store listings rather than from official product pages. Pricing was mentioned in search results but not verified against an official pricing page.
• ›Schedulist's website made no effort to publish structured information in a machine-readable or statically fetchable form—no open graph tags, no llms.txt, no static pricing or features pages. The official domain was essentially opaque to the agent.
• ›The agent explicitly called out five gaps in what it could verify: inaccessibility of the website itself, unclear web vs. mobile availability, vague Pro tier feature details, team collaboration scope, and free tier limitations beyond integrations/recurrences.