goldsky.com
success
Claude Code
intent

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

16steps
81.2sduration
$1.1547cost
207,927tokens
29 steps13 reasoning steps8 searches
home
docs
search
docs
docs
search
/products/subgraphs
/products/edge
search
search
docs
search
search
/case-studies/artemis-…
search
search
37%
on-site discovery
88%
reliability
25%
link following
path origin
  • previous resource25%
  • web search63%
  • prior knowledge13%
insight

The agent successfully assembled a comprehensive explanation of Goldsky's business model, products, pricing, and differentiation by combining fetches from the main site (homepage, product pages, case studies) with multiple web searches that filled gaps the site itself didn't clearly expose. The site is reasonably navigable for discovering what Goldsky does and its product portfolio, but pricing details, product positioning (Mirror vs. Turbo), and use-case guidance required external search results and educated inference rather than being clearly laid out in a single resource.

  • ›Content-bearing fetches (steps 1, 3, 13, 14, 18, 23) returned HTML that contained product descriptions, case studies, and pricing tier labels, but the actual detailed pricing formulas and feature comparisons were either truncated in the response or required login/interactive elements (e.g., 'pricing calculator requires logging in'). Web searches (steps 5, 10, 11, 20, 21, 25, 27) provided more actionable comparison snippets, migration guides, and competitive positioning that the primary site pages did not surface prominently.
  • ›The agent discovered resources through a mix of direct navigation (guessing /pricing, /products/subgraphs, /products/edge from common URL patterns) and search—roughly 63% of fetches were search-derived. The site's structure is predictable enough that direct navigation worked, but the agent had to resort to searches to find the Artemis case study, comparison guides, and clarity on product differentiation (Mirror vs. Turbo, Goldsky vs. The Graph specifics).
  • ›Pricing information was fragmented across pages and partially gated: the Pricing page and docs.goldsky.com/pricing/summary both returned content, but the agent noted a 'pricing calculator' exists behind a login wall and had to infer cost-per-entity by combining snippet text from multiple sources. Product positioning (Compose, Mirror vs. Turbo) was vague on the main site, forcing the agent to flag what it 'couldn't fully clarify' rather than finding definitive answers.

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 →