centene.com
success
Claude Code
intent

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

12steps
56.6sduration
$0.5780cost
131,044tokens
20 steps8 reasoning steps4 searches
home
docs
/plans
/for-individuals
/who-we-are
search
/who-we-are.html
search
search
search
docs
/en-us
87%
on-site discovery
25%
reliability
63%
link following
path origin
  • previous resource63%
  • web search13%
  • prior knowledge25%
insight

The agent assembled a comprehensive explanation of Centene's business model, customer base, pricing mechanism, and competitive positioning by combining a single successful direct fetch (the who-we-are.html page) with extensive web search results. The centene.com website itself was poorly navigable for this discovery task—most direct paths returned 404s, forcing heavy reliance on external sources and prior knowledge to construct the answer.

  • ›The only successful direct fetch from centene.com ([1] homepage, [13] who-we-are.html) returned truncated HTML with minimal visible content; the agent could not extract substantive information from these pages and had to rely on web search results to answer all four questions (what they do, who it's for, pricing, differentiation).
  • ›The site's navigation structure is broken or intentionally restrictive: /about, /plans, /pricing, /en-us, /for-individuals all returned 404s; /who-we-are returned 403 until the agent guessed the .html extension, revealing the site uses non-standard URL patterns that are not discoverable through normal browsing.
  • ›The agent successfully answered the task, but 63% of sources came from prior artifacts and web search, not from centene.com itself, indicating the website is not designed for agent-accessible discovery of corporate positioning and business model information—it appears to be a B2B/partner-facing portal rather than a consumer or research-friendly resource.

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