Mercury vs Wise Business
Mercury wins · 40–8 (6 drawn)
Accounting integrations — stories about accounting integrations in this arenaAccounting integrations
Stories about accounting integrations in this arena
Close automation
ai-native userUse AI automations to close my books faster each month
weight 2 · round to MercuryMercury explicitly advertises syncing with QuickBooks, Xero, and NetSuite plus AI-powered automations to 'close your books faster' (mercury-docs-6), backed by supporting AI automation features like auto-reading bills, auto-attaching receipts, and API write actions for categorizing transactions/invoices (mercury-docs-3, mercury-docs-5, mercury-docs-29). Missing for 10: independent/hands-on verification that the accounting sync and AI automations actually reduce close time, and no detail on depth of QBO/Xero/NetSuite reconciliation accuracy.
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
- [claimed-docs] “Write actions such as making payments, categorizing transactions, creating invoices, and uploading receipts”
- [claimed-docs] “Generate and send invoices based on CRM, billing, or usage data”
Developer accounting access
developerView and manage accounting data through a dedicated API
weight 1 · round to MercuryMercury publishes a dedicated REST API with extensive accounting-related resources — transactions, categories, statements, invoices, customers/AR, webhooks, treasury — supporting both viewing (list/get) and managing (create/update/delete/cancel) data, backed by OAuth2, scoped tokens, a sandbox environment, versioned docs, an official CLI (verified working via probe), and a Go SDK. Probes independently confirm the CLI installs and lists real resource commands and the sandbox/interactive docs are functional, giving strong first-party plus hands-on corroboration. Missing for 10: independent third-party developer reviews of the core REST API itself (vs. MCP) and a publicly downloadable OpenAPI spec (confirmed internal-only via probe).
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
- [claimed-docs] “OAuth2 API: Start OAuth2 web flow; Obtain an access token — Mercury supports OAuth2 authorization for third-party/programmatic access alongs…”
- [claimed-docs] “Our Sandbox environment is designed to make it easy for you to test API calls in a safe, simulated version of Mercury — no real money involv…”
- [claimed-docs] “There are three types of tokens: read-only, read-write, and custom.”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [claimed-docs] “Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API request…”
- [claimed-docs] “Every endpoint page on the API Reference hub (docs.mercury.com/reference, ReadMe) embeds a live request runner and generated code samples: "…”
- [claimed-docs] “API base paths are versioned under /api/v1/ ("get https://api.mercury.com/api/v1/account/{accountId}/cards") and the docs hub nav publishes …”
- [claimed-docs] “Official Go SDK, MercuryTechnologies/mercury-go: "The Mercury Go library provides convenient access to the Mercury REST API from application…”
- [probe] “PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://doc…”
Wise exposes a documented 'Global Payments API' for sending/receiving money and business payments (wise-docs-6, wise-probe-1), which could be used to pull transaction/account data for accounting purposes, but there is no explicit documentation of endpoints for statements, balance history, or accounting-specific data management, and no OpenAPI spec is discoverable (wise-probe-2 shows 404s). Missing for 10: explicit accounting-data endpoints (statements, categorization, reconciliation), formal API reference/OpenAPI spec, and independent developer corroboration of using the API for accounting integration.
- [claimed-docs] “How to make business payments via API from a Wise account.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
Erp sync
finance-leadSync transactions and expenses automatically with my accounting software
weight 3 · round to MercuryMercury explicitly advertises syncing with QuickBooks, Xero, and NetSuite plus AI-powered receipt/category automation (mercury-docs-6, mercury-docs-5, mercury-docs-28), and its API exposes transaction/category/statement endpoints that could underlie such syncs (mercury-docs-12). However, this is purely first-party marketing copy with no docs detailing sync mechanics, frequency, or field-mapping, and no independent/hands-on confirmation that the QuickBooks/Xero/NetSuite sync works reliably in practice. Missing for 10: technical documentation of the sync mechanism, independent or community verification of accounting-software sync reliability, and detail on which transaction/expense fields are mapped.
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction.”
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
finance-leadRely on real-time bidirectional sync with my ERP instead of manual journal entries
weight 3 · round to MercuryMercury advertises syncing with QuickBooks, Xero, and NetSuite to help close books faster (mercury-docs-6), which addresses the ERP-integration theme, but there is no detail confirming true real-time bidirectional sync (versus periodic export/import) or automated journal-entry creation, and no independent/hands-on evidence validating the sync's reliability or completeness. Missing for 10: documentation of bidirectional data flow direction, real-time sync frequency/latency, automated journal entry mapping, and independent confirmation the integration works as described.
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
Accounts payments — opening accounts and moving money — setup, transfers, payment railsAccounts payments
Opening accounts and moving money — setup, transfers, payment rails
Account structure
finance-leadView account and routing numbers and generate a bank verification letter anytime
weight 1 · round to Wise BusinessMercurynone0/10The evidence pack covers cards, payments, invoicing, API/MCP tooling, and statement PDF downloads, but nowhere mentions displaying account/routing numbers or generating a bank verification letter — a standard banking feature that a business bank like Mercury could plausibly offer, but no evidence confirms it exists.
Wise documents providing 'global account details' for receiving payments (wise-docs-9), which supports viewing account/routing numbers, but there is no evidence of a dedicated bank verification letter generation feature. Additionally, community reports show account/routing numbers can change without warning (wise-comm-2, wise-comm-3, wise-comm-5), undercutting the 'anytime' reliability implied by the story. Missing for 10: documented bank verification letter/document generation tool, and confirmation that account numbers remain stable enough to be trusted 'anytime'.
- [claimed-docs] “Get paid easily in other currencies with global account details.”
- [community] “I received notification that my US bank account number will stop working immediately and I should not use it anywhere and remove it from any…”
- [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
- [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”
finance-leadOpen multiple checking sub-accounts and auto-allocate incoming deposits across them
weight 2 · round to MercuryA long-term hands-on user reports creating 'dozens of purpose-named accounts with auto-funding rules,' directly confirming both multiple checking sub-accounts and automated allocation of funds across them. No first-party Mercury docs in the pack explicitly describe the sub-account/auto-allocation feature or its configuration options, so evidence rests on a single community account rather than documented capability. Missing for 10: first-party docs on creating sub-accounts and configuring auto-allocation rules, and additional independent corroboration.
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
Wise Businessnone0/10The evidence pack shows Wise Business supports multi-currency accounts, global payments, and cards, but nothing about creating multiple checking sub-accounts or auto-allocating incoming deposits across them—no rules-based deposit splitting or sub-account structuring is mentioned anywhere.
Bill pay
finance-leadUpload bills and route them through an approval workflow before paying vendors
weight 3 · round to MercuryMercury's bill-pay feature explicitly supports uploading/reading bills via AI and an approve-then-pay flow (mercury-docs-3), plus granular permissions letting specific roles (e.g., an accountant) execute payments (mercury-docs-11) and spend/approval controls (mercury-docs-10, mercury-docs-38). The MCP tool inventory also lists dedicated approval-workflow endpoints like listSendMoneyApprovalRequests and getSafeRequest(s) (mercury-probe-5), corroborating a real multi-step approval mechanism for vendor payments. Missing for 10: no first-party documentation detailing the full workflow UI/steps (multi-approver routing rules, thresholds), and no independent/hands-on user report specifically validating the bill-approval process end-to-end.
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Built-in permissions means our accountant can easily make payments — literally one click and it’s done.”
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “Earn 1.5% cashback on credit card spend, and control team expenses with cards, reimbursements, limits, and approvals all in one place.”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
finance-leadSet up approval permissions so designated teammates can approve and send payments with one click
weight 2 · round to MercuryMercury docs explicitly describe granular user permissions and built-in approval permissions that let designated teammates (e.g. an accountant) approve and send payments in one click, and product marketing highlights team spend controls with approvals. Community evidence corroborates real-world use of card/account permission controls, though not specifically the one-click approval flow. Missing for 10: independent/hands-on confirmation of the one-click approval UX itself and detail on how granular approval roles are configured (e.g., approval thresholds, multi-approver workflows).
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “Built-in permissions means our accountant can easily make payments — literally one click and it’s done.”
- [claimed-docs] “Earn 1.5% cashback on credit card spend, and control team expenses with cards, reimbursements, limits, and approvals all in one place.”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
Invoicing
finance-leadCreate and send branded invoices with built-in payment collection
weight 2 · round to MercuryMercury explicitly supports sending manual/automatic invoices with flexible payment methods and customer management (mercury-docs-4), a dedicated Invoices API (create/list/get/update/cancel, download PDF) (mercury-docs-13), and invoice volume tied to paid plans (mercury-docs-21). However, evidence does not confirm invoice 'branding' customization (logos/colors) or hands-on/community confirmation of the invoicing UX itself. missing for 10: independent/hands-on evidence of invoice branding customization options, and third-party confirmation of the payment-collection experience from a customer's perspective.
- [claimed-docs] “Send manual and automatic invoices, accept flexible payment methods, and manage customer details right from your Mercury account.”
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
- [claimed-docs] “Create up to 500 invoices/month on Mercury Plus, or unlimited invoices with Pro”
- [claimed-docs] “Generate and send invoices based on CRM, billing, or usage data”
Money movement
founderSend money abroad that arrives in under a minute
weight 2 · round to Wise BusinessMercurynone0/10Mercury advertises 'no-fee USD payments around the globe' but nothing in the evidence specifies transfer speed, let alone a sub-minute arrival time for international payments; typical wire/ACH rails imply multi-day settlement, and no probe or doc confirms near-instant delivery abroad.
- [claimed-docs] “Send no-fee USD payments around the globe”
Vendor docs explicitly claim most payments arrive in under 20 seconds and cover 40+ currencies/160+ countries, directly supporting the story. However, community evidence shows operational disruptions (account detail changes, account blocks) that undermine reliability of the payment experience, and there's no independent corroboration of actual speed claims. Missing for 10: independent/hands-on verification of the under-a-minute speed claim, and resolution of community reliability concerns.
- [claimed-docs] “Send payments globally, in under 20 seconds”
- [claimed-docs] “Most arrive in under 20 seconds.”
- [claimed-docs] “Make payments and get paid in 40+ currencies.”
- [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
- [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”
finance-leadSend domestic ACH and wire payments to vendors
weight 3 · round to MercuryMercury's core banking product supports sending ACH transfers and wires, evidenced by API docs referencing 'initiate ACH transfers' and payment creation (mercury-docs-16, mercury-docs-29, mercury-docs-9), plus independent community corroboration of reliable wire transfers in production use (mercury-comm-1). AI bill-pay features (mercury-docs-3) further support vendor payment workflows for finance leads. missing for 10: dedicated documentation detailing wire vs ACH fees, transfer limits, cutoff times, and a full end-to-end vendor payment approval workflow beyond generic mentions.
- [claimed-docs] “Pull balances, list transactions, and initiate ACH transfers — all through a single REST API”
- [claimed-docs] “Write actions such as making payments, categorizing transactions, creating invoices, and uploading receipts”
- [claimed-docs] “Find any transaction, vendor, or card, or jump straight to creating payments, transfers, and more — all from one universal search bar.”
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
Wise Business docs confirm global/business payments via API and US bank account details (implying domestic transfers), but no explicit mention of ACH or wire transfer mechanics, batch vendor payments, or approval workflows for finance teams. Community reports also show real friction — sudden change of US account/routing details with no notice (wise-comm-3) and a business account being fully blocked over a category mismatch (wise-comm-6) — which undercuts reliability for ongoing vendor payments. missing for 10: explicit ACH/wire terminology, vendor batch-payment/approval workflow evidence, and confirmation that account-detail volatility doesn't disrupt recurring vendor payments.
- [claimed-docs] “Send payments globally, in under 20 seconds”
- [claimed-docs] “How to make business payments via API from a Wise account.”
- [claimed-docs] “Make payments and get paid in 40+ currencies.”
- [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
- [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”
finance-leadSend international payments in local currencies with transparent fees
weight 3 · round to Wise BusinessMercurynone0/10Mercury's documented international payment feature is explicitly USD-only ('Send no-fee USD payments around the globe' — mercury-docs-7), with no evidence of multi-currency/local-currency payment support, FX conversion, or transparent FX fee disclosure anywhere in the API, MCP, or product docs.
- [claimed-docs] “Send no-fee USD payments around the globe”
Docs show international payments in 40+ currencies with rate lock guarantees and no hidden fees/markups, directly matching the finance-lead's need for transparent-fee international payments; community evidence corroborates it's used for real business payments (NET 30-90 terms) and is seen as reliable vs alternatives. Missing for 10: independent fee-transparency audits and more detail on actual fee schedules beyond marketing claims, plus account-detail-change incidents that add operational friction risk not solely about fee transparency.
- [claimed-docs] “Send payments globally, in under 20 seconds”
- [claimed-docs] “Most arrive in under 20 seconds.”
- [claimed-docs] “Lock in exactly what your recipient will get for up to 24 hours. If the rate drops, you won’t lose out.”
- [claimed-docs] “Pay and withdraw cash worldwide without any hidden fees or markups.”
- [claimed-docs] “Make payments and get paid in 40+ currencies.”
- [community] “I feel they are more reliable than PayPal.”
- [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”
Multi currency
founderHold and manage balances in multiple currencies from one account
weight 2 · round to Wise BusinessMercurynone0/10Evidence shows Mercury offers USD checking/savings/Treasury accounts and no-fee USD international payments (mercury-docs-7, mercury-docs-39), but nothing indicates the ability to hold or manage balances in foreign currencies (e.g., EUR, GBP) within a single account — all documented balances, cards, and API/MCP tools reference USD only. Missing for 10: any documentation of multi-currency account creation, foreign-currency balance holding, or currency conversion/FX management features.
- [claimed-docs] “Send no-fee USD payments around the globe”
- [claimed-docs] “Apply for free checking and savings accounts with zero minimums, earn up to 3.89% yield with Treasury by Mercury Advisory”
- [claimed-docs] “Track your balance - easy access to account level balances, with ability to download statements as PDFs”
Wise Business documentation clearly supports holding and receiving in 40+ currencies with global account details from one account, matching the founder story directly. Missing for 10: independent hands-on review of the multi-currency dashboard/balance management UI itself (community evidence cited relates to account-detail change notices, not to the core multi-currency holding capability).
- [claimed-docs] “Receive payment in 40+ currencies”
- [claimed-docs] “Get paid easily in other currencies with global account details.”
- [claimed-docs] “Make payments and get paid in 40+ currencies.”
- [claimed-docs] “Create accounts for 160+ countries”
founderReceive payments using local account details in multiple currencies
weight 2 · round to Wise BusinessMercurynone0/10Evidence shows Mercury offers USD checking/savings accounts and sending no-fee USD payments globally, but there is no evidence of local currency receiving account details (e.g., local IBAN/EUR, GBP, local clearing numbers) for accepting multi-currency payments — this is a fair question for a business banking product but Mercury's evidence pack is USD-centric throughout.
- [claimed-docs] “Send no-fee USD payments around the globe”
- [claimed-docs] “Apply for free checking and savings accounts with zero minimums, earn up to 3.89% yield with Treasury by Mercury Advisory”
Wise Businessdisputedcontradicted5/10Wise Business documents receiving payments via local account details in 40+ currencies/160+ countries (wise-docs-1,3,9,12), but concrete hands-on reports show these account details can change with zero notice, breaking real business payment flows with enterprise clients on NET30/90 terms (wise-comm-3, wise-comm-5), and one founder's entire business account was blocked due to a category mismatch (wise-comm-6). Missing for 10: independent verification of stability of account details over time, and resolution/track record after the reported incidents.
- [claimed-docs] “Create accounts for 160+ countries”
- [claimed-docs] “Receive payment in 40+ currencies”
- [claimed-docs] “Get paid easily in other currencies with global account details.”
- [claimed-docs] “Make payments and get paid in 40+ currencies.”
- [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
- [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”
- [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”
Operational efficiency
finance-leadSearch across all transactions, vendors, and cards from one universal search bar and jump straight into initiating a payment
weight 1 · round to MercuryMercury's own marketing docs explicitly describe a universal search bar to find any transaction, vendor, or card and jump straight into creating payments/transfers, directly matching the story. missing for 10: no independent/hands-on verification or screenshots of the search UI in action, and no community corroboration of this specific feature.
- [claimed-docs] “Find any transaction, vendor, or card, or jump straight to creating payments, transfers, and more — all from one universal search bar.”
Wise Businessnone0/10No evidence of a universal search bar across transactions, vendors, and cards, nor any UI navigation feature that lets a finance-lead jump from search results into initiating a payment. Evidence pack only covers payment sending, currency accounts, cards issuance, and unrelated account-closure complaints.
Payment transparency
finance-leadSee the exact delivery estimate for an ACH or wire transfer before confirming it
weight 2 · round to Wise BusinessMercurynone0/10The evidence pack covers cards, invoicing, API/MCP/CLI tooling, and sandbox testing, but nothing describes a transfer confirmation UI showing an estimated delivery date/time for ACH or wire payments before the user confirms.
Wise advertises general speed ('most arrive in under 20 seconds') and a rate-lock guarantee, but there is no evidence of a specific, itemized delivery-time estimate shown per ACH/wire transfer before confirmation. missing for 10: concrete UI/API evidence of a per-transaction delivery estimate for ACH/wire, confirmation-screen screenshots or docs showing exact ETA, independent corroboration of estimate accuracy.
- [claimed-docs] “Most arrive in under 20 seconds.”
- [claimed-docs] “Lock in exactly what your recipient will get for up to 24 hours. If the rate drops, you won’t lose out.”
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnMercury explicitly documents an llms.txt endpoint for AI agents ('For AI agents: visit https://docs.mercury.com/llms.txt for an index of all pages formatted in Markdown and endpoints in OpenAPI. Append .md to any documentation page URL...'), and a live probe confirms llms.txt returns HTTP 200 with the expected markdown index content. This directly satisfies the story of pointing an agent at agent-oriented docs. Missing for 10: the OpenAPI spec referenced by llms.txt is not actually publicly downloadable (404s on all conventional paths, openapiVisibility set to admin-only), a minor inconsistency between the llms.txt promise and reality.
- [claimed-docs] “Mercury API docs state: 'For AI agents: visit https://docs.mercury.com/llms.txt for an index of all pages formatted in Markdown and endpoint…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mercury.com/llms.txt # Mercury API Documentation > Documentation for Mercury API Append .md to an…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.mercury.com/openapi.json, https://docs.mercury.com/swagger.json, https://docs.mercury.c…”
- [probe] “PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://doc…”
A direct probe confirms llms.txt is live at docs.wise.com/llms.txt returning HTTP 200 with structured agent-oriented content describing the Global Payments API, showing an AI agent can be pointed at this file successfully. Missing for 10: independent/community confirmation of agents actually consuming it, and a discoverable OpenAPI spec (all candidate paths 404) to complement the llms.txt for deeper agentic use.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to MercuryMercury ships an official CLI (mercury-cli, verified via probe: install, version, full command tree) explicitly runnable from terminal, script, or CI pipeline, plus a REST API with scoped API tokens, an OAuth2 flow, a sandbox environment, and an official Go SDK — all suitable for headless/CI automation. Docs explicitly state 'Run Mercury operations from your terminal, a script, or a CI pipeline' and provide sandbox base URLs for safe automated testing. missing for 10: no independent third-party report of the CLI actually running inside a CI pipeline end-to-end, no official npm/PyPI SDK (only Go), and no public OpenAPI spec download for tooling generation.
- [claimed-docs] “Run Mercury operations from your terminal, a script, or a CI pipeline”
- [claimed-docs] “Issue scoped API tokens with fine-grained permissions”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [claimed-docs] “Our Sandbox environment is designed to make it easy for you to test API calls in a safe, simulated version of Mercury — no real money involv…”
- [claimed-docs] “Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API request…”
- [claimed-docs] “Official Go SDK, MercuryTechnologies/mercury-go: "The Mercury Go library provides convenient access to the Mercury REST API from application…”
- [claimed-docs] “Test safely in the sandbox, then swap one URL for production”
Wise documents an API for making business payments programmatically (wise-docs-6) and an llms.txt referencing a 'Global Payments API' (wise-probe-1), suggesting some headless/automation capability exists. However, no OpenAPI/swagger spec is discoverable at standard locations (wise-probe-2 shows 404s), and there is no explicit mention of CI integration, SDKs, webhooks, or automation-friendly tooling. Missing for 10: discoverable API spec, CI/CD examples, SDK/CLI tooling, and any explicit automation-focused documentation.
- [claimed-docs] “How to make business payments via API from a Wise account.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
ai-native userDrive the product through a documented public API
weight 3 · round to MercuryMercury publishes a comprehensive, versioned REST API (accounts, cards, transactions, invoices, payments, treasury) with interactive docs, OAuth2 and scoped API tokens, a sandbox environment, an official Go SDK, and an official CLI (verified via probe) covering the full resource surface — clearly documented and independently confirmed as working. It also explicitly caters to AI agents via llms.txt, agent skills repo, and a hosted MCP server. missing for 10: no publicly downloadable OpenAPI spec (confirmed gated to admin-only) and no official Python/Node SDKs, only community packages.
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
- [claimed-docs] “Mercury API docs state: 'For AI agents: visit https://docs.mercury.com/llms.txt for an index of all pages formatted in Markdown and endpoint…”
- [claimed-docs] “OAuth2 API: Start OAuth2 web flow; Obtain an access token — Mercury supports OAuth2 authorization for third-party/programmatic access alongs…”
- [claimed-docs] “Issue scoped API tokens with fine-grained permissions”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [claimed-docs] “Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API request…”
- [claimed-docs] “Every endpoint page on the API Reference hub (docs.mercury.com/reference, ReadMe) embeds a live request runner and generated code samples: "…”
- [claimed-docs] “Official Go SDK, MercuryTechnologies/mercury-go: "The Mercury Go library provides convenient access to the Mercury REST API from application…”
- [probe] “PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://doc…”
Wise publishes public API docs (docs.wise.com) explicitly covering account creation, global payments, and business payments via API, and the llms.txt probe confirms a 'Global Payments API' surface. Missing for 10: a discoverable OpenAPI/swagger spec (all probed endpoints 404'd) and independent developer corroboration of API usage/reliability.
- [claimed-docs] “How to make business payments via API from a Wise account.”
- [claimed-docs] “Create accounts for 160+ countries”
- [claimed-docs] “Send payments globally, in under 20 seconds”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to MercuryMercury documents scoped/least-privilege credential issuance for agents: read-only, read-write, and custom API tokens (mercury-docs-35), 'Issue scoped API tokens with fine-grained permissions' (mercury-docs-20), OAuth2 authorization flows (mercury-docs-15), and dashboard-based revocation (mercury-docs-25). This is independently corroborated by a live probe of the hosted MCP server showing OAuth2/PKCE-gated access with explicit granular scopes (read, offline_access) and a read-only-only tool inventory (mercury-probe-4, mercury-probe-5), confirming scoped agent credentials work in practice. Missing for 10: independent hands-on verification of actually minting a 'custom' scoped token end-to-end and assigning it to a live agent workflow.
- [claimed-docs] “Issue scoped API tokens with fine-grained permissions”
- [claimed-docs] “There are three types of tokens: read-only, read-write, and custom.”
- [claimed-docs] “The ability to revoke access at any time from your Mercury dashboard”
- [claimed-docs] “OAuth2 API: Start OAuth2 web flow; Obtain an access token — Mercury supports OAuth2 authorization for third-party/programmatic access alongs…”
- [probe] “PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offe…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
Wise Businessnone0/10No evidence of scoped or least-privilege API credential issuance (e.g., token scoping, permission granularity, or per-agent API keys); docs mention API payments but nothing about credential scoping mechanisms, and OpenAPI/spec probes 404.
- [claimed-docs] “How to make business payments via API from a Wise account.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
ai-native userBuild against official SDKs
weight 2 · round to MercuryMercury ships one official SDK (Go, generated via Stainless) plus a public REST API, official CLI, and MCP server, giving AI-native builders real programmatic surface area, but there is no official JS/TypeScript or Python SDK — only community packages (e.g. n8n-nodes-mercury) — and the OpenAPI spec is deliberately kept non-public (openapiVisibility:'admin'), limiting SDK-generation/tooling for other languages. missing for 10: official SDKs in mainstream AI-stack languages (JS/Python), publicly downloadable OpenAPI spec, independent hands-on confirmation of SDK usage beyond docs.
- [claimed-docs] “Official Go SDK, MercuryTechnologies/mercury-go: "The Mercury Go library provides convenient access to the Mercury REST API from application…”
- [claimed-docs] “Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self…”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [probe] “PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://doc…”
- [claimed-docs] “Pull balances, list transactions, and initiate ACH transfers — all through a single REST API”
- [claimed-docs] “Test safely in the sandbox, then swap one URL for production”
Wise Businessnone0/10Evidence shows Wise has business payment APIs and docs (wise-docs-6, wise-probe-1) but nothing about official SDKs/client libraries for developers; the OpenAPI spec itself 404s across all standard paths (wise-probe-2), suggesting even machine-readable API definitions aren't published, let alone language SDKs.
- [claimed-docs] “How to make business payments via API from a Wise account.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
ai-native userSubscribe to events via webhooks
weight 2 · round to MercuryMercury's Accounts Receivable API explicitly documents webhook endpoint management (Create/Update/Verify/Get/Delete) and an Events API to retrieve emitted events, and the CLI also exposes a dedicated 'webhooks' resource command, confirming first-class webhook subscription support. Missing for 10: independent/hands-on confirmation of actually receiving a webhook payload, and documentation of supported event types/payload schemas.
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to MercuryMercury's docs.mercury.com/reference hub is a ReadMe-based interactive API reference with a live 'Try It!' request runner, language-specific code samples (Shell, Node, Ruby, PHP, Python), Bearer auth field, and real endpoint schemas, backed by a sandbox environment for safe testing. This is corroborated by probes confirming the reference page loads and the sandbox base URLs work. Missing for 10: publicly downloadable OpenAPI spec (confirmed 404/admin-only via probes), and no independent hands-on account of actually running examples through the 'Try It' button.
- [claimed-docs] “Every endpoint page on the API Reference hub (docs.mercury.com/reference, ReadMe) embeds a live request runner and generated code samples: "…”
- [claimed-docs] “Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API request…”
- [probe] “PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://doc…”
- [claimed-docs] “Our Sandbox environment is designed to make it easy for you to test API calls in a safe, simulated version of Mercury — no real money involv…”
Wise Businessnone0/10No evidence of an interactive API reference with runnable examples; probes for OpenAPI/swagger specs all returned 404, and docs pack only lists feature descriptions, not interactive tooling.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to MercuryMercurydisputedcontradicted4/10Mercury's llms.txt claims endpoints are documented 'in OpenAPI' format for AI agents (mercury-docs-14), and the docs hub has an interactive API reference, but direct probes of all standard OpenAPI spec paths return 404, and the reverify probe confirms the OpenAPI 3.0 definitions exist internally but are deliberately hidden from public download (showOpenAPIDownload:false, openapiVisibility:admin). So the claimed machine-readable spec is not actually obtainable by an AI-native user. Missing for 10: a publicly downloadable OpenAPI/JSON spec file, confirmation the llms.txt claim resolves to an actual retrievable machine-readable spec.
- [claimed-docs] “Mercury API docs state: 'For AI agents: visit https://docs.mercury.com/llms.txt for an index of all pages formatted in Markdown and endpoint…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.mercury.com/openapi.json, https://docs.mercury.com/swagger.json, https://docs.mercury.c…”
- [probe] “PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://doc…”
Wise Businessnone0/10Wise Business exposes a documented API (payments, accounts, cards) so an OpenAPI-style machine-readable spec is a fair expectation, but direct probes for openapi.json/swagger.json and related paths all returned 404, and no evidence shows a downloadable spec elsewhere.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
- [claimed-docs] “How to make business payments via API from a Wise account.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to MercuryMercury documents a dedicated sandbox environment (sandbox.mercury.com/signup, api-sandbox.mercury.com base URL, oauth2-sandbox base URL) explicitly stated to use 'dummy data' with 'no real money involved,' and production tokens are rejected in sandbox, enforcing isolation; the API docs and CLI also expose an --environment sandbox|production flag confirming first-class sandbox support across API and CLI. missing for 10: no independent/hands-on community report of actually using the sandbox (only vendor docs and a CLI probe showing the flag exists, not an end-to-end sandbox test transcript).
- [claimed-docs] “Test safely in the sandbox, then swap one URL for production”
- [claimed-docs] “Our Sandbox environment is designed to make it easy for you to test API calls in a safe, simulated version of Mercury — no real money involv…”
- [claimed-docs] “Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API request…”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
Wise Businessnone0/10No evidence in the pack mentions a sandbox or test environment for Wise Business API testing; documentation focuses on live payment features, account creation, and API usage without any sandbox/test-mode reference. missing for 10: mention of sandbox environment, test API keys, or non-production testing mode.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to MercuryMercury's API is clearly versioned (/api/v1/, with a v1-pre/v1/v2 version picker) and Mercury publishes a dated public changelog with migration guidance for breaking changes (e.g. the credit statement sign-convention change), showing real practice around versioning and change management. However, the evidence explicitly states no written deprecation/sunset policy page exists anywhere on docs.mercury.com, so there is no formal documented policy an AI-native integrator could point to for guarantees on deprecation timelines. missing for 10: a published formal deprecation/sunset policy document, explicit version-lifecycle/support-window commitments, and independent confirmation that breaking changes are always preceded by adequate notice.
- [claimed-docs] “API base paths are versioned under /api/v1/ ("get https://api.mercury.com/api/v1/account/{accountId}/cards") and the docs hub nav publishes …”
- [claimed-docs] “Mercury publishes a public API changelog (docs.mercury.com/changelog) with dated change notices and migration guidance, e.g. "Credit Stateme…”
- [claimed-docs] “Every endpoint page on the API Reference hub (docs.mercury.com/reference, ReadMe) embeds a live request runner and generated code samples: "…”
Wise Businessnone0/10No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes all returned 404, and community evidence actually shows abrupt, undocumented breaking changes (bank account details changing with zero notice) rather than a managed deprecation process.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
- [community] “I received notification that my US bank account number will stop working immediately and I should not use it anywhere and remove it from any…”
- [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
- [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to MercuryMercury exposes per-resource CRUD endpoints (cards, invoices, transactions, categories) and a CLI/API that let scripts loop to create many cards or invoices, and a real customer reports creating 'hundreds of virtual debit cards' and 'dozens of purpose-named accounts' this way. However there's no documented native bulk/batch endpoint (e.g. batch-create invoices/cards in one call), and the MCP server is entirely read-only (list/get only, no write tools), so bulk write actions must be hand-scripted item-by-item via the REST API or CLI rather than a first-class bulk operation feature. Missing for 10: a documented batch/bulk-create API endpoint, bulk operations support in the MCP/agent surface, and vendor documentation explicitly describing bulk workflows.
- [claimed-docs] “Instantly spin up as many virtual cards as you need. Create cards for any purpose — ad spend, contractors, you name it.”
- [claimed-docs] “Create up to 500 invoices/month on Mercury Plus, or unlimited invoices with Pro”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to MercuryMercury exposes an Events/Webhooks API (create/update/verify webhook endpoints, get events) that lets external systems react to account events, and ships some built-in automatic behaviors (auto-attach receipts, automatic cashback deposit, AI bill-reading automations). However there is no evidence of a native in-product 'if event X then action Y' rule-builder that AI-native users can configure themselves — webhooks require the user to build their own listener/automation logic outside Mercury, and MCP tools are read-only so agents cannot trigger write actions from natural-language rules. Missing for 10: a documented rules/automation engine or trigger-action builder inside Mercury, and evidence that MCP/agent tooling can autonomously execute rule-based actions.
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
- [claimed-docs] “Earn unlimited cashback automatically deposited into your account — no manual redemption or confusing points.”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to MercuryMercury offers some recurring, automation-like features (automatic invoices, AI-powered bill-pay automations, auto-funding rules for accounts) but there is no evidence of a general-purpose scheduler or 'recurring job/workflow' API, CLI command, or MCP tool that an AI-native user could invoke to schedule arbitrary tasks. The MCP server is explicitly read-only (31 get/list tools) and the CLI/API expose transactional resources, not job scheduling. Missing for 10: dedicated recurring-job/cron API or MCP tool, evidence of scheduling arbitrary workflows beyond built-in invoice/bill automations, and any documentation of a scheduler for AI agents.
- [claimed-docs] “Send manual and automatic invoices, accept flexible payment methods, and manage customer details right from your Mercury account.”
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
Cards spend — issuing cards and controlling spend — limits, approvals, expense captureCards spend
Issuing cards and controlling spend — limits, approvals, expense capture
Card controls
finance-leadSet department or program budgets with automatically enforced spend limits
weight 2 · round to MercuryMercury supports per-card spending limits, spend controls, and granular user permissions (mercury-docs-10, mercury-docs-38), and the Cards API lets you 'manage spending limits' programmatically (mercury-docs-36), which enforces spend caps at the card/user level. However, there is no evidence of a dedicated department- or program-level 'budget' object that aggregates multiple cards/users under one enforced ceiling — only individual card limits and role-based permissions are documented. Missing for 10: explicit department/program budget creation, budget rollup/aggregation across multiple cards or cost centers, and automatic alerts/enforcement tied to a program-level allocation rather than per-card limits.
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “You can now issue virtual cards, manage spending limits, and control card lifecycle states — all through the API.”
- [claimed-docs] “Earn 1.5% cashback on credit card spend, and control team expenses with cards, reimbursements, limits, and approvals all in one place.”
- [claimed-docs] “Built-in permissions means our accountant can easily make payments — literally one click and it’s done.”
finance-leadSet per-card spend limits and granular controls for each employee
weight 3 · round to MercuryMercury explicitly markets per-card spend limits and granular permissions ('Curb team spend with card limits, spend controls, and granular user permissions'), backed by virtual card creation, card lifecycle/limit management via API, and independent community confirmation of creating hundreds of virtual cards with individual limits. missing for 10: no hands-on walkthrough of setting a specific per-employee limit in the UI, and no detail on the granularity of permission types available to finance leads beyond marketing copy.
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “Instantly spin up as many virtual cards as you need. Create cards for any purpose — ad spend, contractors, you name it.”
- [claimed-docs] “You can now issue virtual cards, manage spending limits, and control card lifecycle states — all through the API.”
- [claimed-docs] “Earn 1.5% cashback on credit card spend, and control team expenses with cards, reimbursements, limits, and approvals all in one place.”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
finance-leadInstantly freeze a lost or stolen card and order a replacement
weight 2 · round to MercuryMercury lets you retrieve cards and, via the Cards API, 'manage spending limits and control card lifecycle states' (mercury-docs-1, mercury-docs-36), which plausibly covers freezing/deactivating a card, but there is no explicit documentation of a 'freeze card' action or of ordering a physical replacement card for a lost/stolen card. missing for 10: explicit freeze/lock card documentation, explicit lost/stolen card replacement flow, UI or API evidence of the finance-lead-facing freeze button.
- [claimed-docs] “Retrieve all debit and credit cards associated with a specific account.”
- [claimed-docs] “You can now issue virtual cards, manage spending limits, and control card lifecycle states — all through the API.”
- [claimed-docs] “Instantly spin up as many virtual cards as you need. Create cards for any purpose — ad spend, contractors, you name it.”
Wise Businessnone0/10Evidence shows Wise issues debit cards worldwide, but there is no mention of card freezing/locking or replacement-ordering functionality anywhere in the pack.
- [claimed-docs] “Issue debit cards worldwide”
finance-leadRequest a transaction limit increase directly from a self-service screen
weight 1 · round to MercuryMercury documents self-service control over card spend limits ("Curb team spend with card limits, spend controls" and API support to "manage spending limits"), which lets an admin set/adjust limits directly rather than submit a request for approval. There is no explicit evidence of a dedicated 'request a transaction/credit limit increase' self-service screen or approval workflow. Missing for 10: explicit UI/flow for submitting and approving a limit-increase request, confirmation this applies to overall account/credit limits (not just per-card spend caps), and independent/hands-on verification of the flow.
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “You can now issue virtual cards, manage spending limits, and control card lifecycle states — all through the API.”
- [claimed-docs] “Earn 1.5% cashback on credit card spend, and control team expenses with cards, reimbursements, limits, and approvals all in one place.”
Card issuance
finance-leadInstantly create virtual cards scoped to a specific purpose like ad spend or a single vendor
weight 3 · round to MercuryMercury's docs explicitly market instant virtual card creation scoped to purposes like ad spend or vendor use, backed by spend controls/limits and an API for issuing/managing card lifecycle, and a 5-year customer corroborates creating hundreds of individually-limited virtual cards in practice. Missing for 10: explicit documentation of merchant-lock/single-vendor restriction mechanics beyond naming and limits, and independent confirmation specifically of 'purpose-scoped' (vs just limited) cards.
- [claimed-docs] “Instantly spin up as many virtual cards as you need. Create cards for any purpose — ad spend, contractors, you name it.”
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “You can now issue virtual cards, manage spending limits, and control card lifecycle states — all through the API.”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
Wise Businessnone0/10Evidence only mentions issuing debit cards worldwide (wise-docs-4) with no mention of virtual cards, spend controls, or scoping cards to a vendor/purpose — the specific capability finance leads need for scoped spend controls is absent.
- [claimed-docs] “Issue debit cards worldwide”
finance-leadIssue physical debit or credit cards to employees with defined roles
weight 2 · round to MercuryMercury documents issuing business debit/credit cards to employees with spend limits and granular permissions (mercury-docs-10, mercury-docs-27, mercury-docs-38, mercury-docs-1), and a community user confirms creating many cards with individual limits (mercury-comm-1). However most product copy emphasizes virtual cards (mercury-docs-2) and no evidence explicitly details a physical-card issuance workflow tied to defined employee roles. Missing for 10: explicit documentation of physical card ordering/shipping process, and role-based (not just limit-based) card issuance controls.
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “Access business credit cards as soon as day one — no minimums, credit checks, or personal guarantees.”
- [claimed-docs] “Earn 1.5% cashback on credit card spend, and control team expenses with cards, reimbursements, limits, and approvals all in one place.”
- [claimed-docs] “Retrieve all debit and credit cards associated with a specific account.”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
Evidence only shows a thin claim that Wise lets businesses 'issue debit cards worldwide' with no detail on assigning employee roles, spending controls, or credit card issuance. missing for 10: evidence of credit card issuance, role-based permissions/spend controls per employee, and any independent corroboration of card issuance workflow.
- [claimed-docs] “Issue debit cards worldwide”
Card rewards
founderSpend and withdraw cash abroad on a company card without hidden foreign fees
weight 1 · round to Wise BusinessMercurynone0/10The evidence pack covers card issuance, virtual cards, cashback, and no-fee USD payments/transfers, but nothing addresses foreign transaction fees, currency conversion fees, or ATM cash withdrawal abroad on a Mercury card. 'No-fee USD payments around the globe' (mercury-docs-7) refers to outbound payments, not card spend/withdrawal abroad, so it does not substantiate this specific claim.
Wise docs explicitly state cards can be issued worldwide and used to 'pay and withdraw cash worldwide without any hidden fees or markups,' directly matching the founder's story. Community evidence corroborates general reliability but doesn't specifically address card fee transparency, and there's no independent hands-on verification of the no-hidden-fee claim for card withdrawals abroad. Missing for 10: independent/hands-on confirmation of actual ATM withdrawal fees and card FX markup transparency in practice.
- [claimed-docs] “Issue debit cards worldwide”
- [claimed-docs] “Pay and withdraw cash worldwide without any hidden fees or markups.”
- [community] “I feel they are more reliable than PayPal.”
founderEarn automatic cashback on card spend without manual redemption steps
weight 2 · round to MercuryMercury explicitly advertises automatic, unlimited cashback deposited directly into the account with no manual redemption or points system, and separately states a concrete 1.5% cashback rate on credit card spend, directly matching the founder story. Missing for 10: independent/community corroboration that the cashback mechanic works as described in practice, and clarity on whether it applies uniformly to debit vs credit cards.
- [claimed-docs] “Earn unlimited cashback automatically deposited into your account — no manual redemption or confusing points.”
- [claimed-docs] “Earn 1.5% cashback on credit card spend, and control team expenses with cards, reimbursements, limits, and approvals all in one place.”
Receipt management
ai-native userHave receipts automatically captured and coded the moment a card is used, without manual entry
weight 3 · round to MercuryMercury lets users email or upload receipts and auto-attaches them to the matching card transaction (mercury-docs-5/28), and there's a mercury-receipt-upload agent skill for automating this (mercury-supp-agent-skills), plus a transaction-attachment API endpoint (mercury-docs-12). However, this is not truly automatic capture 'the moment a card is used' — it requires the user to email/upload the receipt themselves rather than passive/automatic capture at time of swipe, and there's no OCR/auto-coding of receipt line items into categories mentioned, only attachment matching. Missing for 10: evidence of automatic receipt capture without any manual send/upload step (e.g., via merchant integration or physical receipt scanning at point of sale), evidence of automatic line-item categorization/coding from receipt contents, and independent/hands-on confirmation this works reliably in practice.
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction.”
- [claimed-docs] “Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self…”
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
Wise Businessnone0/10No evidence Wise offers receipt capture, OCR, or expense coding features tied to card transactions; documentation only covers accounts, payments, and card issuance, not receipt automation.
- [claimed-docs] “Issue debit cards worldwide”
- [claimed-docs] “How to make business payments via API from a Wise account.”
finance-leadHave receipts automatically attached to the right transaction by emailing or uploading them
weight 2 · round to MercuryMercury's docs explicitly state receipts can be emailed or uploaded and are auto-attached to the correct card transaction, directly matching the story, with API support for uploading transaction attachments. missing for 10: independent/hands-on confirmation (e.g. community report) that auto-attach matching works reliably in practice, and no detail on edge cases (mismatched/ambiguous receipts).
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction.”
- [claimed-docs] “Write actions such as making payments, categorizing transactions, creating invoices, and uploading receipts”
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
Onboarding — getting started and time-to-first-value storiesOnboarding
Getting started and time-to-first-value stories
Embedded finance
developerOffer embedded banking accounts to my customers without holding my own financial license
weight 1 · round to Wise BusinessMercurynone0/10Mercury's evidence describes a business bank account plus an API/MCP/CLI for managing that single business's own accounts, cards, invoices, and payments — not a banking-as-a-service platform for issuing white-labeled accounts to a developer's end customers under Mercury's charter. Nothing in the docs, changelog, SDKs, or API catalog mentions account issuance for third-party end users, program management, or BaaS partnership terms.
- [claimed-docs] “Pull balances, list transactions, and initiate ACH transfers — all through a single REST API”
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
- [claimed-docs] “Write actions such as making payments, categorizing transactions, creating invoices, and uploading receipts”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
Wise's own docs explicitly claim businesses without financial licenses can offer accounts to their customers, backed by supporting account/currency/card issuance and FDIC passthrough features. However, this is entirely first-party marketing/docs with no independent case study confirming a developer actually embedding Wise accounts for end customers, and community reports show real operational risk (a Wise Business account being fully blocked over category mismatch, and account details changing with no notice) that could undermine trust in offering these as a foundation for customer-facing banking. missing for 10: independent/hands-on corroboration of the embedded accounts flow, and resolution of the compliance/account-stability concerns raised by users.
- [claimed-docs] “How businesses without financial licenses can offer accounts for their customers.”
- [claimed-docs] “Create accounts for 160+ countries”
- [claimed-docs] “Issue debit cards worldwide”
- [claimed-docs] “Opt in and get passthrough FDIC insurance up to $250,000 through our Program Bank.”
- [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”
- [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”
Signup flow
founderCheck my account application status while it's under review
weight 1 · round drawnMercurynone0/10Evidence shows Mercury's onboarding application flow (apply online, CLI 'Onboarding (apply)' command) but nothing about being able to check or track the status of an application while it's under review — no dashboard, CLI, or API endpoint for application/review status is documented anywhere in the pack.
- [claimed-docs] “Apply online in 10 minutes to experience banking unlike anything that’s come before.”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
Switching
founderReplace multiple point solutions for spend, bill pay, and banking with one consolidated platform
weight 2 · round to MercuryMercury documents a unified platform covering banking, virtual/physical cards with spend controls, bill pay with AI-assisted invoice reading, AR/invoicing, receipt auto-attachment, accounting sync (QuickBooks/Xero/NetSuite), Treasury yield, and FX/international payments, all inside one account — directly consolidating spend, bill pay, and banking tools. Independent community evidence (5-year customer) corroborates real-world use across cards, wires, and multi-account structures replacing other tools. missing for 10: no independent evidence of replacing named specific competitor point-solutions (e.g., Expensify/Bill.com) or third-party case studies quantifying tool consolidation.
- [claimed-docs] “Instantly spin up as many virtual cards as you need. Create cards for any purpose — ad spend, contractors, you name it.”
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Send manual and automatic invoices, accept flexible payment methods, and manage customer details right from your Mercury account.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [claimed-docs] “Send no-fee USD payments around the globe”
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “Earn 1.5% cashback on credit card spend, and control team expenses with cards, reimbursements, limits, and approvals all in one place.”
- [claimed-docs] “Apply for free checking and savings accounts with zero minimums, earn up to 3.89% yield with Treasury by Mercury Advisory”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
Wise Business clearly consolidates banking (multi-currency accounts, global payment details), cards, and payment sending/API into one platform, which covers 'banking' and part of 'spend'. However, there is no evidence of dedicated bill-pay/AP automation or spend-management features (approvals, budgets, expense categorization) that founders would need to fully replace those point solutions, and community reports show operational friction (account detail changes, account blocks) that undercut a seamless 'one platform' story. Missing for 10: dedicated bill pay/invoicing workflow, spend management/approval controls, and independent evidence of reliability at scale.
- [claimed-docs] “Create accounts for 160+ countries”
- [claimed-docs] “Receive payment in 40+ currencies”
- [claimed-docs] “Issue debit cards worldwide”
- [claimed-docs] “How to make business payments via API from a Wise account.”
- [claimed-docs] “Get paid easily in other currencies with global account details.”
- [community] “Due to an operational change, your USD account details for your Wise Business and Personal accounts are changing... From today, October 17, …”
- [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”
founderFully onboard onto a new banking platform in about a week instead of months
weight 2 · round to MercuryMercury explicitly advertises rapid onboarding ("Apply online in 10 minutes") and near-instant account usability ("business credit cards as soon as day one — no minimums, credit checks, or personal guarantees"), directly supporting a week-vs-months onboarding claim. However, this is vendor marketing copy only — no independent/community account of an actual end-to-end onboarding timeline, KYC/compliance steps, or founder testimonials confirming real-world speed. Missing for 10: independent or hands-on confirmation of onboarding duration, detail on KYC/compliance steps, and founder testimonials specifically about onboarding speed.
- [claimed-docs] “Apply online in 10 minutes to experience banking unlike anything that’s come before.”
- [claimed-docs] “Access business credit cards as soon as day one — no minimums, credit checks, or personal guarantees.”
Wise Businessnone0/10The evidence pack contains no claims or documentation about how long it takes a founder to open and fully activate a Wise Business account — no onboarding timeline, sign-up flow speed, or verification turnaround is mentioned. The only tangential items describe account creation breadth (160+ countries) and API payment docs, not onboarding speed, and community evidence instead highlights account blocks/changes (wise-comm-6, wise-comm-3) rather than fast onboarding.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to MercuryMercury's REST API, CLI, and SDK expose most core UI actions—accounts, transactions, card issuance/lifecycle, invoices/customers, categories, statements, webhooks, ACH payments, and even Vault agent-card credentials (mercury-docs-12,13,36,37; mercury-probe-3)—with sandbox, versioning, and changelog support. However parity is incomplete: the AI bill-reading/bill-pay flow (mercury-docs-3) has no documented API equivalent, and the hosted MCP surface is explicitly read-only (31 get/list tools, zero write actions per mercury-probe-5), meaning an AI agent using MCP cannot perform actions like payments or invoice creation that a human can in the UI. Missing for 10: documented API/CLI parity for bill-pay AI feature, write-capable MCP tools matching UI actions, and confirmation that all UI-only conveniences (universal search, cashback redemption) have functional API analogs.
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
- [claimed-docs] “Write actions such as making payments, categorizing transactions, creating invoices, and uploading receipts”
- [claimed-docs] “You can now issue virtual cards, manage spending limits, and control card lifecycle states — all through the API.”
- [claimed-docs] “Agents can now pull full card credentials - number, expiry, and CVC - for agent cards through the new Vault API”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
- [probe] “PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offe…”
Docs show the API can create accounts, send/receive payments, and issue cards, mirroring several core UI capabilities (wise-docs-1..6), but there's no evidence of full parity — no OpenAPI/spec found (wise-probe-2 all 404), and UI-only features like rate locks, FDIC opt-in, or dispute/support workflows aren't shown as API-accessible. missing for 10: a published complete API reference/OpenAPI spec, explicit parity statement, coverage of rate-lock/insurance/account-management UI features via API, and independent confirmation of full functional overlap.
- [claimed-docs] “Create accounts for 160+ countries”
- [claimed-docs] “Send payments globally, in under 20 seconds”
- [claimed-docs] “Receive payment in 40+ currencies”
- [claimed-docs] “Issue debit cards worldwide”
- [claimed-docs] “How to make business payments via API from a Wise account.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to MercuryMercury exposes transactions, statements (PDF), categories, invoices, and account data via a documented REST API and CLI, which provides a path to programmatically export financial data in standard formats (JSON, PDF). However, there is no evidence of a dedicated 'export all my data' bulk-export feature, no mention of CSV/standard banking export formats beyond PDF statements, and no documentation addressing account closure or leaving with full data portability guarantees. missing for 10: a documented full-account data export/closure workflow, explicit open standard formats (e.g., CSV/OFX) beyond PDF, and any guarantee of data portability upon account closure.
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
- [claimed-docs] “Pull balances, list transactions, and initiate ACH transfers — all through a single REST API”
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [claimed-docs] “Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API request…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userControl data retention and deletion
weight 2 · round drawnMercurynone0/10Evidence shows only the ability to revoke MCP/API access (mercury-docs-25), but nothing about controlling data retention periods or deleting stored/processed data for AI-native usage; banking retention requirements make this a fair question but no capability is documented.
- [claimed-docs] “The ability to revoke access at any time from your Mercury dashboard”
Security — security posture and hardening storiesSecurity
Security posture and hardening stories
Access control
finance-leadDefine granular user roles and permissions across team members, locations, and departments
weight 3 · round to MercuryMercury explicitly advertises 'granular user permissions' and 'built-in permissions' allowing role-differentiated access (e.g., accountant given payment-only access) plus scoped/read-only/read-write/custom API tokens, which supports role-based access control for a finance lead. However, there is no evidence of permission structuring specifically by location or department, or of a full admin UI showing role/permission matrix management. Missing for 10: documentation of location- or department-level permission scoping, a detailed permissions matrix/UI walkthrough, and independent confirmation of granular role management beyond marketing claims.
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
- [claimed-docs] “Built-in permissions means our accountant can easily make payments — literally one click and it’s done.”
- [claimed-docs] “Issue scoped API tokens with fine-grained permissions”
- [claimed-docs] “There are three types of tokens: read-only, read-write, and custom.”
Fraud detection
ai-native userHave AI flag anomalous or out-of-policy transactions automatically for review
weight 2 · round to MercuryThe official mercury-skills repo lists a 'mercury-detect-anomaly' skill for the Mercury CLI, indicating an AI-driven anomaly-detection capability exists, but there is no documentation of how it works, whether it flags out-of-policy transactions specifically, or how review/approval is triggered. Missing for 10: detailed docs on anomaly/policy-violation detection logic, automatic flagging-for-review workflow, and independent confirmation the skill functions as described.
- [claimed-docs] “Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self…”
Wise Businessnone0/10No evidence of AI-driven anomaly detection or policy-based transaction flagging in Wise Business docs or community reports; evidence covers payments, cards, and account changes only. missing for 10: any AI/ML anomaly detection feature, policy rule engine, automated flagging or review workflow.
Support reliability — stories about support reliability in this arenaSupport reliability
Stories about support reliability in this arena
Customer support
founderReach live customer support at any time for urgent account issues
weight 2 · round drawnMercurynone0/10The evidence pack contains no mention of live customer support, phone/chat support hours, or urgent account-issue escalation channels; all evidence covers API/product/banking features and MCP/CLI tooling. Missing for 10: any documentation or claim about support channels, live/24-7 availability, or response times for urgent issues.
Wise Businessnone0/10No evidence of live/24-7 customer support access; instead community reports describe support taking 30 days to respond to urgent account issues and accounts being blocked without quick resolution, suggesting no reliable live urgent support channel.
- [community] “My business works with enterprises on NET 30 to NET 90 payment terms, so having account details change without warning is a painful one to c…”
- [community] “Indie developer levelsio's Wise Business account—including incoming and outgoing transfers, cards, etc.—was completely blocked because his W…”
Deposit protection
finance-leadHave deposits automatically swept across partner banks to maximize FDIC insurance coverage
weight 2 · round drawnMercurynone0/10Mercury markets Treasury sweep accounts (mercury-docs-39 mentions 'Treasury by Mercury Advisory' yield) but no evidence describes automatic sweeping of deposits across multiple partner banks specifically to maximize FDIC coverage — the docs focus on cards, invoicing, API/MCP tooling, and yield, not multi-bank FDIC sweep networks.
Wise Businessnone0/10Wise only documents passthrough FDIC insurance up to $250,000 through a single named Program Bank, not an automated multi-bank sweep network that would extend coverage beyond that cap; no evidence of sweeping deposits across multiple partner banks.
- [claimed-docs] “Opt in and get passthrough FDIC insurance up to $250,000 through our Program Bank.”
Treasury yield — stories about treasury yield in this arenaTreasury yield
Stories about treasury yield in this arena
Cash automation
finance-leadAutomate cash management with auto top-up between accounts and low-balance alerts
weight 2 · round to MercuryA long-time customer describes creating 'dozens of purpose-named accounts with auto-funding rules' (mercury-comm-1), which is real-world evidence of auto top-up/fund-transfer automation between accounts, and Mercury's Treasury product (mercury-docs-39) supports the treasury-yield angle. However, there is no vendor documentation describing configurable auto top-up rules or low-balance alert features anywhere in the docs/API/MCP evidence. missing for 10: first-party docs on auto top-up configuration, explicit low-balance alert/notification feature, and any API/webhook evidence for balance threshold alerts.
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
- [claimed-docs] “Apply for free checking and savings accounts with zero minimums, earn up to 3.89% yield with Treasury by Mercury Advisory”
Yield generation
finance-leadEarn yield on operating cash balances without moving funds to a separate institution
weight 3 · round to MercuryMercury explicitly offers 'Treasury by Mercury Advisory' with yield up to 3.89% directly within the Mercury account/dashboard, alongside free checking/savings, so operating cash can earn yield without moving funds to a separate institution. Missing for 10: independent/hands-on verification of the yield product's mechanics (e.g., sweep structure, FDIC coverage details) and community corroboration of actual yield experience beyond the vendor claim.
- [claimed-docs] “Apply for free checking and savings accounts with zero minimums, earn up to 3.89% yield with Treasury by Mercury Advisory”
Wise Businessnone0/10No evidence in the pack mentions interest, yield, or return on operating cash balances held in Wise Business accounts; only FDIC pass-through insurance and payments/currency features are documented.
- [claimed-docs] “Opt in and get passthrough FDIC insurance up to $250,000 through our Program Bank.”
- [claimed-docs] “Create accounts for 160+ countries”
- [claimed-docs] “Get paid easily in other currencies with global account details.”
finance-leadBuild a cash cushion in a high-yield savings sub-account with automated transfer rules
weight 2 · round to MercuryMercury offers a high-yield Treasury product (up to 3.89% yield) and supports multiple purpose-named sub-accounts, and a long-tenure customer reports using 'auto-funding rules' across dozens of these accounts, supporting the described workflow. However, there is no official documentation describing a dedicated 'automated transfer rule' feature or explicit high-yield savings sub-account mechanics — this evidence comes only from a single community anecdote, not vendor docs or API endpoints. Missing for 10: official docs on automated/recurring transfer rule configuration, explicit sub-account-to-Treasury auto-sweep feature documentation, and independent verification beyond one HN comment.
- [claimed-docs] “Apply for free checking and savings accounts with zero minimums, earn up to 3.89% yield with Treasury by Mercury Advisory”
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
- [community] “5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-n…”
founderEarn interest on balances held in multiple currencies
weight 1 · round drawnMercurynone0/10Evidence shows Mercury offers yield via 'Treasury by Mercury Advisory' (up to 3.89%) but this and all cash/banking references are USD-only — there is no mention of interest-bearing balances in multiple currencies, multi-currency accounts, or FX-denominated yield anywhere in the pack. Missing for 10: any documentation of multi-currency account holding, multi-currency interest rates, or FX yield products.
- [claimed-docs] “Apply for free checking and savings accounts with zero minimums, earn up to 3.89% yield with Treasury by Mercury Advisory”
- [claimed-docs] “Send no-fee USD payments around the globe”
Not comparable on these axes
ai-native userHave AI automatically assign GL codes to transactions across entities to accelerate close
weight 3 · not comparableMercury's docs mention 'AI-powered automations to close your books faster' when syncing with QuickBooks/Xero/NetSuite, and the API exposes a Categories resource plus 'Update transaction metadata' endpoint, suggesting some categorization/GL-code capability. However, there is no concrete evidence of AI automatically assigning GL codes specifically, nor any support for multi-entity operations. Missing for 10: explicit documentation of automated GL-code/category assignment logic, evidence of multi-entity/consolidated close workflows, and any hands-on or independent confirmation of this working in practice.
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [claimed-docs] “Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; …”
ai-native userHave AI read incoming bills and auto-populate payment details for my review
weight 3 · not comparableMercury explicitly markets an AI bill-pay feature that reads bills, auto-populates payment details, and remembers past recipients for quick approval, directly matching the story (mercury-docs-3). However, this is a single marketing-line claim with no deeper documentation of the review/approval workflow, no independent or hands-on corroboration, and the separate MCP tool inventory confirms only read-only capabilities with no bill-reading or auto-populate tools exposed there. Missing for 10: detailed product documentation of the bill-reading/approval UI, independent user reports confirming accuracy, and API/MCP support for this specific workflow.
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
ai-native userHave vendor invoices automatically matched to purchase orders, coded, and routed for payment
weight 2 · not comparableMercury's bill pay AI reads and auto-populates bill details and remembers recipients for quick approval (mercury-docs-3), and permissions allow routing payments to approvers like accountants (mercury-docs-11), but there is no evidence of purchase-order matching or GL/expense coding logic tying invoices to POs — core parts of the described workflow are unevidenced. missing for 10: purchase order matching/reconciliation, explicit invoice coding to GL categories tied to POs, and a documented multi-step approval routing workflow for AP.
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Built-in permissions means our accountant can easily make payments — literally one click and it’s done.”
- [claimed-docs] “Curb team spend with card limits, spend controls, and granular user permissions.”
finance-leadHave overdue invoices automatically followed up on without manual chasing
weight 1 · not comparableMercurynone0/10Mercury offers invoicing features (manual/automatic invoice creation, Accounts Receivable API for invoices, customers, webhooks/events) but no evidence describes automated reminders or follow-up chasing on overdue/unpaid invoices specifically. The invoicing API supports create/list/get/update/cancel operations, not a documented dunning or overdue-reminder workflow.
- [claimed-docs] “Send manual and automatic invoices, accept flexible payment methods, and manage customer details right from your Mercury account.”
- [claimed-docs] “Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download …”
- [claimed-docs] “Generate and send invoices based on CRM, billing, or usage data”
- [claimed-docs] “Create up to 500 invoices/month on Mercury Plus, or unlimited invoices with Pro”
finance-leadLock in an exchange rate for a fixed window before completing a transfer
weight 1 · not comparableMercuryn/aMercury is a US-focused business banking/payments product primarily dealing in USD (no-fee USD payments); there is no evidence of FX/multi-currency transfer features at all, let alone a rate-lock mechanism. Locking an exchange rate for a fixed window is a cross-border FX product feature that doesn't fit Mercury's documented scope of domestic USD banking, cards, invoicing, and API/MCP tooling.
Wise explicitly offers a rate lock ('Lock in exactly what your recipient will get for up to 24 hours') via wise-docs-8, directly matching the story, but this is a fixed 24-hour window rather than a flexible/finance-lead-configurable window, and there's no independent corroboration or API-level documentation of this feature for Business specifically. missing for 10: evidence of business-specific (vs. consumer) rate-lock terms, longer/configurable lock windows, and independent confirmation of reliability.
- [claimed-docs] “Lock in exactly what your recipient will get for up to 24 hours. If the rate drops, you won’t lose out.”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableMercuryn/aMercury is a banking/fintech platform, not an AI agent or assistant host; its AI-native positioning is as an MCP *server* (mcp.mercury.com) that other agents connect to, not as a client/host that plugs in third-party MCP servers to gain their tools. There is no evidence of any Mercury interface (chat, agent, orchestrator) into which external MCP servers can be registered — the natural and only role evidenced is the reverse direction, so this client-side axis is a category error for this product.
- [claimed-docs] “Set the MCP server URL to `https://mcp.mercury.com/mcp`.”
- [probe] “PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offe…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
ai-native userConnect an agent via an official MCP server
weight 3 · not comparableMercury ships an official, hosted MCP server at https://mcp.mercury.com/mcp, documented and independently verified live via probes showing OAuth2-gated (PKCE, dynamic client registration) access and a concrete inventory of 31 read-only tools (balances, transactions, cards, invoices, etc.), matching the docs' description of connecting agents to financial context. Missing for 10: write/action capabilities via MCP (currently read-only by design) and independent community corroboration of real-world agent usage beyond vendor docs/probes.
- [claimed-docs] “Set the MCP server URL to `https://mcp.mercury.com/mcp`.”
- [claimed-docs] “What's my balance today?”
- [claimed-docs] “Track your balance - easy access to account level balances, with ability to download statements as PDFs”
- [claimed-docs] “The ability to revoke access at any time from your Mercury dashboard”
- [probe] “PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offe…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
Wise Businessn/aWise Business is a fintech/payments platform, not an AI agent; no evidence of an official MCP server being offered, and this is a fair 'none' vs 'na' distinction—since Wise is not itself an agent, the axis would apply if evidence existed, but nothing in the pack even hints at an MCP server offering (only an API and llms.txt probe).
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.wise.com/llms.txt # Global Payments API: Send & Receive Money > Wise Platform offer domestic and c…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.wise.com/openapi.json, https://docs.wise.com/swagger.json, https://docs.wise.com/api/op…”
ai-native userUse an official CLI
weight 2 · not comparableMercury ships an official, actively maintained CLI (mercury-cli, Mercury's own GitHub org) with a documented installer, verified working `--version`/`--help`, full resource command tree (accounts, cards, payments, invoices, treasury, etc.), auth flows, sandbox/production environments, and even an official agent-skills repo built specifically to drive the CLI for AI-native workflows. missing for 10: independent third-party (non-Mercury) reviews or adoption reports of the CLI specifically, and confirmation of write-action success beyond documented help output.
- [probe] “PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The offi…”
- [claimed-docs] “Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self…”
- [claimed-docs] “Run Mercury operations from your terminal, a script, or a CI pipeline”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableMercury offers AI-driven automation for specific workflows (auto-reading bills, auto-attaching receipts, AI-powered bookkeeping close) and an MCP server plus agent skills like mercury-analyze-spend and mercury-detect-anomaly that let AI query balances/transactions in natural language and surface anomalies. However, there's no evidence of proactive, in-product generated insights/dashboards (e.g., spend trend analysis, cash-flow forecasting, or automatic suggestions surfaced in the UI) — the MCP tools are read-only query/retrieval, not generative insight/suggestion features, and the skills repo is a separate CLI-driven agent toolkit rather than an in-product experience. missing for 10: proactive/native in-app AI insights or suggestions dashboard, evidence of forecasting or recommendation generation, independent confirmation these AI features produce actionable suggestions beyond data retrieval.
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
- [claimed-docs] “Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self…”
- [claimed-docs] “you can ask natural language questions like \`What's my balance today?\` and \`Graph my last 6 months of transactions\`”
Wise Businessn/aWise Business is a payments/banking product; there is no evidence of AI-generated insights or suggestions from user data within the product. This capability is not a fair expectation of a payments platform's core product category, making it an off-axis question for this type of product.
ai-native userSet up automations that run autonomously in the background
weight 2 · not comparableMercury ships several automation primitives that can run in the background — webhooks/events API for reactive automation, auto-invoicing, AI-driven receipt matching and bookkeeping sync, plus an official CLI/API usable from scripts or CI pipelines and an 'agent skills' repo for CLI-driven automations. However, the flagship agent-facing surface (the hosted MCP server) is explicitly read-only (31 get/list tools, no write actions), so autonomous write-side actions (payments, invoices) would have to go through the API/CLI/webhooks rather than a persistent scheduled agent runtime, and no dedicated scheduler/cron/'run this automation on a trigger' product feature is documented. Missing for 10: a first-party scheduling/trigger engine for autonomous multi-step workflows, evidence of write-capable autonomous agent execution, and independent confirmation that background automations run reliably unattended.
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Send manual and automatic invoices, accept flexible payment methods, and manage customer details right from your Mercury account.”
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [claimed-docs] “Run Mercury operations from your terminal, a script, or a CI pipeline”
- [claimed-docs] “Write actions such as making payments, categorizing transactions, creating invoices, and uploading receipts”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
- [claimed-docs] “Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self…”
- [probe] “PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offe…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableMercurynone0/10Mercury exposes narrow AI-powered automations (bill scanning, receipt auto-attach, bookkeeping sync) and offers external interfaces (API, CLI, MCP server) for other agents/tools to connect to Mercury data, but there is no evidence of a built-in conversational AI assistant inside the Mercury product itself that a user can delegate tasks to.
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
- [probe] “PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offe…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
ai-native userOperate the product with natural-language commands
weight 2 · not comparableMercury ships a live, OAuth-gated hosted MCP server confirmed via probe to support natural-language queries like 'What's my balance today?' and 'Graph my last 6 months of transactions' (mercury-docs-23, mercury-docs-32, mercury-probe-4). However, independent tool-inventory verification shows all 31 MCP tools are read-only (get*/list*) with zero write/send/create actions, so natural-language commands can query data but cannot execute operations like payments or invoice creation. missing for 10: natural-language-driven write/action capability (payments, transfers, invoice creation) via MCP, and broader hands-on confirmation beyond query examples.
- [claimed-docs] “What's my balance today?”
- [claimed-docs] “you can ask natural language questions like \`What's my balance today?\` and \`Graph my last 6 months of transactions\`”
- [claimed-docs] “Give your agents the same financial context you have — no code required”
- [claimed-docs] “Query balances, transaction history, and account data in natural language”
- [probe] “PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offe…”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableMercurynone0/10Evidence shows Mercury's API, CLI, MCP server, and sandbox for building integrations/automations, plus an API changelog for endpoint version history, but nothing about versioning, reviewing, or rolling back user-created automations themselves (e.g., no workflow/rule history, diff, or undo mechanism for automations built on top of Mercury).
ai-native userHave vendor contracts parsed by AI to auto-populate procurement request forms
weight 2 · not comparableMercurynone0/10Mercury's AI document-reading is limited to bills for bill-pay (auto-populating bill details) and receipt auto-attach; there is no evidence of parsing vendor contracts or auto-populating procurement request forms, which is a distinct workflow not covered in any docs, API, or MCP tool inventory.
- [claimed-docs] “AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
- [claimed-docs] “Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
- [probe] “PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getA…”
ai-native userHave booked travel rates automatically monitored and rebooked when prices drop
weight 1 · not comparableMercuryn/aMercury is a business banking/finance platform (cards, payments, invoicing, treasury); travel booking and travel-rate monitoring/rebooking is entirely outside its product category, not a banking feature.
ai-native userRead the product's source under an open license
weight 2 · not comparableMercuryn/aMercury is a proprietary banking/fintech product, not open-source software; the question of reading its source under an open license is a category error for this type of product (a bank platform), not an applicable openness axis.
ai-native userSelf-host the core product
weight 3 · not comparableMercuryn/aMercury is a hosted banking/fintech SaaS platform (accounts, cards, payments, API/MCP access to a regulated financial service); self-hosting the 'core product' is a category error since banking infrastructure cannot be run by customers themselves — this axis does not apply to this kind of product.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableMercurynone0/10No evidence anywhere in the pack addresses data residency, regional storage options, or geographic control over where account/API/MCP data is stored; Mercury's docs, API, and MCP materials are silent on this axis despite it being a fair question for a financial data platform serving international customers. Missing for 10: any mention of data region selection, residency guarantees, or geo-specific storage/compliance options.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableMercuryn/aMercury is a business banking/API platform, not an AI model provider or consumer content service that trains models on user data — the 'prevent my data from being used to train AI models' privacy axis doesn't apply to this category of product.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableMercuryn/aMercury is a banking/fintech platform, not an AI tool that itself collects/transmits telemetry about a user's usage of the product—no evidence pack item addresses telemetry opt-out and this axis is a mismatch for a financial services product's evidence.