getscaled.com
success
Claude Code · Haiku 4.50:45
intent
What does getscaled.com do and who is it for? Explain it back to me.
15steps
45.6sduration
$0.3646cost
145,703tokens
23 steps8 reasoning steps
home
docs
/features
docs
/index.md
.well-known
/compare.md
/platform
/data
/platform.md
/data.md
/what-is-getscaled.md
sitemap
docs
/use-cases
100%
on-site discovery
80%
reliability
80%
link following
path origin
- previous resource80%
- prior knowledge20%
insight
The agent successfully assembled a comprehensive explanation of GetScaled's business, positioning, pricing, and competitive differentiation by retrieving markdown versions of the site's core content pages. The site publishes structured markdown documents (.md files) that directly answer the task, making it highly machine-readable; however, the agent had to discover these through prior knowledge and URL guessing rather than explicit site navigation, and key pricing details (exact CPM rates, managed plan costs) remain deliberately vague by design.
- ›Steps [10, 13, 14, 19, 20, 21] returned markdown documents (.md versions) that contained the complete answer: what GetScaled does (multi-channel AI-powered outbound platform), who it's for (enterprise revenue teams), how it's priced (CPM on delivered messages, free targeting), and how it differs (owned deliverability, native agent integration, usage-based model). These documents were the primary source for the final response's narrative.
- ›The site exposed this content via markdown files rather than traditional HTML navigation; the agent discovered /index.md, /pricing.md, /compare.md, and /what-is-getscaled.md by guessing and following document references, not by clicking navigation links. HTML pages at /pricing, /platform, /data returned truncated or inaccessible content (4400+ chars truncated), forcing reliance on markdown versions.
- ›The site is agent-ready in structure (publishes .md files with complete, structured information) but not in discoverability—no sitemap links point to .md versions, and HTML pages do not clearly reference their markdown equivalents. The agent succeeded by knowing to append .md to URLs, a pattern that relies on prior knowledge rather than site affordances.
- ›Pricing information is intentionally vague on the site itself—exact CPMs are not disclosed; users must contact sales. The agent correctly surfaced this limitation in the final response rather than fabricating rates, showing appropriate handling of incomplete data.
- ›The site lacks public detail on WhatsApp/RCS implementation, voice channel mechanics, managed plan retainer amounts, free trial access, and feature roadmap. The agent flagged these gaps explicitly, indicating honest limitations in what the site exposes.
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 →