# Airwallex Spend and Issuing vs Spendesk API + MCP

> Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Spendesk API + MCP's 62.3 (B), and leads in 4 of 7 scored categories. Spendesk API + MCP leads on schema & documentation. Both do spend transactions. Category scores, facts, verdicts and agent notes side by…

- Canonical: https://www.anchorterminal.com/compare/airwallex-vs-spendesk
- Markdown: https://www.anchorterminal.com/compare/airwallex-vs-spendesk.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/airwallex-vs-spendesk.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/airwallex-vs-spendesk.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-08

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

- Airwallex Spend and Issuing: grade B, 68.3/100, rank #187 of 722. Markdown https://www.anchorterminal.com/tools/airwallex.md · JSON https://www.anchorterminal.com/api/v1/tools/airwallex.json
- Spendesk API + MCP: grade B, 62.3/100, rank #342 of 722. Markdown https://www.anchorterminal.com/tools/spendesk.md · JSON https://www.anchorterminal.com/api/v1/tools/spendesk.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 55
- Agent ergonomics, 69 against 62
- Payments & pricing, 25 against 0
- Maintenance & community, 66 against 57

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

### Spendesk API + MCP (B)

Good 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:
- Schema & documentation, 87 against 69

Watch for: No public price, free tier or self-serve signup. API access and demo credentials are requested from a Spendesk representative


## Score by category

| Category | Weight | Airwallex Spend and Issuing | Spendesk API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 77 | 55 | Airwallex Spend and Issuing +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 69 | 87 | Spendesk API + MCP +18 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 62 | Airwallex Spend and Issuing +7 |
| Security & auth | 14% (17.5 this run) | 84 | 86 | Spendesk API + MCP +2 |
| Payments & pricing | 10% (12.5 this run) | 25 | 0 | Airwallex Spend and Issuing +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 66 | 57 | Airwallex Spend and Issuing +9 |
| Transparency & trust | 7% (8.8 this run) | 78 | 80 | Spendesk API + MCP +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.3 · B** | **62.3 · B** | |

## Facts side by side

| Fact | Airwallex Spend and Issuing | Spendesk API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Airwallex | Spendesk SAS |
| Hosted endpoint | `https://api.airwallex.com` | `https://public-api.spendesk.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 Spendesk's terms and conditions and a separate Spendesk API agreement |
| Tools exposed | none | 62 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-30 | 2026-09-29 |
| Terms last updated | 2025-06-20 | couldn't be read |
| Privacy policy last updated | no date given | 2025-03-01 |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| 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.

**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, no official SDK was found, and the status page lists three critical incidents between 2 and 29 September 2026.

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

### 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, and treat `Tool not found` (-32601) as a missing permission
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, Airwallex Spend and Issuing or Spendesk API + MCP?

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

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

Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Spendesk API + MCP at https://public-api.spendesk.com.


## For agents

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

## Other comparisons with Airwallex Spend and Issuing or Spendesk 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)
- [BILL vs Spendesk API + MCP](https://www.anchorterminal.com/compare/bill-vs-spendesk.md)
- [Brex vs Spendesk API + MCP](https://www.anchorterminal.com/compare/brex-vs-spendesk.md)
- [Expensify vs Spendesk API + MCP](https://www.anchorterminal.com/compare/expensify-vs-spendesk.md)
- [Mercury API vs Spendesk API + MCP](https://www.anchorterminal.com/compare/mercury-vs-spendesk.md)
- [Pleo API + MCP vs Spendesk API + MCP](https://www.anchorterminal.com/compare/pleo-vs-spendesk.md)
- [Ramp vs Spendesk API + MCP](https://www.anchorterminal.com/compare/ramp-vs-spendesk.md)