{ "data": { "a": { "slug": "airwallex", "name": "Airwallex Spend and Issuing", "vendor": "Airwallex", "vendorUrl": "https://www.airwallex.com", "kind": "http-api", "category": "spend-management", "summary": "Airwallex is a multi-currency business account with company cards, expense management and bill pay. Its REST API issues and controls cards, reads card transactions and expenses, and creates vendors, purchase orders and bills. A CLI and MCP server use OAuth.", "url": "https://www.anchorterminal.com/tools/airwallex", "markdownUrl": "https://www.anchorterminal.com/tools/airwallex.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/airwallex.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/airwallex.json", "repo": "https://github.com/airwallex/airwallex-marketplace", "license": "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", "transports": [ "http" ], "remoteUrl": "https://api.airwallex.com", "packages": [ { "registry": "npm", "name": "@airwallex/node-sdk" } ], "auth": "mixed", "authNotes": "Access is self-serve in the sandbox and for an Airwallex customer in production. A user with the Owner, Admin or Developer role creates a key in the web app under Developer, then API keys. Scoped keys grant Read or Write per resource and can be tied to IP ranges, and admin keys are unrestricted. A key and client ID exchange at `POST /api/v1/authentication/login` for a bearer token that lasts 30 minutes. Spend resources need organisation-level permissions. The CLI, the MCP servers and partner apps use OAuth 2.0 with 64 scopes, and only Owner, Admin and Finance Admin users can consent. The service agreement says Airwallex must first approve API access, and the CLI guide says card and Issuing commands may need support to enable them.", "pricing": "freemium", "pricingNotes": "No separate API fee is published. The US pricing page lists Explore at $0 with up to 10 free Spend users, Grow at $12 per active Spend user a month up to 250 users, and Accelerate on request. It lists direct Spend API integration with an ERP under Accelerate and sends platform API and embedded finance use to sales. A sandbox account opens at once from a signup form with no payment card or contract, so an agent's owner can start there. Card, FX and transfer fees are on a separate fee schedule (checked 2026-10-08).", "priceSummary": "$12 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the API reference pages read or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 7, "npmWeekly": 44464, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://www.airwallex.com/docs/", "llmsTxt": "https://www.airwallex.com/docs/llms.txt", "capabilities": [ "spend.transactions", "spend.cards", "spend.expenses", "spend.bills", "spend.procurement" ], "tags": [ "hosted", "freemium", "api-key", "oauth", "mcp", "cli", "llms-txt", "webhooks", "sandbox", "multi-currency", "soc2", "pci-dss", "iso27001", "status-page", "security-txt", "bug-bounty" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 68.3, "grade": "B", "agentReady": false, "rank": 210, "ranked": true, "rankOf": 842, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 66, "payments": 25, "reliability": 77, "schema": 69, "security": 84, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Scoped API keys grant Read or Write per resource, can be limited to listed IP ranges, and exchange for bearer tokens that last 30 minutes", "A sandbox account opens at once from a signup form, with the full API except Connected Accounts and simulation endpoints for card transactions", "Rate limits are published with numbers, 100 requests a second per account and 20 per endpoint in production, with backoff guidance for 429", "Create calls such as `POST /api/v1/issuing/cards/create` and `POST /api/v1/spend/bills/create` require a `request_id`, so a retried request isn't applied twice", "status.airwallex.com has separate Spend, Issuing, API Gateway and Sandbox components, and none was named in an incident between 27 April and 8 October 2026" ], "weaknesses": [ "No OpenAPI spec was found. The reference is a Markdown page per endpoint, and the CLI prints one endpoint's schema at a time", "Each Spend endpoint we read (expenses, vendors, bills, purchase orders) is marked beta, and the pricing page lists direct Spend API integration under the custom-priced Accelerate plan", "The Spend API reads expenses and sets sync status. No endpoint was found to attach a receipt, code a card expense or approve one", "The only server SDK is `@airwallex/node-sdk`, still in beta and last published on 31 December 2025", "No SLA was found, and the Security Audit Logs API is open to selected accounts only and covers logins, user changes and key changes, not API calls" ], "agentNotes": [ "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", "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", "Send a fresh UUID as `request_id` on every create call and reuse the same value when retrying after a timeout", "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`", "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`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 66, "payments": 25, "reliability": 77, "schema": 69, "security": 84, "transparency": 64 }, "provenanceScore": 92 }, "connect": { "install": "curl -fsSL https://static.airwallex.com/developer-tools/airwallex-cli/install.sh | sh", "http": "curl -X POST https://api.sandbox.airwallex.com/api/v1/authentication/login \\\n -H 'Content-Type: application/json' \\\n -H 'x-api-key: {{YOUR_API_KEY}}' \\\n -H 'x-client-id: {{YOUR_CLIENT_ID}}'", "claudeCode": "claude mcp add-json airwallex '{ \"type\": \"http\", \"url\": \"https://mcp.airwallex.com/mcp\" }'", "config": { "mcpServers": { "airwallex": { "type": "http", "url": "https://mcp.airwallex.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/spend.transactions", "tool": "https://letme.dev/airwallex" }, "area": "domain-data", "unitPrices": [ { "item": "Explore plan", "unit": "seat-month", "usd": 0, "note": "Up to 10 free Spend users. No separate API fee is published" }, { "item": "Grow plan", "unit": "seat-month", "usd": 12, "note": "Per active Spend user, up to 250. Accelerate, which lists direct Spend API integration, is priced on request" } ], "provenance": { "legalEntity": "Airwallex US, LLC", "domain": "airwallex.com", "domainRegistered": "2015-11-08", "endpointOnVendorDomain": true, "terms": "https://www.airwallex.com/us/terms/application-programming-interface-terms", "privacy": "https://www.airwallex.com/us/terms/privacy-policy-airwallex", "statusPage": "https://status.airwallex.com", "changelog": "https://www.airwallex.com/docs/api/changelog", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms and privacy policy cited are the US ones. The US privacy policy names Airwallex US, LLC among the entities responsible, and the site footer gives Airwallex US, LLC (NMLS #1928093) as the licensed money transmitter. Other regions have their own entities and documents.", "The API terms (API Developer Terms and Conditions) are dated 20 June 2025. The service agreement was last updated on 2 December 2025 and took effect on 1 January 2026. The Spend Management Terms are dated 6 December 2023.", "The API answers at api.airwallex.com and api.sandbox.airwallex.com, and the MCP servers at mcp.airwallex.com and mcp.sandbox.airwallex.com.", "www.airwallex.com/.well-known/security.txt lists bugbounty@airwallex.com and security@airwallex.com and an expiry of 30 June 2030. The timestamp has a space inside it, which isn't the RFC 9116 format.", "The US privacy policy shows no last-updated line in the text we read. The global policy at /terms/privacy-policy is dated 26 February 2026.", "RDAP for airwallex.com gives a registration date of 2015-11-08." ], "score": 92 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/airwallex.json", "live": { "slug": "airwallex", "probe": { "target": "https://api.airwallex.com", "method": "get", "lastAt": "2026-10-09T09:26:41.683956164Z", "lastOk": true, "lastStatus": 404, "lastMs": 90, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 43, "p95ms24h": 72, "samples24h": 151, "samples30d": 151, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 101, "ok": 101 } ] }, "vendorStatus": { "page": "https://status.airwallex.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T09:24:52.834444734Z" }, "updatedAt": "2026-10-09T09:26:41.683956164Z" } }, "answer": "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.", "b": { "slug": "payhawk", "name": "Payhawk API + MCP", "vendor": "Payhawk Limited", "vendorUrl": "https://payhawk.com", "kind": "http-api", "category": "spend-management", "summary": "Spend management platform from Payhawk Limited in London, covering company cards, expenses, bills, purchase orders and travel. Outside agents reach it through a REST Developer API with read-only or full-access keys, and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/payhawk", "markdownUrl": "https://www.anchorterminal.com/tools/payhawk.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/payhawk.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/payhawk.json", "license": "Proprietary service under Payhawk's general terms and conditions", "transports": [ "http" ], "remoteUrl": "https://api.payhawk.com", "packages": [], "auth": "mixed", "authNotes": "Access needs a Payhawk customer account. An Administrator, an IT Administrator or a user with a custom role creates an API key in the portal under Settings, Integrations, choosing read-only or full access, and can regenerate it. The key goes in the `X-Payhawk-ApiKey` header or as a Bearer token. Two system-generated keys per account cannot be deleted by users. Group-level keys reach the group endpoints. If the key is not active, the API page says to write to partners@payhawk.com. The MCP server accepts OAuth 2 authorisation code with PKCE, where each user signs in with a Payhawk login and the assistant acts with that user's role.", "pricing": "paid", "pricingNotes": "Sold by quote per module (Travel, Cards and Expenses, Accounts Payable, Procurement) on annual or multi-year contracts, with unit-based charges for extra cards, reimbursements, purchase orders and invoices. The one published price is the Growth programme at 149 pounds a month for single-entity firms in the UK or EEA with fewer than 20 employees, with an optional 7-day trial for eligible customers. The API page says the API is free for all Payhawk accounts, and the pricing page lists Developer API access and the MCP server in the modules. A development sandbox is requested through a form on the API page (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI definition, the help centre or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 82, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developers.payhawk.com", "llmsTxt": "https://payhawk.com/llms.txt", "openapi": "https://api.payhawk.com/api/v3/docs.json", "capabilities": [ "spend.transactions", "spend.expenses", "spend.cards", "spend.bills", "spend.procurement" ], "tags": [ "hosted", "enterprise", "api-key", "oauth", "mcp", "openapi", "llms-txt", "webhooks", "sales-led", "status-page", "soc2", "iso27001" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 57.1, "grade": "C", "agentReady": false, "rank": 561, "ranked": true, "rankOf": 842, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 53, "payments": 13, "reliability": 58, "schema": 71, "security": 71, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public OpenAPI 3.1 definition with 105 paths and 179 operations, covering expenses, cards, fund accounts, suppliers, purchase orders and 24 webhook event types", "API keys are created as read-only or full access, sent in a header, and managed by administrators or a custom role", "The limit of 15 requests a second is stated on every operation, and responses carry RateLimit headers with Retry-After on a 429", "The MCP server acts with the signed-in user's own role, previews every write for confirmation, and never starts a payment or transfer", "SOC 1 and SOC 2 Type 2, ISO 27001, PCI DSS Level 1 and a penetration test attestation are downloadable from the trust page" ], "weaknesses": [ "No self-serve route. The API needs a Payhawk customer account, and a development sandbox is requested through a form", "No official SDK on npm or PyPI, no API changelog and no deprecation policy were found. Release notes cover the product only", "The API page's FAQ contradicts the definition on the host name, the page size and whether expenses can be created or reviewed", "The status page is drawn by script, so its incident history could not be read. The terms disclaim service levels", "The MCP server has 82 tools, is not in the official MCP registry, and no guidance on prompt injection was found" ], "agentNotes": [ "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", "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", "Pass `$filter` as URL-encoded JSON, for example `{\"status\":{\"$equal\":\"draft\"}}`. Date filters compare the date part only", "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", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.1 } ], "editorialScores": { "ergonomics": 52, "maintenance": 53, "payments": 13, "reliability": 58, "schema": 71, "security": 71, "transparency": 55 }, "provenanceScore": 100 }, "connect": { "http": "curl https://api.payhawk.com/api/v3/accounts/YOUR_ACCOUNT_ID/fund-accounts \\\n -H \"X-Payhawk-ApiKey: YOUR_API_KEY\"" }, "letme": { "capability": "https://letme.dev/spend.transactions", "tool": "https://letme.dev/payhawk" }, "area": "domain-data", "provenance": { "legalEntity": "Payhawk Limited", "domain": "payhawk.com", "domainRegistered": "2003-07-06", "endpointOnVendorDomain": true, "terms": "https://payhawk.com/terms", "privacy": "https://payhawk.com/privacy", "statusPage": "https://status.payhawk.com", "changelog": "https://payhawk.com/release-notes", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms name Payhawk Limited (company number 11747263, Chancery House, 53-64 Chancery Lane, London WC2A 1QS) as the contracting entity worldwide and Payhawk Inc., a Delaware corporation, in the US. Payhawk EOOD in Sofia owns the platform.", "Cards are issued by Payhawk Financial Services UAB in the EEA, Payhawk Financial Services Limited in the UK and Cross River Bank in the US, per the site footer.", "The API answers at api.payhawk.com and the MCP server at mcp.payhawk.com. An unauthenticated POST to /mcp returned 401 with a WWW-Authenticate header naming the protected resource metadata.", "payhawk.com/.well-known/security.txt has a contact, a policy link and an expiry of 1 January 2030.", "The terms were last updated on 9 December 2025, the privacy policy on 29 June 2026 and the Data Processing Addendum on 26 June 2026.", "The release notes cover the product. No changelog for the API was found.", "RDAP for payhawk.com gives a registration date of 2003-07-06. The terms' company number dates the company later, so the domain predates the vendor." ], "score": 100 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/payhawk.json", "live": { "slug": "payhawk", "probe": { "target": "https://api.payhawk.com", "method": "get", "lastAt": "2026-10-09T09:27:00.11605886Z", "lastOk": true, "lastStatus": 404, "lastMs": 123, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 53, "p95ms24h": 123, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-09", "probes": 20, "ok": 20 } ] }, "vendorStatus": { "page": "https://status.payhawk.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:58:24.812233514Z" }, "updatedAt": "2026-10-09T09:27:00.11605886Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Airwallex", "b": "Payhawk Limited", "name": "Vendor" }, { "a": "https://api.airwallex.com", "b": "https://api.payhawk.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "Proprietary service under Payhawk's general terms and conditions", "name": "Licence" }, { "a": "none", "b": "82", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-10-08", "name": "Last release" }, { "a": "2025-06-20", "b": "2025-12-09", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-06-29", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "7 stars, 44k npm/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "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.", "question": "Which is better for AI agents, Airwallex Spend and Issuing or Payhawk API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Airwallex Spend and Issuing and Payhawk API + MCP need an API key?" }, { "answer": "Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Payhawk API + MCP at https://api.payhawk.com.", "question": "Can an agent call Airwallex Spend and Issuing and Payhawk API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 77 against 58", "Agent ergonomics, 69 against 52", "Security \u0026 auth, 84 against 71", "Payments \u0026 pricing, 25 against 13", "Maintenance \u0026 community, 66 against 53" ], "also": null, "goodFor": "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.", "slug": "airwallex", "watchFor": "No OpenAPI spec was found. The reference is a Markdown page per endpoint, and the CLI prints one endpoint's schema at a time" }, { "aheadOn": null, "also": null, "goodFor": "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.", "slug": "payhawk", "watchFor": "No self-serve route. The API needs a Payhawk customer account, and a development sandbox is requested through a form" } ], "job": { "capability": "spend.transactions", "name": "Spend transactions" }, "others": [ { "json": "https://www.anchorterminal.com/compare/airwallex-vs-bill.json", "title": "Airwallex Spend and Issuing vs BILL", "url": "https://www.anchorterminal.com/compare/airwallex-vs-bill" }, { "json": "https://www.anchorterminal.com/compare/airwallex-vs-brex.json", "title": "Airwallex Spend and Issuing vs Brex", "url": "https://www.anchorterminal.com/compare/airwallex-vs-brex" }, { "json": "https://www.anchorterminal.com/compare/airwallex-vs-expensify.json", "title": "Airwallex Spend and Issuing vs Expensify", "url": "https://www.anchorterminal.com/compare/airwallex-vs-expensify" }, { "json": "https://www.anchorterminal.com/compare/airwallex-vs-mercury.json", "title": "Airwallex Spend and Issuing vs Mercury API", "url": "https://www.anchorterminal.com/compare/airwallex-vs-mercury" }, { "json": "https://www.anchorterminal.com/compare/airwallex-vs-pleo.json", "title": "Airwallex Spend and Issuing vs Pleo API + MCP", "url": "https://www.anchorterminal.com/compare/airwallex-vs-pleo" }, { "json": "https://www.anchorterminal.com/compare/airwallex-vs-ramp.json", "title": "Airwallex Spend and Issuing vs Ramp", "url": "https://www.anchorterminal.com/compare/airwallex-vs-ramp" }, { "json": "https://www.anchorterminal.com/compare/airwallex-vs-spendesk.json", "title": "Airwallex Spend and Issuing vs Spendesk API + MCP", "url": "https://www.anchorterminal.com/compare/airwallex-vs-spendesk" }, { "json": "https://www.anchorterminal.com/compare/bill-vs-payhawk.json", "title": "BILL vs Payhawk API + MCP", "url": "https://www.anchorterminal.com/compare/bill-vs-payhawk" }, { "json": "https://www.anchorterminal.com/compare/brex-vs-payhawk.json", "title": "Brex vs Payhawk API + MCP", "url": "https://www.anchorterminal.com/compare/brex-vs-payhawk" }, { "json": "https://www.anchorterminal.com/compare/expensify-vs-payhawk.json", "title": "Expensify vs Payhawk API + MCP", "url": "https://www.anchorterminal.com/compare/expensify-vs-payhawk" }, { "json": "https://www.anchorterminal.com/compare/mercury-vs-payhawk.json", "title": "Mercury API vs Payhawk API + MCP", "url": "https://www.anchorterminal.com/compare/mercury-vs-payhawk" }, { "json": "https://www.anchorterminal.com/compare/payhawk-vs-pleo.json", "title": "Payhawk API + MCP vs Pleo API + MCP", "url": "https://www.anchorterminal.com/compare/payhawk-vs-pleo" }, { "json": "https://www.anchorterminal.com/compare/payhawk-vs-ramp.json", "title": "Payhawk API + MCP vs Ramp", "url": "https://www.anchorterminal.com/compare/payhawk-vs-ramp" }, { "json": "https://www.anchorterminal.com/compare/payhawk-vs-spendesk.json", "title": "Payhawk API + MCP vs Spendesk API + MCP", "url": "https://www.anchorterminal.com/compare/payhawk-vs-spendesk" } ], "scores": [ { "airwallex": 77, "by": 19, "edge": "airwallex", "key": "reliability", "name": "Reliability", "payhawk": 58, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "airwallex": 69, "by": 2, "edge": "payhawk", "key": "schema", "name": "Schema \u0026 documentation", "payhawk": 71, "weight": 13 }, { "airwallex": 69, "by": 17, "edge": "airwallex", "key": "ergonomics", "name": "Agent ergonomics", "payhawk": 52, "weight": 13 }, { "airwallex": 84, "by": 13, "edge": "airwallex", "key": "security", "name": "Security \u0026 auth", "payhawk": 71, "weight": 14 }, { "airwallex": 25, "by": 12, "edge": "airwallex", "key": "payments", "name": "Payments \u0026 pricing", "payhawk": 13, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "airwallex": 66, "by": 13, "edge": "airwallex", "key": "maintenance", "name": "Maintenance \u0026 community", "payhawk": 53, "weight": 7 }, { "airwallex": 78, "by": 0, "edge": "", "key": "transparency", "name": "Transparency \u0026 trust", "payhawk": 78, "weight": 7 } ], "summary": "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.", "verdicts": { "airwallex": "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": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/airwallex-vs-payhawk", "json": "https://www.anchorterminal.com/compare/airwallex-vs-payhawk.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/airwallex-vs-payhawk.md", "slim": "https://www.anchorterminal.com/compare/airwallex-vs-payhawk.min.md" }, "markdown": "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.\n\n- 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\n- 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\n\n## Which one, for what\n\n### Airwallex Spend and Issuing (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 77 against 58\n- Agent ergonomics, 69 against 52\n- Security \u0026 auth, 84 against 71\n- Payments \u0026 pricing, 25 against 13\n- Maintenance \u0026 community, 66 against 53\n\nWatch 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\n\n### Payhawk API + MCP (C)\n\nGood 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.\n\nWatch for: No self-serve route. The API needs a Payhawk customer account, and a development sandbox is requested through a form\n\n\n## Score by category\n\n| Category | Weight | Airwallex Spend and Issuing | Payhawk API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 77 | 58 | Airwallex Spend and Issuing +19 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 71 | Payhawk API + MCP +2 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 52 | Airwallex Spend and Issuing +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 84 | 71 | Airwallex Spend and Issuing +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 13 | Airwallex Spend and Issuing +12 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 66 | 53 | Airwallex Spend and Issuing +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 78 | 78 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **68.3 · B** | **57.1 · C** | |\n\n## Facts side by side\n\n| Fact | Airwallex Spend and Issuing | Payhawk API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Airwallex | Payhawk Limited |\n| Hosted endpoint | `https://api.airwallex.com` | `https://api.payhawk.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| 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 |\n| Tools exposed | none | 82 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-09-30 | 2026-10-08 |\n| Terms last updated | 2025-06-20 | 2025-12-09 |\n| Privacy policy last updated | no date given | 2026-06-29 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 7 stars, 44k npm/wk | none |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Airwallex Spend and Issuing\n\n1. 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\n2. 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\n3. Send a fresh UUID as `request_id` on every create call and reuse the same value when retrying after a timeout\n4. 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`\n5. 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`\n\n### Payhawk API + MCP\n\n1. 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\n2. 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\n3. Pass `$filter` as URL-encoded JSON, for example `{\"status\":{\"$equal\":\"draft\"}}`. Date filters compare the date part only\n4. 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\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Airwallex Spend and Issuing or Payhawk API + MCP?\n\nAirwallex 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.\n\n### Do Airwallex Spend and Issuing and Payhawk API + MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Airwallex Spend and Issuing and Payhawk API + MCP without installing anything?\n\nYes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Payhawk API + MCP at https://api.payhawk.com.\n\n\n## For agents\n\n- 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\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"airwallex\", \"b\": \"payhawk\"}`. From a terminal: `anchor compare airwallex payhawk`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/airwallex.json and https://www.anchorterminal.com/api/v1/tools/payhawk.json\n\n## Other comparisons with Airwallex Spend and Issuing or Payhawk API + MCP\n\n- [Airwallex Spend and Issuing vs BILL](https://www.anchorterminal.com/compare/airwallex-vs-bill.md)\n- [Airwallex Spend and Issuing vs Brex](https://www.anchorterminal.com/compare/airwallex-vs-brex.md)\n- [Airwallex Spend and Issuing vs Expensify](https://www.anchorterminal.com/compare/airwallex-vs-expensify.md)\n- [Airwallex Spend and Issuing vs Mercury API](https://www.anchorterminal.com/compare/airwallex-vs-mercury.md)\n- [Airwallex Spend and Issuing vs Pleo API + MCP](https://www.anchorterminal.com/compare/airwallex-vs-pleo.md)\n- [Airwallex Spend and Issuing vs Ramp](https://www.anchorterminal.com/compare/airwallex-vs-ramp.md)\n- [Airwallex Spend and Issuing vs Spendesk API + MCP](https://www.anchorterminal.com/compare/airwallex-vs-spendesk.md)\n- [BILL vs Payhawk API + MCP](https://www.anchorterminal.com/compare/bill-vs-payhawk.md)\n- [Brex vs Payhawk API + MCP](https://www.anchorterminal.com/compare/brex-vs-payhawk.md)\n- [Expensify vs Payhawk API + MCP](https://www.anchorterminal.com/compare/expensify-vs-payhawk.md)\n- [Mercury API vs Payhawk API + MCP](https://www.anchorterminal.com/compare/mercury-vs-payhawk.md)\n- [Payhawk API + MCP vs Pleo API + MCP](https://www.anchorterminal.com/compare/payhawk-vs-pleo.md)\n- [Payhawk API + MCP vs Ramp](https://www.anchorterminal.com/compare/payhawk-vs-ramp.md)\n- [Payhawk API + MCP vs Spendesk API + MCP](https://www.anchorterminal.com/compare/payhawk-vs-spendesk.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Airwallex Spend and Issuing vs Payhawk API + MCP", "url": "" } ], "description": "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.", "facts": [ "Airwallex Spend and Issuing B 68.3", "Payhawk API + MCP C 57.1", "scores" ], "h1": "Airwallex Spend and Issuing vs Payhawk API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-airwallex-vs-payhawk.png", "path": "/compare/airwallex-vs-payhawk", "published": "2026-10-01", "section": "tools", "title": "Airwallex Spend and Issuing vs Payhawk API + MCP for AI agents", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/airwallex-vs-payhawk" }, "tokens": { "markdown": 2350, "slim": 730 }, "version": 1 }