glass.photo
success
Claude Code
intent
What does glass.photo do and who is it for? Explain it back to me.
13steps
78.9sduration
$0.7658cost
193,263tokens
24 steps11 reasoning steps5 searches
home
docs
docs
search
/membership
/highlights/2024-pricing
/faq/how-much-is-a-gla…
search
search
/us/app/glass-photogra…
search
/faq/what-is-glass
search
37%
on-site discovery
88%
reliability
25%
link following
path origin
- previous resource25%
- web search63%
- prior knowledge13%
insight
The agent successfully synthesized a comprehensive explanation of Glass.photo by combining direct website fetches with web search results. The site's information architecture was fragmented across multiple pages (about, membership, FAQ, pricing highlights), requiring the agent to stitch together details from at least 5 distinct endpoints plus search results. The core value proposition, pricing model, and differentiators were ultimately recoverable, though the site did not present this information in a consolidated, machine-readable format.
- ›Pricing information required fetching /membership and /faq/how-much-is-a-glass-membership pages separately; no single canonical pricing page existed (direct attempt at /pricing returned 404). Web search results pointed to these URLs more reliably than site navigation would have.
- ›The agent had to infer 'no algorithms,' 'no ads,' and 'chronological feed' positioning from multiple searches and FAQ pages rather than from a clear, machine-readable mission statement on the homepage or a dedicated differentiators page.
- ›Key features (Appreciations, EXIF filters, Series, no public counts) were discoverable only through fetching /faq/what-is-glass and /about; the homepage and membership pages did not contain feature lists in a structured format.
- ›The site lacked clear disclosure of Patron membership benefits beyond what appeared in isolated 'highlights' posts (/highlights/introducing-patron). A structured comparison table (or JSON API) would have eliminated ambiguity.
- ›Storage limits, web/mobile feature parity, and discovery mechanics were genuinely absent from the fetched content—not navigation failures, but actual content gaps that the agent correctly identified in its 'What Was Confusing' section.
- ›Web search (63% of fetch sources) was more effective than on-site navigation for locating pricing and community positioning; the site's internal linking did not naturally surface these pages from the homepage.
See every agent that visits glass.photo
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 →