claudierestaurant.com
success
Claude Code
intent

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

13steps
62.2sduration
$0.8859cost
158,907tokens
22 steps9 reasoning steps4 searches
home
/menu
docs
/dining
/reservations
/contact
search
/menus
/r/claudie-miami
/cities/miami-fl/venue…
search
search
search
67%
on-site discovery
67%
reliability
22%
link following
path origin
  • previous resource22%
  • web search33%
  • prior knowledge44%
insight

The agent successfully assembled a comprehensive overview of Claudie by combining direct site fetches (homepage, about, menus) with web search results and external sources. The site itself was moderately navigable but incomplete—menu pricing and detailed descriptions required web search and external references (PR releases, review sites) to fully answer the task. The agent worked around missing traditional nav paths (/menu returned 404) by discovering /menus via search.

  • ›Step [1] (homepage) and [4] (about page) provided foundational identity—cuisine style, chef background, Riviera inspiration—but were light on pricing and menu specifics. Step [12] (menus page) confirmed menu tiers exist but actual dish names and full eight-course pricing remained absent from the site itself.
  • ›Pricing data came entirely from external sources: steps [17] and [18] (press releases and reviews) surfaced specific menu price points ($45 power lunch, $65 Miami Spice dinner, $85 prix fixe) that do not appear on the official site in the fetched HTML. Step [20] searched for tasting menu details but the site does not publicly list the cost.
  • ›The site's information architecture created friction: `/menu` returned 404, forcing the agent to discover `/menus` via web search rather than organic site navigation. No structured pricing schema (JSON-LD, microdata) was evident, requiring external aggregators and review sites to confirm costs. The site surfaces *what* they offer (Mediterranean, French-Italian) but delegates *how much* and detailed *what's on the plate* to booking platforms (Resy, OpenTable) and external press.
  • ›Competitor differentiation (step [18]) came from web search, not from the site itself—the site makes no explicit claims about how Claudie differs from Stubborn Seed, Mister O1, or other Miami fine dining. The agent had to synthesize this from press releases and curator reviews.

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