Mercury vs Relay

Close automation

1. ai-native userUse AI automations to close my books faster each month

   weight 2 · round to Mercury
   Mercury✓fullclaimed7/10

   Mercury 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”

   proof ↗⚑ flag

   Relay—none0/10

   Relay offers rule-based automation (auto-transfers, categorization, sync to QuickBooks/Xero) but there is no evidence of AI-driven automation specifically aimed at closing the books faster—no mention of AI reconciliation, AI-assisted month-end close, or similar. missing for 10: any AI-specific book-closing automation, evidence of month-end close acceleration, AI-powered reconciliation or reporting features.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [claimed-docs] “Use Plaid to securely connect Relay to your other money apps like Expensify.”

   proof ↗⚑ flag

2. ai-native userHave AI automatically assign GL codes to transactions across entities to accelerate close

   weight 3 · round to Mercury
   Mercury~partialclaimed3/10

   Mercury'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; …”

   proof ↗⚑ flag

   Relay—none0/10

   Relay is a business banking platform whose evidence shows expense categorization and syncing to QuickBooks/Xero, but no mention of AI-driven GL code assignment across entities or multi-entity close acceleration. Missing for 10: any AI-based GL coding feature, multi-entity support, or close-acceleration workflow.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”

   proof ↗⚑ flag

Developer accounting access

1. developerView and manage accounting data through a dedicated API

   weight 1 · round to Mercury
   Mercury✓fullprobed9/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay—none0/10

   Evidence shows Relay syncing transaction data into QuickBooks/Xero and Plaid-based app connections, but there is no mention of a developer-facing API to view or manage accounting data programmatically. Missing for 10: any public API docs, endpoints, authentication, or SDK for accounting data access.

   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [claimed-docs] “Use Plaid to securely connect Relay to your other money apps like Expensify.”

   proof ↗⚑ flag

Erp sync

1. finance-leadSync transactions and expenses automatically with my accounting software

   weight 3 · round to Relay
   Mercury~partialclaimed6/10

   Mercury 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; …”

   proof ↗⚑ flag

   Relay✓fullclaimed7/10

   Relay's docs explicitly describe receipt capture, real-time categorization, and automatic syncing to accounting software (relay-docs-3), plus named integrations with QuickBooks Online and Xero for detailed transaction sync (relay-docs-19) and Plaid-based connections to apps like Expensify (relay-docs-20). Missing for 10: independent/hands-on verification of the accounting sync quality and no detail on reconciliation accuracy or setup friction reported by users.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [claimed-docs] “Use Plaid to securely connect Relay to your other money apps like Expensify.”

   proof ↗⚑ flag

2. finance-leadRely on real-time bidirectional sync with my ERP instead of manual journal entries

   weight 3 · round drawn
   Mercury~partialclaimed4/10

   Mercury 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.”

   proof ↗⚑ flag

   Relay~partialclaimed4/10

   Relay documents syncing transaction data into QuickBooks Online and Xero (relay-docs-19) and categorizing expenses in real time (relay-docs-3), which reduces manual entry, but this is one-way transaction sync into small-business accounting software, not bidirectional sync with an ERP system replacing journal entries. Missing for 10: evidence of true ERP (e.g., NetSuite/SAP) integration, bidirectional sync (journal entries flowing back), and any independent confirmation of 'real-time' accuracy beyond marketing copy.

   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Use Plaid to securely connect Relay to your other money apps like Expensify.”

   proof ↗⚑ flag

Account structure

1. finance-leadView account and routing numbers and generate a bank verification letter anytime

   weight 1 · round to Relay
   Mercury—none0/10

   The 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.

   ⚑ flag

   Relay✓fullclaimed8/10

   Relay's own support docs explicitly state that account/routing numbers can be viewed anytime under Accounts → Account Details, and a bank verification letter can be generated from the same screen, directly matching the story. Missing for 10: independent/hands-on community confirmation of this specific feature and detail on letter format/turnaround time.

   • [claimed-docs] “Go to Accounts → Account Details in the Relay app to view your numbers anytime, or generate a bank verification letter from the same screen.”

   proof ↗⚑ flag

2. finance-leadOpen multiple checking sub-accounts and auto-allocate incoming deposits across them

   weight 2 · round to Relay
   Mercury✓fullcommunity7/10

   A 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…”

   proof ↗⚑ flag

   Relay✓fullprobed8/10

   Relay's docs clearly support opening up to 20 checking sub-accounts (including Profit-First style nicknaming) and automating transfers across them by dollar amount or percentage, and community evidence corroborates the auto-partitioning behavior in practice. missing for 10: independent verification of allocation reliability/edge cases (e.g., failed or delayed auto-transfers) and more detail on configuring percentage-based rules beyond marketing copy.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Open up to 20 checking accounts and nickname them to match your Profit First setup: Income, Profit, Owner's Pay, Taxes, Operating Expenses.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://support.relayfi.com/llms.txt # Relay > Relay is an online business banking platform for small businesse…”

   proof ↗⚑ flag

Bill pay

1. ai-native userHave AI read incoming bills and auto-populate payment details for my review

   weight 3 · round to Mercury
   Mercury~partialprobed6/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay—none0/10

   Evidence shows bill upload, delegation, and approval automation (relay-docs-4) but nothing about AI reading bill contents to extract payment details for review — no OCR/AI-parsing capability is documented anywhere in the pack.

   ⚑ flag

2. finance-leadUpload bills and route them through an approval workflow before paying vendors

   weight 3 · round to Relay
   Mercury~partialprobed7/10

   Mercury'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…”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Relay's docs directly support bill upload and vendor payment with approval workflows: relay-docs-4 explicitly states 'Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid,' and relay-docs-17 confirms 'Multi-step approval rules' as a product feature, matching the persona's need to route bills through approvals before paying vendors. Community evidence (relay-comm-1) corroborates that Relay handles money partitioning and payments, though notes manual execution steps for external payments. Missing for 10: independent hands-on review of the bill-approval workflow specifically (most community evidence focuses on account partitioning/cards rather than AP approval routing), and no detail on how many approval steps/roles are configurable.

   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Multi-step approval rules”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

3. finance-leadSet up approval permissions so designated teammates can approve and send payments with one click

   weight 2 · round to Mercury
   Mercury✓fullcommunity8/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay~partialcommunity6/10

   Relay docs mention 'automate approvals' and 'define roles' for teammates, and pricing page lists 'Multi-step approval rules' as a feature, supporting configurable approval permissions for payments. However, there's no detailed documentation on the one-click approve/send UX for designated approvers, and community reviews note some users experienced 'issues with permissions,' suggesting occasional friction. Missing for 10: explicit description of one-click approve/send workflow, detailed permission granularity (e.g., approval thresholds per teammate), and hands-on confirmation the feature works smoothly.

   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Multi-step approval rules”
   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

4. ai-native userHave vendor invoices automatically matched to purchase orders, coded, and routed for payment

   weight 2 · round to Mercury
   Mercury~partialclaimed4/10

   Mercury'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.”

   proof ↗⚑ flag

   Relay—none0/10

   Relay's evidence shows bill upload, approval routing, and vendor payment (relay-docs-4, relay-docs-17), but nothing about matching invoices to purchase orders or automated GL/expense coding tied to POs — a specific three-way-match AP capability that is absent from all docs and community sources.

   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Multi-step approval rules”

   proof ↗⚑ flag

Invoicing

1. finance-leadHave overdue invoices automatically followed up on without manual chasing

   weight 1 · round to Relay
   Mercury—none0/10

   Mercury 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”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay's own marketing states invoicing lets you 'request payments... and let Relay handle the follow-up' and supports recurring invoices, directly claiming automated dunning for overdue invoices. However there's no detail on how follow-up scheduling/reminders work, no support-doc walkthrough, and no independent/community corroboration that this feature works as described in practice. missing for 10: detailed documentation of follow-up cadence/rules, hands-on or community validation of automated chasing actually reducing manual work.

   • [claimed-docs] “Create invoices, request payments, offer flexible payment options, and let Relay handle the follow-up.”
   • [claimed-docs] “Build and send a branded invoice with built-in payment collection from Invoices — no separate tool needed.”
   • [claimed-docs] “Recurring invoices”

   proof ↗⚑ flag

2. finance-leadCreate and send branded invoices with built-in payment collection

   weight 2 · round to Relay
   Mercury✓fullclaimed7/10

   Mercury 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”

   proof ↗⚑ flag

   Relay✓fullclaimed8/10

   Relay's docs explicitly describe building and sending branded invoices with built-in payment collection ('no separate tool needed'), plus flexible payment options, automated follow-up, and recurring invoices as a feature tier. Missing for 10: independent/hands-on community corroboration of invoicing feature usage and details on branding customization depth.

   • [claimed-docs] “Create invoices, request payments, offer flexible payment options, and let Relay handle the follow-up.”
   • [claimed-docs] “Build and send a branded invoice with built-in payment collection from Invoices — no separate tool needed.”
   • [claimed-docs] “Recurring invoices”

   proof ↗⚑ flag

Money movement

1. founderSend money abroad that arrives in under a minute

   weight 2 · round drawn
   Mercury—none0/10

   Mercury 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”

   proof ↗⚑ flag

   Relay—none0/10

   Evidence shows Relay wires (domestic and international) can send 'same-day' at best, and ACH takes 1-3 business days — nothing supports transfers arriving in under a minute. The axis applies since cross-border payments are a core banking feature, but no evidence of near-instant delivery exists.

   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [community] “Relay's international transfer system is incredibly easy to use. Pricing is straightforward - although not exactly affordable at $10 per out…”

   proof ↗⚑ flag

2. finance-leadSend domestic ACH and wire payments to vendors

   weight 3 · round to Relay
   Mercury✓fullcommunity7/10

   Mercury'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…”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Relay's docs explicitly describe paying vendors via ACH and wire, with delivery estimates (1-3 days ACH, same-day wires), bill upload/approval workflows, and limit management, and community evidence confirms these payments work in practice (with the caveat that execution is manual, not autonomous). Pricing tiers also confirm faster ACH is available on Pro plan. Missing for 10: independent hands-on verification of wire payment success/reliability at scale, more detail on wire fees/limits.

   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”
   • [claimed-docs] “Check your current limits under Accounts → Limits, then request an increase right from that screen.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”
   • [community] “Relay's basic plan is entirely free, at $0/month... if your business needs faster, same-day ACH and more advanced billing features, then the…”

   proof ↗⚑ flag

3. finance-leadSend international payments in local currencies with transparent fees

   weight 3 · round to Relay
   Mercury—none0/10

   Mercury'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”

   proof ↗⚑ flag

   Relay~partialcommunity4/10

   Relay supports sending and receiving international wires (docs-9, docs-23) with a clear $10 fee disclosed and waived on Pro plan (relay-comm-5), giving some fee transparency, but there is no evidence of actual local-currency disbursement, FX rate handling, or multi-currency accounts — wires appear to be standard bank wires, not localized payouts. Missing for 10: local currency payment execution, FX rate transparency, multi-currency support evidence, independent confirmation of international payment reliability.

   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [community] “Relay's international transfer system is incredibly easy to use. Pricing is straightforward - although not exactly affordable at $10 per out…”

   proof ↗⚑ flag

Multi currency

1. founderHold and manage balances in multiple currencies from one account

   weight 2 · round drawn
   Mercury—none0/10

   Evidence 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”

   proof ↗⚑ flag

   Relay—none0/10

   Relay's evidence describes opening up to 20 checking accounts and receiving/sending international wires, but all of these appear to be USD sub-accounts for organizing cash, not accounts that hold balances in multiple currencies (e.g., EUR, GBP) simultaneously. No evidence pack item describes multi-currency balance holding or FX conversion features.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Open up to 20 checking accounts and nickname them to match your Profit First setup: Income, Profit, Owner's Pay, Taxes, Operating Expenses.”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [community] “Relay's international transfer system is incredibly easy to use. Pricing is straightforward - although not exactly affordable at $10 per out…”

   proof ↗⚑ flag

2. founderReceive payments using local account details in multiple currencies

   weight 2 · round drawn
   Mercury—none0/10

   Evidence 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”

   proof ↗⚑ flag

   Relay—none0/10

   Evidence shows Relay is a US business banking platform offering USD checking accounts and the ability to receive international wires into those accounts (relay-docs-13, relay-docs-23), but there is no evidence of local account details (e.g., IBAN/sort code equivalents) issued in multiple currencies for receiving payments locally in each currency, which is what this story requires.

   • [claimed-docs] “Deposit ACH transfers, wires, checks, cash and payouts from payment processors like PayPal, Stripe, Square and more.”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”

   proof ↗⚑ flag

Operational efficiency

1. finance-leadSearch across all transactions, vendors, and cards from one universal search bar and jump straight into initiating a payment

   weight 1 · round to Mercury
   Mercury✓fullclaimed7/10

   Mercury'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.”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence in the pack mentions a universal/global search bar that spans transactions, vendors, and cards, nor any workflow for jumping from search results into initiating a payment; the docs describe discrete screens (Accounts, Cards, Invoices, Limits) rather than a unified search experience. missing for 10: any mention of a search feature, cross-entity search UI, or search-to-payment flow.

   ⚑ flag

Payment transparency

1. finance-leadSee the exact delivery estimate for an ACH or wire transfer before confirming it

   weight 2 · round to Relay
   Mercury—none0/10

   The 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.

   ⚑ flag

   Relay✓fullclaimed8/10

   relay-docs-9 explicitly states ACH takes 1–3 business days, wires can send same-day, and that users see the exact delivery estimate before confirming a transfer — directly matching the story. Missing for 10: independent/hands-on confirmation (e.g. screenshot or user report) of the pre-confirmation estimate UI beyond first-party support docs.

   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Mercury
   Mercury✓fullprobed8/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay✓fullprobed7/10

   There is direct probe evidence that Relay's support site serves a working llms.txt file at https://support.relayfi.com/llms.txt returning HTTP 200 with structured content describing the product, confirming an agent-oriented docs endpoint exists. Missing for 10: no evidence of broader agent-oriented documentation beyond this single file, no confirmation it covers full product surface, and no independent/community corroboration of agents actually using it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://support.relayfi.com/llms.txt # Relay > Relay is an online business banking platform for small businesse…”

   proof ↗⚑ flag

2. ai-native userDrive the product through a documented public API

   weight 3 · round to Mercury
   Mercury✓fullprobed9/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence of a documented public API for programmatic/agentic access; all evidence pertains to the banking product's manual UI features, integrations via Plaid/QuickBooks, and support docs, not an API for driving Relay programmatically. missing for 10: public API docs, authentication/reference, SDKs, or any mention of API endpoints.

   ⚑ flag

3. ai-native userSubscribe to events via webhooks

   weight 2 · round to Mercury
   Mercury✓fullprobed7/10

   Mercury'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…”

   proof ↗⚑ flag

   Relay—none0/10

   Relay is a business banking platform; no evidence anywhere in the pack mentions webhooks, event subscriptions, or any API-based notification system for developers/agents. Missing for 10: any webhook documentation, event types, subscription/callback mechanism, or API reference.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Mercury
   Mercury~partialprobed5/10

   Mercury 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\`”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence in the pack mentions AI-generated insights, suggestions, forecasting, or any AI/ML-driven analysis within Relay; all listed features are manual banking, transfer, invoicing, and card-management tools. missing for 10: any mention of AI-powered insights, anomaly detection, spend suggestions, or predictive analytics, first-party or independent corroboration of such a feature.

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Mercury~partialprobed5/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay offers rule-based automations that run without manual intervention — auto-transfers on deposit, percentage/dollar-based multi-account splits, multi-step approval rules, and recurring invoices (relay-docs-1, relay-docs-6, relay-docs-15, relay-docs-17, relay-docs-18) — which qualifies as background automation. However this is traditional banking rule automation, not AI/agent-driven decisioning, and community evidence notes manual execution is still required for many external payments (relay-comm-1). Missing for 10: any AI/LLM-based autonomous decision-making, agent-triggered actions, or evidence of automations beyond simple scheduled/rule-based transfers.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Multi-step approval rules”
   • [claimed-docs] “Recurring invoices”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Mercury
   Mercury~partialprobed7/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay—none0/10

   Relay is a business banking platform with a standard app UI; the evidence pack shows only manual navigation flows (menus, screens like Accounts → Limits) and no natural-language command interface, chatbot, or agentic control surface. There is an llms.txt file which suggests machine-readability but not that end users can operate the product via natural language. Missing for 10: any evidence of a natural-language interface, chat-based commands, or AI assistant for operating the account.

   • [probe] “PROBE llms.txt: HTTP 200 at https://support.relayfi.com/llms.txt # Relay > Relay is an online business banking platform for small businesse…”
   • [claimed-docs] “Go to Accounts → Account Details in the Relay app to view your numbers anytime, or generate a bank verification letter from the same screen.”
   • [claimed-docs] “Check your current limits under Accounts → Limits, then request an increase right from that screen.”

   proof ↗⚑ flag

Api quality

1. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Mercury
   Mercury!disputedcontradicted4/10

   Mercury'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…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence of an OpenAPI/Swagger spec or any machine-readable API documentation; evidence only covers banking features, support articles, and an llms.txt file (which is not an API spec).

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Mercury
   Mercury~partialprobed6/10

   Mercury 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 …”

   proof ↗⚑ flag

   Relay~partialclaimed4/10

   Relay offers some bulk-style automation — auto-transferring funds across up to 20 accounts, issuing up to 50 cards, multi-step approval rules, and bulk vendor bill uploads — but these are manual UI-driven configurations rather than a programmatic/bulk-API interface an AI-native user could drive across many items at once. Missing for 10: evidence of an API or agent-facing bulk operation endpoint, batch transaction processing, or CSV/bulk import-export capability confirmed by independent testing.

   • [claimed-docs] “Open up to 20 checking accounts and nickname them to match your Profit First setup: Income, Profit, Owner's Pay, Taxes, Operating Expenses.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Issue 50 virtual or physical Visa debit cards to your team”
   • [claimed-docs] “Multi-step approval rules”
   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Mercury~partialprobed5/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay supports rule-based automation for money movement — auto-transferring deposits across accounts, percentage/dollar-based automated transfers, and multi-step approval rules — which satisfies a narrow slice of 'define rules that trigger actions on events.' However, these are fixed banking-specific triggers (deposits, thresholds, approvals) rather than a general-purpose, AI-native event/action framework (no webhooks, API-triggered rules, or custom event definitions are evidenced). Missing for 10: evidence of programmable/custom event triggers via API or webhooks, broader condition-action rule builder beyond transfers/approvals, and any AI-agent-facing automation interface.

   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Multi-step approval rules”
   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Relay
   Mercury~partialprobed3/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay~partialclaimed4/10

   Relay supports recurring financial automations like scheduled/percentage-based account transfers, recurring invoices, and automated approval rules, which count as recurring workflow scheduling within its banking domain. However there's no evidence of a general-purpose job/workflow scheduler, API/webhook triggers, or any AI-native automation surface for arbitrary tasks. Missing for 10: API-based scheduling, arbitrary workflow/job automation beyond money movement, AI-agent-facing scheduling interface.

   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Recurring invoices”
   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Multi-step approval rules”

   proof ↗⚑ flag

Card controls

1. finance-leadSet department or program budgets with automatically enforced spend limits

   weight 2 · round to Mercury
   Mercury~partialclaimed6/10

   Mercury 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.”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay lets admins issue cards with set spend limits, define roles, and separate funds into up to 20 checking accounts (useful as informal department/program buckets) with automated transfer rules, and 'multi-step approval rules' are mentioned on the pricing page. However there's no explicit 'budget' object with rolling caps per department/program beyond individual card limits, and community reviews note 'problems with prescribed limits,' suggesting enforcement isn't perfectly reliable. Missing for 10: a dedicated budget-creation feature (vs just card limits/accounts), documented department-level aggregate spend caps, and clear evidence enforcement is robust in practice.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Multi-step approval rules”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”
   • [community] “For Relay's physical cards, there is a maximum daily card transaction limit of $7,000 and an ATM withdrawal limit of $1,000 per card.”

   proof ↗⚑ flag

2. finance-leadSet per-card spend limits and granular controls for each employee

   weight 3 · round to Mercury
   Mercury✓fullcommunity8/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay~partialcommunity7/10

   Relay's docs confirm card issuance with spend limits, role definitions, real-time transaction tracking, and multi-step approval rules (relay-docs-2, relay-docs-16, relay-docs-17), directly supporting granular per-card controls for employees. However, community reviews note occasional 'problems with prescribed limits' and permission glitches (relay-comm-2), and hard caps like a $7,000 daily card limit (relay-comm-4) suggest some inflexibility. Missing for 10: deeper documentation on category/merchant-level restrictions, audit trails for limit changes, and independent confirmation that granular controls work flawlessly at scale.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Issue 50 virtual or physical Visa debit cards to your team”
   • [claimed-docs] “Multi-step approval rules”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”
   • [community] “For Relay's physical cards, there is a maximum daily card transaction limit of $7,000 and an ATM withdrawal limit of $1,000 per card.”

   proof ↗⚑ flag

3. finance-leadInstantly freeze a lost or stolen card and order a replacement

   weight 2 · round to Relay
   Mercury~partialclaimed3/10

   Mercury 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.”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   relay-docs-8 directly documents freezing a card instantly in-app and ordering a replacement (5–7 business days), matching the story exactly, with community reviews (relay-comm-2) corroborating a functional, user-friendly card management experience. Missing for 10: independent hands-on confirmation specifically of the freeze/replace flow (vs general app usability).

   • [claimed-docs] “Open Cards in the app to freeze it instantly and order a replacement — it typically arrives in 5–7 business days.”
   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

4. finance-leadRequest a transaction limit increase directly from a self-service screen

   weight 1 · round to Relay
   Mercury~partialclaimed4/10

   Mercury 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.”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   First-party support docs explicitly describe a self-service flow: view current limits under Accounts → Limits and request an increase directly from that screen, with related help articles confirming the limits view. This matches the finance-lead story closely. Missing for 10: independent/hands-on confirmation that limit-increase requests are actually approved smoothly (one community review vaguely mentions 'problems with prescribed limits'), and no explicit persona-specific (finance-lead role) detail.

   • [claimed-docs] “Check your current limits under Accounts → Limits, then request an increase right from that screen.”
   • [claimed-docs] “How to View Your Account Limits in Relay”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

Card issuance

1. finance-leadInstantly create virtual cards scoped to a specific purpose like ad spend or a single vendor

   weight 3 · round to Mercury
   Mercury✓fullcommunity8/10

   Mercury'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…”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay supports issuing multiple virtual/physical Visa cards with spend limits and role-based controls (relay-docs-2, relay-docs-16), which enables purpose-scoped cards for things like a vendor or ad spend, but there's no evidence of instant creation flows, per-card vendor/merchant-locking, or category-specific restrictions tailored to 'ad spend' style use cases. missing for 10: evidence of instant/quick card issuance UX, vendor-lock or merchant-category restriction features, and independent confirmation of ease/speed of scoped card creation.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Issue 50 virtual or physical Visa debit cards to your team”
   • [claimed-docs] “Check your current limits under Accounts → Limits, then request an increase right from that screen.”

   proof ↗⚑ flag

2. finance-leadIssue physical debit or credit cards to employees with defined roles

   weight 2 · round to Relay
   Mercury~partialcommunity6/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Docs explicitly state issuing Visa debit or credit cards with defined roles and spend limits, real-time tracking (relay-docs-2), physical/virtual card issuance up to 50 cards (relay-docs-16), and card freeze/replacement management (relay-docs-8). Community evidence corroborates card limits and permissions in practice (relay-comm-4, relay-comm-2). Missing for 10: independent hands-on verification of role-based permission granularity and credit card specifics beyond marketing copy.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Issue 50 virtual or physical Visa debit cards to your team”
   • [claimed-docs] “Open Cards in the app to freeze it instantly and order a replacement — it typically arrives in 5–7 business days.”
   • [community] “For Relay's physical cards, there is a maximum daily card transaction limit of $7,000 and an ATM withdrawal limit of $1,000 per card.”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

Card rewards

1. founderSpend and withdraw cash abroad on a company card without hidden foreign fees

   weight 1 · round drawn
   Mercury—none0/10

   The 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.

   ⚑ flag

   Relay—none0/10

   The evidence covers Relay's domestic checking, cards, invoicing, and international wire transfers (with a $10 fee), but nowhere states or documents that its Visa debit/credit cards have no foreign transaction fees or how cash withdrawals abroad are priced. This is a fair question for a business card product, but no first-party or community evidence confirms fee-free foreign card spend/withdrawal.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [community] “Relay's international transfer system is incredibly easy to use. Pricing is straightforward - although not exactly affordable at $10 per out…”

   proof ↗⚑ flag

2. founderEarn automatic cashback on card spend without manual redemption steps

   weight 2 · round to Mercury
   Mercury✓fullclaimed8/10

   Mercury 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.”

   proof ↗⚑ flag

   Relay—none0/10

   Evidence covers card issuance, spend limits, savings APY, and expense tracking, but nothing in the pack mentions cashback rewards on card spend at all. missing for 10: any mention of cashback program, rewards rate, or automatic redemption on Relay cards.

   ⚑ flag

Procurement automation

1. ai-native userHave vendor contracts parsed by AI to auto-populate procurement request forms

   weight 2 · round drawn
   Mercury—none0/10

   Mercury'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…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence anywhere in the pack of AI parsing vendor contracts or auto-populating procurement request forms; Relay's evidence covers banking, cards, invoicing, bill pay, and accounting sync but nothing about contract parsing or procurement workflows. missing for 10: any AI contract-parsing capability, any procurement request form feature, any evidence of document ingestion/AI extraction.

   ⚑ flag

Receipt management

1. ai-native userHave receipts automatically captured and coded the moment a card is used, without manual entry

   weight 3 · round to Mercury
   Mercury~partialclaimed6/10

   Mercury 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; …”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay's own docs state it can 'Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically' (relay-docs-3), directly matching the story, but there's no detail on the actual capture mechanism (e.g., automatic prompt at time of swipe vs. manual photo upload) and no independent or hands-on corroboration of this specific feature working seamlessly. Missing for 10: independent/community validation of the receipt-capture flow, technical detail on how capture is triggered at point-of-sale, and any evidence it truly requires zero manual entry.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”

   proof ↗⚑ flag

2. finance-leadHave receipts automatically attached to the right transaction by emailing or uploading them

   weight 2 · round to Mercury
   Mercury✓fullclaimed8/10

   Mercury'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; …”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay's marketing docs mention capturing receipts and categorizing expenses in real time with sync to accounting software, implying some auto-matching capability, but there is no evidence of an email-in receipt feature or detailed matching logic to specific transactions. missing for 10: explicit email-to-receipt ingestion method, confirmation that receipts are auto-matched to the correct transaction, and independent/hands-on verification of this workflow.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”

   proof ↗⚑ flag

Signup flow

1. founderCheck my account application status while it's under review

   weight 1 · round to Relay
   Mercury—none0/10

   Evidence 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…”

   proof ↗⚑ flag

   Relay✓fullclaimed7/10

   relay-docs-12 directly confirms founders can check application status anytime from the homepage during the 1-2 business day review period, with email notification on decision. missing for 10: no independent/community corroboration of the status-checking UX itself, and no detail on what status states are shown.

   • [claimed-docs] “Most applications are reviewed within 1–2 business days. You can check your status anytime from the homepage — we'll email you as soon as a …”

   proof ↗⚑ flag

Switching

1. founderReplace multiple point solutions for spend, bill pay, and banking with one consolidated platform

   weight 2 · round drawn
   Mercury✓fullcommunity8/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Relay documents an all-in-one platform combining multiple checking/savings accounts, cards with spend controls, bill pay with approvals, invoicing/receivables, receipt capture, and accounting sync (QuickBooks/Xero), directly replacing separate spend management, bill pay, and banking tools, and community reviews corroborate the multi-account and interest features in real use. missing for 10: independent case studies explicitly confirming founders consolidated away from other named point solutions, and more hands-on verification of bill pay/invoicing depth beyond docs and one HN mention.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Create invoices, request payments, offer flexible payment options, and let Relay handle the follow-up.”
   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

2. founderFully onboard onto a new banking platform in about a week instead of months

   weight 2 · round to Mercury
   Mercury~partialclaimed6/10

   Mercury 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.”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay shows a fast application review (1-2 business days per relay-docs-12) and easy setup of accounts, cards, and invoicing, suggesting quick onboarding, but there's no explicit evidence of an end-to-end 'week-long' onboarding timeline or migration process from another bank. missing for 10: documented full onboarding timeline/case study, evidence of migrating existing banking relationships/data within a week, independent confirmation of onboarding speed beyond application approval.

   • [claimed-docs] “Most applications are reviewed within 1–2 business days. You can check your status anytime from the homepage — we'll email you as soon as a …”
   • [claimed-docs] “Go to Accounts → Account Details in the Relay app to view your numbers anytime, or generate a bank verification letter from the same screen.”
   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Mercury
   Mercury~partialprobed7/10

   Mercury'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…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence pack item mentions a public API, developer platform, or programmatic access to Relay's banking features; all evidence describes UI/app-based workflows (mobile app, web app screens) with no API documentation or endpoints referenced.

   ⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Mercury
   Mercury~partialprobed5/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay—none0/10

   Relay is a business banking platform; nothing in the evidence pack mentions bulk data export in open formats (CSV/JSON/OFX) or account portability/closure workflows for users to 'leave' with their data. Accounting sync (relay-docs-3) implies data transfer to third-party software but is not documented as a user-controlled full data export/exit mechanism.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”

   proof ↗⚑ flag

Access control

1. finance-leadDefine granular user roles and permissions across team members, locations, and departments

   weight 3 · round drawn
   Mercury~partialclaimed5/10

   Mercury 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.”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay documents role definition, card-level spend limits, and multi-step approval rules (relay-docs-2, relay-docs-17), which supports basic team permissioning, but there's no evidence of granular controls segmented by location or department, nor detailed role-based access management. A community review also notes 'issues with permissions' as a minor complaint (relay-comm-2), suggesting the feature isn't fully robust in practice. Missing for 10: department/location-level permission scoping, audit trail of permission changes, and independent confirmation that role granularity works reliably at scale.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Multi-step approval rules”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

Fraud detection

1. ai-native userHave AI flag anomalous or out-of-policy transactions automatically for review

   weight 2 · round to Mercury
   Mercury~partialclaimed3/10

   The 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…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence in the pack mentions AI-driven anomaly detection, fraud monitoring, or automated flagging of out-of-policy transactions; Relay's documented features are manual controls like spend limits, roles, and multi-step approval rules, not AI-based review triggers.

   ⚑ flag

Customer support

1. founderReach live customer support at any time for urgent account issues

   weight 2 · round to Relay
   Mercury—none0/10

   The 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.

   ⚑ flag

   Relay~partialcommunity4/10

   Community reviews mention 'helpful customer support' generally, but no evidence specifies 24/7 or live/urgent support availability, response times, or channels (phone/chat). missing for 10: documentation of support hours/availability, urgent-issue escalation process, live-agent channel details, and independent verification of responsiveness during emergencies.

   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

Deposit protection

1. finance-leadHave deposits automatically swept across partner banks to maximize FDIC insurance coverage

   weight 2 · round drawn
   Mercury—none0/10

   Mercury 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.

   ⚑ flag

   Relay—none0/10

   Evidence shows Relay lets users open multiple checking accounts and automate internal transfers between them (Profit First style) and offers high-yield savings, but there is no mention of a multi-bank sweep network or expanded FDIC coverage across partner banks. missing for 10: any documentation of an FDIC sweep program, partner bank network, or expanded insurance coverage mechanism.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Open up to 20 checking accounts and nickname them to match your Profit First setup: Income, Profit, Owner's Pay, Taxes, Operating Expenses.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”

   proof ↗⚑ flag

Cash automation

1. finance-leadAutomate cash management with auto top-up between accounts and low-balance alerts

   weight 2 · round to Relay
   Mercury~partialcommunity4/10

   A 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”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay supports automated transfer rules between accounts by dollar amount or percentage (relay-docs-15) and cash-cushion/high-yield savings automation (relay-docs-6, relay-docs-24), corroborated by a community report of automatic money partitioning (relay-comm-1). However, there is no evidence of a specific 'low-balance alert' notification feature or threshold-triggered auto top-up logic. Missing for 10: explicit low-balance alert/notification capability, confirmation that transfers can be triggered by balance thresholds rather than just fixed schedules/percentages, independent verification of alerting reliability.

   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

Yield generation

1. finance-leadEarn yield on operating cash balances without moving funds to a separate institution

   weight 3 · round drawn
   Mercury✓fullclaimed7/10

   Mercury 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”

   proof ↗⚑ flag

   Relay✓fullcommunity7/10

   Relay offers built-in high-yield savings accounts (up to 3.00% APY) that automatically pull idle operating cash into yield-bearing accounts within the same platform, and community evidence corroborates that tax/reserve balances earn extra interest without moving funds elsewhere. missing for 10: independent verification of actual APY competitiveness/consistency over time, and clearer detail on withdrawal friction or limits on savings-account access for operating cash.

   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

2. finance-leadBuild a cash cushion in a high-yield savings sub-account with automated transfer rules

   weight 2 · round to Relay
   Mercury~partialcommunity6/10

   Mercury 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…”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Relay explicitly offers high-yield savings accounts (up to 3.00% APY) plus automated rules to move idle cash from operating accounts into savings, directly matching the story, and community evidence corroborates automated partitioning with interest earned on set-aside funds. Missing for 10: independent verification of actual APY rates achieved and hands-on testing of the automation rule reliability specifically for savings sweeps.

   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

3. founderEarn interest on balances held in multiple currencies

   weight 1 · round drawn
   Mercury—none0/10

   Evidence 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”

   proof ↗⚑ flag

   Relay—none0/10

   Relay's evidence shows only USD-based high-yield savings (up to 3.00% APY) and international wire transfers, but no support for holding balances in multiple currencies or earning interest on non-USD balances. Missing for 10: multi-currency account support, evidence of interest-bearing balances in currencies other than USD.

   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”

   proof ↗⚑ flag