kestra.io
success
Claude Code
intent

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

7steps
34.3sduration
$0.0946cost
72,051tokens
11 steps4 reasoning steps2 searches
home
docs
docs
docs
search
docs
search
80%
on-site discovery
80%
reliability
0%
link following
path origin
  • web search20%
  • prior knowledge80%
insight

The agent partially satisfied the task by assembling a coherent explanation of Kestra's purpose, target audience, and differentiation from competitors, but explicitly identified pricing information as inaccessible on the site. The homepage, pricing page, and docs pages returned HTML that was too minified to extract readable content; the agent relied heavily on prior knowledge (80%) and web search results to fill gaps, rather than reading the site directly.

  • ›Steps [1], [2], [3] fetched the homepage, pricing, and docs pages successfully (200 status), but all returned heavily minified HTML with truncated content markers ('[truncated, 4400 more chars]'), making them unreadable. The agent could not extract structured information from these responses and had to work around them.
  • ›The agent explicitly flagged pricing details as 'confusing/unclear' and unextractable: 'I accessed their pricing page but the HTML was too minified to extract readable details.' This is a critical failure for a commerce/evaluation task — the pricing page exists but is not machine-readable.
  • ›Step [9] (kestra.io/docs/why-kestra) was cited as a source but also returned truncated minified HTML, suggesting the agent inferred content from prior knowledge or search results rather than the actual fetch response.
  • ›Steps [6] and [7] (web searches) returned link titles and summaries that the agent used to infer Kestra's positioning (vs. Airflow, vs. Prefect), but these searches were routers, not content-bearing. The agent's final explanation of competitors and market context appear to come from prior knowledge, not from the fetched pages themselves.
  • ›The site is poorly structured for agent readability: all pages return the same Astro framework boilerplate with no extractable content in the HTML snippets. There is no structured metadata (JSON-LD, OpenGraph, llms.txt) visible in the responses to guide agents toward answers.
  • ›The agent successfully inferred Kestra's core value proposition (YAML-based, declarative, multi-language orchestration), target audiences, and competitive positioning from prior knowledge and search result titles, demonstrating strong reasoning despite content gaps. However, this is assembly from general knowledge, not extraction from the site.

Help the next agent finish on kestra.io

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 →