Mercury vs Ramp
Mercury scores higher on the AgentReady, 81/100 against 64/100. They differ on 8 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Mercury. Mercury is a fintech company providing radically different banking for entrepreneurs, offering business banking, cards, expense management, payments, invoicing, and accounting in one platform.
Ramp. Ramp is a corporate finance platform that combines cards, expenses, bill payments, and banking with AI-powered automation.
Where Mercury is ahead
Mercury passes clear canonical domain, clear product positioning 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: authentication documented. Ramp misses it.
And on adopt, cli available and mcp integration available. Ramp misses those.
Finally, on operate, agent compatibility verified. Ramp misses it.
Where Ramp is ahead
Ramp passes structured api reference, and Mercury does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.
What neither does
Both fail search discoverable, public docs discoverable, llms-full.txt / full agent docs, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution. 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. Ramp leads 75 to 67. Mercury misses search discoverable, public docs discoverable, llms-full.txt / full agent docs; Ramp misses search discoverable, clear canonical domain, clear product positioning, public docs discoverable, llms-full.txt / full agent docs, mcp discoverable.
Understand. Mercury leads 92 to 58. Mercury misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Ramp misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Both sit at 88/100 here. Mercury misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk; 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.
Operate is whether an agent can run against it in production and recover when a call fails. Mercury leads 78 to 33. Mercury misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution; 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.
Pricing
Mercury does not publish a machine-readable starting price and has a free tier. Ramp does not publish one and has a free tier.
Signal by signal
| Signal | Mercury | Ramp |
|---|---|---|
| AgentReady | 81 | 64 |
| Discovery | 67 | 75 |
| Understanding | 92 | 58 |
| Adoption | 88 | 88 |
| Operability | 78 | 33 |
| Public API | Yes | Yes |
| MCP server | Yes | Unknown |
| OpenAPI spec | Unknown | Yes |
| CLI | Yes | Unknown |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Mercury clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Mercury and Ramp. Alternatives to each: Mercury, Ramp.
An agent can fetch this as data: POST /v1/compare {"slugs": ["mercury", "ramp"]}