The agent successfully assembled a comprehensive overview of Baptist Health by combining website fetches with web search. The site's navigation structure was brittle (many 404s on guessed URLs), forcing the agent to rely heavily on web search to discover the correct URL paths (/about, /care-services, /about/baptist-health-medical-group). Once it found the right pages, they contained substantive content about the organization's mission, services, nursing credentials, and financial assistance policies. However, pricing transparency and patient process flows remain scattered and incomplete on the public site.

• ›Steps [1, 6] returned homepage and locations page; steps [3, 4, 5, 7] were all 404s on guessed URLs, indicating poor URL predictability. The agent recovered by using web search (step [9]) to discover the correct /about and /care-services paths.
• ›Steps [11, 12, 13] (About, Care Services, Medical Group pages) and steps [15, 17, 18, 19, 20] (search results) provided the factual backbone: 10 hospitals, 1,820+ providers, Magnet nursing designations across all hospitals, Christ-centered not-for-profit mission, and financial assistance programs. These were all cited in the final response.
• ›Pricing information was fragmented: step [15] found an 'Accepted Insurance Plans' page and step [20] found a 'Financial Assistance' page, but neither provided transparent rate cards or procedure pricing. The agent noted this gap explicitly ('not transparent about standard rates').
• ›The site is heavily JavaScript-rendered; the agent noted it 'couldn't access detailed page content through standard fetching,' suggesting content is client-side rendered and may not be fully indexable. This explains why web search was necessary as a bridge (33% of fetches sourced from web search).
• ›No user-facing 'how to access care' workflow, new patient onboarding flow, or step-by-step process documentation appears on the site—the agent had to infer the patient journey rather than find it explicitly documented.