nubank.com.br
success
Claude Code
intent

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

16steps
71.8sduration
$0.9846cost
181,195tokens
21 steps5 reasoning steps6 searches
home
/produtos
/en/about
/conta
docs
/cartao
/sobre
search
search
search
/nubank-vs-uala-vs-int…
search
/blogs/target-market/n…
search
/us/blog/what-is-nubank
search
80%
on-site discovery
70%
reliability
30%
link following
path origin
  • previous resource30%
  • web search20%
  • prior knowledge50%
insight

The agent assembled a comprehensive overview of Nubank by bypassing the JavaScript-heavy website and relying entirely on web search and external sources. The nubank.com.br site itself proved largely unnavigable for content extraction, returning either JavaScript-rendered HTML or 404 errors on logical URLs (/produtos, /sobre, /pricing), forcing the agent to construct its answer from third-party articles, competitor comparison pages, and venture capital analyses rather than Nubank's own documentation.

  • ›The homepage and product pages (steps [1], [3], [4], [5], [7], [8], [9]) returned JavaScript-heavy HTML or 404 errors, rendering direct site navigation useless for content extraction. The agent correctly pivoted to web search rather than attempting to parse unrendered JavaScript.
  • ›All substantive information came from external sources: web searches (steps [11], [12], [13], [15], [17], [19]) returned links to third-party analyses, and fetches of those external pages (steps [14], [16], [18]) provided the actual product details, pricing, target market, and competitive positioning that should have been on Nubank's own site.
  • ›The site's pricing structure (/pricing endpoint at step [4]) returned successfully (200) but contained only rendered JavaScript, so the agent had to infer pricing from external sources rather than Nubank's official documentation. This represents a significant identity-layer failure—Nubank does not expose its core value proposition (no fees, CDI returns) in a machine-readable or easily parseable format.
  • ›The agent cited sources but had to assemble fragments: pricing details from SME Banking Platform review, target market demographics from CanvasBusinessModel, competitive positioning from NuMundo Ventures comparison, and features from Wise's explainer. None of these were published by Nubank itself on their domain.
  • ›The agent successfully delivered a thorough, well-structured answer despite site friction, but this required heavy lifting with prior knowledge (50% of fetches sourced from prior knowledge according to the metadata) and external discovery—a user trying to learn about Nubank from nubank.com.br alone would have been blocked.

See every agent that visits nubank.com.br

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 →