Head to head · Spend management · October 2026 research run

Airwallex Spend and Issuing vs BILL

Airwallex Spend and Issuing scores 69 (B) on agent readiness against BILL's 62.6 (B), and leads in 4 of 7 scored categories. BILL leads on reliability and schema & documentation. Both do spend management.

Best spend management and procurement platforms for AI agents · All 36 spend comparisons

Which one, for what

Airwallex Spend and Issuing B

Best 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, 79 against 67

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

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 B

Best 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

  • Reliability, 81 against 72
  • 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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Airwallex Spend and Issuing +34

Airwallex Spend and Issuing 66

The airwallex-marketplace repository, which carries the AgentOS and developer plugins, tagged v0.2.12 on 14 October 2026 with updated developer skills. The newest API version is 2026-08-21 (30). Nine marketplace tags between 6 August and 14 October, and API version 2026-08-21 (20). Closed service. The changelog lists backwards-incompatible changes only, support is a help centre ticket or developer.support@airwallex.com, and the marketplace repository showed one open issue on 8 October. Response times couldn't be observed (9 of 15). Per the 8 October check, not re-read on 1 November, @airwallex/node-sdk was last published on 31 December 2025 as 2.1.0-beta.5 and is the only server SDK. The official MCP registry has no Airwallex entry of the vendor's own, only a third party's (io.github.codespar/mcp-airwallex) (4 of 15). The marketplace repository has no CI workflow, and the CLI is a binary installed by script whose version we couldn't read (3 of 10).

BILL 32

The changelog's latest dated entry is 21 May 2026, 166 days before 3 November. The docs platform's metadata showed bill-v3-api.json updated on 5 October 2026 (per the 20 October check, not re-read on 3 November), and the MCP server guide is still dated 16 October, so the API is still changing without dated notes. The 19 October launch is a press release and a blog post, not a changelog entry (20 of 30). No dated changelog entry falls in the last 90 days (0). Closed service with a changelog, an RSS feed and a developer programme email address. Response times couldn't be observed, and the changelog has been silent for over four months (7 of 15). No official SDK was found, and the MCP server isn't in the official MCP registry, as its own guide says of connector directories. A Postman collection is published (2 of 15). There is no package to assess. The spec and docs are current (3 of 10).

Security & auth Airwallex Spend and Issuing +28

Airwallex Spend and Issuing 84

Scoped API keys grant Read or Write per resource at organisation or account level, can be edited, regenerated, duplicated and deleted, and can be tied to IP ranges. Keys travel only in headers and exchange for a bearer token that lasts 30 minutes. Partner apps, the CLI and the MCP server use OAuth with 64 scopes (30). Read is separate from Write, the AgentOS tools don't start transfers, conversions or payouts by default, CLI writes ask for confirmation, and cards take limits, merchant category rules and remote authorisation. Unrestricted admin keys still exist, and API writes have no confirmation step (17 of 20). The AgentOS page warns about indirect prompt injection from documents and web pages, tool poisoning by other MCP servers and auto-approve modes. Expense descriptions, comments and merchant names are untrusted text (11 of 15). GET /api/v1/audit_log/security_audit_logs records logins, user management and key changes for selected accounts only, key changes trigger an email, and no per-call log was found (8 of 15). security.txt with contacts, a bug bounty that has been invite-only since 13 July 2021, SOC 1 and SOC 2 Type 2, ISO 27001 and PCI DSS Level 1 on the trust centre (18 of 20).

BILL 56

The AP and AR API signs in with a user's username and password plus a developer key, sent in the request body, and the session carries that user's role with no scopes. The Spend & Expense API takes a token an ADMIN user generates, with no scopes documented. Sync tokens for app partners can't make payments. The MCP server uses OAuth with PKCE (S256) and a revocation endpoint, with only openid and offline_access as scopes. No secret travels in a URL (16 of 30). Creating a payment, adding a funding bank account and enabling vendor auto-pay need a session trusted by multi-factor authentication, user roles limit who can pay, bill approval policies are in the API, and the MCP server is read-only. No confirmation step was found for other writes, such as creating a vendor card (16 of 20). Bill and invoice text, vendor names and memos are untrusted content, and no prompt-injection guidance was found (3 of 15). An audit trail endpoint covers vendor creates and edits with the user and source, and users can review and disconnect MCP connections under Connected apps. The AI hub launched on 19 October logs the actions BILL's own AI takes, in the web app. It isn't said to cover MCP or API calls, and no audit endpoint for other objects or for API calls was found (7 of 15). Annual SOC 1 and SOC 2 Type II audits and a vulnerability disclosure programme on HackerOne. No bounty is stated and security.txt returns 404 (14 of 20).

Schema & documentation BILL +14

Airwallex Spend and Issuing 69

No public OpenAPI spec was found. The paths we tried under /docs/api return the docs shell, and the CLI prints one endpoint's schema with --api-schema-only. Each endpoint has a structured Markdown reference page, which earns part credit (6 of 25). llms.txt at /docs/llms.txt and a Markdown twin of every guide and reference page (10). Endpoint and field descriptions state purpose, and deprecated endpoints name their replacement. Few say when not to call (14 of 20). Fields carry types, formats, required flags and possible values. Amounts are strings, and status filters warn that new values may appear (12 of 15). Every reference page has a cURL request and a response example, and Spend and Issuing each have an error code page. The create bill page lists 400, 404 and 500 but not 401 or 429 (12 of 15). Dated API versions (latest 2026-08-21), an x-api-version override and a changelog of backwards-incompatible changes by version (15).

BILL 83

Two public OpenAPI 3.0.1 files, bill-v3-api.json with 314 operations and connect-events-api.json with 12, per the 20 October check, not re-read on 3 November (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). Every operation has a summary and a description, with a median of 209 characters, links to the guide and notes such as the MFA requirement on payments. Few say when not to call an endpoint (14 of 20). 110 enums, 499 required lists, 271 formats, 82 length limits and 32 patterns. The spec declares no security schemes, so credentials appear as header parameters, and filters is a string with its own syntax (11 of 15). 1,025 examples. Errors are documented as one 4XX and one 5XX array on 311 operations, with 12 common codes explained and over 500 left to the v2 Errors.json call (10 of 15). The path is versioned v3 and the changelog is dated with an RSS feed. Its latest entry is 21 May 2026, and neither the MCP server, whose guide was updated on 16 October, nor the 19 October AI launch has an entry (13 of 15).

Transparency & trust Airwallex Spend and Issuing +12

Airwallex Spend and Issuing 79

Closed service with terms at stable URLs. The API terms are dated 20 June 2025, the service agreement took effect on 1 January 2026 and the Spend Management Terms are dated 6 December 2023. The plugin repository is Apache-2.0 and the Node SDK is MIT (16 of 30). The privacy policy describes retention by purpose and legal duty without fixed periods, names the countries where data is hosted, and says personal data may be processed to develop or improve Airwallex's AI and machine learning. A DPA is published as part of the customer agreement (18 of 30). Breaking changes ship as dated versions and an account stays on its version until it migrates. The API terms require a developer to implement an update within six months at most, give 30 days' notice of adverse changes to the terms, and let Airwallex discontinue services at its discretion. No retirement dates for old versions were found (12 of 20). A public list of processors and sub-processors, updated 7 October 2026, gives each one's category, role and region (18 of 20).

BILL 67

Closed service with terms at stable URLs, the Developer Terms (effective 3 March 2026) and the General Terms of Service (last updated 10 February 2025) (15 of 30). The Privacy Notice (effective 30 January 2026) covers the products and describes retention by criteria without fixed periods. No data processing agreement was found on the legal index, and the notice, unchanged on 20 October, says nothing on training models with customer data. The 19 October launch blog says BILL's AI gets sharper with every transaction across every business on the platform, which the notice doesn't address. That gap is the one already counted here (12 of 30). The Developer Terms commit BILL to commercially reasonable efforts at 30 days' notice of deprecations and breaking changes, and the same document keeps the right to change or discontinue the API at any time. The MFA phone change of 3 April 2026 was announced on 6 February, and the FAQ says there are no plans to deprecate v2 (14 of 20). No sub-processor list or data location statement was found. The legal index has a bank partners page (3 of 20).

Reliability BILL +9

Airwallex Spend and Issuing 72

Read with the hosted lines and scored on the REST API for Issuing and Spend. status.airwallex.com is a Statuspage site with 22 components in three groups (products, systems and data centres), among them Spend, Issuing, API Gateway and Sandbox (20). Its history feed, read on 1 November 2026, holds 25 entries back to 16 July. In the 90 days from 3 August the incidents on other products (Mastercard payments on 15 August, Google Pay on 16 September, USD deposits from 29 September to 5 October, Hong Kong payment methods on 8 and 9 October, PIX on 16 October, FX quotes and payouts on 27 October) don't touch Spend, Issuing or the API Gateway. The Sandbox component had certain simulation functions unavailable during unannounced essential maintenance from 26 to 29 October, a partial incident, so minor incidents only (20). Limits are published, 100 requests a second per account, 20 per endpoint and 50 concurrent in production, and 20, 10 and 10 in the sandbox (15). The docs ask for exponential backoff with jitter on 429 and creates take a required request_id. No Retry-After header is documented (12 of 15). No SLA was found, and the service agreement supplies the services as is and as available (0). Issuing is generally available, but the four Spend endpoints we read are marked beta, as are the Node SDK and the AgentOS skills (5 of 10).

BILL 81

Read with the hosted lines and scored on the v3 REST API. A Statuspage site at www.billcomstatus.com has 15 components, among them API Servers, Virtual Card and Multi-Factor Authentication (20). Its incident history shows nothing after 15 April 2026, only scheduled maintenance windows, the latest on 30 October with another posted for 13 November, so the 90 days from 5 August are clean (30). Limits are published with numbers, 20,000 requests an hour per developer key, three concurrent per key per organisation, 200 logins an hour and 60 Spend & Expense calls a minute per token (15). The docs give the two limit errors, BDC_1144 and BDC_1322, and a backoff example in Python. No Retry-After header is documented, and no idempotency key is accepted on the v3 API's write operations, payments included (7 of 15). The docs say production is backed by SLAs, but no SLA document was found and the General Terms of Service supply the service as is (0). The v3 API is generally available. The MCP server is beta (9 of 10).

Agent ergonomics Airwallex Spend and Issuing +9

Airwallex Spend and Issuing 69

page_size runs from 1 to 100 and defaults to 100 on Spend lists. No field selection or expand parameter was found, and the CLI has a --compact flag (15 of 25). Spend lists and card transaction events page with a page bookmark and page_after and page_before, while cards and legacy transactions use page_num and has_more. Filters cover status, sync status, legal entity and created-at range, with a 30-day default window (16 of 20). Errors return code, message, source and details, and 429 responses carry a trace_id. The Spend error page lists three codes (15 of 20). request_id is required on create calls for cards, bills and purchase orders. Airwallex says the production MCP server annotates write tools, which we couldn't read without an account. The two tools on the keyless Docs MCP server carry readOnlyHint (16 of 20). Creating a bill needs eleven required fields. The only server SDK is @airwallex/node-sdk in beta, and the CLI has a dry-run flag (7 of 15).

BILL 60

max sizes a page, with a default of 20 and a ceiling of 100 on AP and AR lists and 50 on Spend & Expense lists. No field selection was found (16 of 25). Lists return nextPage and prevPage cursors and take filters with nine operators, including ranges on createdTime and updatedTime, and sort (19 of 20). Errors are an array of objects with a BDC_ code, severity, category and message, and the common codes page gives a fix for each of 12 codes. Rate limit errors don't state when to retry (15 of 20). No idempotency key on the 203 write operations of the v3 API. X-Idempotent-Key is accepted on two webhook subscription calls, and a bulk payment request succeeds or fails as a whole. The MCP server is read-only, its guide of 16 October says names, parameters and responses can change between releases, and its tool annotations couldn't be read without an account (5 of 20). AP and AR calls need a login first and two headers on every call, and the session ends after 35 minutes idle. No official SDK was found, only a Postman collection (5 of 15).

Score by category

CategoryWeightAirwallex Spend and IssuingBILLEdge
Reliability16%7281BILL +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6983BILL +14
Agent ergonomics13%6960Airwallex Spend and Issuing +9
Security & auth14%8456Airwallex Spend and Issuing +28
Payments & pricing10%3838even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6632Airwallex Spend and Issuing +34
Transparency & trust7%7967Airwallex Spend and Issuing +12
Negative events≤1500
TotalB 69/100B 62.6/100

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-10-142026-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
Agent reviews3.5/5 (4)2.5/5 (4)

The panel on both

One of the 2 reviewers who reviewed both rates Airwallex Spend and Issuing higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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 69 (B) on agent readiness against BILL's 62.6 (B), and leads in 4 of 7 scored categories. BILL leads on reliability and 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.