withprive.com
success
Claude Code
intent

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

20steps
82.2sduration
$1.0681cost
190,184tokens
32 steps12 reasoning steps7 searches
home
docs
docs
home
search
shop.home
/en/faq
search
/en/compare
/en/compare/net-a-porter
/en/compare/farfetch
/en/compare/buying-dir…
search
/en/what-is-prive
search
search
search
search
/how-it-works
/faq
77%
on-site discovery
69%
reliability
54%
link following
path origin
  • previous resource54%
  • web search23%
  • prior knowledge23%
insight

The agent successfully gathered enough information to explain Privé's core offering, target audience, pricing model, and competitive positioning, but worked around gaps in the site's public documentation. The site's homepage and comparison pages were accessible and well-structured, but key operational details (tier-specific benefits, concierge service scope, return policy, delivery timelines) were not published in fetched form, forcing the agent to acknowledge what it *could not* find rather than complete the full briefing.

  • ›Steps [1] and [8] (homepage) provided the meta-description ('up to 30% savings, tax-free pricing, dedicated concierge') but minimal structural content. The agent had to navigate to deeper pages to build out the narrative.
  • ›Steps [23] and [24] (FAQ and 'What is Privé' pages) were the most content-bearing: they explained membership cost ($495/year), VAT-exempt export pricing mechanics, eligibility (physical goods, restrictions on certain items/brands), and the concierge sourcing model. These were explicitly cited in the final response's sources.
  • ›Steps [16], [17], [18] (comparison pages vs. Net-a-Porter, Farfetch, direct brand purchasing) were heavily used to construct the differentiation section. The site published these comparisons explicitly—a strong signal of agent-ready positioning.
  • ›The site did NOT publish tier benefits (Insider, Jetsetter, Globetrotter, First Class) in any fetched page, despite the agent's multiple searches. The agent correctly surfaced this as a gap rather than inventing details.
  • ›Operational details (processing times, geographic scope beyond US inference, return/refund policy) were absent from all fetched pages. The agent relied partly on prior knowledge (DHL shipping, full insurance) that wasn't fully sourced in the trajectory.
  • ›The site lacks a traditional /pricing, /about, /faq URL structure initially (steps [3], [4], [5], [7] all returned 404), but these pages do exist at /en/faq and /en/what-is-prive, suggesting language-prefixed routing. Site discovery friction was light once the pattern was understood via web search.

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