newbalance.com
success
Claude Code
intent

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

15steps
87.9sduration
$1.0145cost
173,611tokens
25 steps10 reasoning steps7 searches
home
docs
/womens
/mens
search
search
/running
search
/shoes-apparel-and-acc…
search
search
search
/help
search
/shopping
87%
on-site discovery
50%
reliability
50%
link following
path origin
  • previous resource50%
  • web search13%
  • prior knowledge38%
insight

The agent assembled a comprehensive overview of New Balance by relying almost entirely on web search and prior knowledge, since the official website was largely inaccessible (403/404 errors on product pages and category links). The agent successfully answered what New Balance does, who it's for, how it's priced, and how it differs from competitors—but had to work around the site's technical barriers and JavaScript-heavy rendering to do so. The site's e-commerce functionality and content delivery proved poorly suited to bot/API access.

  • ›Web searches (steps 7, 9, 12, 21, 23) supplied all substantive content: pricing tiers, width options, private ownership, US manufacturing, and competitive positioning. The site itself returned only boilerplate HTML shells that rendered JavaScript-dependent content the agent could not parse.
  • ›Homepage and category pages (/mens, /womens, /about) fetched successfully but contained no readable text content in their responses—all rendering was deferred to client-side JS, making them hollow to direct inspection.
  • ›Specific product and pricing pages triggered 403 Forbidden or 404 errors, blocking direct verification of actual prices, inventory, and product details. The agent noted this friction explicitly in the final response.
  • ›The agent relied on prior knowledge for 38% and web search for 13%, with 50% sourced from previous artifacts, indicating heavy dependence on external sources rather than site-native content discovery.
  • ›Site is not agent-ready: it lacks machine-readable product data, structured pricing, or accessible product pages. No llms.txt, schema.org markup, or API alternative was apparent or discoverable.

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 →