Head to head · Spend transactions · October 2026 research run

Airwallex Spend and Issuing vs BILL

Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against BILL's 60.9 (C), and leads in 4 of 7 scored categories. BILL 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

  • Agent ergonomics, 69 against 60
  • Security & auth, 84 against 56
  • Maintenance & community, 66 against 32
  • Transparency & trust, 78 against 66

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

BILL C

Good for A US company already on BILL that wants an agent to create and read bills, run approvals, schedule vendor payments, raise invoices and manage budgets, vendor cards, card transactions and reimbursements.

Ahead on

  • Schema & documentation, 83 against 69

Watch for

POST /v3/login takes a user's username and password with a developer key, and the session carries that user's role with no scopes

Score by category

CategoryWeight this runAirwallex Spend and IssuingBILLEdge
Reliability16%207781BILL +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26983BILL +14
Agent ergonomics13%16.26960Airwallex Spend and Issuing +9
Security & auth14%17.58456Airwallex Spend and Issuing +28
Payments & pricing10%12.52525even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86632Airwallex Spend and Issuing +34
Transparency & trust7%8.87866Airwallex Spend and Issuing +12
Negative events≤1500
Total68.3 · B60.9 · C

Facts side by side

FactAirwallex Spend and IssuingBILL
KindHTTP APIHTTP API
VendorAirwallexBILL Holdings, Inc.
Hosted endpointhttps://api.airwallex.comhttps://gateway.prod.bill.com/connect
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 BILL Developer Terms and the BILL General Terms of Service
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-302026-05-21
Terms last updated2025-06-202026-03-03
Privacy policy last updatedno date given2026-01-30
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.

BILL

A public OpenAPI 3.0.1 spec covers 326 operations, a self-serve sandbox moves no money, and payments need a session trusted by multi-factor authentication. The AP and AR API signs in with a user's password and has no scopes, no idempotency key protects payment calls, and no official SDK 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

BILL

  1. Sign in with POST /v3/login and send sessionId and devKey as headers on every AP and AR call. The session expires after 35 minutes idle
  2. Send the apiToken header alone on /v3/spend/ paths. Spend & Expense calls need no login and are limited to 60 a minute per token
  3. Complete the MFA challenge before POST /v3/payments. An untrusted session fails with BDC_1361
  4. Read back payments before retrying a failed POST /v3/payments. No idempotency key is accepted, so a blind retry can pay twice
  5. Keep to three concurrent requests per developer key per organisation and 20,000 an hour. After BDC_1144, wait for the next hour

Questions

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

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

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

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

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

Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and BILL at https://gateway.prod.bill.com/connect.

Other comparisons with Airwallex Spend and Issuing or BILL

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.