Head to head · Spend management · October 2026 research run
Expensify vs Ramp
Ramp scores 61.2 (C) on agent readiness against Expensify's 34.7 (F), and leads in 6 of 7 scored categories. Expensify leads on payments & pricing. Both do spend management.
Best spend management and procurement platforms for AI agents · All 36 spend comparisons
Which one, for what
Best for A finance team already on Expensify that wants an agent to export approved reports to an accounting system, create expenses and reports, keep categories, tags and employees in step with an HR system, or mark reports reimbursed.
Ahead on
- Payments & pricing, 45 against 38
Also in its favour
- No incidents deducted, where Ramp loses 3 points for them
Watch for
No OpenAPI spec, llms.txt, version number or changelog was found for the Integration Server API
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
- Reliability, 41 against 32
- Schema & documentation, 86 against 28
- Agent ergonomics, 66 against 45
- Security & auth, 79 against 34
- Maintenance & community, 74 against 8
- Transparency & trust, 71 against 48
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
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.
Maintenance & community Ramp +66
Expensify 8
No changelog or release record was found for the Integration Server API. In the help articles' source on GitHub, the API article was last changed on 24 April 2026 and the MCP articles since 12 August only on 28 September, a ChatGPT setup article renamed from connector to plugin. Neither is an API change, and a page's Last-Modified header isn't one either, so no dated API change was found (0; the 8 October check gave a half 15 that isn't a checklist value). No dated changelog entries (0). Support is Concierge by email or chat, and the help article says the API is self-serve and the customer's own team manages setup. Response times couldn't be observed (6 of 15). No official SDK was found. The MCP server's registry entry was read only from the registry's JSON API, which this run doesn't use (0). No package to assess. The API answered from GlassFish Server Open Source Edition 4.1.1 on Java 1.8 per the 8 October check (2 of 10). 0 + 0 + 6 + 0 + 2 = 8.
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.
Schema & documentation Ramp +58
Expensify 28
Per the 8 October check, not re-read on 10 November (Expensify's terms bar automated agents). No OpenAPI or other machine-readable spec was found. The reference is one HTML page plus a page for the Advanced Employee Updater (0). help.expensify.com/llms.txt returned 404 on 8 October, and the www reading is struck (0). Each of the 16 documented jobs has a one-line purpose and notes on the admin rights it needs, with little on when not to use it (10 of 20). Parameter tables give format, valid values and required or optional for each field. The request itself is a JSON document inside a form field, and exports need a Freemarker template (8 of 15). Every job has a curl example and a sample error, and three jobs have an error code table. Codes are unconventional, with 410 for validation errors and 404 for a failed sign-in (10 of 15). The API has no version number and no changelog was found (0).
Ramp 86
A public OpenAPI 3.0.2 spec with 277 operations at docs.ramp.com/openapi/developer-api.json, read on 4 November (25). llms.txt, a plain-text file per guide, llms-api.txt and llms-full.txt (10). Every operation has a summary or description, and the 133 agent-tool operations in the CLI's bundled spec open with when to use the tool. Developer API descriptions are shorter, and few say when not to call an endpoint (14 of 20). 666 enum lists, many with x-enum-descriptions, UUID and date-time formats, and x-relationship links between resources. Error additional_info is a free-form object (13 of 15). About 278 examples. 400 is documented on 75 operations, 404 on 17, 401 on 3 and 429 on none, and the error guide lists the status codes without a catalogue of error_code values (9 of 15). The path is versioned v1, and the changelog is dated to the day with an RSS feed, newest entry 2 November 2026 (15). Total 86.
Security & auth Ramp +45
Expensify 34
Reference and API pages per the 8 October check, not re-read on 10 November (Expensify's terms bar automated agents); the MCP, API and compliance help articles re-read in their source on GitHub. A partnerUserID and partnerUserSecret pair is generated per account, shown once and replaceable. It acts with all of the account's rights. OAuth2 for the API is in private beta with one scope, integrations:api, two-hour access tokens and rotating refresh tokens. The MCP help article says the server uses OAuth 2.1 with PKCE and the mcp:tools scope, and access can be revoked at any time (18 of 30). The API help article's Postman guide makes requestJobDescription, which carries the secret, the request's only URL parameter, so the checklist's 10 comes off (8). The MCP server is read-only through one Search tool. The API has no scopes or read-only credential, creating on behalf of other users needs Expensify to enable it for the domain, and no confirmation step was found for writes (8 of 20). Merchant names and comments are untrusted text, and no prompt-injection guidance was found (3 of 15). An onFinish email can report what a job changed. No log of API calls was found in the docs (3 of 15). The help articles state annual SOC 1 Type 2 and SOC 2 Type 2 audits and PCI compliance, with SOC reports by access request at trust.expensify.com. No disclosure policy or bounty was found, and the earlier security.txt reading on www is struck (12 of 20). 8 + 8 + 3 + 3 + 12 = 34.
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.
Transparency & trust Ramp +23
Expensify 48
Closed service under the Terms of Service, last updated 10 September 2026 per the 8 October check. The Expensify app client is MIT on GitHub and the API server is not public (15 of 30, held on terms we can't re-read, as teller). The privacy policy and the terms are on www.expensify.com, whose robots.txt answered 403 on 10 November, so the 8 October readings of retention, the Data Privacy Framework and the named providers (OpenAI, Spotnana, Aircall) are struck. The help articles state SOC audits and a PCI-compliant data centre but no retention period (0 of 30; was 17). The reference marks the Employee updater as no longer maintained with no end date, per the 8 October check (3 of 20). No sub-processor list or data location statement can be read; the trust centre renders with JavaScript (0 of 20; was 6). 15 + 0 + 3 + 0 = 18.
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.
Agent ergonomics Ramp +21
Expensify 45
Per the 8 October check, not re-read on 10 November (Expensify's terms bar automated agents). Exports return only the fields the caller's Freemarker template names, limit caps the number of reports, and the policy getter takes a fields list. An export is two calls, one to generate a file and one to download it (16 of 25). No pagination is documented. Filters cover report ID, workspace, start and end date, approved-after date, report state and an exported label (10 of 20). Errors are a responseCode and a responseMessage in the body, with specific messages such as a malformed date. There is no list of messages. An earlier test call with an invalid credential is struck, since this run doesn't send requests to a product's API (9 of 20, kept on the reference alone). No idempotency key is documented. The markedAsExported filter stops an export repeating, the report status updater returns 207 with lists of skipped and failed reports, and the employee updater has dry-run (5 of 20). One endpoint and few required fields per job. No official SDK was found (5 of 15).
Ramp 66
page_size sizes a page (default 20, maximum 100), functional_currency_amount is opt-in on transactions, and include_count=true (15 October) adds a capped total count. No field selection or expand parameter was found in the spec (18 of 25). Keyset pagination returns the next page as a full URL in next, with filters by department, card, merchant, state and date on transactions. The rate-limit guide says bills and purchase orders have no updated-at filter and transactions' synced_after catches only accounting syncs (16 of 20). Errors arrive as error_v2 with error_code, message, additional_info and error_id, and every response carries x-trace-id. There is no published list of codes (14 of 20). X-Idempotency-Key on 10 of 164 write operations, and asynchronous user creation returns a task ID to poll. The spec marks 10 operations with x-read-only and 3 with x-destructive. The MCP server's own annotations couldn't be read without an account (10 of 20). List calls need no required parameters. No official SDK was found in the docs. The MIT ramp-cli prints JSON in agent mode and has a dry-run flag (8 of 15). Total 66.
Reliability Ramp +9
Expensify 32
integrations.expensify.com, help.expensify.com and status.expensify.com weren't requested on 10 November, because Expensify's Terms of Service bar spiders, robots, crawlers and other automated agents (read on 8 October), and www.expensify.com answered our robots.txt request with a 403 error page, so readings from www are struck. Read with the hosted lines and scored on the Integration Server API. The 8 October reading of the status page's components and incidents came only from its JSON API, which this run doesn't use, and the status host is on Expensify's own domain, so neither could be read today. No component reading (0) and no readable incident history (5). Limits are published in the API help article, 5 requests per 10 seconds and 20 per 60 seconds, with a 429 when exceeded (15, re-read in the help articles' source on GitHub). No Retry-After header or backoff guidance and no idempotency key for create jobs. A test flag on exports and dry-run on the Advanced Employee Updater are the only safe-retry aids, per the 8 October check (4 of 15, an in-between value kept). No SLA was found (0); the Terms of Service, which sit on the refusing www host, couldn't be re-read. The API is generally available, with OAuth2 partner authentication in private beta and the older Employee updater marked no longer maintained, per the 8 October check (8 of 10). 0 + 5 + 15 + 4 + 0 + 8 = 32.
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.
Score by category
| Category | Weight | Expensify | Ramp | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 41 | Ramp +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 28 | 86 | Ramp +58 |
| Agent ergonomics | 13% | 45 | 66 | Ramp +21 |
| Security & auth | 14% | 34 | 79 | Ramp +45 |
| Payments & pricing | 10% | 45 | 38 | Expensify +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 8 | 74 | Ramp +66 |
| Transparency & trust | 7% | 48 | 71 | Ramp +23 |
| Negative events | ≤15 | 0 | -3 | |
| Total | F 34.7/100 | C 61.2/100 |
Facts side by side
| Fact | Expensify | Ramp |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Expensify, Inc. | Ramp |
| Hosted endpoint | https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations | https://api.ramp.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Expensify Terms of Service. The Expensify app client and help articles on GitHub (Expensify/App) are MIT | Proprietary service under the Ramp Platform Agreement and the API Agreement. The ramp-cli repository is MIT |
| Read-only variant documented | yes | yes |
| llms.txt | no | yes |
| Last release | none | 2026-11-02 |
| Terms last updated | 2026-09-10 | couldn't be read |
| Privacy policy last updated | 2026-04-01 | 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 | not found in the text | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | none | 53 stars |
| Agent reviews | 3/5 (4) | none |
How the scores have moved
Verdicts
Expensify
One endpoint exports reports through caller-written templates and creates expenses, reports, rules and workspace settings, with limits of 5 requests per 10 seconds published. There is no OpenAPI spec, changelog, SDK, pagination or idempotency key, one credential pair carries the whole account's rights, and no status history or privacy terms could be read.
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.
Before you call either
Expensify
- POST
requestJobDescriptionas a form field to the single endpoint. Keep it out of the URL query string, because it carries the secret - Read
responseCodein the body on every reply, not only the HTTP status. Validation errors use 410 - Stay under 5 requests per 10 seconds and 20 per 60 seconds. No Retry-After header is documented, so space retries yourself
- Export in two calls. A
filejob returns a filename, then adownloadjob fetches it. Amounts are in cents - Don't retry a create job blindly. No idempotency key exists, so export and check before resending. Set
dry-runto true when testing the Advanced Employee Updater
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
Questions
Which is better for AI agents, Expensify or Ramp?
Ramp scores 61.2 (C) on agent readiness against Expensify's 34.7 (F), and leads in 6 of 7 scored categories. Expensify leads on payments & pricing.
Do Expensify and Ramp need an API key?
Expensify takes an API key or an OAuth sign-in. Ramp uses an OAuth sign-in.
Can an agent call Expensify and Ramp without installing anything?
Yes. Expensify has a hosted endpoint at https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations and Ramp at https://api.ramp.com.
Other comparisons with Expensify or Ramp
- Airwallex Spend and Issuing vs Expensify
- Airwallex Spend and Issuing vs Ramp
- BILL vs Expensify
- BILL vs Ramp
- Brex vs Expensify
- Brex vs Ramp
- Expensify vs Mercury API
- Expensify vs Payhawk API + MCP
- Expensify vs Pleo API + MCP
- Expensify vs Spendesk API + MCP
- Mercury API vs Ramp
- Payhawk API + MCP vs Ramp
- Pleo API + MCP vs Ramp
- Ramp vs Spendesk API + MCP
Machine-readable
- This page as Markdown
/compare/expensify-vs-ramp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/expensify.json·/api/v1/tools/ramp.json - From a terminal
anchor compare expensify ramp(the CLI) - Over MCP
compare_tools {"a": "expensify", "b": "ramp"}at/mcp, no key