nervos.org
partial
Claude Code
intent

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

5steps
34.3sduration
$0.0157cost
25,967tokens
9 steps4 reasoning steps1 search
home
home
docs.home
docs
search
80%
answer from your site
25%
answer efficiency
67%
followed site links
answer sources
  • from this site80%
  • from search results20%
url discovery
  • given in the task25%
  • followed a link50%
  • guessed the URL25%
insight

The agent assembled a partial but useful overview by working around the rate-limited main site, relying on developer docs and search results. The site's marketing and positioning pages were inaccessible, leaving claims unverified and key business/comparative context missing.

  • ›The main nervos.org domain returned HTTP 429 to every request, forcing the agent to rely on docs.nervos.org and search results rather than primary marketing materials. This is a hard barrier to discovery and identity.
  • ›The developer docs (step [3]) provided technical substance (PoW, RISC-V, Cell model, Layer 1 role) but used domain-specific terms without inline definitions, requiring the agent to acknowledge confusion on 'Cell,' 'script,' and the Nervos/CKB relationship.
  • ›Search results (step [7]) supplied tokenomics (CKByte = 1 byte storage right) and mining mechanics that the docs omitted, but the agent had to trust Nervos's own promotional sources with no third-party verification.
  • ›The site does not publish a direct competitor comparison or pricing schedule in any fetched page, forcing the agent to infer positioning from architecture claims alone.
  • ›The agent correctly flagged unexplained ecosystem projects (Fiber, Spore, OffCKB) as missing context, indicating the site assumes familiarity or fails to onboard newcomers systematically.

Help the next agent finish on nervos.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 →