Xero vs Wave

Agent access

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

   weight 2 · round to Xero
   Xero~partialprobed5/10

   llms.txt returns a 404 (xero-probe-1), so there is no dedicated agent-oriented manifest file, but Xero does provide an official MCP server and AI toolkit documentation (developer.xero.com/documentation/tools/mcp-server, xero-docs-6, xero-docs-19) that an agent could be pointed at instead. This partially satisfies the intent of agent-discoverable docs but not via the standard llms.txt convention. missing for 10: a working llms.txt endpoint, evidence of agent-oriented markdown docs beyond MCP server README, independent confirmation an agent successfully consumes these docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.xero.com/llms.txt”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Xero
   Xero✓fullclaimed7/10

   Xero exposes a documented REST API with OpenAPI spec, official SDKs (xero-node), and a premium 'Custom Connections' option explicitly designed for machine-to-machine (M2M) integrations to a single org without interactive user auth — a direct enabler of headless/CI automation. Missing for 10: explicit CI/CD pipeline examples, documented service-account/headless auth walkthrough, and independent hands-on confirmation of running it unattended in automation pipelines.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [github] “Custom Connections - a Xero premium option for building M2M integrations to a single org”
   • [github] “custom-connections-starter - Basic app showing Custom Connections - a Xero premium option for building M2M integrations to a single org”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Xero—none0/10

   Evidence only shows Xero publishing its own MCP server (and AI Toolkit) so external agents can call Xero's tools, not Xero acting as an MCP client that lets users plug arbitrary external MCP servers into it to extend its own tool use. No documentation of a client-side MCP integration point in Xero (e.g., JAX or other AI features consuming outside MCP servers) is present.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Xero
   Xero✓fullprobed8/10

   Xero ships an official MCP server (xero-mcp-server) documented on developer.xero.com and GitHub, providing standardized MCP protocol access to accounting features like contacts, chart of accounts, and invoices, and Xero also promotes an 'AI Toolkit' including the MCP server, OpenAI Agents SDK and LangChain integration. Missing for 10: independent/hands-on third-party verification of the MCP server's reliability and breadth of tool coverage beyond vendor docs.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   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

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Xero—none0/10

   Evidence shows Xero offers SDKs, an OpenAPI spec, and an MCP server, but there is no mention of an official CLI tool anywhere in the pack.

   ⚑ flag

   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

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

   weight 3 · round to Xero
   Xero✓fullclaimed9/10

   Xero has a well-documented public developer API with official OpenAPI spec, SDKs (xero-node), and a developer portal (developer.xero.com), enabling programmatic access; this is independently confirmed by the GitHub repos and OpenAPI descriptions. missing for 10: independent third-party hands-on verification of API robustness beyond vendor/SDK docs.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Xero
   Xero~partialclaimed4/10

   Xero's OpenAPI spec documents OAuth 2.0 security scopes, and Custom Connections offers M2M credentials scoped to a single org — both provide a technical basis for least-privilege API access, but none of the evidence specifically ties this to issuing scoped credentials for an AI agent (the MCP server docs describe protocol bridging, not credential scoping/permissions setup for agents). Missing for 10: explicit documentation of agent-specific scope selection, least-privilege credential issuance workflow for MCP/agent use, and independent confirmation of this being used for AI agents.

   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [github] “Custom Connections - a Xero premium option for building M2M integrations to a single org”
   • [github] “custom-connections-starter - Basic app showing Custom Connections - a Xero premium option for building M2M integrations to a single org”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”

   proof ↗⚑ flag

   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

8. ai-native userBuild against official SDKs

   weight 2 · round to Xero
   Xero✓fullprobed8/10

   Xero maintains official SDKs (xero-node) generated from official OpenAPI specs, plus a dedicated AI Toolkit with an official MCP server, OpenAI Agents SDK and LangChain integration, directly enabling AI-native development against Xero's API. missing for 10: independent/hands-on developer corroboration of SDK quality and no evidence of SDKs beyond JS/OpenAPI-generated languages being actively maintained.

   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   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

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Xero—none0/10

   The evidence pack covers Xero's API, SDKs, OpenAPI spec, and MCP server, but contains no mention of webhooks or event subscription capabilities anywhere.

   ⚑ flag

   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

Agentic features

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

   weight 2 · round to Xero
   Xero~partialclaimed6/10

   Xero offers JAX, an AI feature that reconciles transactions, categorizes/matches, and extracts bill details, plus dashboards for KPIs/ratios/benchmarking and 'instant answers about cash flow, profit trends and financial health' — these are AI-generated insights/suggestions drawn from user data inside the product. However, evidence is largely marketing copy without hands-on corroboration of insight quality or breadth (e.g., proactive suggestions beyond reconciliation/invoicing/bill entry). Missing for 10: independent/hands-on verification of AI insight accuracy, broader analytical insights (e.g., forecasting, anomaly detection) beyond reconciliation and bill scanning, and detail on how 'instant answers' works.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”
   • [claimed-docs] “Get instant answers about your cash flow, profit trends and financial health.”
   • [claimed-docs] “Analyze KPIs and ratios”
   • [claimed-docs] “Customize performance dashboards ... Analyze KPIs and ratios”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Xero~partialprobed4/10

   Xero provides APIs, SDKs, and an MCP server enabling third-party or AI agents to trigger accounting actions, and JAX offers some automated reconciliation/invoicing features, but there is no evidence of a native scheduler, workflow/automation builder, or persistent background job system that runs autonomously without an external trigger. missing for 10: documented autonomous scheduling/trigger mechanism, native workflow automation builder, evidence of unattended background execution beyond single AI-assisted actions like JAX.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX is Xero's AI invoicing tool that lets you create, edit, and send invoices using plain-language commands.”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Xero
   Xero~partialclaimed6/10

   Xero has a built-in AI assistant called JAX that handles reconciliation, invoicing, and bill entry via plain-language commands, directly matching the story of delegating tasks to an in-product AI assistant. However, JAX's scope appears limited to a few specific workflows (reconciliation, invoicing, bill extraction) rather than a general-purpose task delegate, and there's no independent/hands-on corroboration beyond vendor marketing pages. Missing for 10: broader task coverage beyond reconciliation/invoicing/bills, independent user reviews confirming JAX's real-world reliability, and clarity on how conversational/agentic the delegation experience actually is.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX is Xero's AI invoicing tool that lets you create, edit, and send invoices using plain-language commands.”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Xero
   Xero~partialclaimed6/10

   Xero's JAX assistant lets users create/edit/send invoices and reconcile bank transactions using plain-language commands, directly supporting natural-language operation for end users (not just developers via MCP). However, this NL capability is documented only for invoicing and reconciliation, not the full product surface (e.g., bills, reports, contacts), and there's no independent/hands-on corroboration of JAX's reliability. Missing for 10: NL command support across broader workflows (reporting, bill pay, contact management), and independent verification of JAX's real-world accuracy.

   • [claimed-docs] “JAX is Xero's AI invoicing tool that lets you create, edit, and send invoices using plain-language commands.”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Xero—none0/10

   Evidence shows Xero has a developer portal with API docs, OpenAPI specs, and SDKs, but nothing indicates an interactive API reference with runnable/try-it-now examples (e.g., Swagger UI-style live console); the OpenAPI repo is just spec files for SDK generation. missing for 10: any mention of an interactive/try-it console, runnable code examples in-browser, or sandboxed API playground.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Xero
   Xero✓fullclaimed9/10

   Xero maintains an official GitHub repo of OpenAPI (Swagger) descriptions with OAuth 2.0 security schema, explicitly used to generate SDKs, giving a clear machine-readable API spec download. Missing for 10: independent third-party validation/hands-on confirmation of spec completeness or versioning practices.

   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Xero—none0/10

   No evidence of a dedicated sandbox/demo company environment for testing against the Xero API without touching live production data; the developer docs, SDKs, and MCP server evidence describe general API access but never mention a sandbox, demo org, or test environment. Missing for 10: any mention of a sandbox/demo company, test credentials, or isolated non-production environment for API/agent testing.

   ⚑ flag

   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

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

   weight 2 · round to Xero
   Xero~partialclaimed3/10

   Xero publishes an official OpenAPI spec and developer portal (xero-docs-2, xero-docs-32) implying a versioned API surface, but no evidence describes a documented deprecation policy, version sunset timeline, or changelog for breaking changes. missing for 10: explicit deprecation/versioning policy docs, sunset timelines, changelog of API version history.

   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Xero
   Xero~partialprobed5/10

   Xero documents native bulk-style workflows such as paying multiple bills at once and exporting a single payment file for many suppliers (xero-docs-25, xero-docs-30), and its REST API/SDK and MCP server expose programmatic access that could be scripted for batch operations (xero-gh-1, xero-docs-19). However there is no evidence of a dedicated bulk/batch API endpoint or MCP tool for bulk-updating invoices, contacts, or other records across many items at once. Missing for 10: explicit bulk/batch API or MCP tool documentation, evidence of bulk operations beyond bill payments (e.g., bulk invoicing, bulk contact updates), and independent confirmation of bulk operation reliability.

   • [claimed-docs] “Export a payment file from Xero and upload it directly to your online banking to pay multiple bills in one go. Each supplier receives a sing…”
   • [claimed-docs] “Pay multiple bills at once and automate reconciliation ensuring records are always up-to-date.”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Xero
   Xero~partialprobed3/10

   Xero shows built-in automations (JAX auto-reconciliation matching, duplicate bill detection, automated bill data extraction) and exposes APIs/webhooks plus an MCP server that could be used by developers to build custom event-triggered actions, but there is no evidence of a native user-facing rules/trigger builder where an AI-native user defines arbitrary 'if event then action' rules. Missing for 10: a documented rules engine or webhook/trigger configuration UI, evidence of custom trigger-action mapping, and independent confirmation that such automation works end-to-end.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”
   • [claimed-docs] “Detect and flag duplicate bills automatically to minimize fraud and payment errors”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Wave
   Xero—none0/10

   No evidence Xero supports scheduling recurring jobs/workflows for AI-native automation; the pack covers APIs, SDKs, MCP server, and accounting features but nothing about scheduled/recurring automation triggers or workflow scheduling.

   ⚑ flag

   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

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

   weight 1 · round drawn
   Xero—none0/10

   No evidence anywhere in the pack of versioning, review, or rollback capabilities for automations/workflows in Xero; the evidence covers API/SDK access, MCP server, invoicing, reconciliation, and multi-currency features but nothing about automation version history or rollback.

   ⚑ flag

   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

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 Xero
   Xero~partialprobed5/10

   Xero's JAX assistant automates transaction categorization/matching for bank reconciliation, and the MCP server exposes accounting objects (invoices, chart of accounts, contacts) for programmatic/agent access, so the building blocks for an agent-driven reconciliation exist. However, there is no evidence of an agent performing a full month-end close workflow — no documented exception-flagging logic, no 'prepared for human review' close package, and no first-party or hands-on report of an agent doing this end-to-end. Missing for 10: exception flagging/anomaly detection features, month-end close packaging or review workflow, and evidence of an agent (vs. human using JAX UI) orchestrating the full process via MCP.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”

   proof ↗⚑ flag

   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

Bank feeds

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

   weight 3 · round to Wave
   Xero✓fullclaimed7/10

   Xero explicitly markets bank feed connections with JAX auto-categorizing/matching transactions and integration directory entries (e.g., Mercury) show direct bank connections, supporting daily automatic import and reconciliation. Missing for 10: explicit documentation of daily-sync frequency/reliability, and independent hands-on verification of the bank-feed connection process beyond marketing copy.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Connect Mercury with Xero”
   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”

   proof ↗⚑ flag

   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

Categorization

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

   weight 2 · round to Xero
   Xero~partialclaimed6/10

   Xero's AI feature JAX is explicitly described as categorizing and matching imported bank transactions during reconciliation, directly matching the story's core ask. However, evidence does not confirm that JAX learns from user corrections over time or how correction-based learning works. missing for 10: evidence of learning/adaptation from user corrections, independent/hands-on verification of categorization accuracy improving over time, detail on how suggestions are generated.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”

   proof ↗⚑ flag

   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

Reconciliation

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

   weight 3 · round to Xero
   Xero~partialclaimed6/10

   Xero's marketing docs describe an AI reconciliation feature (JAX) that connects bank accounts and matches/categorizes transactions, and pay-bills docs mention duplicate detection, but the evidence never explicitly describes the classic bank rec workflow of surfacing matched/unmatched/duplicate transactions for review in the ledger-reconciliation screen itself. missing for 10: first-party documentation of the actual bank reconciliation UI showing matched/unmatched/duplicate transaction states, independent/hands-on verification of the reconciliation workflow, and detail on how duplicates are flagged during bank rec specifically (only bill-duplicate detection is cited).

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Detect and flag duplicate bills automatically to minimize fraud and payment errors”
   • [claimed-docs] “Pay multiple bills at once and automate reconciliation ensuring records are always up-to-date.”

   proof ↗⚑ flag

   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

Bill management

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

   weight 2 · round to Xero
   Xero~partialclaimed6/10

   Xero documents automated bill capture (email/upload with AI extraction to draft bills), duplicate detection, and batch payment file export/upload plus reconciliation, covering most of the bills-AP workflow. However, evidence does not clearly describe a configurable multi-step approval routing workflow (e.g., approval thresholds, multiple approvers) beyond bills being 'ready for approval'. missing for 10: explicit approval-routing/workflow rules documentation, evidence of scheduled (future-dated) payment scheduling beyond batch export, independent/hands-on confirmation of the end-to-end flow.

   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”
   • [claimed-docs] “Export a payment file from Xero and upload it directly to your online banking to pay multiple bills in one go. Each supplier receives a sing…”
   • [claimed-docs] “Pay multiple bills at once and automate reconciliation ensuring records are always up-to-date.”
   • [claimed-docs] “Detect and flag duplicate bills automatically to minimize fraud and payment errors”

   proof ↗⚑ flag

   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

Payables

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

   weight 2 · round drawn
   Xero—none0/10

   The evidence pack covers bill payment, duplicate detection, reconciliation, and invoicing features, but contains no mention of accounts payable aging reports or point-in-time vendor balance reporting.

   ⚑ flag

   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

Close process

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

   weight 2 · round drawn
   Xero—none0/10

   No evidence in the pack mentions period locking, closing periods, or preventing edits to prior-period transactions; all evidence covers invoicing, payments, multi-currency, MCP/API tooling, and general reviews. missing for 10: any mention of period lock/close feature, permission controls for locked periods, or reopening workflow.

   ⚑ flag

   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

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

   weight 3 · round drawn
   Xero—none0/10

   Evidence shows only basic bank transaction reconciliation via JAX AI, but no evidence of a structured month-end close checklist, accrual tracking, or review sign-off workflow that an accountant could run to manage close processes.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”

   proof ↗⚑ flag

   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

Collaboration

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

   weight 3 · round to Wave
   Xero—none0/10

   The evidence pack contains no mention of inviting an accountant/bookkeeper, user roles, or permission-scoped access to the books — it focuses on APIs, MCP servers, invoicing, reconciliation, and app marketplace integrations. Xero is well known to have this feature in reality, but per the rules only the evidence pack can be judged, and no citation here addresses accountant invites or role-based access.

   ⚑ flag

   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

Data access

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

   weight 3 · round to Xero
   Xero~partialclaimed6/10

   Xero has a documented OpenAPI-spec-based API and SDKs (xero-node) that expose accounting endpoints including reports like Trial Balance and general ledger data via the Accounting API, with an official OpenAPI description repo confirming open format specs. However, no evidence explicitly confirms a full 'general ledger' export endpoint or trial balance report details, and no independent developer corroboration of actually pulling GL/trial balance data is present. missing for 10: explicit documentation/evidence of a dedicated general ledger/trial balance endpoint, independent developer confirmation of successful GL/trial balance extraction, and detail on data completeness/limits of these reports via the API.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications”

   proof ↗⚑ flag

   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

Integrations

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

   weight 2 · round to Xero
   Xero✓fullclaimed7/10

   Xero documents direct bank-feed reconciliation via JAX (xero-docs-20/27), native Stripe payment integration (xero-docs-23, xero-intdir-3), and payroll connectivity via the Gusto app in its App Store (xero-intdir-4), all designed to feed ledger data automatically. Missing for 10: independent/hands-on verification that these integrations reliably auto-sync in practice, and clearer detail on native payroll (vs. third-party Gusto) ledger posting.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Use Stripe to accept online payments by credit and debit cards, digital wallets, Klarna, ACH Debit, and more”
   • [claimed-docs] “Stripe makes it easy to accept payments from debit cards, credit cards, Apple Pay, and Google Pay for online invoices sent from Xero—so you …”
   • [claimed-docs] “Behind every successful business is a thriving team. Hire, pay, insure, and support your employees with Gusto’s all-in-one people platform.”
   • [claimed-docs] “Connect Mercury with Xero”

   proof ↗⚑ flag

   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

Migration

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

   weight 1 · round to Xero
   Xero~partialclaimed5/10

   Xero's app marketplace lists a third-party partner (Q2X) that explicitly handles QuickBooks-to-Xero migrations 'ensuring a smooth transition of your historical data,' and Xero even subsidizes 'simple conversions,' showing migration support exists. However this is a third-party service rather than a native first-party import tool, is scoped mainly to QuickBooks, and no evidence details preservation of full transaction-level granularity or migration from other accounting systems generally. Missing for 10: native first-party migration/import tooling, evidence covering non-QuickBooks source systems, and detail on transaction-level fidelity guarantees.

   • [claimed-docs] “The Q2X team ensures a seamless transition from QuickBooks to Xero. Our specialists will help set up a Xero account and handle the migration…”
   • [claimed-docs] “The Q2X team ensures a seamless transition from QuickBooks to Xero. Our specialists will help set up a Xero account and handle the migration…”

   proof ↗⚑ flag

   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

Invoicing

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

   weight 3 · round to Wave
   Xero✓fullclaimed8/10

   Xero provides customizable invoice templates, a Pay Now button with Stripe online payments, and invoice tracking that alerts when a customer opens the invoice, directly covering creation, sending, online payment, and view/payment status tracking. Community feedback also corroborates value of invoicing/Stripe integration. Missing for 10: independent hands-on verification of read-receipt accuracy and paid-status timing beyond vendor docs.

   • [claimed-docs] “Use customizable invoice templates to create professional invoices fast – add your logo, payment terms, and branding.”
   • [claimed-docs] “Add your logo and payment terms to Xero's templates for professional invoices”
   • [claimed-docs] “Use Stripe to accept online payments by credit and debit cards, digital wallets, Klarna, ACH Debit, and more”
   • [claimed-docs] “Give customers a slick payment process with a Pay Now button on invoices – and encourage prompt payments”
   • [claimed-docs] “Invoice tracking lets you know the moment a customer opens your invoice, so you can follow up at exactly the right time.”
   • [claimed-docs] “I like Xero for its overall simplicity, especially compared to QuickBooks Online. I find the invoicing feature and Stripe integration in Xer…”
   • [claimed-docs] “Stripe makes it easy to accept payments from debit cards, credit cards, Apple Pay, and Google Pay for online invoices sent from Xero—so you …”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Wave
   Xero—none0/10

   The evidence pack covers invoicing features like templates, Pay Now buttons, invoice tracking, and JAX AI invoicing, but contains no mention of recurring/repeating invoice scheduling or automated overdue payment reminders. Missing for 10: any documentation of recurring invoice setup, reminder scheduling rules, or overdue-customer notification workflows.

   ⚑ flag

   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

Receivables

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

   weight 2 · round to Xero
   Xero~partialclaimed4/10

   Evidence shows Xero has invoicing, invoice tracking (open/paid status), and contact/customer management (xero-docs-29, xero-docs-19, xero-docs-13), which are prerequisites for AR tracking, but there is no explicit mention of an aging report or per-customer balance report in the pack. missing for 10: explicit aging report feature documentation, per-customer outstanding balance report, independent/hands-on confirmation of AR reporting.

   • [claimed-docs] “Invoice tracking lets you know the moment a customer opens your invoice, so you can follow up at exactly the right time.”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “Use customizable invoice templates to create professional invoices fast – add your logo, payment terms, and branding.”
   • [claimed-docs] “Add your logo and payment terms to Xero's templates for professional invoices”

   proof ↗⚑ flag

   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

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 to Xero
   Xero~partialprobed5/10

   Xero provides a full accounting API, SDKs, OpenAPI spec, and an official MCP server with Chart of Accounts and invoice management capabilities, which an agent could use to draft journal entries programmatically. However, there is no documented review-queue/approval workflow, draft-vs-post distinction for journal entries specifically, or accountant-facing review mechanism exposed via the API/MCP server. missing for 10: explicit journal entry draft/post API documentation, a review-queue or approval-hold feature for accountant sign-off, and evidence of an accountant-facing review UI tied to agent-created entries.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   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

Chart of accounts

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

   weight 3 · round to Xero
   Xero~partialclaimed3/10

   The MCP server docs mention 'Chart of Accounts management' as a supported feature, indicating Xero exposes COA management capability, but there is no evidence detailing account types, sub-accounts, or class/tag (tracking category) dimensions. missing for 10: evidence of account type configuration, sub-account hierarchy support, and tracking category/tag/class dimension customization.

   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”

   proof ↗⚑ flag

   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

Journal entries

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

   weight 3 · round to Wave
   Xero—none0/10

   The evidence pack covers invoicing, bill pay, reconciliation, multi-currency, and API/MCP tooling, but contains no mention of manual journal entries, debit/credit balancing, or journal memos anywhere in the docs, SDK, or MCP feature list. Missing for 10: any documentation of a manual journal entry feature, evidence of debit/credit balance validation, or memo/narration support on journals.

   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”

   proof ↗⚑ flag

   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

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 to Xero
   Xero~partialprobed5/10

   Xero natively flags duplicate bills (xero-docs-31) and has JAX AI reconciling/categorizing transactions (xero-docs-20/27), and its official MCP server + APIs (xero-docs-3/14/19, xero-probe-2) let a developer build a custom agent to query ledger data for anomaly detection. However there's no evidence of a purpose-built 'monitor ledger for spend anomalies pre-close' agent or workflow — this would require custom development on top of the API/MCP server rather than an out-of-box capability. Missing for 10: a documented anomaly-detection/close-audit agent feature, evidence of spend-anomaly (not just duplicate-bill) flagging, and any close-process integration.

   • [claimed-docs] “Detect and flag duplicate bills automatically to minimize fraud and payment errors”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   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

Audit trail

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

   weight 3 · round drawn
   Xero—none0/10

   No evidence in the pack references audit trails, change history, user activity logs, or ledger version tracking anywhere in Xero's documentation or community reports; the pack covers APIs, MCP servers, invoicing, reconciliation, and integrations but nothing about audit logging.

   ⚑ flag

   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

Multi entity

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

   weight 2 · round to Xero
   Xero~partialclaimed3/10

   The only relevant evidence is a marketing line claiming Xero can 'generate consolidated financial statements in multiple currencies,' which is ambiguous and likely refers to multi-currency transaction consolidation within a single entity rather than true multi-legal-entity consolidation (parent/subsidiary structures). No evidence describes managing separate legal entities, intercompany eliminations, or org-to-org consolidation tools. Missing for 10: explicit multi-entity/subsidiary management features, intercompany elimination support, and independent confirmation of cross-entity consolidated reporting.

   • [claimed-docs] “Generate consolidated financial statements in multiple currencies for a clear view of your financial position”
   • [claimed-docs] “Xero's multi-currency accounting software lets you do business in multiple currencies with ease. Get real-time foreign exchange rates, simpl…”
   • [claimed-docs] “Xero's multi-currency accounting software lets you do business in multiple currencies with ease.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Xero
   Xero~partialprobed6/10

   Xero has a comprehensive REST API with OpenAPI spec, SDKs, and an official MCP server exposing contacts, chart of accounts, and invoicing, indicating broad API coverage of core accounting workflows. However, there is no evidence confirming full parity with newer AI/UI-only features like JAX (AI invoicing/reconciliation assistant), KPI/benchmarking dashboards, or all pricing-plan features being exposed via API. missing for 10: confirmation that JAX AI features, performance dashboards/benchmarking, and all UI-exclusive workflows are accessible via API/MCP, independent verification of full UI-API parity.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX is Xero's AI invoicing tool that lets you create, edit, and send invoices using plain-language commands.”
   • [claimed-docs] “Analyze KPIs and ratios”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Xero
   Xero~partialclaimed4/10

   Xero exposes API/OpenAPI access and third-party migration services (Q2X) that imply data can be extracted, but there is no documented native 'export all my data' bulk/open-format export feature or data-portability policy aimed at users leaving the platform. missing for 10: a first-party bulk data export tool/feature, documented open-format (CSV/JSON) full-account export, and any explicit data-portability/exit policy statement.

   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”
   • [claimed-docs] “The Q2X team ensures a seamless transition from QuickBooks to Xero. Our specialists will help set up a Xero account and handle the migration…”

   proof ↗⚑ flag

   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

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Xero—none0/10

   Xero is closed-source SaaS; while SDKs and API specs (xero-node, OpenAPI descriptions) are open, the actual product source code is proprietary and not published under any open license. No evidence of an open-source core product exists in the pack.

   ⚑ flag

   Wave—none0/10

   Wave is a closed commercial SaaS accounting product; there is no evidence of an open-source repository or open license for its source code, and probes for standard openness/API signals (llms.txt, openapi) returned 404. The developer portal is also walled off, further indicating no open access to source.

   • [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

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

   weight 2 · round drawn
   Xero—none0/10

   No evidence in the pack mentions data residency, regional data storage options, or location choice for Xero data; all evidence covers APIs, SDKs, MCP server, invoicing, and other unrelated features. missing for 10: any mention of data residency/region selection, storage location controls, or compliance documentation addressing where customer data is stored.

   ⚑ flag

   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

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Xero—none0/10

   No evidence in the pack addresses data retention or deletion controls for AI-native usage (e.g., API-level data purge, retention policies for MCP/agent access, or user-controlled deletion settings); coverage is limited to product features and integrations unrelated to retention/deletion. missing for 10: retention policy documentation, deletion/export APIs, MCP/agent-specific data lifecycle controls.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Xero—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for AI/agent interactions with Xero; all evidence covers unrelated product features (invoicing, MCP server, integrations).

   ⚑ flag

   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

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 to Xero
   Xero~partialprobed6/10

   Xero has a documented official MCP server exposing accounting data (contacts, chart of accounts, invoices) plus a full API/SDK/OpenAPI spec, which could let an agent pull live ledger data to answer affordability-type questions, and Xero markets 'JAX' and 'instant answers about cash flow' features. However, there's no evidence of a natural-language reasoning layer that combines live ledger pulls with a financial-affordability judgment ('can we afford X') — the MCP server's documented capabilities are CRUD-style (contacts, invoices, chart of accounts) not analytical queries, and no hands-on example shows this exact grounded Q&A flow working. missing for 10: evidence of the MCP/API surfacing cash-flow or budget-analysis endpoints usable for affordability reasoning, and a concrete example/transcript of an agent answering such a question grounded in live data.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”
   • [claimed-docs] “Get instant answers about your cash flow, profit trends and financial health.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”

   proof ↗⚑ flag

   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

Custom reports

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

   weight 2 · round drawn
   Xero—none0/10

   No evidence in the pack addresses custom report building, or filtering/grouping by class, location, or tracking-category/tag dimensions; the pack covers invoicing, payments, multi-currency, AI tools, and API/MCP integrations but nothing about the reporting/tracking-category feature set. Missing for 10: any mention of custom report builder, tracking categories (class/location), tag dimensions, or report filtering/grouping capabilities.

   ⚑ flag

   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

Statements

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

   weight 3 · round drawn
   Xero~partialclaimed6/10

   Xero's marketing pages reference core financial reporting capability ("Get instant answers about your cash flow, profit trends and financial health", "Generate consolidated financial statements", "Analyze KPIs and ratios", customizable dashboards), consistent with an accounting platform producing P&L, balance sheet and cash-flow reports. However, the evidence pack lacks explicit documentation naming these three statements, period-selection controls, or independent corroboration of accuracy/on-demand generation. Missing for 10: explicit product docs naming P&L/balance sheet/cash-flow statement generation, evidence of date-range/period flexibility, and independent user validation of report accuracy.

   • [claimed-docs] “Get instant answers about your cash flow, profit trends and financial health.”
   • [claimed-docs] “Generate consolidated financial statements in multiple currencies for a clear view of your financial position”
   • [claimed-docs] “Analyze KPIs and ratios”
   • [claimed-docs] “Customize performance dashboards ... Analyze KPIs and ratios”

   proof ↗⚑ flag

   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