What does app.onchain.cc do and who is it for? Explain it back to me.
- web search67%
- prior knowledge33%
The agent assembled a comprehensive explanation of onchain.cc by combining web search results and documentation fetches, primarily from GitBook docs and Spanish-language news articles about Bitso's launch. The site itself (app.onchain.cc and onchain.cc) rendered as JavaScript-heavy Next.js apps that returned no human-readable content, forcing the agent to rely on external sources (search results, GitBook, news articles) to answer the task. The agent successfully delivered what was asked for—a plain-English explanation of what they do, who it's for, pricing, and differentiation—but had to bridge heavy gaps in the primary site's navigability.
- ›Steps [5], [10], [13], [16] were web search results that surfaced key resources (GitBook FAQ, Bitso launch announcements in Spanish, Colosseum terms). The search queries themselves were well-targeted and returned actionable links.
- ›Step [6] (GitBook FAQ fetch) and the Spanish news article from step [16] were the most content-bearing—they provided concrete details on features, positioning, and Bitso's involvement. The primary onchain.cc domain (steps [1], [3], [11], [12]) returned only minified Next.js bundles with no readable HTML content, making direct navigation useless.
- ›Pricing information (0.15% base fee, rank-based discounts, $300K prize pool) came from GitBook docs and news articles, not from the main site. The agent had to cite sources outside the primary domain and relied on 67% web search to fill gaps.
- ›The agent noted seven significant gaps: vague 'Trenches' mechanics, incomplete fee schedules, inaccessible UI/UX details, undefined chain coverage list, unverified performance claims, lack of explicit competitor positioning, and missing token launch details. These reflect the site's minimal public documentation and JavaScript-rendered architecture.
- ›The 'heavy_bridge' friction classification is justified: the agent could not extract answers directly from app.onchain.cc or onchain.cc; it had to bridge via search, external docs, and news coverage to construct a coherent answer.
Help the next agent finish on app.onchain.cc
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 →