Head to head · Spend transactions · October 2026 research run

Airwallex Spend and Issuing vs Pleo API + MCP

Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Pleo API + MCP's 62.9 (B), and leads in 6 of 7 scored categories. Pleo API + MCP leads on schema & documentation. Both do spend transactions.

Which one, for what

Airwallex Spend and Issuing B

Good 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, 77 against 71
  • Agent ergonomics, 69 against 55
  • Security & auth, 84 against 71
  • Payments & pricing, 25 against 15

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

Pleo API + MCP B

Good for An agent that completes, codes, reviews and queues expenses for a Pleo customer on the Optimise plan, or for a bookkeeping integration that exports accounting entries and syncs tags, tax codes, accounts and vendors.

Ahead on

  • Schema & documentation, 82 against 69

Watch for

The pricing page lists MCP on the Optimise plan only (£18 per user per month, three users minimum, sold through a demo)

Score by category

CategoryWeight this runAirwallex Spend and IssuingPleo API + MCPEdge
Reliability16%207771Airwallex Spend and Issuing +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26982Pleo API + MCP +13
Agent ergonomics13%16.26955Airwallex Spend and Issuing +14
Security & auth14%17.58471Airwallex Spend and Issuing +13
Payments & pricing10%12.52515Airwallex Spend and Issuing +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86664Airwallex Spend and Issuing +2
Transparency & trust7%8.87875Airwallex Spend and Issuing +3
Negative events≤1500
Total68.3 · B62.9 · B

Facts side by side

FactAirwallex Spend and IssuingPleo API + MCP
KindHTTP APIHTTP API
VendorAirwallexPleo Technologies A/S
Hosted endpointhttps://api.airwallex.comhttps://external.pleo.io
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
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 Pleo's Master Service Agreement, API Terms of Service and AI Access Terms
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-302026-10-02
Terms last updated2025-06-20no date given
Privacy policy last updatedno date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity7 stars, 44k npm/wknone

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.

Pleo API + MCP

The hosted MCP server acts with the connecting user's own Pleo permissions, is off until an admin enables it per entity, and can't move money, change cards or alter limits. It is listed only on the Optimise plan, its tool definitions aren't published, API keys need enabling by Pleo support, and no official SDK or SLA was found.

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

Pleo API + MCP

  1. Ask a company admin to enable Pleo MCP access under Settings, General, Pleo AI for each entity before connecting. It is off by default
  2. Name the entity in every request when working outside the default one. Each MCP request targets one entity and the choice doesn't persist
  3. Set the AI client to require approval for Pleo write tools. Pleo leaves confirmation to the client and doesn't enforce it server-side
  4. Send API keys as the Basic auth username with an empty password to external.pleo.io. Legacy tokens for openapi.pleo.io don't work there
  5. Budget every endpoint against one bucket of 600 requests a minute per credential, and on 429 wait for Retry-After or back off from one second
  6. Swap mcp.staging.pleo.io for mcp.pleo.io in the Claude Code command when moving from staging to production. Each needs its own OAuth sign-in

Questions

Which is better for AI agents, Airwallex Spend and Issuing or Pleo API + MCP?

Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Pleo API + MCP's 62.9 (B), and leads in 6 of 7 scored categories. Pleo API + MCP leads on schema & documentation.

Do Airwallex Spend and Issuing and Pleo API + MCP need an API key?

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

Can an agent call Airwallex Spend and Issuing and Pleo API + MCP without installing anything?

Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Pleo API + MCP at https://external.pleo.io.

Other comparisons with Airwallex Spend and Issuing or Pleo 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.