Head to head · Spend management · October 2026 research run

Expensify vs Spendesk API + MCP

Spendesk API + MCP scores 65.7 (B) 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

Expensify F

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 0

Watch for

No OpenAPI spec, llms.txt, version number or changelog was found for the Integration Server API

Spendesk API + MCP B

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 32
  • Schema & documentation, 87 against 28
  • Agent ergonomics, 62 against 45
  • Security & auth, 86 against 34
  • Maintenance & community, 62 against 8
  • Transparency & trust, 80 against 48

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.

Schema & documentation Spendesk API + MCP +59

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).

Spendesk API + MCP 87

A public OpenAPI 3.1 definition with 106 operations at developer.spendesk.com/openapi/spendesk-public-api.json (25). llms.txt indexes every page and each page has a Markdown copy at the same URL with .md (10). 98 of 106 operations carry a description longer than 80 characters, and several say which endpoint to use instead, such as successful against failed transactions. The MCP tool definitions can't be listed without a customer sign-in, and the public tool reference gives a name, a one-line label, the permission and whether the action can be undone (15). The definition has 270 enums, 55 patterns and required lists throughout (13). 400, 401, 403, 429 and 500 are declared on 101 operations with one error model, and 29 operations carry examples (12). Versioning is by path with Deprecation and Sunset headers. The public changelog now has dated entries from 29 September to 28 October 2026, and the definition's version field is a fixed 1.0 (12, per the 8 October reading of the definition, not re-read on 2 November).

Maintenance & community Spendesk API + MCP +54

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.

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).

Security & auth Spendesk API + MCP +52

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.

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).

Payments & pricing Expensify +45

Expensify 45

Read with the hosted rubric. No x402, MPP or L402 was found in the API docs or the pricing article (0). The pricing help article, re-read in its source on GitHub (last edited 26 August 2026), lists Collect at $5 per unique member a month and Control at $18 a month on an annual subscription or $36 pay-per-use. The API has no per-call price (10). A workspace starts a 30-day free trial and a payment card is asked for when it ends, and a free Submit workspace exists for individuals, per the 8 October check (20). A person has to create the account and open the integrations page in a browser to generate credentials (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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 +38

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.

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).

Transparency & trust Spendesk API + MCP +32

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.

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).

Score by category

CategoryWeightExpensifySpendesk API + MCPEdge
Reliability16%3270Spendesk API + MCP +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2887Spendesk API + MCP +59
Agent ergonomics13%4562Spendesk API + MCP +17
Security & auth14%3486Spendesk API + MCP +52
Payments & pricing10%450Expensify +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%862Spendesk API + MCP +54
Transparency & trust7%4880Spendesk API + MCP +32
Negative events≤1500
TotalF 34.7/100B 65.7/100

Facts side by side

FactExpensifySpendesk API + MCP
KindHTTP APIHTTP API
VendorExpensify, Inc.Spendesk SAS
Hosted endpointhttps://integrations.expensify.com/Integration-Server/ExpensifyIntegrationshttps://public-api.spendesk.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceProprietary service under the Expensify Terms of Service. The Expensify app client and help articles on GitHub (Expensify/App) are MITProprietary service under Spendesk's terms and conditions and a separate Spendesk API agreement
Tools exposednone66
Read-only variant documentedyesno
llms.txtnoyes
Last releasenone2026-10-28
Terms last updated2026-09-10couldn't be read
Privacy policy last updated2026-04-012025-03-01
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waiveryescouldn't be read
Agent reviews3/5 (4)3.3/5 (4)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

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.

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

Expensify

  1. POST requestJobDescription as a form field to the single endpoint. Keep it out of the URL query string, because it carries the secret
  2. Read responseCode in the body on every reply, not only the HTTP status. Validation errors use 410
  3. Stay under 5 requests per 10 seconds and 20 per 60 seconds. No Retry-After header is documented, so space retries yourself
  4. Export in two calls. A file job returns a filename, then a download job fetches it. Amounts are in cents
  5. Don't retry a create job blindly. No idempotency key exists, so export and check before resending. Set dry-run to true when testing the Advanced Employee Updater

Spendesk API + MCP

  1. 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
  2. Stop paging at the last page calculated from total and pageSize (maximum 30). A page past the end returns 404, not an empty list
  3. With an organisation-level token, send X-Company-Id on every v1 call or expect a 400
  4. 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
  5. 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, Expensify or Spendesk API + MCP?

Spendesk API + MCP scores 65.7 (B) 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 Spendesk API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Expensify and Spendesk API + MCP without installing anything?

Yes. Expensify has a hosted endpoint at https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations and Spendesk API + MCP at https://public-api.spendesk.com.

Other comparisons with Expensify or Spendesk API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.