{ "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": 187, "ranked": true, "rankOf": 722, "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-08T21:12:03.204142811Z", "lastOk": true, "lastStatus": 404, "lastMs": 37, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 44, "p95ms24h": 75, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.airwallex.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:05:50.696967861Z" }, "updatedAt": "2026-10-08T21:12:03.204142811Z" } }, "answer": "Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Pleo API + MCP's 62.9 (B), and leads in 6 of 7 scored categories. Pleo API + MCP leads on schema \u0026 documentation.", "b": { "slug": "pleo", "name": "Pleo API + MCP", "vendor": "Pleo Technologies A/S", "vendorUrl": "https://www.pleo.io/en", "kind": "http-api", "category": "spend-management", "summary": "Spend management platform from Pleo Technologies A/S in Copenhagen, covering company cards, expenses, reimbursements, invoices and accounting exports. Outside agents reach it through a hosted MCP server for expense work and a REST API built for accounting integrations.", "url": "https://www.anchorterminal.com/tools/pleo", "markdownUrl": "https://www.anchorterminal.com/tools/pleo.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pleo.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pleo.json", "license": "Proprietary service under Pleo's Master Service Agreement, API Terms of Service and AI Access Terms", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://external.pleo.io", "packages": [], "auth": "mixed", "authNotes": "A person signs in for every route. The MCP server uses OAuth 2.0 in a browser (authorisation code with PKCE, dynamic client registration, no keys to configure) and acts with the connecting user's Pleo role, once a company admin has enabled MCP access for that entity. The External API accepts OAuth 2.0 bearer tokens with resource scopes for partner integrations, whose client ID and secret Pleo issues after review in its Early Access Programme. A single company can use a Standalone API Key with chosen scopes and an expiry, sent as the Basic auth username, but only after Pleo support or a Customer Success Manager enables keys for the organisation.", "pricing": "paid", "pricingNotes": "Per-user plans, with no separate charge for the API or the MCP server. The pricing page shown to a UK visitor lists Start at £8 per user per month, Build at £14 and Optimise at £18, the last two cheaper billed yearly and with a three-user minimum. MCP is listed on Optimise only, which is sold through a demo. Start and Build have a Try for free button and the signup form states 21 days free. Whether the trial needs a payment card isn't stated. A staging environment with test data exists for customers with API keys enabled and for approved partners. Fees for payments and foreign exchange are extra (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI specs or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developers.pleo.io/", "llmsTxt": "https://developers.pleo.io/llms.txt", "openapi": "https://developers.pleo.io/reference/Export%20API.json", "capabilities": [ "spend.transactions", "spend.expenses", "spend.bills" ], "tags": [ "official", "hosted", "mcp", "oauth", "api-key", "openapi", "llms-txt", "webhooks", "closed-source", "status-page", "bug-bounty", "sandbox" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 62.9, "grade": "B", "agentReady": false, "rank": 325, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 55, "maintenance": 64, "payments": 15, "reliability": 71, "schema": 82, "security": 71, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The hosted MCP server acts with the connecting user's own Pleo permissions, is off until an admin enables it per entity, and can't move money, change cards or alter limits. It is listed only on the Optimise plan, its tool definitions aren't published, API keys need enabling by Pleo support, and no official SDK or SLA was found.", "bestFor": "An agent that completes, codes, reviews and queues expenses for a Pleo customer on the Optimise plan, or for a bookkeeping integration that exports accounting entries and syncs tags, tax codes, accounts and vendors.", "strengths": [ "MCP server at mcp.pleo.io/mcp uses OAuth with PKCE and dynamic client registration, and acts with the connecting user's Pleo permissions", "Payments, card changes and spending-limit changes are blocked through the MCP by design, per the AI Access Terms", "Eleven current OpenAPI 3.0.1 specs with 162 operations, plus llms.txt, llms-full.txt and a Markdown copy of every docs page", "One documented rate limit of 600 requests a minute per credential, with written 429 and Retry-After guidance", "Staging hosts for both the API (external.staging.pleo.io) and the MCP server (mcp.staging.pleo.io/mcp)", "Sub-processor list with locations, customer data in AWS Ireland, and 30 days' notice of new sub-processors in the DPA" ], "weaknesses": [ "The pricing page lists MCP on the Optimise plan only (£18 per user per month, three users minimum, sold through a demo)", "MCP tool names, schemas and count aren't published, so they can't be read without a customer sign-in", "Standalone API keys aren't self-service. Pleo support or a Customer Success Manager enables them, and partner OAuth clients go through a reviewed programme", "No Idempotency-Key header, no official SDK and no entry in the official MCP registry", "The API terms call the API a beta version that Pleo may discontinue at any time, and no SLA was found", "No end-of-life date is published for the deprecated Legacy API, and its Q3 2026 replacements for employee writes and wallet balance aren't in the docs" ], "agentNotes": [ "Ask a company admin to enable Pleo MCP access under Settings, General, Pleo AI for each entity before connecting. It is off by default", "Name the entity in every request when working outside the default one. Each MCP request targets one entity and the choice doesn't persist", "Set the AI client to require approval for Pleo write tools. Pleo leaves confirmation to the client and doesn't enforce it server-side", "Send API keys as the Basic auth username with an empty password to external.pleo.io. Legacy tokens for openapi.pleo.io don't work there", "Budget every endpoint against one bucket of 600 requests a minute per credential, and on 429 wait for Retry-After or back off from one second", "Swap mcp.staging.pleo.io for mcp.pleo.io in the Claude Code command when moving from staging to production. Each needs its own OAuth sign-in" ], "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": 62.9 } ], "editorialScores": { "ergonomics": 55, "maintenance": 64, "payments": 15, "reliability": 71, "schema": 82, "security": 71, "transparency": 63 }, "provenanceScore": 87 }, "connect": { "http": "curl --request GET \\\n-u \"YOUR-API-KEY:\" \\\n-H \"Accept: application/json;charset=UTF-8\" \\\n\"https://external.staging.pleo.io/v2/employees\"", "claudeCode": "claude mcp add --transport http pleo-mcp-staging https://mcp.staging.pleo.io/mcp", "config": { "mcpServers": { "pleo": { "url": "https://mcp.pleo.io/mcp" } } } }, "letme": { "capability": "https://letme.dev/spend.transactions", "tool": "https://letme.dev/pleo" }, "area": "domain-data", "provenance": { "legalEntity": "Pleo Technologies A/S", "domain": "pleo.io", "domainRegistered": "2015-10-07", "endpointOnVendorDomain": true, "terms": "https://developers.pleo.io/page/terms-of-service", "privacy": "https://www.pleo.io/legal-documents/pleo-privacy-policy-en.pdf", "statusPage": "https://status.pleo.io", "changelog": "https://developers.pleo.io/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The website footer names Pleo Technologies A/S (36538686), Ravnsborg Tværgade 5C, 2200 København N, Denmark. UK payment services come from Pleo Financial Services UK Ltd, FCA firm reference 1020730, company number 15842283.", "The API Terms of Service on the developer portal name Pleo Technologies A/S, carry no date, and describe the API as a beta version. The UK Master Service Agreement has an effective date of 7 September 2026 and is governed by the laws of England and Wales.", "The API answers at external.pleo.io and the MCP server at mcp.pleo.io, both pleo.io subdomains. The MCP host publishes its OAuth metadata at https://mcp.pleo.io/.well-known/oauth-authorization-server", "www.pleo.io/.well-known/security.txt and pleo.io/.well-known/security.txt both return 403 with an AccessDenied body. The vulnerability disclosure policy gives security-vd@pleo.io as the reporting address.", "The privacy notice is dated June 2026 and the Data Processing Agreement 14 October 2025. An AI Access Terms document covers the MCP server.", "RDAP from the .io registry gives a registration date of 2015-10-07 for pleo.io." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/pleo.json", "live": { "slug": "pleo", "probe": { "target": "https://external.pleo.io", "method": "get", "lastAt": "2026-10-08T21:12:18.801661057Z", "lastOk": true, "lastStatus": 403, "lastMs": 75, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 88, "p95ms24h": 163, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-10-08", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://status.pleo.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:22.5618046Z" }, "securityTxt": { "url": "https://pleo.io/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-10-08T15:38:57.657849973Z" }, "pages": [ { "url": "https://developers.pleo.io/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:58.324737763Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7369dd13eb7c" }, { "url": "https://developers.pleo.io/page/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:18:00.641635735Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5da670693385" } ], "updatedAt": "2026-10-08T21:12:18.801661057Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Airwallex", "b": "Pleo Technologies A/S", "name": "Vendor" }, { "a": "https://api.airwallex.com", "b": "https://external.pleo.io", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable 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 Pleo's Master Service Agreement, API Terms of Service and AI Access Terms", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-10-02", "name": "Last release" }, { "a": "2025-06-20", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "b": "", "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 Pleo API + MCP's 62.9 (B), and leads in 6 of 7 scored categories. Pleo API + MCP leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Airwallex Spend and Issuing or Pleo API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Airwallex Spend and Issuing and Pleo API + MCP need an API key?" }, { "answer": "Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Pleo API + MCP at https://external.pleo.io.", "question": "Can an agent call Airwallex Spend and Issuing and Pleo API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 77 against 71", "Agent ergonomics, 69 against 55", "Security \u0026 auth, 84 against 71", "Payments \u0026 pricing, 25 against 15" ], "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": [ "Schema \u0026 documentation, 82 against 69" ], "also": null, "goodFor": "An agent that completes, codes, reviews and queues expenses for a Pleo customer on the Optimise plan, or for a bookkeeping integration that exports accounting entries and syncs tags, tax codes, accounts and vendors.", "slug": "pleo", "watchFor": "The pricing page lists MCP on the Optimise plan only (£18 per user per month, three users minimum, sold through a demo)" } ], "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-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-pleo.json", "title": "BILL vs Pleo API + MCP", "url": "https://www.anchorterminal.com/compare/bill-vs-pleo" }, { "json": "https://www.anchorterminal.com/compare/brex-vs-pleo.json", "title": "Brex vs Pleo API + MCP", "url": "https://www.anchorterminal.com/compare/brex-vs-pleo" }, { "json": "https://www.anchorterminal.com/compare/expensify-vs-pleo.json", "title": "Expensify vs Pleo API + MCP", "url": "https://www.anchorterminal.com/compare/expensify-vs-pleo" }, { "json": "https://www.anchorterminal.com/compare/mercury-vs-pleo.json", "title": "Mercury API vs Pleo API + MCP", "url": "https://www.anchorterminal.com/compare/mercury-vs-pleo" }, { "json": "https://www.anchorterminal.com/compare/pleo-vs-ramp.json", "title": "Pleo API + MCP vs Ramp", "url": "https://www.anchorterminal.com/compare/pleo-vs-ramp" }, { "json": "https://www.anchorterminal.com/compare/pleo-vs-spendesk.json", "title": "Pleo API + MCP vs Spendesk API + MCP", "url": "https://www.anchorterminal.com/compare/pleo-vs-spendesk" } ], "scores": [ { "airwallex": 77, "by": 6, "edge": "airwallex", "key": "reliability", "name": "Reliability", "pleo": 71, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "airwallex": 69, "by": 13, "edge": "pleo", "key": "schema", "name": "Schema \u0026 documentation", "pleo": 82, "weight": 13 }, { "airwallex": 69, "by": 14, "edge": "airwallex", "key": "ergonomics", "name": "Agent ergonomics", "pleo": 55, "weight": 13 }, { "airwallex": 84, "by": 13, "edge": "airwallex", "key": "security", "name": "Security \u0026 auth", "pleo": 71, "weight": 14 }, { "airwallex": 25, "by": 10, "edge": "airwallex", "key": "payments", "name": "Payments \u0026 pricing", "pleo": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "airwallex": 66, "by": 2, "edge": "airwallex", "key": "maintenance", "name": "Maintenance \u0026 community", "pleo": 64, "weight": 7 }, { "airwallex": 78, "by": 3, "edge": "airwallex", "key": "transparency", "name": "Transparency \u0026 trust", "pleo": 75, "weight": 7 } ], "summary": "Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Pleo API + MCP's 62.9 (B), and leads in 6 of 7 scored categories. Pleo API + MCP leads on schema \u0026 documentation. 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.", "pleo": "The hosted MCP server acts with the connecting user's own Pleo permissions, is off until an admin enables it per entity, and can't move money, change cards or alter limits. It is listed only on the Optimise plan, its tool definitions aren't published, API keys need enabling by Pleo support, and no official SDK or SLA was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/airwallex-vs-pleo", "json": "https://www.anchorterminal.com/compare/airwallex-vs-pleo.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/airwallex-vs-pleo.md", "slim": "https://www.anchorterminal.com/compare/airwallex-vs-pleo.min.md" }, "markdown": "Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Pleo API + MCP's 62.9 (B), and leads in 6 of 7 scored categories. Pleo API + MCP leads on schema \u0026 documentation. Both do spend transactions.\n\n- 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\n- Pleo API + MCP: grade B, 62.9/100, rank #325 of 722. Markdown https://www.anchorterminal.com/tools/pleo.md · JSON https://www.anchorterminal.com/api/v1/tools/pleo.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 71\n- Agent ergonomics, 69 against 55\n- Security \u0026 auth, 84 against 71\n- Payments \u0026 pricing, 25 against 15\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### Pleo API + MCP (B)\n\nGood for: An agent that completes, codes, reviews and queues expenses for a Pleo customer on the Optimise plan, or for a bookkeeping integration that exports accounting entries and syncs tags, tax codes, accounts and vendors.\n\nAhead on:\n- Schema \u0026 documentation, 82 against 69\n\nWatch for: The pricing page lists MCP on the Optimise plan only (£18 per user per month, three users minimum, sold through a demo)\n\n\n## Score by category\n\n| Category | Weight | Airwallex Spend and Issuing | Pleo API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 77 | 71 | Airwallex Spend and Issuing +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 82 | Pleo API + MCP +13 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 55 | Airwallex Spend and Issuing +14 |\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 | 15 | Airwallex Spend and Issuing +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 66 | 64 | Airwallex Spend and Issuing +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 78 | 75 | Airwallex Spend and Issuing +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **68.3 · B** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Airwallex Spend and Issuing | Pleo API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Airwallex | Pleo Technologies A/S |\n| Hosted endpoint | `https://api.airwallex.com` | `https://external.pleo.io` |\n| Transports | HTTP | HTTP, Streamable 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 Pleo's Master Service Agreement, API Terms of Service and AI Access Terms |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-30 | 2026-10-02 |\n| Terms last updated | 2025-06-20 | no date given |\n| Privacy policy last updated | no date given | |\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**Pleo API + MCP.** The hosted MCP server acts with the connecting user's own Pleo permissions, is off until an admin enables it per entity, and can't move money, change cards or alter limits. It is listed only on the Optimise plan, its tool definitions aren't published, API keys need enabling by Pleo support, and no official SDK or SLA was found.\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### Pleo API + MCP\n\n1. Ask a company admin to enable Pleo MCP access under Settings, General, Pleo AI for each entity before connecting. It is off by default\n2. Name the entity in every request when working outside the default one. Each MCP request targets one entity and the choice doesn't persist\n3. Set the AI client to require approval for Pleo write tools. Pleo leaves confirmation to the client and doesn't enforce it server-side\n4. Send API keys as the Basic auth username with an empty password to external.pleo.io. Legacy tokens for openapi.pleo.io don't work there\n5. Budget every endpoint against one bucket of 600 requests a minute per credential, and on 429 wait for Retry-After or back off from one second\n6. Swap mcp.staging.pleo.io for mcp.pleo.io in the Claude Code command when moving from staging to production. Each needs its own OAuth sign-in\n\n## Questions\n\n### Which is better for AI agents, Airwallex Spend and Issuing or Pleo API + MCP?\n\nAirwallex Spend and Issuing scores 68.3 (B) on agent readiness against Pleo API + MCP's 62.9 (B), and leads in 6 of 7 scored categories. Pleo API + MCP leads on schema \u0026 documentation.\n\n### Do Airwallex Spend and Issuing and Pleo 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 Pleo API + MCP without installing anything?\n\nYes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Pleo API + MCP at https://external.pleo.io.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/airwallex-vs-pleo.json, and with the fewest tokens: https://www.anchorterminal.com/compare/airwallex-vs-pleo.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"airwallex\", \"b\": \"pleo\"}`. From a terminal: `anchor compare airwallex pleo`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/airwallex.json and https://www.anchorterminal.com/api/v1/tools/pleo.json\n\n## Other comparisons with Airwallex Spend and Issuing or Pleo 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 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 Pleo API + MCP](https://www.anchorterminal.com/compare/bill-vs-pleo.md)\n- [Brex vs Pleo API + MCP](https://www.anchorterminal.com/compare/brex-vs-pleo.md)\n- [Expensify vs Pleo API + MCP](https://www.anchorterminal.com/compare/expensify-vs-pleo.md)\n- [Mercury API vs Pleo API + MCP](https://www.anchorterminal.com/compare/mercury-vs-pleo.md)\n- [Pleo API + MCP vs Ramp](https://www.anchorterminal.com/compare/pleo-vs-ramp.md)\n- [Pleo API + MCP vs Spendesk API + MCP](https://www.anchorterminal.com/compare/pleo-vs-spendesk.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "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 Pleo API + MCP", "url": "" } ], "description": "Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Pleo API + MCP's 62.9 (B), and leads in 6 of 7 scored categories. Pleo API + MCP leads on schema \u0026 documentation. Both do spend transactions. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Airwallex Spend and Issuing B 68.3", "Pleo API + MCP B 62.9", "scores" ], "h1": "Airwallex Spend and Issuing vs Pleo API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-airwallex-vs-pleo.png", "path": "/compare/airwallex-vs-pleo", "published": "2026-10-01", "section": "tools", "title": "Airwallex Spend and Issuing vs Pleo API + MCP for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/airwallex-vs-pleo" }, "tokens": { "markdown": 2350, "slim": 730 }, "version": 1 }