portreya.com
success
Claude Code
intent

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

7steps
41.3sduration
$0.5372cost
70,868tokens
11 steps4 reasoning steps3 searches
home
docs
/features
search
search
/ai-headshot-generator
search
75%
on-site discovery
75%
reliability
50%
link following
path origin
  • previous resource50%
  • web search25%
  • prior knowledge25%
insight

The agent successfully understood Portreya's core offering, pricing, and competitive positioning, but had to work around a Next.js-rendered site that served mostly HTML scaffolding rather than content-bearing responses. The site was poorly navigable for automated discovery—the agent relied on web search results and prior knowledge to fill gaps that direct page fetches could not satisfy, ultimately assembling a coherent answer from fragments rather than finding it published in one accessible location.

  • ›Steps [1], [3], and [8] returned Next.js HTML scaffolding with minimal text content, forcing the agent to pivot to web search. The pricing page (step [3]) was fetched but did not yield readable pricing details from the raw HTML—pricing data came instead from search snippet context (steps [6], [7]) and prior knowledge.
  • ›The agent discovered what Portreya does primarily through web search results (steps [6] and [7]) which returned snippet titles like 'AI Headshot Generator for Headshots in Minutes' rather than from the fetched pages themselves. The /features route returned a 404 (step [4]), eliminating a natural discovery path.
  • ›Step [8] (the /ai-headshot-generator page) was fetched but again returned only HTML scaffolding, suggesting the site uses client-side rendering that agent fetches cannot fully evaluate. The agent had to reconstruct understanding from search results and external sources (Startup Buffer, Fritz.ai blog posts cited as sources) rather than from primary content on portreya.com itself.
  • ›The final response cites sources from portreya.com blog posts and external review sites (Startup Buffer, Fritz.ai), indicating the agent assembled competitive comparisons and detailed pricing from secondary sources rather than finding this information natively published on Portreya's own pages in agent-readable form.
  • ›The agent explicitly noted in step [5] that 'the site uses Next.js with dynamic rendering, so I'm getting mostly HTML scaffolding,' indicating low agent-readiness due to client-side rendering architecture that obfuscates content from programmatic access.

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