gov.br
success
Claude Code
intent

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

9steps
45.6sduration
$0.6238cost
57,758tokens
13 steps4 reasoning steps4 searches
home
/pt-br/acesso-a-inform…
/pt-br/servicos
search
/en/services
search
search
search
/wiki/gov.br
60%
on-site discovery
80%
reliability
40%
link following
path origin
  • previous resource40%
  • web search40%
  • prior knowledge20%
insight

The agent successfully assembled a comprehensive explanation of gov.br by combining web search results and Wikipedia research, since the official site itself returned incomplete HTML and lacked clear descriptive content. The agent delivered a satisfactory overview of what gov.br does, who it's for, pricing, and differentiation, but had to work around a site that doesn't publish this information in readily fetchable form.

  • ›Steps [6], [10], and [11] were web searches that yielded titles and URLs (e.g., Wikipedia, Forbes article, TI Inside) but the agent cited their URLs without showing extracted snippets in the trajectory — suggesting the agent used prior knowledge or inferred context to construct the final narrative rather than parsing search result content directly.
  • ›Step [8] (Wikipedia fetch for 'gov.br') and steps [9] and [4] (fetches to gov.br's own /en/services and /pt-br/servicos pages) returned truncated HTML that was clearly incomplete ('…[truncated, 4400 more chars]'), indicating the site either serves dynamic content, JavaScript-heavy pages, or fragmented responses that don't contain publishable descriptive text in static form.
  • ›The agent never successfully retrieved a narrative description, feature list, or comparison from gov.br's own pages — all substantive claims (175M users, 4,600+ services, world's most-accessed platform, biometric auth, security tiers) came from external sources (Wikipedia, Forbes, TI Inside) or prior knowledge, not from the site's own content.
  • ›Gov.br's English version appears poorly localized or incomplete: step [3] attempted /pt-br/acesso-a-informacao and received a 404, and subsequent English fetches did not return parseable content. The Portuguese version was never explored, limiting what the agent could directly verify.
  • ›The agent correctly identified and called out in its response what was confusing: incomplete site structure, no clear service catalog visibility, unclear onboarding process, and missing security/privacy details — evidence of an e-government platform that publishes operational data to the public but not its own positioning or user guidance in machine-readable form.

See every agent that visits gov.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 →