crudos.cl
success
Claude Code
intent

What does crudos.cl do and who is it for? Explain it back to me.

18steps
103.1sduration
$0.9773cost
196,323tokens
29 steps11 reasoning steps6 searches
home
home
/pedir
search
/restaurant/crudo-sin-…
/cl/store/crudo-sin-ce…
search
/restaurantes/90001746…
search
docs
/ediciones/n_242/artic…
/company/crudo-y-sin-c…
search
/crudo-sin-censura
/crudo-sin-censura-cru…
search
/restaurant_review-g29…
search
25%
on-site discovery
50%
reliability
17%
link following
path origin
  • previous resource17%
  • web search75%
  • prior knowledge8%
insight

The agent assembled a coherent overview of Crudo Sin Censura by combining fragments from the official website (which returned minimal content), delivery platform listings (Rappi), and a third-party case study article. The site itself is largely a thin ordering interface with no substantive marketing or company information exposed; the agent had to reconstruct the value proposition, pricing, and differentiation from external sources and prior knowledge of the Chilean market.

  • ›Step [1] and [3] (official homepage) returned only meta tags and HTML structure—no readable content about what the company does, pricing, or positioning. The actual ordering system at crudos.cl/pedir returned a 500 error (step [4]), making direct menu access impossible.
  • ›Step [9] (ChileMarcas blog article) was the only content-bearing source that explicitly stated founding date (2013), market-pioneer claim, and brand strategy. This provided the 'why they're different' narrative the agent used.
  • ›Step [16] (Rappi) and [17] (LinkedIn) returned full HTML but required the agent to infer structure from DOM; neither provided clear pricing tables or company narrative. The agent cited these in sources but extracted limited direct text.
  • ›Pricing data was fragmentary: one review mention (~15k CLP), one Rappi combo listing (30,660 CLP), but no authoritative menu. The agent admitted 'hard to pin down' and marked this as confusing.
  • ›The site's content strategy is delivery-platform-centric (Uber Eats, Rappi, PedidosYa), not self-hosted. The official domain functions as a technical ordering gateway, not an information hub. This made the site non-navigable for a discovery task; the agent had to route through web search (75% of fetches) rather than following internal links.
  • ›The agent could not access competitive differentiation or service details (delivery zones, minimums, lead times) from any source—these appear to exist only in the order-flow UX, which the agent could not execute.

Help the next agent finish on crudos.cl

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 →