alshhbaa.com
success
Claude Code
intent
What does alshhbaa.com do and who is it for? Explain it back to me.
8steps
29.8sduration
$0.0684cost
64,832tokens
10 steps2 reasoning steps1 search
home
docs
docs
llms.txt
.well-known
/en/pricing
/ar
search
100%
on-site discovery
71%
reliability
86%
link following
path origin
- previous resource86%
- prior knowledge14%
insight
The agent successfully assembled a comprehensive overview of Alshhbaa Copperware by discovering and combining machine-readable resources (llms.txt and pricing.md) with the site's HTML pages. The site proved reasonably navigable for an agent, with structured metadata and developer-facing documentation that contained the core business model, services, and pricing framework—though the primary HTML pages were JavaScript-heavy and uninformative on their own.
- ›Step [5] (llms.txt) was the breakthrough: it provided a concise, agent-optimized summary describing Alshhbaa as a 'Specialist Chandelier Company and Bespoke Workshop' with core value proposition, target clients, and service offerings. This file was not discovered via navigation but via prior knowledge/standard artifact probing.
- ›Step [7] (pricing.md) delivered the most structured pricing information available on the site, detailing the three-tier model (showroom collections, residential bespoke, hospitality/sacred/commercial) and qualifiers that affect cost. This was discovered by following a reference in llms.txt, not by browsing the site directly.
- ›Steps [1], [3], and [8] (HTML pages at /, /pricing, /en/pricing) returned only CSS, HTML structure, and boilerplate—no actual content readable without JavaScript execution. The site's primary pages are not agent-readable without a headless browser; the agent had to fall back on machine-readable artifacts (llms.txt, pricing.md) that sit outside the main content layer.
- ›The agent correctly identified gaps: no example pricing ranges, portfolio details inaccessible, lead process unclear, warranty specifics missing, and international availability undocumented. These are genuine site omissions, not retrieval failures—the information simply is not published.
- ›The site publishes structured metadata for agents (llms.txt, pricing.md, .well-known/openapi.json references) but does not make it discoverable through navigation; the agent had to know to probe for these artifacts. This suggests the site is 'agent-aware' but not agent-friendly in its IA.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →