alien.dev
success
Claude Code
intent

What does alien.dev do and who is it for? Explain it back to me.

6steps
22.8sduration
$0.1409cost
39,806tokens
8 steps2 reasoning steps
home
docs
docs
llms.txt
.well-known/api-catalog
llms-full.txt
100%
on-site discovery
100%
reliability
83%
link following
path origin
  • previous resource83%
  • prior knowledge17%
insight

The agent successfully built a comprehensive explanation of alien.dev's core offering, target market, and differentiation by fetching the homepage, docs page, and full documentation content. However, the task was only partially satisfied because the agent could not retrieve concrete pricing details or competitive comparisons—these were either not published on the site or required navigation into gated resources. The site was moderately navigable: it published structured docs and offered machine-readable artifact files (llms.txt, llms-full.txt), but pricing specifics and customer experience walkthroughs remained opaque.

  • ›Step [1] (homepage) provided initial context about what Alien does (multi-cloud BYOC deployment) but did not contain pricing or differentiation details; the agent relied on doc navigation to deepen understanding.
  • ›Step [4] (llms.txt) and Step [6] (llms-full.txt) were the primary content sources: they contained architectural details (push/pull connection models, resource APIs, remote commands, Containers/Workers/Sandboxes abstractions) that directly answered 'how it works' and 'what's different'—indicating the site publishes technical positioning in machine-readable form.
  • ›Step [2] (/pricing) returned a 200 but the truncated response suggests the pricing page is client-side rendered or dynamically loaded; the agent could not extract per-resource rates, cost tiers, or comparison pricing, forcing it to acknowledge this gap in the final answer rather than assembling false details.
  • ›The agent discovered most content by direct URL guesses (prior knowledge: 17%) and inferred navigation (following to /docs, then probing for .well-known/api-catalog and llms-full.txt)—suggesting the site's navigation was not explicitly crawled from HTML links, but the well-known artifacts were discoverable.
  • ›The agent could not find customer experience details (deployment portal screenshots, onboarding flow), competitive positioning explainers, or why Alien is better than CloudFormation/Terraform—these either require deeper docs exploration, blog posts, or sales collateral outside the accessible scope.

Help the next agent finish on alien.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 →