What does 2027.dev do and who is it for? Explain it back to me.
- previous resource64%
- web search27%
- prior knowledge9%
The agent assembled a partial but useful explanation of 2027.dev's purpose, audience, and key differentiator (GetDX comparison) by combining content from the homepage, about page, arena leaderboard, docs site, and evals page. However, the site's missing pricing page (404 on /pricing) and access-gated documentation (404s on /getting-started and /pricing within docs) prevented the agent from fulfilling a core requirement of the task—transparent pricing information. The agent had to rely on inference and web search to conclude that pricing was not publicly available, rather than retrieving it from the site itself.
- ›Step [0] (homepage) and step [2] (about page) clearly articulated the core value proposition ('evaluate Agent Experience, catch friction points, become the tool AI agents choose') and positioning (agent-readiness for developer tool creators), providing immediate answers to 'what they do' and 'who it's for.'
- ›Step [5] (DevTool Arena) and step [15] (evals page) were interactive product pages that revealed the leaderboard and evaluation registration flow, but neither contained pricing tiers, costs, or business model details—only a 'request access' call-to-action.
- ›Steps [21] and [23] (web search results pointing to Medium article and GetDX comparison) were the only sources that addressed 'how it's different'—the Medium URL itself was blocked (403), forcing the agent to infer the GetDX relationship from search snippets alone rather than primary product documentation.
- ›The site published no machine-readable pricing, no detailed technical docs (docs.2027.dev returned partial HTML without navigation), and no explicit product comparison. The agent had to declare this gap honestly rather than fabricate details, reducing task completion to 'partial.'
- ›The site is moderately discoverable (homepage, arena, evals exist and are fetchable) but poorly structured for agent navigation: no pricing page, docs broken for key sections (/getting-started, /pricing), and no public business model statement—requiring the agent to work around unavailable content.
Help the next agent finish on 2027.dev
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 →