intake.es
partial
Claude Code
intent

What does intake.es do and who is it for? Explain it back to me.

28steps
138.6sduration
$2.3958cost
430,385tokens
45 steps17 reasoning steps16 searches
home
home
search
/en
/en/pricing
/en/features
search
docs
/en/integrations
search
/en
search
docs
search
/en/product
/es/comparativas/pylon
search
search
/es/precios
search
search
search
search
search
search
search
search
search
75%
on-site discovery
67%
reliability
33%
link following
path origin
  • previous resource33%
  • web search25%
  • prior knowledge42%
insight

The agent assembled a partial understanding of Intake by combining fragments from the homepage, product page, and a comparison page, but could not access pricing details despite multiple attempts. The site's large, truncated HTML responses prevented extraction of pricing tiers and comprehensive features; the agent had to rely on meta descriptions and inferred positioning rather than actual page content. The core value proposition (account-aware AI support agent for SaaS) was identifiable, but key commercial and technical details remained inaccessible.

  • ›Steps [1], [3], [7], [9], [16] fetched the homepage and pricing page but all returned truncated HTML ("4400 more chars") that cut off before rendering visible content, preventing the agent from extracting pricing tables, plan names, or feature lists despite multiple attempts at the same URLs.
  • ›Steps [24] and [25] successfully returned product page and Pylon comparison page, which provided meta descriptions and established Intake's positioning (AI agent that reads account data, resolves repetitive questions, escalates to humans) — these were the only content-bearing pages that returned usable information.
  • ›Step [31] fetched the Spanish pricing page (/es/precios) with the same truncation pattern, confirming the site's HTML delivery strategy prevents mid-page content extraction; no pricing numbers, tiers, or cost structure were ever accessible.
  • ›The agent never discovered a working pricing page, feature list, blog, documentation, or customer testimonials — either they do not exist on the site or are behind dynamic rendering that plain HTML fetches cannot access.
  • ›The site is minimally agent-readable: homepage and product pages are marketing-focused with sparse navigation; no structured data (schema.org), API docs, or machine-readable comparison tables were present.
  • ›The agent relied on search results and prior knowledge (42% + 33% of sources) rather than the site itself, indicating intake.es does not surface detailed product information in a form accessible to headless navigation.

Help the next agent finish on intake.es

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 →