Head to head · Spend management · October 2026 research run
Ramp vs Spendesk API + MCP
Spendesk API + MCP scores 65.7 (B) on agent readiness against Ramp's 61.2 (C), and leads in 4 of 7 scored categories. Ramp leads on payments & pricing and maintenance & community. Both do spend management.
Best spend management and procurement platforms for AI agents · All 36 spend comparisons
Which one, for what
Ramp C
Best 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, 38 against 0
- Maintenance & community, 74 against 62
Watch for
No public status page was found. status.ramp.com doesn't resolve, and no status link appears in the docs or trust centre
Best 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, 70 against 41
- Security & auth, 86 against 79
- Transparency & trust, 80 against 71
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
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Ramp +38
Ramp 38
Read with the hosted rubric. Ramp's API isn't paid for by x402, MPP or L402. Ramp does let an agent pay other sellers by x402 from a funded wallet or by Stripe MPP, which is a product capability and not a way to buy access (0). Plan prices are public, Free at $0 per user per month and Plus at $15 per user per month plus a platform fee by team size that isn't stated, with Enterprise on request. The API has no per-call price (10). The Free plan needs no payment card, but it needs an approved Ramp business account, and sandbox access is by request form, so partial credit (15 of 20). The Developer MCP server answers docs questions with no account. Account data needs an admin to create an app in the dashboard or a person to complete an OAuth sign-in (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Spendesk API + MCP 0
Read with the hosted rubric. No x402, MPP or L402 (0). The pricing page describes a fixed monthly fee plus variable fees per transaction and asks for a quote, with no figures (0). No free tier or trial found. Demo credentials are requested from Spendesk together with API access (0). A person at a paying customer creates the key or approves the OAuth connection, and dynamic client registration is open to supported partners only (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
Reliability Spendesk API + MCP +29
Ramp 41
Read with the hosted lines and scored on the Developer API, the surface an outside agent calls with a token. No public status page was found. status.ramp.com still doesn't resolve on 4 November, and llms.txt, the rate-limit, error and MCP guides and the trust centre link none (0). With no page there is no incident history to read, which the checklist scores 5 (5, from 0, the reading other listings without a status page take). The limit is published, 200 requests per 10 seconds per source IP, plus 100 token requests per 10 seconds, with 429 able to block requests for 60 seconds (15). The rate-limit guide now says to honour Retry-After when present and otherwise use exponential backoff with jitter, and the error and timeout guides say to check whether a write completed and follow the endpoint's idempotency behaviour before retrying it. X-Idempotency-Key is accepted on 10 of 164 write operations, payments, funds and card creation among them, and five more take an idempotency_key body field. Documented 429 handling with safe-retry guidance on writes (15, from 9). No SLA was found in the Platform Agreement or the API Agreement, per the 8 October reading (0). The API is v1, but 104 of 277 operations carry x-beta (6 of 10). Total 41.
Spendesk API + MCP 70
Read with the hosted lines and scored on the public REST API and the MCP server on the same host. status.spendesk.com on Atlassian Statuspage has components by product area with incident history, though none for the public API (20). The status host's robots.txt disallows /api/, so the 8 October reading from incidents.json is struck and the window from 4 August was read from the /history pages on 2 November. It lists 11 incidents opened in the window, each naming one product area or a share of users. The longest platform-wide one, "Spendesk access is down" on 2 September (about 1 hour 55 minutes), "affected platform access and performance for some users". Sign-in to the application failed for about 59 minutes on 29 September, one component. International transfers in the EEA, Amazon card tokenisation, e-invoices, email notifications, 3DS on iOS and subscription card details were each one product. None says the API was down for everyone, so this run reads every one as partial, minor only (20). Limits are published as 1,000 requests a minute per company and credential and 500 concurrent requests (15). Every response carries x-ratelimit-limit, remaining and reset headers and the docs give pacing guidance. Live reads with Cache-Control: no-cache (28 October 2026) answer 429 with Retry-After, but an Idempotency-Key exists only for creating an intake (10). The docs say the team attempts to guarantee 99 per cent availability, which is a target and not a published SLA (0). The read API is generally available, while cards, transactions, invoices, purchase orders, webhooks and MCP write actions are experimental or beta (5).
Maintenance & community Ramp +12
Ramp 74
The changelog's latest entry is 2 November 2026 (Canadian applications, beta), and ramp-cli v0.2.91 was tagged on 3 November (30). Dated changelog entries from 10 August to 2 November 2026 number 33, and ramp-cli has 94 tags in its clone (20). Closed service with a daily-dated changelog and RSS feed. Support is a ticket raised from the developer console and answered by email. Response times couldn't be observed (10 of 15). No official SDK was found, and Ramp's MCP server wasn't in the official MCP registry on 8 October, where the only Ramp entry was a third party's (com.mcparmory/ramp). The official CLI is current (6 of 15). The CLI repository runs CI (ci.yml) with binary and npm package workflows. It installs from a script or Homebrew, not PyPI (8 of 10). Total 74.
Spendesk API + MCP 62
The newest changelog entry, "Request the latest data with Cache-Control: no-cache", was created on 28 October 2026 (30). Six changelog entries were created between 5 and 28 October 2026 (5, 10, 10, 10, 16 and 28 October), each describing a change to the API or the MCP server, so the backfill doubt of 8 October no longer applies (20). Closed service with a public changelog and a support address for API consumers (support-public-api@spendesk.com). No public forum or issue tracker was found (8). No official SDK on npm or PyPI, and no entry in the official MCP registry on 2 November 2026 (0). Nothing is packaged to assess. Convention pages state they are replayed against the demo environment weekly, last on 29 September 2026, per the 8 October check (4).
Transparency & trust Spendesk API + MCP +9
Ramp 71
Closed service with terms at stable URLs, the Platform Agreement (updated 22 September 2026) and the API Agreement (26 March 2026). The legal pages render only by script, and the 8 October check read them from the script files the pages load, which this run doesn't count. The lines resting on them are held, as ref's and Prefactor's were when their script-drawn terms were struck. The CLI is MIT (16 of 30). The privacy policy (21 August 2026) was read from the same script files. It describes retention by criteria without fixed periods and says Ramp will give notice and obtain permission before training a general-purpose model on company content. The DPA (10 July 2026) deletes personal data on written request after termination (held, 20 of 30). The changelog labels deprecated fields and names replacements, but the API Agreement, per the same struck reading, says Ramp may change or discontinue the APIs with or without notice, and no notice period is published (held, 6 of 20). The trust centre, re-read on 4 November, lists sub-processors and key service providers and posts update notifications, with the full documents behind an access request and NDA (13 of 20). Total 55.
Spendesk API + MCP 80
Closed service. The terms page lists the customer terms, a DORA addendum, a Spendesk API agreement and partner terms, with a subscription for updates and previous versions. We couldn't open the documents, whose links are drawn by JavaScript (12). The privacy policy (March 2025, version 0.5) names a DPO, EU hosting and retention periods for the data Spendesk controls, and refers to a DPA for platform data, which we didn't read. The MCP docs say that data read by an assistant goes to the assistant's provider (20). Deprecation and Sunset headers carry dates and the policy supports the current and previous version, with no minimum notice period stated. Experimental endpoints may change (12). The sub-processor list dated 31 August 2026 gives each processor's address, purpose, data types, location and safeguards (20).
Security & auth Spendesk API + MCP +7
Ramp 79
OAuth 2.0 with client credentials or the authorisation code grant, 84 scopes in the spec in resource:read and resource:write form, tokens bound to scopes at issue and sent in the Authorization header, a revoke endpoint, and PKCE (S256) on the MCP server, per the 8 October metadata reading (30). Read scopes are separate from write scopes, card numbers need cards:read_vault and a production review by Ramp, and MCP and CLI users act with their own Ramp permissions. The MCP guide now gives a Read-only connection option on the consent screen, which hides tools that make changes (Full access is the default), and admins can limit MCP use by role, department or user. A client credentials token acts with the app creator's permissions, MCP tools can approve transactions and reimbursements for an approver, and no confirmation step was found for writes (15 of 20). Memos, comments, merchant names and receipts are untrusted text, and no prompt-injection guidance was found (3 of 15). GET /developer/v1/audit-logs/events filters by user, date, event type and actor type (Plus plan), responses carry a trace ID, and MCP calls are attributed to the signed-in user (13 of 15). A valid security.txt expiring 18 March 2027 (re-read on 4 November), and the trust centre lists SOC 1 and SOC 2 Type 2 reports, ISO 27001, ISO 42001, PCI DSS, FedRAMP Moderate and a Responsible Disclosure entry. No bounty is stated (18 of 20). Total 79.
Spendesk API + MCP 86
OAuth 2.0 authorisation code with PKCE (S256), 37 documented scopes, one-hour access tokens and rotating refresh tokens for MCP and partner apps. API keys carry only the scopes ticked, expire within a year, and a token can request fewer scopes than its key (30). Read and write are separate scopes. MCP write permissions are off on every connection until an Admin enables them with a second factor, each user then ticks them, and every call checks the user's role. Confirmation before a write is an instruction to the assistant, not enforced, and production has no dry-run mode apart from export previews (17). The safety page names prompt injection through supplier names, invoice lines and documents, and advises read-only use and approval of each action (12). An action log per MCP connection records date, tool, status, user, company and correlation ID, without arguments. No equivalent for API keys was found (12). security.txt, updated on 28 October 2026, is valid until 1 October 2027 and describes a bug bounty paying up to 2,000 euros. The security page states ISO 27001:2022. No SOC 2 report or public advisories were found, and the trust centre needs JavaScript (15).
Score by category
| Category | Weight | Ramp | Spendesk API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 41 | 70 | Spendesk API + MCP +29 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 87 | Spendesk API + MCP +1 |
| Agent ergonomics | 13% | 66 | 62 | Ramp +4 |
| Security & auth | 14% | 79 | 86 | Spendesk API + MCP +7 |
| Payments & pricing | 10% | 38 | 0 | Ramp +38 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 74 | 62 | Ramp +12 |
| Transparency & trust | 7% | 71 | 80 | Spendesk API + MCP +9 |
| Negative events | ≤15 | -3 | 0 | |
| Total | C 61.2/100 | B 65.7/100 |
Facts side by side
| Fact | Ramp | Spendesk API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Ramp | 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 | 66 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-11-02 | 2026-10-28 |
| 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 |
| Agent reviews | none | 3.3/5 (4) |
How the scores have moved
Verdicts
Ramp
A 277-operation OpenAPI spec is public, OAuth 2.0 scopes split read from write, MCP connections can be read-only, and the guides cover 429, Retry-After and safe write retries. No public status page or SLA was found, 104 operations are marked beta, and field removals are logged the day they ship.
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 and changed without notice in October 2026, and no official SDK was found.
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 10 seconds per source IP. On 429 honour
Retry-Afterwhen present, otherwise back off with jitter, since a burst can block for 60 seconds - Reuse access tokens. Token requests have their own limit of 100 per 10 seconds per source IP
- Send
X-Idempotency-Keywhere an endpoint accepts it. Elsewhere read back after a timeout before retrying a write, since an error doesn't prove nothing changed
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, treat
Tool not found(-32601) as a missing permission, and reconnect to refresh the tool list - 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 65.7 (B) on agent readiness against Ramp's 61.2 (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
- Airwallex Spend and Issuing vs Ramp
- Airwallex Spend and Issuing vs Spendesk API + MCP
- BILL vs Ramp
- BILL vs Spendesk API + MCP
- Brex vs Ramp
- Brex vs Spendesk API + MCP
- Expensify vs Ramp
- Expensify vs Spendesk API + MCP
- Mercury API vs Ramp
- Mercury API vs Spendesk API + MCP
- Payhawk API + MCP vs Ramp
- Payhawk API + MCP vs Spendesk API + MCP
- Pleo API + MCP vs Ramp
- Pleo API + MCP vs 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