zerocms.io
success
Claude Code
intent

What does zerocms.io do and who is it for? Explain it back to me.

15steps
54.7sduration
$0.4989cost
161,814tokens
19 steps4 reasoning steps2 searches
home
docs
docs
docs
/features
/index.html.md
/features/index.html.md
sitemap
sitemap
docs
/early-partners/index.…
search
/insights/best-cms-for…
search
docs
92%
on-site discovery
85%
reliability
77%
link following
path origin
  • previous resource77%
  • web search8%
  • prior knowledge15%
insight

The agent successfully gathered comprehensive information about ZeroCMS by fetching the site's core pages (homepage, pricing, features) and supplementing with web search for competitive positioning. The site is well-navigable with clear information architecture; the agent found pricing, features, and target audience clearly laid out. However, some technical details (AI credit conversion, monorepo handling, custom quality checks) were not explicitly documented, requiring the agent to note gaps rather than fill them with speculation.

  • ›Steps [1], [4], [6] returned the core value proposition and feature set directly from the site's native content. Step [4] (homepage markdown) and step [6] (features page) provided the clearest positioning: 'Git-based, AI-native CMS' with 'zero code changes' and automatic schema detection—all cited in the final response.
  • ›Step [5] (pricing page) was the single source for pricing tiers, costs, and plan limits; the agent extracted three plans (Solo, Team, Business) with credit allocations and user counts directly from the fetched markdown. This was explicitly cited as a source.
  • ›Steps [2], [3] were routing/discovery steps (navigation to /pricing and /features from homepage) that led to content-bearing fetches; they are not directly content-bearing themselves but enabled discovery.
  • ›Steps [14] and [15] (web search + external article fetch) were required to answer 'how it's different from alternatives'—ZeroCMS's own site does not publish competitive comparisons, so the agent had to bridge the gap via external CMS comparison articles. Step [17] was a routing search that did not yield new content.
  • ›The site surfaced all primary information (what, who, pricing) through standard navigation and markdown pages. The agent relied on prior knowledge (~15%) for guesses like /pricing and /features URLs, but those proved correct, showing the site follows predictable URL conventions.
  • ›The agent identified and transparently called out three specific gaps: AI credit token-to-credit conversion, monorepo subscription model, and custom quality check syntax—demonstrating good awareness of what the site left undocumented rather than inventing answers.
  • ›The 'early access' status was discoverable from step [1] (homepage). The early-partner program and trial terms were found in steps [5] and [12], showing the site surfaced pricing nuance and partner options via dedicated pages.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →