Head to head · Spend transactions · October 2026 research run
Ramp vs Spendesk API + MCP
Spendesk API + MCP scores 62.3 (B) on agent readiness against Ramp's 57.3 (C), and leads in 4 of 7 scored categories. Ramp leads on payments & pricing and maintenance & community. Both do spend transactions.
Which one, for what
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
- Payments & pricing, 25 against 0
- Maintenance & community, 74 against 57
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
Good for A finance team already on Spendesk that wants an assistant to analyse spend, follow invoices and prepare the accounting close, or an ERP sync reading payables and settlements.
Ahead on
- Reliability, 55 against 30
- Security & auth, 86 against 79
- Transparency & trust, 80 against 70
Also in its favour
- No incidents deducted, where Ramp loses 3 points for them
Watch for
No public price, free tier or self-serve signup. API access and demo credentials are requested from a Spendesk representative
Score by category
| Category | Weight this run | Ramp | Spendesk API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 30 | 55 | Spendesk API + MCP +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 87 | Spendesk API + MCP +1 |
| Agent ergonomics | 13%16.2 | 66 | 62 | Ramp +4 |
| Security & auth | 14%17.5 | 79 | 86 | Spendesk API + MCP +7 |
| Payments & pricing | 10%12.5 | 25 | 0 | Ramp +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 74 | 57 | Ramp +17 |
| Transparency & trust | 7%8.8 | 70 | 80 | Spendesk API + MCP +10 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 57.3 · C | 62.3 · B |
Facts side by side
| Fact | Ramp | Spendesk API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Ramp Business Corporation | Spendesk SAS |
| Hosted endpoint | https://api.ramp.com | https://public-api.spendesk.com |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under the Ramp Platform Agreement and the API Agreement. The ramp-cli repository is MIT | Proprietary service under Spendesk's terms and conditions and a separate Spendesk API agreement |
| Tools exposed | none | 62 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-07 | 2026-09-29 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | couldn't be read | 2025-03-01 |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | 53 stars | none |
Verdicts
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.
Spendesk API + MCP
Scoped credentials, MCP write permissions that are off by default, an action log and published guidance on prompt injection suit delegated finance work. Access needs a paying customer and a request to Spendesk, most write endpoints are experimental, no official SDK was found, and the status page lists three critical incidents between 2 and 29 September 2026.
Before you call either
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
Spendesk API + MCP
- Request a token at POST /v1/auth/token with HTTP Basic (client ID and secret). It lasts 3,600 seconds, so renew on a 401
- Stop paging at the last page calculated from
totalandpageSize(maximum 30). A page past the end returns 404, not an empty list - With an organisation-level token, send
X-Company-Idon every v1 call or expect a 400 - The MCP server refuses API keys. Connect with OAuth authorisation code and PKCE, and treat
Tool not found(-32601) as a missing permission - After an unclear write result, read the object again before retrying. Creating a purchase order or supplier twice creates two
Questions
Which is better for AI agents, Ramp or Spendesk API + MCP?
Spendesk API + MCP scores 62.3 (B) on agent readiness against Ramp's 57.3 (C), and leads in 4 of 7 scored categories. Ramp leads on payments & pricing and maintenance & community.
Do Ramp and Spendesk API + MCP need an API key?
Ramp uses an OAuth sign-in. Spendesk API + MCP takes an API key or an OAuth sign-in.
Can an agent call Ramp and Spendesk API + MCP without installing anything?
Yes. Ramp has a hosted endpoint at https://api.ramp.com and Spendesk API + MCP at https://public-api.spendesk.com.
Other comparisons with Ramp or Spendesk API + MCP
Machine-readable
- This page as Markdown
/compare/ramp-vs-spendesk.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/ramp.json·/api/v1/tools/spendesk.json - From a terminal
anchor compare ramp spendesk(the CLI) - Over MCP
compare_tools {"a": "ramp", "b": "spendesk"}at/mcp, no key