run402.com
success
Claude Code
intent

What does run402.com do and who is it for? Explain it back to me.

9steps
39.1sduration
$0.2310cost
76,559tokens
13 steps4 reasoning steps
home
/humans
llms.txt
docs
openapi
/install.txt
/updates.txt
/llms-cli.txt
/humans/terms.html
100%
on-site discovery
89%
reliability
89%
link following
path origin
  • previous resource89%
  • prior knowledge11%
insight

The agent successfully retrieved and synthesized a comprehensive explanation of run402.com's purpose, target audience, pricing, and differentiation by fetching the site's machine-readable documentation (llms.txt, llms-cli.txt, and openapi.json). The site is well-structured for agent navigation—it explicitly routes agents to technical docs and publishes pricing and feature details in fetchable text files—but the documentation assumes deep technical knowledge and scatters key information across multiple documents, requiring the agent to assemble a coherent picture from fragments.

  • ›Step [4] (llms.txt) and [5] (llms-cli.txt) were the core content sources: they directly answered what Run402 does ('Postgres + REST + Auth + Storage + static & Astro-SSR site hosting + same-origin routes + Node 22 functions + email + image generation'), who it's for ('agent-first'), and how it differs (autonomous agent identity, x402 payment protocol, atomic deploys). Step [8] (openapi.json) provided pricing tiers and payment mechanisms.
  • ›The site explicitly routes AI agents away from the human landing page (/humans) to technical documentation files (llms.txt, llms-cli.txt), indicating intentional agent-first design. However, pricing information was not consolidated—the agent had to extract tier names and costs from OpenAPI descriptions and terms references rather than finding a dedicated pricing document.
  • ›The site does NOT publish a traditional 'comparison with alternatives' section anywhere. The agent inferred differentiation by reading the x402 payment model and agent-autonomy framing from the technical docs, then constructed the comparison from prior knowledge about Supabase/Firebase/Vercel. This required synthesis beyond what the site explicitly states.
  • ›Critical friction: there is no /pricing page (returned 404 in step [6]), forcing the agent to hunt for pricing across three different documents. The homepage and /humans page contain only comments directing agents elsewhere, not usable content. A human user would find the site opaque without prior technical knowledge.

See every agent that visits run402.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 →