cibc.com
success
Claude Code
intent

What does cibc.com do and who is it for? Explain it back to me.

13steps
69.4sduration
$0.8854cost
162,860tokens
16 steps3 reasoning steps5 searches
home
/en/personal-banking.h…
/en/personal-banking/c…
/en/personal-banking/m…
/en/personal-banking/c…
search
search
/en/personal-banking/b…
search
search
/en/business-banking.h…
/en/products-and-servi…
search
100%
on-site discovery
63%
reliability
63%
link following
path origin
  • previous resource63%
  • prior knowledge38%
insight

The agent assembled a comprehensive explanation of CIBC's services, target customers, pricing, and competitive positioning by relying heavily on web search results and prior knowledge rather than direct navigation of cibc.com. The website itself was poorly navigable—many product pages returned 404 errors, forcing the agent to source most of its answer from external third-party sites, fee PDFs, and general knowledge. The final response is well-structured and largely accurate, but it demonstrates that CIBC's public website does not surface product information in a machine-readable or even easily browsable form.

  • ›Steps [8], [9], and [12] successfully fetched product pages (/mortgages, /credit-cards, /bank-accounts) that returned 200 status, but the HTML responses were truncated and contained no visible content summaries in the trajectory. The agent extracted no substantive details from these pages—they served mainly as routing waypoints.
  • ›Steps [10], [11], [13], and [14] were web searches that actually delivered the agent's core answer: pricing tiers ($4.95–$29.95/month), fee structures, competitive comparisons, and digital features. These external sources, not CIBC's own website, provided the structured data needed to answer the task.
  • ›The agent's final response cites external sources (Wealthvieu, WealthNorth, Finder, Hardbacon, Wikipedia) far more than CIBC's own domain. Even the detailed pricing table appears to come from third-party aggregators and PDFs, not from navigable product pages on cibc.com.
  • ›Early attempts to guess product page URLs ([3], [4], [7]) all returned 404s, indicating either missing pages or incorrect URL structure. The agent never recovered a complete product directory or information architecture from the site itself.
  • ›The agent's own final response includes a 'What Was Confusing or Unclear' section explicitly noting that 'CIBC's website is heavily JavaScript-based, making it difficult to see full product information' and that 'many detailed product pages returned 404 errors.' This self-awareness confirms the site's poor navigability.
  • ›The agent succeeded despite the website being poorly indexed for agent navigation: it pivoted to web search and external sources, leveraging 63% of its fetches from prior knowledge/artifacts rather than primary navigation. This is a workaround, not a reflection of site usability.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →