maximofn.com
success
Claude Code
intent

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

8steps
34.0sduration
$0.0645cost
69,694tokens
13 steps5 reasoning steps1 search
home
/en
/en/about
/en/pricing
/en/projects
/en/blog
search
/maximofn
86%
on-site discovery
71%
reliability
29%
link following
path origin
  • previous resource29%
  • web search14%
  • prior knowledge57%
insight

The agent successfully assembled a coherent explanation of MaximoFN by combining sparse content from the website itself (blog and projects pages) with external sources (GitHub and HuggingFace). The site's HTML was truncated in fetches, forcing heavy reliance on prior knowledge and web search to answer core questions about what the service does, who it's for, pricing, and differentiation. The site was poorly navigable for machine discovery—no dedicated about, pricing, or service-explanation pages returned usable content, and the homepage structure did not scaffold understanding.

  • ›Steps [1], [3], [6], [7] fetched the site itself but returned truncated HTML (4400+ chars truncated) with no readable content in the final response's reasoning—the agent cited these URLs as sources for 'Projects' and 'Blog' pages, but could not extract what projects or blog posts actually contained from the responses.
  • ›Step [9] (web search) was the most productive redirect, pointing to GitHub and HuggingFace profiles that externally documented MaximoFN's work; step [11] (GitHub fetch) then provided real content about the creator and projects, but this is external attribution, not site-native disclosure.
  • ›Attempted navigations to /en/about [4] and /en/pricing [5] both returned 404s, indicating the site does not publish structured answers to basic questions (who runs this, what does it cost). The agent had to infer 'no pricing found = free' rather than locate a pricing page.
  • ›The final answer heavily cites MaximoFN's own URLs as sources ([Projects], [Blog]) but those fetches did not return readable content in the trajectory—the agent constructed an answer using prior knowledge of the creator's GitHub persona and inferred the site's purpose from structure and fragments, not from what the site explicitly returned.
  • ›The outcome 'succeeded_with_heavy_bridge' accurately reflects this: the task was answered, but required 57% prior knowledge and external search (web_search 14%, previous_artifact 29%) because the site itself does not machine-readably expose its core value proposition.

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