ora
vellum.ai
success
Claude Code
intent

What does vellum.ai do and who is it for? Explain it back to me.

12steps
49.6sduration
$0.4505cost
180,081tokens
23 steps11 reasoning steps1 search
home
docs
docs
/md
docs
/compare-assistants
/compare-assistants/ve…
search
/compare-assistants/ve…
.well-known
docs
docs
100%
on-site discovery
82%
reliability
91%
link following
path origin
  • previous resource91%
  • prior knowledge9%
insight

The agent successfully assembled a comprehensive explanation of Vellum's positioning, features, target audience, and competitive differentiation by retrieving markdown versions of the homepage, comparisons pages, and docs. However, the task was only partially satisfied on pricing — the agent could access pricing page URLs but could not fetch rendered pricing details, so it provided only high-level tier information (free + $50+/month) without tier-specific feature breakdowns or the 'pay-as-you-go credits' mechanics. The site is moderately agent-ready: markdown endpoints exist and were discoverable, but the pricing page is client-side rendered and inaccessible, and some details require prior knowledge or inference.

  • ›Step [6] (homepage markdown) and [19] (docs markdown) provided core positioning and feature set; these were the primary sources for 'what Vellum does.' The markdown endpoint at /md was guessed from prior knowledge but proved highly valuable.
  • ›Steps [13] and [21] (comparison pages) were explicitly cited and provided the differentiation narrative against Claude Cowork and Grok Bot — the site publishes structured competitive comparisons that are readily machine-readable.
  • ›Step [9] (comparisons index) was a router that listed available comparisons but did not itself contain pricing or detailed feature data; it enabled discovery of [13] and [21].
  • ›Pricing details were a clear gap: the /pricing URL responded with rendered HTML (step [3], [8], [11]) that could not be parsed for specific tiers or per-tier feature limits. The agent fell back to web search snippet fragments and prior knowledge to mention '$50+/month' and 'pay-as-you-go credits,' but could not ground these in a fetched pricing page.
  • ›The site's markdown-friendly architecture (/.md suffix, Accept: text/markdown) was not explicitly advertised on the homepage but was discoverable via the /compare-assistants page header and worked reliably, indicating intentional agent support.

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 →