docs.nexus.xyz
success
Claude Code
intent

What does docs.nexus.xyz do and who is it for? Explain it back to me.

5steps
49.4sduration
$0.3012cost
23,463tokens
7 steps2 reasoning steps1 search
home
home
/overview/introduction
search
home
67%
answer from your site
75%
answer efficiency
67%
followed site links
answer sources
  • from this site67%
  • from agent knowledge33%
url discovery
  • given in the task25%
  • followed a link50%
  • found via web search25%
insight

The agent partially satisfied the task: it gathered substantive information about Nexus's core offering, architecture, and target users from the site's own documentation, but critical gaps—pricing/fees, competitive positioning, and regulatory clarity—remain unfilled because the docs themselves do not contain this information. The site is navigable but incomplete for the full evaluation task.

  • ›The site exposed core architectural details (protocol-native orderbook, USDX stablecoin, API-first design) across the homepage and introduction pages [1, 3], but pricing and fee structures are entirely absent—docs explicitly state they will be 'detailed ahead of the October 2026 launch.'
  • ›The agent correctly identified that search results [4] added no new facts about fees or competitive positioning; external web searches returned only general perps fee comparison sites and vague launch timeline information, not Nexus-specific pricing.
  • ›The mainnet launch date (October 2026) and testnet-only status came from search results [4], not from docs.nexus.xyz itself, indicating the documentation does not make its development stage clearly explicit in fetched pages.
  • ›The agent had to synthesize positioning from fragments across two sites (docs.nexus.xyz and nexus.xyz) [1, 3, 5]; neither site explicitly compares themselves to competitors (Hyperliquid, dYdX, etc.), forcing the agent to infer differentiation from architecture rather than direct comparison.
  • ›The regulatory disclaimer ('not a regulated venue') appears in the docs [3], but no compliance roadmap or jurisdiction clarity was available, requiring the agent to flag this as a gap rather than answer it from content.

Help the next agent finish on docs.nexus.xyz

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 →