scb.co.th
success
Claude Code
intent
What does scb.co.th do and who is it for? Explain it back to me.
14steps
69.3sduration
$0.6728cost
162,984tokens
22 steps8 reasoning steps3 searches
home
/th/home
/en/home
/th/personal-banking
/th/corporate-banking
search
/th/personal-banking/d…
/th/personal-banking/l…
search
/en/personal-banking/r…
/th/personal-banking/c…
/th/products
/th/about-us
search
91%
on-site discovery
100%
reliability
55%
link following
path origin
- previous resource55%
- web search9%
- prior knowledge36%
insight
The agent successfully assembled a comprehensive overview of SCB (Siam Commercial Bank) by combining fragments from multiple site pages with prior knowledge, but encountered significant friction: the site's JavaScript-heavy rendering prevented full access to critical pricing data (deposit rates, loan APRs, detailed fee schedules), forcing the agent to acknowledge gaps and rely on incomplete information for the pricing section of the task.
- ›Core identity information (what SCB does, who it serves, history) was retrievable from home page, personal-banking, corporate-banking, and about-us pages—these returned Thai-language meta titles and descriptions confirming service segments (ลูกค้าบุคคล, ลูกค้าธุรกิจขนาดใหญ่) and the '1907 Royal Charter' heritage claim.
- ›Pricing pages were technically reachable (step [20] fetched /en/personal-banking/rates-fees successfully with 200 status) but returned only HTML shell with no actual rate data—the agent could confirm the page structure existed but could not extract current interest rates, APRs, or complete fee schedules due to JavaScript rendering.
- ›The agent compensated by: (1) inferring service categories from page URLs and structure (deposits, loans, cards), (2) extracting a few specific fees mentioned in search results or meta descriptions (16% credit card rate, transfer fees, remittance percentages), (3) citing external sources (Wikipedia, MuralPay) rather than site content for competitive positioning claims.
- ›Navigability was moderate: the site's URL structure is logical (/th/personal-banking, /th/corporate-banking, /th/personal-banking/deposits) and pages return successful status codes, but the lack of server-rendered pricing data makes it opaque to agents; a human visitor would face the same fetch limitation but could scroll or interact with JS.
- ›The agent explicitly called out what it couldn't find (deposit rates, loan APRs, account minimums, comprehensive fee schedules) and correctly attributed the gap to JavaScript rendering, demonstrating awareness of its limitations rather than hallucination.
Help the next agent finish on scb.co.th
Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.
or talk to us about agent readiness →