Get an audit

Head to head · Spend transactions · October 2026 research run

Airwallex Spend and Issuing vs Payhawk API + MCP

Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Payhawk API + MCP's 57.1 (C), and leads in 5 of 7 scored categories. Both do spend transactions.

Airwallex Spend and IssuingAirwallex · HTTP API B68.3/100#210 of 841 Payhawk API + MCPPayhawk Limited · HTTP API C57.1/100#561 of 841

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 58
  • Agent ergonomics, 69 against 52
  • Security & auth, 84 against 71
  • Payments & pricing, 25 against 13
  • Maintenance & community, 66 against 53

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

Payhawk API + MCP C

Good for A finance team already on Payhawk that wants an ERP or accounting sync, master data kept in step, purchase orders raised from another system, or an assistant that answers spend questions and prepares approvals.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No self-serve route. The API needs a Payhawk customer account, and a development sandbox is requested through a form

Score by category

CategoryWeight this runAirwallex Spend and IssuingPayhawk API + MCPEdge
Reliability16%207758Airwallex Spend and Issuing +19
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26971Payhawk API + MCP +2
Agent ergonomics13%16.26952Airwallex Spend and Issuing +17
Security & auth14%17.58471Airwallex Spend and Issuing +13
Payments & pricing10%12.52513Airwallex Spend and Issuing +12
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86653Airwallex Spend and Issuing +13
Transparency & trust7%8.87878even
Negative events≤1500
Total68.3 · B57.1 · C

Facts side by side

FactAirwallex Spend and IssuingPayhawk API + MCP
KindHTTP APIHTTP API
VendorAirwallexPayhawk Limited
Hosted endpointhttps://api.airwallex.comhttps://api.payhawk.com
TransportsHTTPHTTP
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 Payhawk's general terms and conditions
Tools exposednone82
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-09-302026-10-08
Terms last updated2025-06-202025-12-09
Privacy policy last updatedno date given2026-06-29
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.

Payhawk API + MCP

The Developer API has a public OpenAPI 3.1 definition with 179 operations, read-only or full-access keys and a published limit of 15 requests a second. It needs a Payhawk customer account, no official SDK or API changelog was found, and the 82-tool MCP server is added by hand because it is not yet in the assistant directories.

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

Payhawk API + MCP

  1. Send the key in X-Payhawk-ApiKey or as a Bearer token to https://api.payhawk.com/api/v3. A read-only key returns 403 on writes
  2. Page lists with $skip and $take. The help centre gives 1,000 a page and the definition a maximum of 10,000, so count what comes back
  3. Pass $filter as URL-encoded JSON, for example {"status":{"$equal":"draft"}}. Date filters compare the date part only
  4. Keep to 15 requests a second and wait for Retry-After on a 429. Do not send Idempotency-Key when creating a per diem expense, which returns 400
  5. Use a group-level key and the /groups/{groupId} paths for master data in a multi-entity group. Expenses and payments stay on account paths

Questions

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

Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Payhawk API + MCP's 57.1 (C), and leads in 5 of 7 scored categories.

Do Airwallex Spend and Issuing and Payhawk 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 Payhawk API + MCP without installing anything?

Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Payhawk API + MCP at https://api.payhawk.com.

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

Get an auditSee a sample report