longbridge.com
success
Claude Code
intent
What does longbridge.com do and who is it for? Explain it back to me.
7steps
32.3sduration
$0.0612cost
56,235tokens
10 steps3 reasoning steps1 search
home
docs
docs
/products
/en/stocks
/en
search
100%
on-site discovery
100%
reliability
83%
link following
path origin
- previous resource83%
- prior knowledge17%
insight
The agent successfully assembled a comprehensive explanation of Longbridge by combining direct website fetches with web search results. The site's heavy reliance on JavaScript and incomplete page loads in the trajectory forced the agent to supplement its findings with external search results, which provided the clearest pricing and positioning details. While the agent delivered a thorough answer to the task, it worked around the site's limited content accessibility rather than extracting information from fully-rendered, structured pages.
- ›Steps [1–5] fetched core pages (homepage, pricing, about, products, stocks) but returned heavily obfuscated JavaScript responses with minimal visible HTML content; the agent could not extract detailed pricing or positioning from these raw responses alone.
- ›Step [8] (web search) proved essential—external third-party reviews and pricing guides supplied the concrete fee structure (zero commission, exchange fees, stamp duty, SFC levies) that was not clearly available in the site's own fetches. The agent explicitly cited these search results in its final Sources section.
- ›The site's JavaScript-heavy architecture and apparent client-side rendering made direct page fetches non-informative; the agent had to rely on prior knowledge (83% of fetches sourced from previous_artifact) and external search to construct a coherent narrative.
- ›Key gaps remained after site exploration: account minimums, explicit competitive comparisons, and clear regulatory/geo-restriction policies were not discoverable on the pages fetched, forcing the agent to note these as missing rather than provide definitive answers.
- ›The site did not publish structured product/pricing data, competitive differentiation, or target-market positioning in a form that a bot could extract directly; instead, it required assembly from fragments across multiple pages plus external validation.
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 →