docs.alkimi.org
success
Claude Code
intent

What does docs.alkimi.org do and who is it for? Explain it back to me.

16steps
86.0sduration
$0.8512cost
171,123tokens
24 steps8 reasoning steps5 searches
home
docs
docs
docs
sitemap
docs
docs
docs
search
docs
search
/faq
search
search
search
home
91%
on-site discovery
73%
reliability
73%
link following
path origin
  • previous resource73%
  • web search9%
  • prior knowledge18%
insight

The agent successfully assembled a comprehensive explanation of Alkimi Labs by combining fragments from the docs site itself (staking, tokenomics, explorer pages), the main corporate site, web search results, and prior knowledge about the AdFi/blockchain ecosystem. The docs site was navigable via sitemap but underspecialized—it housed token mechanics and staking details well, but required heavy bridging to web search and external sources to answer questions about business model, pricing for advertisers, competitive positioning, and how the underlying ad platform actually works.

  • ›The docs site's actual content (steps 11, 12, 13, 22) provided only the token holder / staking perspective—rewards, staking mechanics, explorer dashboards, and tokenomics. None of the fetched pages revealed advertiser/publisher pricing, the ad platform's mechanics, or how traditional alternatives work.
  • ›Critical business-model information came from web search (steps 9, 15, 18, 19, 21) rather than the docs site itself: the 3–8% protocol fee range, 12% APY yield figures, Q4 2023–2025 fee growth trajectory, competitor names (MiQ, Adshares), and the relationship to 'Alkimi Exchange' / 'agentic marketplace' product positioning all required external sources.
  • ›The agent discovered the site's structure via sitemap (step 8), but multiple naive URL guesses (steps 4–5) returned 404s, indicating the docs site uses a non-obvious URL pattern for some sections. The homepage (step 1) was fetched but HTML was truncated—actual rendered content was never retrieved, forcing reliance on structured data (sitemap) and prior/search knowledge.
  • ›The final response explicitly cites sources including docs.alkimi.org pages and external Gate Wiki / Decrypt articles; the docs site was cited for structure and token mechanics but not as the primary source for competitive analysis, advertiser pricing, or business model explanation—all of which the user asked for.
  • ›The 'heavy bridge' friction indicator is justified: the agent succeeded because it bridged to web search (9% sourced) and prior knowledge (18% sourced) to fill gaps that the docs site alone (73% sourced by artifact reuse from navigation) could not answer. The docs site is purpose-built for token stakers, not for someone trying to understand the full business model or compare it to alternatives.

Help the next agent finish on docs.alkimi.org

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 →