{ "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 Mercury API's 63.8 (B), and leads in 5 of 7 scored categories. Mercury API leads on payments \u0026 pricing.", "b": { "slug": "mercury", "name": "Mercury API", "vendor": "Mercury Technologies, Inc.", "vendorUrl": "https://mercury.com", "kind": "http-api", "category": "spend-management", "summary": "Mercury is a US business banking service with accounts, debit and credit cards, payments and invoicing. Its REST API reads transactions, issues virtual cards with spend limits and sends payments, and a hosted MCP server is in beta.", "url": "https://www.anchorterminal.com/tools/mercury", "markdownUrl": "https://www.anchorterminal.com/tools/mercury.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mercury.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mercury.json", "repo": "https://github.com/MercuryTechnologies/mercury-cli", "license": "Proprietary service under Mercury's Terms of Use. The Mercury CLI on GitHub is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://api.mercury.com/api/v1", "packages": [ { "registry": "go", "name": "github.com/MercuryTechnologies/mercury-cli" }, { "registry": "go", "name": "github.com/MercuryTechnologies/mercury-go" } ], "auth": "mixed", "authNotes": "Access is self-serve for a Mercury customer. A user with permission creates an API token under Settings, Tokens, choosing read-only, read and write, or custom scopes. The token is sent as a Bearer header or as the basic-auth username, is shown once, can be revoked and is deleted after 45 days unused. Tokens with write scopes need an IP allowlist, except the `RequestSendMoney` scope, which queues payments for dashboard approval. The MCP server takes OAuth 2.0 with dynamic client registration and PKCE, where a person signs in and grants `read` and any of five write scopes. OAuth2 clients for integrations that serve other Mercury customers need Mercury's approval through a form.", "pricing": "freemium", "pricingNotes": "No separate API fee was found. A Mercury business account is $0 a month, Plus is $35 and Pro $350 on monthly billing ($29.90 and $299 billed annually). The pricing FAQ says mass payments on the API may incur fees and gives no amount, and mercury.com/api says 100 free ACH transfers a month come with every account. A free sandbox with self-serve signup lets an agent's owner start without a business account or a card. Production access needs an approved Mercury business account (checked 2026-10-08).", "priceSummary": "$35 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the embedded OpenAPI definitions, the API product page or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 35, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.mercury.com", "llmsTxt": "https://docs.mercury.com/llms.txt", "capabilities": [ "spend.transactions", "spend.cards", "spend.expenses" ], "tags": [ "hosted", "freemium", "api-key", "oauth", "mcp", "openapi", "llms-txt", "webhooks", "sandbox", "cli", "status-page", "soc2" ], "lastRelease": "2026-08-12", "graded": true, "anchor": { "graded": true, "score": 63.8, "grade": "B", "agentReady": false, "rank": 293, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 64, "payments": 30, "reliability": 59, "schema": 72, "security": 82, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Custom tokens take per-endpoint scopes, write tokens need an IP allowlist, and payments can be queued for approval in the dashboard through `POST /account/{accountId}/request-send-money`. No rate limits, error catalogue or SLA were found in the reviewed documentation, the changelog carries no dates, and the MCP server is beta.", "bestFor": "A company that banks with Mercury and wants an agent to read balances and transactions, set notes and categories, upload receipts, issue virtual cards with spend limits and queue payments for human approval.", "strengths": [ "Three token tiers (read-only, read and write, custom scopes), with an IP allowlist required for write scopes and unused permissions removed after 45 days", "`POST /account/{accountId}/request-send-money` always queues a payment for approval in the dashboard, and MCP payment tools can only create such requests", "`idempotencyKey` is required on send-money calls, and a repeat returns 409 with the original transaction", "A free sandbox at `https://api-sandbox.mercury.com/api/v1/` with self-serve signup and preloaded test data", "The MCP server uses OAuth 2.0 with dynamic client registration, PKCE S256 and a separate scope for each of its five write tools" ], "weaknesses": [ "No rate limits with numbers and no 429 handling were found in the reviewed documentation", "Reference pages document only 400 and 404 errors with one-line descriptions, and no error body schema or code list was found", "The changelog lists ten entries with no dates, and no deprecation policy was found", "The MCP server is labelled beta and can't create recipients, issue or manage cards, or create invoices", "No SLA. The Terms of Use supply the services as is and cap liability at $1,000" ], "agentNotes": [ "Ask for a Custom token with only the scopes the task needs. Scopes can't be edited later, and a token unused for 45 days is deleted.", "Without a fixed IP address, send payments through `POST /account/{accountId}/request-send-money`. Direct sends through `POST /account/{accountId}/transactions` need an allowlisted IP.", "Send a stored `idempotencyKey` with every payment. The same recipient, account, amount and method within 24 hours returns 400 even with a new key.", "Set `limit` on list calls. `GET /transactions` returns up to 1,000 rows by default.", "Test against `https://api-sandbox.mercury.com/api/v1/` with a sandbox token. Webhooks aren't available in the sandbox." ], "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": 63.8 } ], "editorialScores": { "ergonomics": 68, "maintenance": 64, "payments": 30, "reliability": 59, "schema": 72, "security": 82, "transparency": 42 }, "provenanceScore": 84 }, "connect": { "install": "curl -sSf https://cli.mercury.com/install.sh | sh", "http": "curl https://api.mercury.com/api/v1/accounts --header 'accept: application/json' --header \"Authorization: Bearer TOKEN\"", "claudeCode": "claude mcp add --transport http -s user mercury https://mcp.mercury.com/mcp" }, "letme": { "capability": "https://letme.dev/spend.transactions", "tool": "https://letme.dev/mercury" }, "area": "domain-data", "unitPrices": [ { "item": "Mercury business account", "unit": "month", "usd": 0, "note": "API tokens are created in account settings. ACH, domestic wires and real-time payments are free per the pricing FAQ" }, { "item": "Mercury Plus", "unit": "month", "usd": 35, "note": "$29.90 a month billed annually" }, { "item": "Mercury Pro", "unit": "month", "usd": 350, "note": "$299 a month billed annually" } ], "provenance": { "legalEntity": "Mercury Technologies, Inc.", "domain": "mercury.com", "domainRegistered": "1990-11-30", "endpointOnVendorDomain": true, "terms": "https://mercury.com/legal/terms", "privacy": "https://mercury.com/legal/privacy", "statusPage": "https://status.mercury.com", "changelog": "https://docs.mercury.com/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Terms of Use (last updated 5 October 2026) name Mercury Technologies, Inc. and its affiliates and cover the site, the app and the services, including AI connections made through an API or connector in section 3.2. No separate API or developer agreement was found on the legal index.", "The privacy policy (effective 27 August 2026) names Mercury Technologies, Inc. and applies to Mercury's websites, mobile apps and financial products.", "Mercury states it is a fintech company and not an FDIC-insured bank. Accounts are held under separate agreements with Choice Financial Group and Column N.A., linked from mercury.com/legal.", "The API answers at api.mercury.com, the Vault API at vault-api.mercury.com, the sandbox at api-sandbox.mercury.com and the MCP server at mcp.mercury.com, all mercury.com subdomains.", "mercury.com/.well-known/security.txt returns 404. The security page sends vulnerability reports to security@mercury.com.", "RDAP for mercury.com gives a registration date of 1990-11-30." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mercury.json", "live": { "slug": "mercury", "probe": { "target": "https://api.mercury.com/api/v1", "method": "get", "lastAt": "2026-10-08T21:12:15.175705812Z", "lastOk": true, "lastStatus": 404, "lastMs": 300, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 301, "p95ms24h": 359, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.mercury.com", "indicator": "minor", "summary": "Partial System Degradation", "checkedAt": "2026-10-08T21:06:12.336155671Z" }, "updatedAt": "2026-10-08T21:12:15.175705812Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Airwallex", "b": "Mercury Technologies, Inc.", "name": "Vendor" }, { "a": "https://api.airwallex.com", "b": "https://api.mercury.com/api/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "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 Mercury's Terms of Use. The Mercury CLI on GitHub is Apache-2.0", "name": "Licence" }, { "a": "none", "b": "35", "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-08-12", "name": "Last release" }, { "a": "2025-06-20", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "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": "yes", "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 Mercury API's 63.8 (B), and leads in 5 of 7 scored categories. Mercury API leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Airwallex Spend and Issuing or Mercury API?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Airwallex Spend and Issuing and Mercury API need an API key?" }, { "answer": "Yes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Mercury API at https://api.mercury.com/api/v1.", "question": "Can an agent call Airwallex Spend and Issuing and Mercury API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 77 against 59", "Transparency \u0026 trust, 78 against 63" ], "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": [ "Payments \u0026 pricing, 30 against 25" ], "also": null, "goodFor": "A company that banks with Mercury and wants an agent to read balances and transactions, set notes and categories, upload receipts, issue virtual cards with spend limits and queue payments for human approval.", "slug": "mercury", "watchFor": "No rate limits with numbers and no 429 handling were found in the reviewed documentation" } ], "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-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-mercury.json", "title": "BILL vs Mercury API", "url": "https://www.anchorterminal.com/compare/bill-vs-mercury" }, { "json": "https://www.anchorterminal.com/compare/brex-vs-mercury.json", "title": "Brex vs Mercury API", "url": "https://www.anchorterminal.com/compare/brex-vs-mercury" }, { "json": "https://www.anchorterminal.com/compare/expensify-vs-mercury.json", "title": "Expensify vs Mercury API", "url": "https://www.anchorterminal.com/compare/expensify-vs-mercury" }, { "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/mercury-vs-ramp.json", "title": "Mercury API vs Ramp", "url": "https://www.anchorterminal.com/compare/mercury-vs-ramp" }, { "json": "https://www.anchorterminal.com/compare/mercury-vs-spendesk.json", "title": "Mercury API vs Spendesk API + MCP", "url": "https://www.anchorterminal.com/compare/mercury-vs-spendesk" } ], "scores": [ { "airwallex": 77, "by": 18, "edge": "airwallex", "key": "reliability", "mercury": 59, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "airwallex": 69, "by": 3, "edge": "mercury", "key": "schema", "mercury": 72, "name": "Schema \u0026 documentation", "weight": 13 }, { "airwallex": 69, "by": 1, "edge": "airwallex", "key": "ergonomics", "mercury": 68, "name": "Agent ergonomics", "weight": 13 }, { "airwallex": 84, "by": 2, "edge": "airwallex", "key": "security", "mercury": 82, "name": "Security \u0026 auth", "weight": 14 }, { "airwallex": 25, "by": 5, "edge": "mercury", "key": "payments", "mercury": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "airwallex": 66, "by": 2, "edge": "airwallex", "key": "maintenance", "mercury": 64, "name": "Maintenance \u0026 community", "weight": 7 }, { "airwallex": 78, "by": 15, "edge": "airwallex", "key": "transparency", "mercury": 63, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Mercury API's 63.8 (B), and leads in 5 of 7 scored categories. Mercury API leads on payments \u0026 pricing. 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.", "mercury": "Custom tokens take per-endpoint scopes, write tokens need an IP allowlist, and payments can be queued for approval in the dashboard through `POST /account/{accountId}/request-send-money`. No rate limits, error catalogue or SLA were found in the reviewed documentation, the changelog carries no dates, and the MCP server is beta." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/airwallex-vs-mercury", "json": "https://www.anchorterminal.com/compare/airwallex-vs-mercury.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/airwallex-vs-mercury.md", "slim": "https://www.anchorterminal.com/compare/airwallex-vs-mercury.min.md" }, "markdown": "Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Mercury API's 63.8 (B), and leads in 5 of 7 scored categories. Mercury API leads on payments \u0026 pricing. 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- Mercury API: grade B, 63.8/100, rank #293 of 722. Markdown https://www.anchorterminal.com/tools/mercury.md · JSON https://www.anchorterminal.com/api/v1/tools/mercury.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 59\n- Transparency \u0026 trust, 78 against 63\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### Mercury API (B)\n\nGood for: A company that banks with Mercury and wants an agent to read balances and transactions, set notes and categories, upload receipts, issue virtual cards with spend limits and queue payments for human approval.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 25\n\nWatch for: No rate limits with numbers and no 429 handling were found in the reviewed documentation\n\n\n## Score by category\n\n| Category | Weight | Airwallex Spend and Issuing | Mercury API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 77 | 59 | Airwallex Spend and Issuing +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 72 | Mercury API +3 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 68 | Airwallex Spend and Issuing +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 84 | 82 | Airwallex Spend and Issuing +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 30 | Mercury API +5 |\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 | 63 | Airwallex Spend and Issuing +15 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **68.3 · B** | **63.8 · B** | |\n\n## Facts side by side\n\n| Fact | Airwallex Spend and Issuing | Mercury API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Airwallex | Mercury Technologies, Inc. |\n| Hosted endpoint | `https://api.airwallex.com` | `https://api.mercury.com/api/v1` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\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 Mercury's Terms of Use. The Mercury CLI on GitHub is Apache-2.0 |\n| Tools exposed | none | 35 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-09-30 | 2026-08-12 |\n| Terms last updated | 2025-06-20 | no date given |\n| Privacy policy last updated | no date given | no date given |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\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 | yes |\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**Mercury API.** Custom tokens take per-endpoint scopes, write tokens need an IP allowlist, and payments can be queued for approval in the dashboard through `POST /account/{accountId}/request-send-money`. No rate limits, error catalogue or SLA were found in the reviewed documentation, the changelog carries no dates, and the MCP server is beta.\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### Mercury API\n\n1. Ask for a Custom token with only the scopes the task needs. Scopes can't be edited later, and a token unused for 45 days is deleted.\n2. Without a fixed IP address, send payments through `POST /account/{accountId}/request-send-money`. Direct sends through `POST /account/{accountId}/transactions` need an allowlisted IP.\n3. Send a stored `idempotencyKey` with every payment. The same recipient, account, amount and method within 24 hours returns 400 even with a new key.\n4. Set `limit` on list calls. `GET /transactions` returns up to 1,000 rows by default.\n5. Test against `https://api-sandbox.mercury.com/api/v1/` with a sandbox token. Webhooks aren't available in the sandbox.\n\n## Questions\n\n### Which is better for AI agents, Airwallex Spend and Issuing or Mercury API?\n\nAirwallex Spend and Issuing scores 68.3 (B) on agent readiness against Mercury API's 63.8 (B), and leads in 5 of 7 scored categories. Mercury API leads on payments \u0026 pricing.\n\n### Do Airwallex Spend and Issuing and Mercury API 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 Mercury API without installing anything?\n\nYes. Airwallex Spend and Issuing has a hosted endpoint at https://api.airwallex.com and Mercury API at https://api.mercury.com/api/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/airwallex-vs-mercury.json, and with the fewest tokens: https://www.anchorterminal.com/compare/airwallex-vs-mercury.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"airwallex\", \"b\": \"mercury\"}`. From a terminal: `anchor compare airwallex mercury`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/airwallex.json and https://www.anchorterminal.com/api/v1/tools/mercury.json\n\n## Other comparisons with Airwallex Spend and Issuing or Mercury API\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 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 Mercury API](https://www.anchorterminal.com/compare/bill-vs-mercury.md)\n- [Brex vs Mercury API](https://www.anchorterminal.com/compare/brex-vs-mercury.md)\n- [Expensify vs Mercury API](https://www.anchorterminal.com/compare/expensify-vs-mercury.md)\n- [Mercury API vs Pleo API + MCP](https://www.anchorterminal.com/compare/mercury-vs-pleo.md)\n- [Mercury API vs Ramp](https://www.anchorterminal.com/compare/mercury-vs-ramp.md)\n- [Mercury API vs Spendesk API + MCP](https://www.anchorterminal.com/compare/mercury-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 Mercury API", "url": "" } ], "description": "Airwallex Spend and Issuing scores 68.3 (B) on agent readiness against Mercury API's 63.8 (B), and leads in 5 of 7 scored categories. Mercury API leads on payments \u0026 pricing. Both do spend transactions. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Airwallex Spend and Issuing B 68.3", "Mercury API B 63.8", "scores" ], "h1": "Airwallex Spend and Issuing vs Mercury API", "image": "https://www.anchorterminal.com/assets/og/compare-airwallex-vs-mercury.png", "path": "/compare/airwallex-vs-mercury", "published": "2026-10-01", "section": "tools", "title": "Airwallex Spend and Issuing vs Mercury API for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/airwallex-vs-mercury" }, "tokens": { "markdown": 2250, "slim": 680 }, "version": 1 }