zkward.com
success
Claude Code
intent
What does zkward.com do and who is it for? Explain it back to me.
18steps
81.9sduration
$1.3086cost
256,762tokens
25 steps7 reasoning steps9 searches
home
docs
docs
docs
/features
docs
search
search
search
search
zkvanguard.home
search
search
search
search
/zkvanguard/zkvanguard
/zkvanguard/zkvanguard…
search
78%
on-site discovery
33%
reliability
44%
link following
path origin
- previous resource44%
- web search22%
- prior knowledge33%
insight
The agent successfully understood zkward by pivoting to the GitHub repository (step 21) after the main website proved unhelpful, extracting the complete product definition, pricing, and architecture from the README. The zkward.com website itself is not agent-navigable — it's a client-side React SPA with no static content or navigation links, forcing the agent to rely on web search and a secondary source (GitHub) to answer the task.
- ›Step [21] (GitHub README) was the sole content-bearing source and delivered the core answer: what zkward does (AI-managed USDC vault), who it's for (retail crypto investors), pricing (0.5% AUM + 10% performance fee), and key differentiators (prediction market integration, ZK-STARK proofs, 8-gate safety system). No information in the final response came from zkward.com itself.
- ›The zkward.com homepage (step [1]) returned only compiled JavaScript/React with no readable text, meta tags, or navigation. Attempts to guess common routes (/pricing, /about, /docs, /features, /blog in steps [2]–[7]) all returned 404s or empty boilerplate, indicating either a SPA-only architecture or missing content pages.
- ›The agent had to bridge a critical discovery gap: web search (steps [9]–[19]) initially returned no results about zkward specifically, yielding unrelated RWA and zero-knowledge projects instead. Only after searching "zkward AI agent RWA Cronos zkEVM 2026" (step [19]) did the GitHub repository surface in results. The site itself published no discoverable information and did not appear in its own brand search results.
- ›The agent noted but could not resolve a blockchain discrepancy: website meta tags mention Cronos zkEVM, but the GitHub README clearly states Sui mainnet. This suggests either outdated website metadata or multi-chain operation — the site itself provides no clarification.
- ›Pre-audit status and TVL cap ($10K) were extracted from the GitHub README but represent significant risk factors not surfaced on the marketing site. The site fails to disclose security posture or product maturity.
Help the next agent finish on zkward.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 →