balanz.com
success
Claude Code
intent

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

17steps
76.6sduration
$0.9190cost
164,966tokens
25 steps8 reasoning steps5 searches
home
/precios
/comisiones
/comisiones
search
/educacion/balanz-comi…
search
docs
search
search
/caracteristicas
/sobre-balanz
/ventajas
search
/empresa
/empresa
/por-que-balanz
83%
on-site discovery
100%
reliability
42%
link following
path origin
  • previous resource42%
  • web search17%
  • prior knowledge42%
insight

The agent successfully gathered enough information to explain Balanz's core business, pricing, and competitive positioning, but had to heavily supplement official site content with external broker comparison articles. Balanz.com's own pages returned 200s but were not fully rendered in the fetches (truncated HTML), forcing the agent to rely on third-party review sites (Rankia, Awake Trader) and prior knowledge for concrete pricing tables, feature comparisons, and client statistics. The site's information architecture exists but is not agent-accessible in a usable form.

  • ›Steps [16] and [20] (external comparison sites) were the primary sources of concrete pricing details (commission rates: 0.60-0.70% for stocks, 0.20% for bonds, minimum trade amounts), differentiators (vs. IOL and PPI), and customer counts (200k+ active clients). These were cited directly in the final response's Sources section.
  • ›Steps [1], [3], [4], [5], [6], [8], [9], [10] all returned 200 status from official Balanz pages (/comisiones, /caracteristicas, /precios, /empresa, /ventajas, /sobre-balanz, /por-que-balanz) but responses were truncated and contained no visible structured content — the agent could not extract pricing or feature tables from them. The agent noted in its response that /precios and /caracteristicas pages 'don't exist (404s)' but steps [3], [5] actually returned 200s, suggesting the HTML rendering was broken or content was client-side rendered.
  • ›The agent relied on 42% prior knowledge and web search (17%) because the official site was not machine-readable. The agent explicitly called out confusing UX gaps: pricing scattered across pages, no dedicated features/pricing page, jargon (CEDEARs, MEP, CCL) undefined on the main site, and 'no cost' messaging that obscures transaction fees.
  • ›The site is not agent-ready for self-contained discovery: key pages exist but do not publish their content in a fetchable, plain-text form. The agent had to assemble its answer from fragments (navigation hints from homepage fetch), prior knowledge of Argentine finance, and external third-party sources that explicitly compared Balanz to competitors.

See every agent that visits balanz.com

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 →