Wave vs Mercury Books

Agent access

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

   weight 2 · round to Mercury Books
   Wave—none0/10

   A direct probe found no llms.txt file (404) and no agent-oriented docs surface; Wave's marketing pages contain no mention of llms.txt or agent-consumable documentation, and its developer portal is blocked to crawlers.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books!disputedcontradicted2/10

   Mercury's blog promises a future MCP layer for agents, but direct probes show no llms.txt file (404) and no discoverable OpenAPI/agent-oriented docs at any candidate path, meaning there is currently nothing an agent could be pointed at. Missing for 10: a live llms.txt or agent-readable docs file, a shipped API/MCP endpoint, any evidence of the promised MCP layer actually existing.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS with no evidence of a CLI, headless mode, or CI-friendly automation surface; llms.txt and OpenAPI probes both 404, and the developer/API portal is walled off with no documented programmatic interface. Nothing suggests Wave can be run headlessly or scripted in a CI pipeline.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Mercury explicitly frames a full API and MCP layer as a future roadmap item ('Soon...'), and direct probes for API/OpenAPI/llms.txt endpoints all returned 404s, confirming no headless/CI-usable interface exists today. Command is a plain-language, in-app assistant, not a scriptable or automatable interface.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Wave—none0/10

   Wave is small-business accounting/invoicing SaaS; no evidence of an MCP server or ability to plug MCP tools in. llms.txt and OpenAPI probes both 404, and the developer portal is inaccessible/undocumented on public pages, so the applicable axis (as a SaaS product could plausibly expose an MCP integration) has no supporting evidence.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   The only MCP-related evidence is a forward-looking statement that an MCP layer is coming 'soon' to let external agents call Mercury Books' own actions — this describes Mercury exposing an MCP server, not the product consuming external MCP servers' tools, and it is explicitly not yet shipped (confirmed by 404 probes for API/openapi endpoints). There is no evidence users can plug third-party MCP servers into Mercury Books today.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Wave—none0/10

   Wave is an accounting SaaS product, so an official MCP server is a plausible axis, but there is no evidence of any MCP server, API docs accessible, or agent integration; probes for llms.txt and OpenAPI both 404, and the developer portal is walled off from crawling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Mercury only states that an MCP layer is coming 'soon' for AI agents, with no evidence it currently exists; probes for API/OpenAPI/llms.txt endpoints all return 404s, confirming no official MCP server is live today.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Wave—none0/10

   No evidence of any official CLI for Wave; probes for llms.txt and API docs both 404/403, and marketing pages document no CLI, API, or agent tooling surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence of a CLI; only future-planned API/MCP layer is mentioned, and probes for llms.txt/openapi endpoints returned 404s, indicating no current programmatic or CLI tooling exists.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Wave—none0/10

   Marketing pages document no public API, and direct probes for llms.txt/OpenAPI both 404; the developer portal exists but is blocked to crawlers so no documented, accessible API surface is evidenced.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Mercury explicitly says a full accounting API and MCP layer are coming 'soon,' not currently available, and direct probes for llms.txt and OpenAPI docs both returned 404s, confirming no public API exists today.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Wave—none0/10

   No evidence of any API credential system, scoped tokens, or agent-oriented access controls; Wave's role-based access is for human collaborators (admin/editor/viewer), and its developer/API portal could not even be crawled to confirm any credentialing mechanism exists.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Evidence only mentions a future accounting API and MCP layer as 'soon' (not yet shipped), with no mention of API keys, OAuth scopes, or least-privilege credential issuance; probes confirm no OpenAPI/spec or docs endpoints currently exist. There is no evidence Mercury Books lets a user issue scoped credentials for an agent today.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Wave—none0/10

   No evidence of official SDKs for AI-native/programmatic use; llms.txt and OpenAPI probes both 404, and the developer/GraphQL API portal is walled off from crawling with no documentation surfaced. Marketing pages describe only end-user accounting features, not SDKs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Mercury explicitly frames the accounting API and MCP layer as future ('Soon'), and probes confirm no live OpenAPI/llms.txt endpoints exist yet — there is no official SDK currently available to build against.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Wave—none0/10

   No evidence of webhook support anywhere in Wave's marketing pages or developer portal; the developer portal itself couldn't be crawled and is described as documenting no webhook surface, and llms.txt/openapi probes both returned 404.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence pack item mentions webhooks or event subscriptions; the only programmatic-access claim is a forward-looking 'soon' API/MCP mention, and probes confirm no public API/openapi spec exists yet. Missing for 10: any webhook documentation, event types, or subscription mechanism.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Mercury Books
   Wave—none0/10

   Evidence shows OCR data extraction and automation (auto-categorize, reminders) but no AI-generated insights, analysis, or suggestions surfaced to users; reports are static comparisons, not AI-driven recommendations. No mention of AI/ML-based insight generation anywhere in the pack.

   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

   Mercury Books✓fullclaimed7/10

   Mercury Command lets users ask natural-language questions about their financial data and get AI-grounded answers, plus AI-driven GL code suggestions and categorization, directly inside Books. missing for 10: independent/hands-on verification of insight quality, no detail on proactive suggestion generation beyond categorization/GL coding, and Mercury's own caveat that automation is not full autopilot.

   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”
   • [claimed-docs] “Ask Mercury Command a question about your books, or hand off a bookkeeping task to it directly, in plain language.”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”

   proof ↗⚑ flag

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

   weight 2 · round to Mercury Books
   Wave~partialprobed4/10

   Wave ships several fixed, always-on background automations (auto bank import/categorization, recurring invoices with auto payment reminders, auto payroll tax filing) that run without manual triggering, per wave-docs-2, wave-docs-5, wave-docs-10, wave-docs-14. However these are hard-coded product features, not a general-purpose automation/agent framework the user can configure, and there is no API, webhook, or MCP surface documented for building custom autonomous workflows (wave-probe-1, wave-probe-2, wave-supp-dev-portal-wall). Missing for 10: a configurable automation builder, any AI-agent/orchestration capability, and a documented API/webhook layer for extending automations.

   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books~partialclaimed5/10

   Mercury Books documents continuous, automatic categorization/reconciliation and a Command assistant that can be handed bookkeeping tasks in plain language (bulk GL coding, categorization rules), which is real background automation. However, the vendor itself explicitly cautions that 'a connected system isn't the same as fully automated' and that it should not be treated as 'putting your books on autopilot,' and the promised MCP/agent layer for end-to-end autonomous handling is described as 'soon,' not shipped. Missing for 10: a live, user-configurable autonomous automation/agent layer (MCP) with independent confirmation it runs unattended in production.

   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Mercury Books
   Wave—none0/10

   No evidence anywhere in the pack of a built-in AI assistant or agentic feature; Wave's docs describe automation (auto-import, OCR, reminders) but nothing about delegating tasks to an AI assistant, and the developer portal is inaccessible with no API/AI mention on marketing pages.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”

   proof ↗⚑ flag

   Mercury Books✓fullclaimed7/10

   Mercury Books ships a built-in AI assistant called Command that users can query in plain language and delegate bookkeeping tasks to (journal entries, chart of accounts organization, bulk categorization), described as 'AI built-in, not bolted on.' Missing for 10: independent/hands-on verification of Command's task-delegation reliability, and the vendor's own caveat that automation isn't 'autopilot' tempers full agentic delegation claims.

   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Ask Mercury Command a question about your books, or hand off a bookkeeping task to it directly, in plain language.”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”

   proof ↗⚑ flag

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

   weight 2 · round to Mercury Books
   Wave—none0/10

   No evidence of any natural-language command interface, chat assistant, or AI-native control surface; Wave's marketing pages describe only manual UI-based accounting/invoicing features, and probes for llms.txt/openapi found nothing, with the developer portal walled off from crawling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books✓fullclaimed7/10

   Mercury Command lets users ask questions and hand off bookkeeping tasks 'in plain language,' directly matching the natural-language command story, and this is documented across multiple first-party sources describing bulk actions, categorization, and Q&A. Missing for 10: independent/hands-on verification of Command's NL capabilities and confirmation that the broader agent-facing API/MCP layer (still described as 'soon') doesn't gate deeper command coverage.

   • [claimed-docs] “Ask Mercury Command a question about your books, or hand off a bookkeeping task to it directly, in plain language.”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Wave—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes for openapi/llms.txt returned 404s, and the developer portal itself is blocked from crawling with no documented API surface accessible.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   There is no evidence of any interactive API reference or runnable examples; the API is described only as 'soon' coming, and probes for openapi/llms.txt specs both returned 404s, indicating no public API docs exist yet.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Wave—none0/10

   Direct probes for OpenAPI/swagger specs and llms.txt returned 404s, and Wave's developer portal (GraphQL API) is blocked to crawlers with no machine-readable spec surfaced; marketing pages document no API spec at all.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Direct probes for llms.txt and OpenAPI/Swagger spec files all return 404, and docs only mention a future accounting API/MCP layer as an upcoming feature, not something currently downloadable. No machine-readable API spec exists today.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Wave—none0/10

   No evidence of any sandbox, staging, test-mode, or dev environment for Wave; the developer portal is inaccessible and marketing pages document no API/test environment for isolating data from production.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence of any sandbox, staging, or test environment for Mercury Books; the API/MCP layer is described only as forthcoming with no mention of a non-production mode, and probes for docs/OpenAPI endpoints returned 404s.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Wave—none0/10

   No evidence of versioned APIs or a documented deprecation policy; the developer/API portal is inaccessible for crawling and Wave's public marketing pages document no API surface at all, with llms.txt and OpenAPI probes both returning 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   The API is described as forthcoming ('Soon, a full accounting API will make every core Books action available programmatically'), and direct probes for openapi/llms.txt specs return 404s, showing no versioned API or deprecation policy currently exists.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

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

   weight 2 · round to Mercury Books
   Wave~partialprobed2/10

   Wave documents a narrow bulk feature (uploading up to 10 receipts at once with OCR), but there is no evidence of broader bulk operations (e.g., bulk invoice creation/edits, bulk transaction updates) or any API/CLI/MCP surface an AI-native user could script against — the developer portal is crawl-walled and no OpenAPI/llms.txt exists. missing for 10: bulk invoice/transaction/customer operations, programmatic API or CLI access for scripted bulk actions, evidence beyond the 10-item receipt cap.

   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books~partialprobed6/10

   Mercury Command explicitly supports bulk actions like bulk GL code assignment, categorization rules, and clearing categorization backlogs in bulk, which directly addresses bulk operations for an AI-native user. However, this is limited to bookkeeping/categorization tasks rather than a general-purpose bulk API, and the promised full accounting API/MCP layer for broader programmatic bulk actions is only 'coming soon,' with probes confirming no public API/OpenAPI spec exists yet. missing for 10: a live public API or MCP layer enabling arbitrary bulk operations, independent/hands-on verification of bulk actions working at scale, and documentation of bulk operation limits or scope beyond categorization/GL codes.

   • [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

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

   weight 3 · round to Mercury Books
   Wave—none0/10

   Wave offers only a handful of fixed, vendor-built automations (recurring invoices, overdue reminders, auto payroll tax filing, bank auto-categorization) — none of these let a user define custom rules or trigger-action logic on arbitrary events. No evidence of a rules engine, webhooks, or conditional automation builder; the developer/API surface is walled off (403) and marketing pages document no such capability.

   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books~partialclaimed5/10

   Mercury Command explicitly supports creating 'categorization rules' and bulk GL code assignment, which is a form of user-defined rule-based automation triggered by transaction events, and automatic categorization/reconciliation is built-in. However, there's no evidence of a general-purpose rule/trigger-action framework beyond categorization (e.g., rules for invoicing, alerts, or other business events), and Mercury's own docs caution that automation isn't full autopilot. Missing for 10: broader event types beyond categorization, explicit rule configuration UI/API details, and independent confirmation of rule reliability.

   • [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Wave
   Wave~partialprobed3/10

   Wave supports one narrow recurring automation — recurring invoices and payment reminders (wave-docs-10, wave-docs-2) — but there is no evidence of a general-purpose scheduler, API-triggered jobs, or workflow automation platform that an AI-native user could hook into; its developer/API surface is walled off from public documentation (wave-supp-dev-portal-wall, wave-probe-1, wave-probe-2). Missing for 10: programmable/scriptable recurring jobs beyond invoicing, API or webhook-based scheduling, and any AI/automation-platform integration evidence.

   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Evidence shows automatic categorization/reconciliation and an AI assistant (Command) that can be asked to do tasks, but there is no mention of user-defined recurring/scheduled jobs or workflows; the API/MCP layer that might enable this is explicitly described as 'soon' (not yet shipped), and probes for API endpoints 404. Missing for 10: any documented scheduling/recurring-workflow feature, evidence of a live automation API or MCP layer, and independent confirmation of scheduled task execution.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS with no evidence of automation version control, review workflows, or rollback capabilities for AI-driven automations; the evidence pack shows only accounting features (invoicing, payroll, receipts) and confirms no API/developer docs were accessible.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Evidence shows Mercury Books has automation features (Command AI assistant, categorization rules, bulk GL code assignment) but nothing about versioning automation rules, reviewing changes, or rolling back automated actions/decisions. No audit trail, undo, or history/version-control feature is mentioned anywhere in the pack.

   ⚑ flag

Ai reconciliation

1. ai-native userHave an agent reconcile a month end-to-end, matching transactions, flagging exceptions, and preparing the close for human review

   weight 3 · round to Mercury Books
   Wave—none0/10

   Wave's evidence covers auto-import/categorization, invoicing, payroll, and receipts, but there is no mention of an AI agent performing end-to-end reconciliation, flagging exceptions, or preparing a close for human review; no automation/agent framework or API for such orchestration is documented, and the developer portal is a crawl wall with no public API/agent hooks shown.

   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books~partialclaimed5/10

   Mercury Books has continuous automatic reconciliation/categorization and Command can answer questions and offload bookkeeping tasks like journal entries and bulk categorization, but Mercury explicitly states automation is not 'autopilot' and requires human decision-making, and there's no evidence of an agent autonomously running a full month-end close with exception flagging and review prep end-to-end — the MCP/agent layer is only announced as 'soon'. missing for 10: evidence of an actual agent (not just Command chat) performing a full month-end close, explicit exception-flagging workflow, and a shipped MCP/API layer rather than a 'soon' roadmap item.

   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”

   proof ↗⚑ flag

Bank feeds

1. founderConnect bank and credit-card accounts so transactions import automatically every day

   weight 3 · round drawn
   Wave✓fullclaimed8/10

   Wave's Pro Plan explicitly documents automatic daily bank/credit-card feed import with auto-merge and categorization, directly matching the story, and this is corroborated across multiple marketing pages. Missing for 10: independent/hands-on verification (e.g., user reviews confirming daily reliability) beyond vendor claims, and no detail on credit-card-specific connection flow distinct from bank accounts.

   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”

   proof ↗⚑ flag

   Mercury Books✓fullclaimed8/10

   Mercury Books explicitly supports linking external bank accounts, cards, and payroll platforms with transactions pulled in automatically and reconciled/categorized continuously in real time, directly matching the founder story. Multiple first-party docs corroborate this (linking, auto-categorization, continuous reconciliation) and Mercury even publishes an honest caveat that 'connected' isn't 'fully automated,' showing transparency rather than contradiction. missing for 10: independent/hands-on verification beyond Mercury's own docs, and detail on daily import cadence/reliability guarantees.

   • [claimed-docs] “Link external bank accounts, cards, payroll platforms, and more for the complete story of your business.”
   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Third-party data flows in alongside Mercury's own: Books "connects to a growing set of third-party platforms, including Stripe, PayPal, and …”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”

   proof ↗⚑ flag

Categorization

1. founderGet automatic categorization suggestions for imported transactions that learn from my corrections

   weight 2 · round to Mercury Books
   Wave~partialclaimed4/10

   Wave documents automatic bank transaction import and categorization on the Pro Plan (auto-merge/categorize), but no evidence anywhere describes the system learning from user corrections over time — a core part of the story. Missing for 10: any documentation of a learning/adaptive categorization mechanism, evidence that manual recategorization improves future suggestions, and independent/hands-on confirmation of categorization accuracy improving.

   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”

   proof ↗⚑ flag

   Mercury Books✓fullclaimed8/10

   Mercury explicitly states that transactions are 'automatically assigned GL codes based on your categorization history and AI-driven suggestions,' directly supporting the idea of categorization suggestions that improve from past corrections, and Command lets users bulk-adjust GL codes and create rules that presumably feed this history. Mercury's own blog post also candidly notes automation has limits and isn't 'autopilot,' which sets realistic expectations rather than contradicting the feature. Missing for 10: independent/hands-on verification that suggestions specifically adapt after user corrections, and a public API/schema showing the correction-learning mechanism.

   • [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”
   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”

   proof ↗⚑ flag

Reconciliation

1. accountantReconcile each bank account against the ledger with matched, unmatched, and duplicate transactions surfaced for review

   weight 3 · round to Mercury Books
   Wave~partialclaimed4/10

   Wave documents bank auto-import with auto-merge and categorization (implying some duplicate/match handling), but there is no evidence of a dedicated reconciliation view that explicitly surfaces matched, unmatched, and duplicate transactions for accountant review, nor of bank-to-ledger balance reconciliation reporting. Missing for 10: explicit unmatched-transaction review UI, duplicate-transaction flagging documentation, and a formal reconciliation/statement-balance-match report.

   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”

   proof ↗⚑ flag

   Mercury Books~partialclaimed5/10

   Mercury Books claims accounts 'reconcile in real time' automatically with categorization pulled directly from linked banking data (mercury-books-supp-auto-rec, mercury-books-supp-launch), and Mercury's own honest-scope post acknowledges that full automation still requires human review of ambiguous decisions (mercury-books-supp-honest-scope), implying some reconciliation review workflow exists. However, none of the evidence specifically describes a UI or workflow that surfaces matched, unmatched, and duplicate transactions as distinct categories for accountant review — the emphasis is on automation eliminating manual reconciliation work entirely rather than a structured review interface. Missing for 10: explicit documentation of matched/unmatched/duplicate transaction states, a dedicated reconciliation review screen, and independent/hands-on confirmation of this workflow.

   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”

   proof ↗⚑ flag

Bill management

1. accountantCapture vendor bills, route them for approval, and schedule payments from one workflow

   weight 2 · round to Mercury Books
   Wave—none0/10

   Evidence only shows Wave lets users 'create unlimited... bills' as a record type (wave-docs-7); there is no mention of vendor bill capture workflow, approval routing, or scheduled bill payments anywhere in the pack. Wave's payments feature is explicitly for receiving customer payments on invoices, not paying vendors (wave-supp-payments), and no AP-specific workflow is documented.

   • [claimed-docs] “Create unlimited estimates, invoices, bills, and bookkeeping records”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

   Mercury Books~partialclaimed3/10

   Evidence only shows that 'bill pay' transactions are pulled into Mercury Books automatically alongside banking and invoicing data, implying some underlying bill-pay capability exists, but there is no description of a capture-to-approval-to-payment-scheduling workflow, approval routing, or scheduled payments within Books itself. missing for 10: vendor bill capture/OCR, approval routing rules, payment scheduling UI, evidence tying bill pay into an AP-specific workflow rather than just a transaction category.

   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”

   proof ↗⚑ flag

Payables

1. accountantSee accounts payable aging and vendor balances at any point in time

   weight 2 · round drawn
   Wave—none0/10

   Evidence confirms Wave supports creating bills and general accounting reports (month-to-month/year-to-year comparisons), but nothing documents an accounts-payable aging report or vendor balance tracking at a point in time. Missing for 10: AP aging report, vendor balance summary/statement, point-in-time vendor ledger view.

   • [claimed-docs] “Create unlimited estimates, invoices, bills, and bookkeeping records”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Evidence confirms Mercury Books generates P&L, cash flow, and balance sheet reports and mentions 'bill pay' as a data source, but there is no mention of an accounts payable aging report or vendor-balance tracking feature anywhere in the evidence pack. missing for 10: AP aging report, vendor balance report/ledger, point-in-time vendor balance lookups.

   • [claimed-docs] “Generate P&L, cash flow, and balance sheet reports from today’s numbers, not last quarter’s.”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”

   proof ↗⚑ flag

Close process

1. accountantLock closed periods so prior-period numbers cannot change without an explicit reopening

   weight 2 · round drawn
   Wave—none0/10

   No evidence Wave offers period locking or close controls; docs mention role-based access and reports but nothing about locking closed periods or preventing prior-period edits without explicit reopening.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence in the pack mentions period locking, closing periods, or preventing edits to prior-period transactions without explicit reopening; the evidence covers categorization, reconciliation, reports, and accountant invites but not period lock controls.

   ⚑ flag

2. accountantRun a month-end close against a checklist that tracks reconciliations, accruals, and review sign-offs

   weight 3 · round drawn
   Wave—none0/10

   No evidence of any month-end close checklist, reconciliation tracking, accrual management, or review sign-off workflow; Wave's evidence covers invoicing, payroll, receipts, and basic reports only, and it explicitly positions itself as built for small business owners rather than accountants performing formal close processes.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Evidence shows continuous automated reconciliation, accrual/cash accounting choice, and accountant collaboration via comments/tagging, but there is no mention of an actual month-end close checklist artifact, accrual entry tracking, or formal review sign-off workflow that an accountant could run through and mark complete. missing for 10: a defined close checklist feature, accrual scheduling/tracking, sign-off/approval workflow tied to close tasks.

   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “Accountant collaboration without seat caps: "You can invite your bookkeeper or accountant directly to your Mercury account with permissions …”
   • [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
   • [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”

   proof ↗⚑ flag

Collaboration

1. founderInvite my external accountant or bookkeeper with role-scoped access to review and adjust the books

   weight 3 · round to Mercury Books
   Wave✓fullclaimed7/10

   Wave explicitly documents inviting an accountant/bookkeeper with role-scoped access (payroll manager, admin, editor, viewer on Pro, or free accountant/tax pro role), directly matching the story. Missing for 10: independent/hands-on verification of the invite/permissions flow and finer detail on what each role can/cannot edit.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

   Mercury Books✓fullclaimed8/10

   Mercury Books explicitly supports inviting bookkeepers/accountants in-product with role-tailored permissions and no seat caps, allowing them to view transactions, categorizations, and comment/tag on entries. Missing for 10: no independent/hands-on corroboration of the granularity of role-scoping (e.g., specific permission levels) and no detail on whether accountants can directly adjust vs. only comment.

   • [claimed-docs] “Invite your bookkeeper in-product, with unlimited seats at no extra cost.”
   • [claimed-docs] “Accountant collaboration without seat caps: "You can invite your bookkeeper or accountant directly to your Mercury account with permissions …”
   • [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”

   proof ↗⚑ flag

Data access

1. developerPull the full general ledger and trial balance through a documented API in open formats

   weight 3 · round drawn
   Wave—none0/10

   Evidence shows Wave's developer/GraphQL API portal exists but is crawl-walled and unverifiable, and explicit probes for llms.txt/openapi/swagger all return 404; no documentation confirms GL or trial balance export via API in open formats (CSV/JSON/XML). Marketing pages describe UI-based 'reports' but never reference an API endpoint for ledger/trial balance data.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   The evidence explicitly states a full accounting API is only planned ('Soon, a full accounting API will make every core Books action available programmatically'), and direct probes for OpenAPI/llms.txt docs returned 404s, confirming no current documented API for pulling GL/trial balance data in open formats.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

Integrations

1. founderConnect my banking, payments, and payroll systems so their activity flows into the ledger automatically

   weight 2 · round to Mercury Books
   Wave~partialclaimed6/10

   Wave clearly documents automatic bank-feed import/categorization (Pro plan) and integrated online payments that flow directly into invoicing/accounting records, so banking and payments activity does land in the ledger automatically. However, the payroll product's features (direct deposit, tax filing, employee portal) are described in isolation with no explicit statement that payroll transactions sync into the accounting ledger the way bank/payment data does, and there's no evidence of an API/webhook layer for connecting external banking, payment, or payroll systems beyond Wave's own native modules. Missing for 10: explicit documentation that payroll runs automatically post to the general ledger, and any API/integration surface for external banking or payroll systems.

   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”
   • [claimed-docs] “Run payroll in minutes”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [claimed-docs] “Deposit payments directly into your employees’ bank accounts. Less work for you, and your team will love it.”

   proof ↗⚑ flag

   Mercury Books✓fullclaimed8/10

   Mercury Books explicitly supports linking external bank accounts, cards, and payroll platforms, plus named integrations with Stripe, PayPal, and Gusto, with activity flowing automatically into the ledger via continuous categorization and reconciliation. Mercury itself is candid that this is a strong starting point rather than full autopilot, which tempers but doesn't contradict the core claim. Missing for 10: independent/hands-on verification of these integrations working in practice, and a public API/OpenAPI spec was found to 404, indicating limited programmatic verification.

   • [claimed-docs] “Link external bank accounts, cards, payroll platforms, and more for the complete story of your business.”
   • [claimed-docs] “Third-party data flows in alongside Mercury's own: Books "connects to a growing set of third-party platforms, including Stripe, PayPal, and …”
   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
   • [claimed-docs] “Customers with enriched integrations to QuickBooks and NetSuite can now attach Classes to transactions on Mercury.”

   proof ↗⚑ flag

Migration

1. founderMigrate historical books from another accounting system without losing transaction detail

   weight 1 · round to Wave
   Wave~partialclaimed3/10

   Wave mentions an 'onboarding' process for switching from other accounting software like Freshbooks, but this is a single glancing bullet point with no detail on how historical transactions, ledgers, or account balances are actually imported or whether transaction-level detail is preserved. missing for 10: documented import/migration tool, description of data mapping (chart of accounts, historical invoices, journal entries), evidence that no transaction detail is lost, and any independent user reports of successful bookkeeping migrations.

   • [claimed-docs] “Onboarding when switching from other accounting software, like Freshbooks”
   • [claimed-docs] “When you switch from another payroll software, migrating your data is simple.”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence describes an import/migration tool for bringing historical transaction-level data in from QuickBooks/NetSuite or other systems; in fact Mercury explicitly frames Books as a replacement rather than an integration/sync layer for prior accounting systems, and the cited third-party integrations (Stripe, PayPal, Gusto, bank feeds) are for ongoing data flow, not one-time historical migration.

   • [claimed-docs] “Does Mercury Books replace QuickBooks? Yes. Mercury Books is a complete accounting system — not an add-on or integration layer for another p…”
   • [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
   • [claimed-docs] “Third-party data flows in alongside Mercury's own: Books "connects to a growing set of third-party platforms, including Stripe, PayPal, and …”

   proof ↗⚑ flag

Invoicing

1. founderCreate and send invoices with online payment options and see when they are viewed and paid

   weight 3 · round to Wave
   Wave✓fullclaimed9/10

   Wave's docs directly cover invoice creation, branded templates, online payment via 'Pay now' (credit card/bank/Apple Pay), and status tracking (viewed, due, paid) plus overdue reminders — exactly matching the story. Missing for 10: independent/hands-on corroboration beyond vendor marketing pages.

   • [claimed-docs] “Know when an invoice is viewed, becomes due, or gets paid, so you can take the right actions to manage your cash flow.”
   • [claimed-docs] “Customers can click a “Pay now” button on invoices and pay instantly by credit card or secure bank payment (ACH/EFT) for as little as 1%2 pe…”
   • [claimed-docs] “Add your logo and brand colors to our professional invoice templates. Drag-and-drop editing makes it easy to customize!”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Evidence only mentions 'invoicing' as one of many transaction types Mercury Books pulls in automatically (alongside banking, bill pay); there is no evidence of invoice creation/sending, online payment collection, or view/paid status tracking within Mercury Books itself.

   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Third-party data flows in alongside Mercury's own: Books "connects to a growing set of third-party platforms, including Stripe, PayPal, and …”

   proof ↗⚑ flag

2. founderSet up recurring invoices and automatic payment reminders for overdue customers

   weight 2 · round to Wave
   Wave✓fullclaimed8/10

   Wave's documentation explicitly covers both halves of the story: recurring invoices with automatic credit card payments for repeat customers (wave-docs-10), and automatic overdue payment reminders scheduled at 3/7/14 days (wave-docs-2, wave-supp-invoicing). Missing for 10: independent/hands-on corroboration beyond vendor marketing pages, and detail on customizing reminder cadence beyond the fixed schedule.

   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   The evidence pack mentions invoicing only as one data stream feeding into books (transactions across 'banking, invoicing, bill pay'), but there is no mention of recurring invoice scheduling or automated overdue payment reminders anywhere in the docs. This is a fair capability for a full accounting system to offer, so absence of evidence is 'none' rather than 'na'.

   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Link external bank accounts, cards, payroll platforms, and more for the complete story of your business.”

   proof ↗⚑ flag

Receivables

1. accountantTrack accounts receivable with aging reports and per-customer balances

   weight 2 · round drawn
   Wave—none0/10

   Evidence describes general accounting reports (cash-flow trend comparisons) and per-invoice status tracking (viewed/due/paid), but nothing in the pack specifically documents an accounts-receivable aging report or a per-customer balance summary. Missing for 10: explicit AR aging report feature, per-customer balance/statement view, any documentation naming 'aging' or customer-level receivables tracking.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Know when an invoice is viewed, becomes due, or gets paid, so you can take the right actions to manage your cash flow.”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Mercury Books documents P&L, cash flow, and balance sheet reports and mentions invoicing as one of the pulled-in transaction types, but no evidence describes accounts-receivable aging reports or per-customer balance tracking specifically. missing for 10: AR aging report feature, per-customer balance view, any invoicing/AR-specific reporting documentation.

   • [claimed-docs] “Generate P&L, cash flow, and balance sheet reports from today’s numbers, not last quarter’s.”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”

   proof ↗⚑ flag

Ai ledger

1. ai-native userHave an agent draft and post journal entries via the API and leave them in a review queue for my accountant

   weight 3 · round drawn
   Wave—none0/10

   No evidence of an API for posting journal entries, nor any review-queue/approval workflow; the developer portal is inaccessible (403) and marketing pages document no API/MCP/CLI surface, and probes for llms.txt/openapi return 404s.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   The only mention of a programmatic API and MCP layer for agents is explicitly framed as a future roadmap item ('Soon, a full accounting API... will let AI agents handle bookkeeping tasks end-to-end'), not a shipped capability, and probes confirm no live OpenAPI/MCP endpoints exist today (404s on all candidate paths). While Command can draft journal entries via chat and accountants can be invited to collaborate, there is no evidence of an API-driven posting workflow or a formal 'review queue' gating agent-drafted entries for accountant approval.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Accountant collaboration without seat caps: "You can invite your bookkeeper or accountant directly to your Mercury account with permissions …”

   proof ↗⚑ flag

Chart of accounts

1. accountantCustomize the chart of accounts with account types, sub-accounts, and class or tag dimensions

   weight 3 · round to Mercury Books
   Wave—none0/10

   The evidence pack contains no documentation of chart-of-accounts customization, account types, sub-accounts, or class/tag dimensions in Wave; it only vaguely mentions 'Tag it, track it' without describing COA structure, and positions Wave as built for non-accountants using standard double-entry books without customizable account hierarchies. missing for 10: any mention of account type management, sub-account creation, or class/tag dimension reporting.

   • [claimed-docs] “Tag it, track it, and see what's working for your business.”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

   Mercury Books~partialclaimed5/10

   Evidence shows GL code assignment, bulk categorization rules, and Class/tag attachment to transactions (via enriched QuickBooks/NetSuite integrations), plus Command's ability to help 'organize your chart of accounts' — indicating some COA customization exists. However there's no explicit documentation of defining account types or creating sub-accounts within the ledger structure itself. missing for 10: explicit account-type configuration, sub-account creation/hierarchy, and native (non-integration) class/tag dimension setup.

   • [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
   • [claimed-docs] “Customers with enriched integrations to QuickBooks and NetSuite can now attach Classes to transactions on Mercury.”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”

   proof ↗⚑ flag

Journal entries

1. accountantPost manual journal entries with balanced debits, credits, and supporting memos

   weight 3 · round to Mercury Books
   Wave~partialclaimed3/10

   Wave explicitly markets itself as 'real, double-entry accounting software,' implying journal-entry mechanics under the hood, but no evidence pack item documents a manual journal-entry screen, debit/credit balancing UI, or memo field for such entries. Missing for 10: explicit manual journal entry feature documentation, debit/credit balance validation details, memo/note field support, and any independent or hands-on confirmation of this specific workflow.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Mercury Books~partialclaimed5/10

   Books is confirmed as a double-entry accounting system with journal entries as a core capability ("writing journal entries" is explicitly listed as a task Command can help with), implying balanced debit/credit posting, but there's no direct documentation of a manual journal-entry UI, memo/note fields, or debit=credit validation for accountant-initiated entries — most journal entry evidence frames it as an AI-assisted/automated task rather than manual accountant entry. Missing for 10: explicit manual entry screen documentation, memo/attachment support on journal entries, and confirmation of balance validation.

   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”

   proof ↗⚑ flag

Ai audit

1. ai-native userHave an agent monitor the ledger and flag anomalies in spend or duplicate transactions before the close

   weight 3 · round drawn
   Wave—none0/10

   No evidence of any AI agent, anomaly detection, duplicate transaction flagging, or automated audit monitoring capability; Wave's evidence covers manual/human-facing bookkeeping, invoicing, payroll and receipts features only, plus a note that its API/developer surface is not documented publicly.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Evidence shows Command can answer questions and bulk-categorize/reconcile transactions, and an MCP layer for agents is only promised as 'soon,' but nothing describes proactive anomaly detection, duplicate-transaction flagging, or pre-close audit alerts.

   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”

   proof ↗⚑ flag

Audit trail

1. accountantSee a complete audit trail of who changed what and when across the entire ledger

   weight 3 · round drawn
   Wave—none0/10

   Evidence shows multi-user role access (admin/editor/viewer, accountant access) but nowhere documents an audit trail or change log tracking who edited what and when across the ledger. No mention of audit logs, version history, or edit tracking exists in the pack.

   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence describes an audit trail, change log, user attribution, or history of edits across the ledger; the pack focuses on automation, categorization, reporting, and accountant seat invites, none of which document who-changed-what-when tracking. This is a plausible and expected feature for a full accounting system, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

Multi entity

1. accountantManage multiple legal entities and produce consolidated financials across them

   weight 2 · round drawn
   Wave—none0/10

   Wave's pricing is explicitly per-business (subscribe and pay separately for each business), with no mention of consolidation, inter-entity eliminations, or a multi-entity reporting view; evidence explicitly frames Wave as built for individual small business owners, not multi-entity accounting.

   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence anywhere in the pack mentions multiple legal entities, inter-company eliminations, or consolidated financial statements across entities; all documentation describes a single-business books setup with one set of P&L/balance sheet/cash flow reports.

   ⚑ flag

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

   weight 2 · round drawn
   Wave—none0/10

   Evidence shows no accessible API documentation (developer portal returns 403, no OpenAPI/llms.txt found), and marketing pages document no API/CLI surface that would let users mirror UI actions programmatically. There's no evidence of API parity with UI features like invoicing, payroll, or bank feeds.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Mercury's own docs say a full accounting API is coming 'soon' — it does not exist yet — and probes for llms.txt/openapi specs both return 404, confirming no current API parity with the UI.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Wave—none0/10

   No evidence anywhere in the pack of a data export feature (e.g., CSV/QIF export, open-format backups) or data portability tooling; marketing pages focus on invoicing, payroll, receipts, and payments with no mention of exporting or leaving with your data, and the developer/API surface is walled off (403) with no llms.txt or OpenAPI found. Missing for 10: any documented export-to-open-format feature, data portability docs, or migration-out tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence pack item mentions any data export feature, open format (CSV/OFX/JSON) download, or account-closure data portability path; the only related probes (llms.txt, openapi.json) return 404s, and Mercury explicitly positions Books as a replacement system rather than an interoperable one ('not an add-on or integration layer for another platform').

   • [claimed-docs] “Does Mercury Books replace QuickBooks? Yes. Mercury Books is a complete accounting system — not an add-on or integration layer for another p…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Wave—none0/10

   No evidence anywhere in the pack mentions data residency, regional storage options, or compliance controls for choosing where data is stored; Wave's marketing pages focus entirely on accounting/invoicing/payroll features with no privacy-posture or data-location documentation.

   ⚑ flag

   Mercury Books—none0/10

   No evidence anywhere in the pack discusses data residency, region selection, or storage location controls for Mercury Books; the material covers accounting features, AI assistant capabilities, and integrations only.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Wave—none0/10

   Wave is a small-business accounting/invoicing product with no evidence of any data retention or deletion controls, privacy dashboard, or export/erasure tooling in its marketing pages; the developer portal is inaccessible and no API/CLI/MCP docs exist to inspect further.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   The evidence pack contains no mention of data retention policies, deletion controls, export/purge mechanisms, or any privacy-posture settings a user could control; it focuses entirely on accounting features, AI assistant capabilities, and pricing. This is a fair axis for a financial SaaS product handling sensitive business data, but no supporting evidence exists.

   ⚑ flag

3. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS product with no evidence of any telemetry opt-out, privacy controls, or usage-tracking settings documented anywhere in its marketing pages; the developer portal is also inaccessible for verification. No mention of an AI-native usage context or telemetry controls exists in the pack.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   No evidence anywhere in the pack mentions telemetry, usage tracking, data collection settings, or opt-out controls; the material focuses entirely on accounting features, AI assistant capabilities, and pricing. This is a fair privacy-posture question for any SaaS product, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

Ai insights

1. ai-native userAsk an agent "can we afford X?" and get an answer grounded in live ledger data pulled through the API

   weight 3 · round drawn
   Wave—none0/10

   No evidence of any AI agent, chat interface, or query capability grounded in live ledger data; the probes show no llms.txt/OpenAPI surface exposed on marketing domain, and the developer/GraphQL API portal is walled off from crawling with no documented AI integration. Marketing pages only describe reports/dashboards, not agent-accessible querying.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Mercury's own docs frame the accounting API and MCP layer for external agents as a future ('Soon') capability, not something shipped today, and direct probes for an OpenAPI spec or llms.txt on Mercury's docs return 404s, indicating no live API for third-party agents yet. The only grounded Q&A shown (Command) is an in-product assistant, not an externally callable API an outside agent could query.

   • [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
   • [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”

   proof ↗⚑ flag

Custom reports

1. accountantBuild custom reports filtered and grouped by class, location, or tag dimensions

   weight 2 · round drawn
   Wave—none0/10

   Wave's evidence pack shows only basic month-to-month/year-to-year comparison reports; there is no mention of class, location, or tag-based report filtering/grouping, which is a QuickBooks/Xero-style feature Wave does not advertise (Wave is explicitly positioned as not built for accountants' advanced needs).

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

   Mercury Books—none0/10

   Evidence shows Mercury Books generates standard P&L, cash flow, and balance sheet reports, and mentions attaching 'Classes' to transactions only for customers with enriched QuickBooks/NetSuite integrations — not a native custom report builder. No evidence of location or tag dimensions, or of building custom reports filtered/grouped by these dimensions within Books itself.

   • [claimed-docs] “Generate P&L, cash flow, and balance sheet reports from today’s numbers, not last quarter’s.”
   • [claimed-docs] “Customers with enriched integrations to QuickBooks and NetSuite can now attach Classes to transactions on Mercury.”

   proof ↗⚑ flag

Statements

1. founderGenerate an accurate P&L, balance sheet, and cash-flow statement for any period on demand

   weight 3 · round to Mercury Books
   Wave~partialclaimed6/10

   Wave uses real double-entry accounting and explicitly offers accounting reports with month-to-month/year-to-year comparisons to identify cash flow trends, implying core financial statements are generated from bookkeeping data. However, evidence never explicitly names or confirms a formal P&L, balance sheet, and cash-flow statement generated on-demand for any custom period — only general 'accounting reports' are described. Missing for 10: explicit documentation of P&L/balance sheet/cash-flow statement outputs, ability to select arbitrary custom date ranges, and independent/hands-on confirmation of statement accuracy.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

   Mercury Books✓fullclaimed8/10

   Mercury Books explicitly generates P&L, cash-flow, and balance-sheet reports on demand from real-time reconciled data, with cash/accrual choice, positioned as a full double-entry replacement for QuickBooks. This is a core advertised feature with detailed first-party docs, though there's no independent/hands-on corroboration of report accuracy and Mercury itself cautions that automation isn't fully hands-off. Missing for 10: independent verification of statement accuracy, and confirmation that reports are audit-grade/error-free in practice.

   • [claimed-docs] “Generate P&L, cash flow, and balance sheet reports from today’s numbers, not last quarter’s.”
   • [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
   • [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
   • [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
   • [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”

   proof ↗⚑ flag