Head to head · Spend transactions · October 2026 research run

Airwallex Spend and Issuing vs Brex

Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Brex's 60.7 (C), and leads in 3 of 7 scored categories. Brex 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 60
  • Security & auth, 84 against 72
  • Transparency & trust, 78 against 67

Also in its favour

  • No incidents deducted, where Brex loses 3 points for them

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

Brex C

Good for A finance team already on Brex that wants an agent to read expenses and transactions, issue and lock cards, set spend limits, upload receipts and pay vendors.

Ahead on

  • Schema & documentation, 80 against 69

Watch for

The Expenses API update endpoint accepts only memo, so an outside agent can't set a category or custom field on an expense through it

Score by category

CategoryWeight this runAirwallex Spend and IssuingBrexEdge
Reliability16%207760Airwallex Spend and Issuing +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26980Brex +11
Agent ergonomics13%16.26970Brex +1
Security & auth14%17.58472Airwallex Spend and Issuing +12
Payments & pricing10%12.52525even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86666even
Transparency & trust7%8.87867Airwallex Spend and Issuing +11
Negative events≤150-3
Total68.3 · B60.7 · C

Facts side by side

FactAirwallex Spend and IssuingBrex
KindHTTP APIHTTP API
VendorAirwallexBrex LLC
Hosted endpointhttps://api.airwallex.comhttps://api.brex.com
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 Brex Platform Agreement and the Brex Access Agreement
Tools exposednone43
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-09-302026-10-01
Terms last updated2025-06-20no date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
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.

Brex

User tokens carry per-resource scopes with read-only variants, every POST and PUT accepts an Idempotency-Key, and ten OpenAPI specs are public. The Expenses API changes only an expense's memo, there is no customer sandbox or official SDK, and the status page logs API errors lasting over four hours on 4 August 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

Brex

  1. Ask an account admin or card admin for a user token with only the scopes the task needs, and prefer the .readonly variants. A token unused for 90 days expires.
  2. Send a stored Idempotency-Key on every POST and PUT. Create transfer and Create card reject requests without one.
  3. Only settled transactions are returned. Poll card and cash transactions with posted_at_start and a lookback of at least one day.
  4. Keep under 1,000 requests in 60 seconds per client and account, and back off exponentially with jitter on 429.
  5. Send only ASCII in free-text fields, and quote the X-Brex-Trace-Id response header when reporting an error.

Questions

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

Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Brex's 60.7 (C), and leads in 3 of 7 scored categories. Brex leads on schema & documentation.

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

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

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

Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Brex at https://api.brex.com.

Other comparisons with Airwallex Spend and Issuing or Brex

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.