d3x.com
success
Claude Code
intent

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

14steps
61.6sduration
$0.6997cost
106,578tokens
21 steps7 reasoning steps4 searches
home
docs
docs
/index.php
robots.txt
sitemap
/services
search
docs
search
search
search
home
docs
80%
on-site discovery
100%
reliability
30%
link following
path origin
  • previous resource30%
  • web search20%
  • prior knowledge50%
insight

The agent successfully understood D3x's business model, positioning, and pricing by discovering that the primary service is at d3x.ai rather than d3x.com (which only serves a Matrix animation). It assembled a comprehensive explanation by fetching the d3x.ai homepage, pricing page, about page, and conducting web searches that surfaced third-party reviews and comparison articles. The real website (d3x.ai) was fully navigable and information-rich once discovered, but the agent had to work around the decoy d3x.com domain to complete the task.

  • ›Steps [14], [15], [16] returned full HTML from d3x.ai with structured content on the platform's capabilities (guest communication, PMS integration, multi-channel support), pricing tiers (€5/room/month for messaging, €100/month for voice), and company positioning ('operator-built'), which formed the backbone of the answer.
  • ›Steps [18] and [19] (web searches) surfaced third-party review and comparison sites (Hotel Tech Report, Tracxn) that provided competitive differentiation details (Skills Engine, Self-Healing Knowledge Base, autonomous execution, production metrics) and competitor names (Canary, Duve, HiJiffy) — information not found on the d3x.ai site itself.
  • ›The d3x.com domain was a dead-end: all fetch attempts ([1]–[9]) returned identical Matrix animation content with zero business information. The agent had to resort to web search to discover the correct domain (d3x.ai). Once on d3x.ai, pages were well-structured and directly answered the task questions, indicating the site is agent-ready.
  • ›The agent explicitly cited [14], [15], [16], [18], [19] sources in its final response, confirming all content-bearing steps were used. The agent did not cite d3x.com fetches because they contained no useful information.
  • ›Information gaps identified by the agent (enterprise pricing, US availability, ROI metrics) reflect genuine absences on the published site — the agent correctly flagged what was unavailable rather than fabricating answers.

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