one.nz
success
Claude Code
intent
What does one.nz do and who is it for? Explain it back to me.
13steps
91.1sduration
$0.7316cost
110,207tokens
20 steps7 reasoning steps4 searches
home
/about-us
/plans
/broadband
search
/mobile
/business
search
/pay-monthly
/prepay
search
search
/help/one-nz-change
100%
on-site discovery
100%
reliability
44%
link following
path origin
- previous resource44%
- prior knowledge56%
insight
The agent assembled a reasonably comprehensive overview of One NZ by combining prior knowledge (56% of fetch sources) with direct site navigation and targeted web searches. However, the site's JavaScript-heavy rendering meant actual pricing tables, plan details, and detailed service descriptions were not accessible via API calls—the agent had to work around this by citing external review sites (MoneyBalance, Wikipedia) for concrete pricing and positioning data. The site was navigable structurally but opaque in content delivery.
- ›Steps [1], [3]–[5], [8]–[9], [11]–[12], [18] attempted to fetch one.nz pages directly but returned only HTML scaffolding (headers, meta tags, CSS) with no rendered content. The agent explicitly noted: 'The one.nz website pages appear to use heavy JavaScript rendering, so I couldn't pull detailed pricing tables or plan comparisons directly.' This forced reliance on prior knowledge and external sources.
- ›Steps [13], [15], [16] (web searches) returned review sites and Wikipedia, which provided the actual pricing ($10–$88/month mobile plans, $75/month broadband), competitive positioning (5G awards, Vodafone rebrand history), and differentiation claims. These external sources, not the site itself, supplied the core answer content.
- ›The agent correctly cited [1], [3]–[5], [8]–[9], [11]–[12], [18] in its Sources section despite these steps returning no usable content, conflating discovery (finding the URL) with content retrieval (extracting information). Actual answer grounding came from [13], [15], [16] and prior knowledge, not from the official site.
- ›One.nz publishes no machine-readable pricing, plan comparison, or positioning data that the agent could extract. The /plans, /pay-monthly, /prepay, /mobile, /broadband, and /business pages exist but render only via client-side JavaScript, making them inaccessible to API-based agents.
- ›The site's structure is discoverable (navigation links exist), but its content is not. An agent must either execute JavaScript or resort to prior knowledge and third-party review sites to answer basic questions about what One NZ sells, how much it costs, and how it differs from competitors.
Help the next agent finish on one.nz
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 →