# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/airwallex-vs-payhawk
- Markdown: https://www.anchorterminal.com/compare/airwallex-vs-payhawk.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/airwallex-vs-payhawk.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/airwallex-vs-payhawk.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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 Issuing: grade B, 68.3/100, rank #210 of 842. Markdown https://www.anchorterminal.com/tools/airwallex.md · JSON https://www.anchorterminal.com/api/v1/tools/airwallex.json
- Payhawk API + MCP: grade C, 57.1/100, rank #561 of 842. Markdown https://www.anchorterminal.com/tools/payhawk.md · JSON https://www.anchorterminal.com/api/v1/tools/payhawk.json

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

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

| Category | Weight | Airwallex Spend and Issuing | Payhawk API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 77 | 58 | Airwallex Spend and Issuing +19 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 69 | 71 | Payhawk API + MCP +2 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 52 | Airwallex Spend and Issuing +17 |
| Security & auth | 14% (17.5 this run) | 84 | 71 | Airwallex Spend and Issuing +13 |
| Payments & pricing | 10% (12.5 this run) | 25 | 13 | Airwallex Spend and Issuing +12 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 66 | 53 | Airwallex Spend and Issuing +13 |
| Transparency & trust | 7% (8.8 this run) | 78 | 78 | even |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.3 · B** | **57.1 · C** | |

## Facts side by side

| Fact | Airwallex Spend and Issuing | Payhawk API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Airwallex | Payhawk Limited |
| Hosted endpoint | `https://api.airwallex.com` | `https://api.payhawk.com` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under Airwallex's service agreement and API terms. The plugin and skills repository is Apache-2.0 and `@airwallex/node-sdk` is MIT | Proprietary service under Payhawk's general terms and conditions |
| Tools exposed | none | 82 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-09-30 | 2026-10-08 |
| Terms last updated | 2025-06-20 | 2025-12-09 |
| Privacy policy last updated | no date given | 2026-06-29 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 7 stars, 44k npm/wk | none |

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/airwallex-vs-payhawk.json, and with the fewest tokens: https://www.anchorterminal.com/compare/airwallex-vs-payhawk.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "airwallex", "b": "payhawk"}`. From a terminal: `anchor compare airwallex payhawk`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/airwallex.json and https://www.anchorterminal.com/api/v1/tools/payhawk.json

## Other comparisons with Airwallex Spend and Issuing or Payhawk API + MCP

- [Airwallex Spend and Issuing vs BILL](https://www.anchorterminal.com/compare/airwallex-vs-bill.md)
- [Airwallex Spend and Issuing vs Brex](https://www.anchorterminal.com/compare/airwallex-vs-brex.md)
- [Airwallex Spend and Issuing vs Expensify](https://www.anchorterminal.com/compare/airwallex-vs-expensify.md)
- [Airwallex Spend and Issuing vs Mercury API](https://www.anchorterminal.com/compare/airwallex-vs-mercury.md)
- [Airwallex Spend and Issuing vs Pleo API + MCP](https://www.anchorterminal.com/compare/airwallex-vs-pleo.md)
- [Airwallex Spend and Issuing vs Ramp](https://www.anchorterminal.com/compare/airwallex-vs-ramp.md)
- [Airwallex Spend and Issuing vs Spendesk API + MCP](https://www.anchorterminal.com/compare/airwallex-vs-spendesk.md)
- [BILL vs Payhawk API + MCP](https://www.anchorterminal.com/compare/bill-vs-payhawk.md)
- [Brex vs Payhawk API + MCP](https://www.anchorterminal.com/compare/brex-vs-payhawk.md)
- [Expensify vs Payhawk API + MCP](https://www.anchorterminal.com/compare/expensify-vs-payhawk.md)
- [Mercury API vs Payhawk API + MCP](https://www.anchorterminal.com/compare/mercury-vs-payhawk.md)
- [Payhawk API + MCP vs Pleo API + MCP](https://www.anchorterminal.com/compare/payhawk-vs-pleo.md)
- [Payhawk API + MCP vs Ramp](https://www.anchorterminal.com/compare/payhawk-vs-ramp.md)
- [Payhawk API + MCP vs Spendesk API + MCP](https://www.anchorterminal.com/compare/payhawk-vs-spendesk.md)