mona.net.au
success
Claude Code
intent

What does mona.net.au do and who is it for? Explain it back to me.

10steps
54.2sduration
$0.6676cost
88,371tokens
11 steps1 reasoning step4 searches
home
search
docs
/visit
/stuff-to-do
search
/museum-entry
/tickets
search
search
17%
on-site discovery
100%
reliability
0%
link following
path origin
  • web search83%
  • prior knowledge17%
insight

The agent assembled a comprehensive explanation of MONA by combining web search results with attempted direct fetches of the site itself. However, the site's heavy JavaScript rendering made direct content extraction impossible—all fetches returned only HTML boilerplate without accessible page content. The agent successfully answered the task by relying almost entirely on external sources (83% web search) rather than the site's own published information, demonstrating that while MONA's positioning is discoverable externally, the site itself is poorly suited for direct machine-readable content extraction.

  • ›All direct site fetches [0, 2, 3, 4, 7, 8] returned identical truncated Next.js boilerplate with no extractable text content. The agent could not pull pricing, descriptions, or exhibition details directly from the site despite 6 fetch attempts across multiple relevant pages.
  • ›The agent's final answer was sourced primarily from web search results [1, 5, 6, 9] and third-party guides (Wonderful Museums, Tassiedale Devil Abroad, RACV, TripAdvisor) rather than mona.net.au itself. The agent explicitly acknowledged this limitation, stating 'MONA's website is built with Next.js/React and renders content heavily through JavaScript. I couldn't directly extract full text content from their pages.'
  • ›The site is fundamentally inaccessible to non-JavaScript clients: pricing ($39 for non-Tasmanians, $33 concession, $17 under-18, free under-12, free for Tasmanians with $5 deposit), admission categories, festival dates, and collection philosophy were unavailable from direct fetches but found via external sources. The agent had to work around the site's technical architecture rather than reading from it natively.
  • ›Despite the site's poor machine readability, discovery-layer content (that MONA exists, what it is, how it differs from alternatives) was readily available via search results, suggesting good SEO and external coverage. However, transactional and detailed operational information required external lookups rather than being cleanly published on the site itself.

See every agent that visits mona.net.au

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 →