Head to head · Spend transactions · October 2026 research run
Mercury API vs Ramp
Mercury API scores 63.8 (B) on agent readiness against Ramp's 57.3 (C), and leads in 4 of 7 scored categories. Ramp leads on schema & documentation, maintenance & community and transparency & trust. Both do spend transactions.
Which one, for what
Good for A company that banks with Mercury and wants an agent to read balances and transactions, set notes and categories, upload receipts, issue virtual cards with spend limits and queue payments for human approval.
Ahead on
- Reliability, 59 against 30
- Payments & pricing, 30 against 25
Also in its favour
- No incidents deducted, where Ramp loses 3 points for them
Watch for
No rate limits with numbers and no 429 handling were found in the reviewed documentation
Ramp C
Good for A finance team already on Ramp that wants an agent to read transactions, upload receipts, code and split expenses, issue funds with limits, create bills and work with purchase orders and procurement requests.
Ahead on
- Schema & documentation, 86 against 72
- Maintenance & community, 74 against 64
- Transparency & trust, 70 against 63
Watch for
No public status page was found. status.ramp.com doesn't resolve, and no status link appears in the docs, help centre or trust centre pages read
Score by category
| Category | Weight this run | Mercury API | Ramp | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 59 | 30 | Mercury API +29 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 86 | Ramp +14 |
| Agent ergonomics | 13%16.2 | 68 | 66 | Mercury API +2 |
| Security & auth | 14%17.5 | 82 | 79 | Mercury API +3 |
| Payments & pricing | 10%12.5 | 30 | 25 | Mercury API +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 64 | 74 | Ramp +10 |
| Transparency & trust | 7%8.8 | 63 | 70 | Ramp +7 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 63.8 · B | 57.3 · C |
Facts side by side
| Fact | Mercury API | Ramp |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Mercury Technologies, Inc. | Ramp Business Corporation |
| Hosted endpoint | https://api.mercury.com/api/v1 | https://api.ramp.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Mercury's Terms of Use. The Mercury CLI on GitHub is Apache-2.0 | Proprietary service under the Ramp Platform Agreement and the API Agreement. The ramp-cli repository is MIT |
| Tools exposed | 35 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-08-12 | 2026-10-07 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | no date given | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | none | 53 stars |
Verdicts
Mercury API
Custom tokens take per-endpoint scopes, write tokens need an IP allowlist, and payments can be queued for approval in the dashboard through POST /account/{accountId}/request-send-money. No rate limits, error catalogue or SLA were found in the reviewed documentation, the changelog carries no dates, and the MCP server is beta.
Ramp
OAuth 2.0 scopes split read from write across about 40 resources, a 260-operation OpenAPI spec is public, and an audit log endpoint records actions by user and agent. No public status page was found, 89 operations are marked beta, the API Agreement allows changes without notice, and idempotency keys cover only eight write operations.
Before you call either
Mercury API
- Ask for a Custom token with only the scopes the task needs. Scopes can't be edited later, and a token unused for 45 days is deleted.
- Without a fixed IP address, send payments through
POST /account/{accountId}/request-send-money. Direct sends throughPOST /account/{accountId}/transactionsneed an allowlisted IP. - Send a stored
idempotencyKeywith every payment. The same recipient, account, amount and method within 24 hours returns 400 even with a new key. - Set
limiton list calls.GET /transactionsreturns up to 1,000 rows by default. - Test against
https://api-sandbox.mercury.com/api/v1/with a sandbox token. Webhooks aren't available in the sandbox.
Ramp
- Send
scopeon the client credentials token request. Without it Ramp issues a token with no scopes and every resource call fails with 403 - Follow the full URL in
nextto page.page_sizedefaults to 20 and stops at 100, and the cursor is opaque - Stay under 200 requests in any 10 seconds per source IP and back off 1, 2 then 4 seconds on 429. No Retry-After header is documented
- Don't use
synced_afterorfrom_created_atto find changed records. Bills and transactions have no updated-at filter, so subscribe to webhooks - Send
X-Idempotency-Keywhen creating funds or procurement requests. Elsewhere a retried POST can create a duplicate, so read back before retrying
Questions
Which is better for AI agents, Mercury API or Ramp?
Mercury API scores 63.8 (B) on agent readiness against Ramp's 57.3 (C), and leads in 4 of 7 scored categories. Ramp leads on schema & documentation, maintenance & community and transparency & trust.
Do Mercury API and Ramp need an API key?
Mercury API takes an API key or an OAuth sign-in. Ramp uses an OAuth sign-in.
Can an agent call Mercury API and Ramp without installing anything?
Yes. Mercury API has a hosted endpoint at https://api.mercury.com/api/v1 and Ramp at https://api.ramp.com.
Other comparisons with Mercury API or Ramp
Machine-readable
- This page as Markdown
/compare/mercury-vs-ramp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mercury.json·/api/v1/tools/ramp.json - From a terminal
anchor compare mercury ramp(the CLI) - Over MCP
compare_tools {"a": "mercury", "b": "ramp"}at/mcp, no key