Ramp vs Vellum
Vellum scores higher on the AgentReady, 88/100 against 64/100. They differ on 23 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Ramp. Ramp is a corporate finance platform that combines cards, expenses, bill payments, and banking with AI-powered automation.
Vellum. A personal AI assistant that lives in the secure Vellum Cloud, has its own identity, and actually does things in the world.
Where Vellum is ahead
Vellum passes search discoverable, clear canonical domain, clear product positioning, public docs discoverable, llms-full.txt / full agent docs and mcp discoverable, and Ramp does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: openapi / spec quality, request examples provided, response examples provided and errors and status codes documented. Ramp misses those.
And on adopt, no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, cli available and mcp integration available. Ramp misses those.
Finally, on operate, canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented and observable execution. Ramp misses those.
What neither does
Both fail authentication documented, limits / constraints documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. If your agent needs any of those, you will be building it yourself either way.
Score, pillar by pillar
The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.
Discover. Vellum leads 100 to 75. Ramp misses search discoverable, clear canonical domain, clear product positioning, public docs discoverable, llms-full.txt / full agent docs, mcp discoverable; Vellum misses nothing.
Understand. Vellum leads 85 to 58. Ramp misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Vellum misses authentication documented, limits / constraints documented.
Adopt. Vellum leads 100 to 88. Ramp misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, cli available, mcp integration available; Vellum misses nothing.
Operate is whether an agent can run against it in production and recover when a call fails. Vellum leads 67 to 33. Ramp misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified; Vellum misses idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Ramp does not publish a machine-readable starting price and has a free tier. Vellum starts at $30/mo and has a free tier.
| Ramp plans | Vellum plans |
|---|---|
| - | Mighty $30/month |
| - | Super $100/month |
| - | Ultra $200/month |
| - | Custom Plan Custom |
Signal by signal
| Signal | Ramp | Vellum |
|---|---|---|
| AgentReady | 64 | 88 |
| Discovery | 75 | 100 |
| Understanding | 58 | 85 |
| Adoption | 88 | 100 |
| Operability | 33 | 67 |
| Public API | Yes | Yes |
| MCP server | Unknown | Yes |
| OpenAPI spec | Yes | Yes |
| CLI | Unknown | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Vellum clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Ramp and Vellum. Alternatives to each: Ramp, Vellum.
An agent can fetch this as data: POST /v1/compare {"slugs": ["ramp", "vellum"]}