ora
nytimes.com
success
Claude Code · Haiku 4.50:49
intent

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

14steps
49.1sduration
$0.1973cost
134,840tokens
17 steps3 reasoning steps6 searches
home
/subscriptions
docs
/subscription
docs
search
search
/section/us
/section/world
/section/business
search
search
search
search
100%
on-site discovery
88%
reliability
25%
link following
path origin
  • previous resource25%
  • prior knowledge75%
insight

The agent assembled a comprehensive explanation of nytimes.com by combining site exploration with external research. Direct site fetches (homepage, news sections) provided minimal actionable detail—subscription pages failed to render readable content, and the /about URL returned 404. The agent compensated by drawing heavily on prior knowledge and web search results to construct answers about pricing, target demographics, competitive positioning, and bundled services. The site itself proved largely opaque to machine navigation for the discovery-evaluation task; the agent had to work around incomplete or inaccessible pages.

  • Homepage and section pages (steps [1], [9]–[11]) returned valid HTML but contained only boilerplate meta-descriptions and article listings in unstructured form—no machine-readable pricing, company mission, or business model information.
  • The /subscriptions and /subscription endpoints (steps [2], [5]) both loaded but rendered as skeleton SPAs with heavy JavaScript dependencies, returning no readable pricing tables or plan details; similarly, /about returned 404, forcing the agent to seek information elsewhere.
  • The agent's final answer relied primarily on prior knowledge (75% of fetches sourced this way) and external web searches (steps [7]–[8], [12]–[15]) for critical facts: pricing tiers, target demographics, bundled products (Games, Wirecutter, The Athletic), and competitive differentiation. None of this information was cleanly published on the main site in a form the agent could fetch.
  • The agent correctly identified and documented three friction points: subscription page not rendering, lack of transparent article meter disclosure, and missing /about page—demonstrating awareness of what the site failed to surface.

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 →