Head to head · Spend management · October 2026 research run

Airwallex Spend and Issuing vs Expensify

Airwallex Spend and Issuing scores 69 (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

Airwallex Spend and Issuing B

Best for A company already banking with Airwallex in several currencies that wants an agent to issue cards with limits, read card transactions and expenses, load vendors, purchase orders and bills, and sync status to an ERP.

Ahead on

  • Reliability, 72 against 32
  • Schema & documentation, 69 against 28
  • Agent ergonomics, 69 against 45
  • Security & auth, 84 against 34
  • Maintenance & community, 66 against 8
  • Transparency & trust, 79 against 48

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

No OpenAPI spec was found. The reference is a Markdown page per endpoint, and the CLI prints one endpoint's schema at a time

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 38

Watch for

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

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 Airwallex Spend and Issuing +58

Airwallex Spend and Issuing 66

The airwallex-marketplace repository, which carries the AgentOS and developer plugins, tagged v0.2.12 on 14 October 2026 with updated developer skills. The newest API version is 2026-08-21 (30). Nine marketplace tags between 6 August and 14 October, and API version 2026-08-21 (20). Closed service. The changelog lists backwards-incompatible changes only, support is a help centre ticket or developer.support@airwallex.com, and the marketplace repository showed one open issue on 8 October. Response times couldn't be observed (9 of 15). Per the 8 October check, not re-read on 1 November, @airwallex/node-sdk was last published on 31 December 2025 as 2.1.0-beta.5 and is the only server SDK. The official MCP registry has no Airwallex entry of the vendor's own, only a third party's (io.github.codespar/mcp-airwallex) (4 of 15). The marketplace repository has no CI workflow, and the CLI is a binary installed by script whose version we couldn't read (3 of 10).

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.

Security & auth Airwallex Spend and Issuing +50

Airwallex Spend and Issuing 84

Scoped API keys grant Read or Write per resource at organisation or account level, can be edited, regenerated, duplicated and deleted, and can be tied to IP ranges. Keys travel only in headers and exchange for a bearer token that lasts 30 minutes. Partner apps, the CLI and the MCP server use OAuth with 64 scopes (30). Read is separate from Write, the AgentOS tools don't start transfers, conversions or payouts by default, CLI writes ask for confirmation, and cards take limits, merchant category rules and remote authorisation. Unrestricted admin keys still exist, and API writes have no confirmation step (17 of 20). The AgentOS page warns about indirect prompt injection from documents and web pages, tool poisoning by other MCP servers and auto-approve modes. Expense descriptions, comments and merchant names are untrusted text (11 of 15). GET /api/v1/audit_log/security_audit_logs records logins, user management and key changes for selected accounts only, key changes trigger an email, and no per-call log was found (8 of 15). security.txt with contacts, a bug bounty that has been invite-only since 13 July 2021, SOC 1 and SOC 2 Type 2, ISO 27001 and PCI DSS Level 1 on the trust centre (18 of 20).

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.

Schema & documentation Airwallex Spend and Issuing +41

Airwallex Spend and Issuing 69

No public OpenAPI spec was found. The paths we tried under /docs/api return the docs shell, and the CLI prints one endpoint's schema with --api-schema-only. Each endpoint has a structured Markdown reference page, which earns part credit (6 of 25). llms.txt at /docs/llms.txt and a Markdown twin of every guide and reference page (10). Endpoint and field descriptions state purpose, and deprecated endpoints name their replacement. Few say when not to call (14 of 20). Fields carry types, formats, required flags and possible values. Amounts are strings, and status filters warn that new values may appear (12 of 15). Every reference page has a cURL request and a response example, and Spend and Issuing each have an error code page. The create bill page lists 400, 404 and 500 but not 401 or 429 (12 of 15). Dated API versions (latest 2026-08-21), an x-api-version override and a changelog of backwards-incompatible changes by version (15).

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

Reliability Airwallex Spend and Issuing +40

Airwallex Spend and Issuing 72

Read with the hosted lines and scored on the REST API for Issuing and Spend. status.airwallex.com is a Statuspage site with 22 components in three groups (products, systems and data centres), among them Spend, Issuing, API Gateway and Sandbox (20). Its history feed, read on 1 November 2026, holds 25 entries back to 16 July. In the 90 days from 3 August the incidents on other products (Mastercard payments on 15 August, Google Pay on 16 September, USD deposits from 29 September to 5 October, Hong Kong payment methods on 8 and 9 October, PIX on 16 October, FX quotes and payouts on 27 October) don't touch Spend, Issuing or the API Gateway. The Sandbox component had certain simulation functions unavailable during unannounced essential maintenance from 26 to 29 October, a partial incident, so minor incidents only (20). Limits are published, 100 requests a second per account, 20 per endpoint and 50 concurrent in production, and 20, 10 and 10 in the sandbox (15). The docs ask for exponential backoff with jitter on 429 and creates take a required request_id. No Retry-After header is documented (12 of 15). No SLA was found, and the service agreement supplies the services as is and as available (0). Issuing is generally available, but the four Spend endpoints we read are marked beta, as are the Node SDK and the AgentOS skills (5 of 10).

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.

Transparency & trust Airwallex Spend and Issuing +31

Airwallex Spend and Issuing 79

Closed service with terms at stable URLs. The API terms are dated 20 June 2025, the service agreement took effect on 1 January 2026 and the Spend Management Terms are dated 6 December 2023. The plugin repository is Apache-2.0 and the Node SDK is MIT (16 of 30). The privacy policy describes retention by purpose and legal duty without fixed periods, names the countries where data is hosted, and says personal data may be processed to develop or improve Airwallex's AI and machine learning. A DPA is published as part of the customer agreement (18 of 30). Breaking changes ship as dated versions and an account stays on its version until it migrates. The API terms require a developer to implement an update within six months at most, give 30 days' notice of adverse changes to the terms, and let Airwallex discontinue services at its discretion. No retirement dates for old versions were found (12 of 20). A public list of processors and sub-processors, updated 7 October 2026, gives each one's category, role and region (18 of 20).

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.

Agent ergonomics Airwallex Spend and Issuing +24

Airwallex Spend and Issuing 69

page_size runs from 1 to 100 and defaults to 100 on Spend lists. No field selection or expand parameter was found, and the CLI has a --compact flag (15 of 25). Spend lists and card transaction events page with a page bookmark and page_after and page_before, while cards and legacy transactions use page_num and has_more. Filters cover status, sync status, legal entity and created-at range, with a 30-day default window (16 of 20). Errors return code, message, source and details, and 429 responses carry a trace_id. The Spend error page lists three codes (15 of 20). request_id is required on create calls for cards, bills and purchase orders. Airwallex says the production MCP server annotates write tools, which we couldn't read without an account. The two tools on the keyless Docs MCP server carry readOnlyHint (16 of 20). Creating a bill needs eleven required fields. The only server SDK is @airwallex/node-sdk in beta, and the CLI has a dry-run flag (7 of 15).

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

Score by category

CategoryWeightAirwallex Spend and IssuingExpensifyEdge
Reliability16%7232Airwallex Spend and Issuing +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6928Airwallex Spend and Issuing +41
Agent ergonomics13%6945Airwallex Spend and Issuing +24
Security & auth14%8434Airwallex Spend and Issuing +50
Payments & pricing10%3845Expensify +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%668Airwallex Spend and Issuing +58
Transparency & trust7%7948Airwallex Spend and Issuing +31
Negative events≤1500
TotalB 69/100F 34.7/100

Facts side by side

FactAirwallex Spend and IssuingExpensify
KindHTTP APIHTTP API
VendorAirwallexExpensify, Inc.
Hosted endpointhttps://api.airwallex.comhttps://integrations.expensify.com/Integration-Server/ExpensifyIntegrations
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Airwallex's service agreement and API terms. The plugin and skills repository is Apache-2.0 and @airwallex/node-sdk is MITProprietary service under the Expensify Terms of Service. The Expensify app client and help articles on GitHub (Expensify/App) are MIT
Read-only variant documentednoyes
llms.txtyesno
Last release2026-10-14none
Terms last updated2025-06-202026-09-10
Privacy policy last updatedno date given2026-04-01
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity7 stars, 44k npm/wknone
Agent reviews3.5/5 (4)3/5 (4)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Airwallex Spend and Issuing

Scoped API keys split read from write per resource, tokens last 30 minutes, and the sandbox opens at once with no contract. No OpenAPI spec was found, every Spend endpoint read is marked beta, the pricing page lists direct Spend API integration under the custom-priced Accelerate plan, and no SLA was found.

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.

Before you call either

Airwallex Spend and Issuing

  1. Exchange x-client-id and x-api-key at POST /api/v1/authentication/login once, then reuse the bearer token for 30 minutes. The login endpoint allows 100 requests a minute per key
  2. Create Spend keys with organisation-level permissions. With a key linked to several accounts, send x-login-as at login or the token carries no account permissions
  3. Send a fresh UUID as request_id on every create call and reuse the same value when retrying after a timeout
  4. Expect two pagination styles. Spend and card transaction events use the page bookmark with page_after and page_before. Cards and legacy transactions use page_num and has_more
  5. Card and expense lists default to the last 30 days. Pass both created-at bounds to read further back, and fetch a card singly to see its authorization_controls

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

Questions

Which is better for AI agents, Airwallex Spend and Issuing or Expensify?

Airwallex Spend and Issuing scores 69 (B) on agent readiness against Expensify's 34.7 (F), and leads in 6 of 7 scored categories. Expensify leads on payments & pricing.

Do Airwallex Spend and Issuing and Expensify need an API key?

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

Can an agent call Airwallex Spend and Issuing and Expensify without installing anything?

Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Expensify at https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations.

Other comparisons with Airwallex Spend and Issuing or Expensify

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.