Xero vs Kick

Agent access

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

   weight 2 · round to Kick
   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

   Kick✓fullprobed8/10

   A live llms.txt index exists at docs.kick.co/llms.txt (HTTP 200, confirmed by probe) with markdown mirrors and a documented ask-query interface, plus a real MCP JSON-RPC endpoint for docs search, giving agents multiple ways to consume agent-oriented documentation. missing for 10: this is a GitBook platform surface rather than a Kick-built capability, and there's no independent (non-vendor) corroboration of agents actually using it successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.kick.co/llms.txt # Kick Docs ## Business Owners - [Kick Docs for Business Owners](https://docs.ki…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   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

   Kick—none0/10

   No evidence of an API, CLI, or headless automation surface for actual Kick operations: OpenAPI/swagger probes all 404, and the only live MCP endpoint found is a GitBook docs-search server, not a Kick account/ledger API. The single 'MCP/CLI' mention on the pricing page is a bare link with no supporting documentation of scriptable/CI-usable functionality.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “MCP/CLI”

   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

   Kick—none0/10

   There is no evidence that Kick lets users plug external MCP servers into the product so it can call their tools. The only MCP-related evidence is a GitBook-provided docs-search MCP endpoint (serving documentation, not Kick data or actions) and a separate workflow where Kick data is exported to Google Sheets for AI tools to read — neither shows Kick acting as an MCP client consuming external servers.

   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   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

   Kick—none0/10

   The only MCP endpoint found is a generic GitBook platform docs-search server (serverInfo "mcp-typescript server on vercel"), explicitly noted as serving documentation, not Kick account data or ledger actions — not an official Kick-built MCP server. Kick's documented AI workflow instead routes through Google Sheets exports for LLMs, with no first-party MCP server for agent access to financial data or actions.

   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”

   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

   Kick—none0/10

   No evidence of a Kick-built CLI exists; the only 'CLI' mention is an unresolved label on a pricing page, and the actual agent-facing surfaces documented (GitBook llms.txt, GitBook MCP endpoint, Google Sheets AI workflow) are docs-search or spreadsheet integrations, not a command-line interface for interacting with Kick. missing for 10: any documented CLI tool, install instructions, command reference, or hands-on confirmation of a Kick CLI.

   • [claimed-docs] “MCP/CLI”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   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

   Kick—none0/10

   No documented public API for driving Kick itself was found: an OpenAPI/API probe returned 404s everywhere, and the only working MCP endpoint is explicitly a GitBook docs-search server that 'serves documentation, not Kick account data or ledger actions.' The AI integration path is one-way reporting into Google Sheets for LLMs to read, not a programmatic API to act on the product.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   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

   Kick—none0/10

   No evidence of any API credential system, scoped tokens, OAuth grants, or agent-specific permission levels for Kick's product/account data—only role-based access control for human team members and a documentation-search MCP endpoint unrelated to account access. No mention of issuing least-privilege API keys or credentials for AI agents to act on a user's financial data.

   • [claimed-docs] “Kick uses role-based access control so you decide exactly who can see and do what in your workspace.”
   • [claimed-docs] “"All data transmitted to and from Kick is encrypted in transit using TLS. Data at rest is encrypted using AES-256... Kick connects to your f…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”

   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

   Kick—none0/10

   There is no evidence of an official Kick SDK: the OpenAPI/Swagger probe returned 404 on all candidate paths, and the only MCP endpoint found (kick-probe-3) is GitBook's generic docs-search MCP server, not a Kick-built API/SDK — it serves documentation, not account or ledger data. AI workflows are routed indirectly through Google Sheets exports rather than a programmable SDK.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   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

   Kick—none0/10

   No evidence anywhere in the pack of a webhooks feature or event subscription mechanism for Kick account/ledger data; the only outbound integrations mentioned are docs-search MCP (GitBook platform) and Google Sheets sync, neither of which is a webhook subscription API.

   ⚑ 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

   Kick~partialprobed4/10

   Kick documents AI categorization of transactions (auto-labeling ~97% on first pass, confidence-gated, learns from corrections) and real-time P&L updates from that AI action, which is a form of AI acting on user data. However, this is transactional automation, not explicit 'insights and suggestions' (e.g., anomaly flags, forecasts, recommendations) surfaced inside the product itself; the only place data is 'reasoned over' by AI (Gemini/Claude/ChatGPT) is via export to Google Sheets, which is outside the core product UI. Missing for 10: in-app AI-generated insights/recommendations dashboard, proactive suggestions beyond categorization, and evidence of AI reasoning happening natively within Kick rather than via Sheets/GitBook docs-search surfaces.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.kick.co/llms.txt # Kick Docs ## Business Owners - [Kick Docs for Business Owners](https://docs.ki…”

   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

   Kick~partialprobed4/10

   Kick automates categorization, transfer matching, reconciliation checks, and rule-based overrides continuously in the background (kick-supp-categorization, kick-supp-reconciliation, kick-docs-7), which is a form of autonomous background automation for bookkeeping tasks. However, this is limited to Kick's own fixed bookkeeping pipeline, not a general-purpose, user-configurable automation/agent framework that an AI-native user could set up for arbitrary autonomous tasks. missing for 10: evidence of user-defined autonomous workflows/agents beyond built-in categorization rules, a scheduling/trigger system for custom automations, or an automation builder — none is documented; MCP surfaces found are docs-search only, not action-capable agents.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   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

   Kick~partialprobed4/10

   Kick documents AI automation for bookkeeping (auto-categorization with confidence gating, described as 'self-driving' per llms.txt) and logs AI actions in an audit trail, but this is background automation of a fixed task, not a conversational assistant a user delegates arbitrary tasks to. The actual 'ask an AI' workflow routes through external tools (Gemini/Claude/ChatGPT) reasoning over exported Sheets data, not a built-in assistant inside Kick's own UI. Missing for 10: a native in-product chat/assistant interface, evidence of delegating open-ended tasks (not just categorization) to it, and independent confirmation of this workflow beyond vendor docs.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.kick.co/llms.txt # Kick Docs ## Business Owners - [Kick Docs for Business Owners](https://docs.ki…”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   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

   Kick~partialprobed4/10

   Kick supports AI-native interaction only indirectly: reports sync as live data to Google Sheets so Gemini/Claude/ChatGPT can read, reason over, and even write back to the sheet, and the docs are agent-legible via GitBook's MCP/llms.txt surfaces. But there's no evidence of a native chat/NL command interface inside Kick itself for issuing commands like 'recategorize this transaction' or 'send this invoice' — the MCP endpoint found only serves documentation search, not account actions, and AI categorization is automatic/rule-based rather than user-prompted NL commands. Missing for 10: a first-party NL command interface or agent that can execute ledger/invoicing/bill-pay actions directly from user prompts, and independent corroboration of the write-back capability actually altering Kick data (not just the sheet).

   • [claimed-docs] “Your Kick reports land as live spreadsheet data in your workbook, so Gemini, Claude, or ChatGPT can read and reason over them.”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”

   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

   Kick—none0/10

   There's no evidence of an interactive API reference or runnable code examples; probes explicitly show no OpenAPI/Swagger spec exists (all candidate paths 404), and the only 'API-like' surface is GitBook's generic docs-search MCP endpoint, which serves documentation text, not a runnable API reference.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   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

   Kick—none0/10

   A direct probe for an OpenAPI/Swagger spec returned 404 on all candidate paths, and no evidence pack item shows a downloadable machine-readable API spec for Kick's own product API; the only machine-readable surfaces found (llms.txt, GitBook MCP) serve documentation, not an API contract.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   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

   Kick—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ 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

   Kick—none0/10

   No evidence of a public, versioned Kick API exists — the openapi/swagger probe returned 404 on all candidate paths, and the only MCP/API-like surface found is GitBook's generic docs-search MCP endpoint, not a Kick-built account/ledger API. There is no mention anywhere in the docs of API versioning schemes or a deprecation policy.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Kick~partialclaimed5/10

   Kick's AI categorizes ~97% of transactions automatically and rules apply logic across every matching transaction going forward, and multi-entity transaction splitting affects many items at once — all forms of bulk-scale automation. However there is no documented bulk-edit UI, batch API, or CLI/MCP action surface for an AI agent to programmatically trigger bulk operations across many items on demand. Missing for 10: explicit bulk-select/bulk-edit feature, a programmatic bulk-action API or CLI, and evidence of agent-triggered bulk operations beyond passive AI categorization.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “For expenses shared across businesses - like rent, software, or insurance - you can split a single transaction across multiple entities by a…”
   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”

   proof ↗⚑ flag

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

   weight 3 · round to Kick
   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

   Kick~partialclaimed6/10

   Kick's documented Rules feature lets users define logic that overrides AI categorization and 'run automatically whenever a matching transaction syncs' — a real event-triggered automation rule engine. However, this is scoped narrowly to transaction categorization events rather than a general-purpose trigger/action framework spanning arbitrary events (e.g., invoicing, bill pay, entity actions). Missing for 10: evidence of rules triggering on non-categorization events, multi-step or cross-feature actions, and any user-facing rule builder UI/API details beyond the single doc description.

   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   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

   Kick—none0/10

   Kick documents event-driven automation (AI categorization on sync, rules triggered by matching transactions) but no evidence of user-schedulable recurring jobs/workflows (e.g., recurring invoices, scheduled reports, cron-like automation) that an AI-native user could set up and manage.

   ⚑ 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

   Kick—none0/10

   Kick documents an audit trail (Activity tab) that logs categorization/rule changes, but there is no evidence of versioning automation Rules or rolling back an automation to a prior state — only a log of what happened, not a way to view/restore prior rule versions.

   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”

   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 drawn
   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

   Kick~partialprobed5/10

   Kick's AI auto-categorizes ~97% of transactions and gates low-confidence items for manual review, and the product includes month-end period locks and a full audit trail logging AI agent actions — echoing pieces of an end-to-end reconciliation workflow. However, the reconciliation docs themselves describe reconciliation as a process of comparing Kick's records to bank statements without documenting that Kick's AI actually performs the matching/flagging of reconciliation exceptions (as opposed to categorization); there's no evidence of a single agent command that walks through match, flag, and prepare-for-review end-to-end. Missing for 10: documented AI-driven bank-statement matching/exception flagging specific to reconciliation (not just categorization), and a described single-agent workflow that completes a full month-end close autonomously.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.kick.co/llms.txt # Kick Docs ## Business Owners - [Kick Docs for Business Owners](https://docs.ki…”

   proof ↗⚑ flag

Bank feeds

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

   weight 3 · round drawn
   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

   Kick✓fullclaimed7/10

   Kick's docs confirm bank/credit-card connection via Plaid with automatic transaction sync ('every transaction in Kick comes from a bank feed or an import'), AI categorization triggered 'when transactions sync into Kick', and a PDF/CSV fallback for institutions Plaid doesn't cover. This clearly delivers the core capability, though the exact 'daily' cadence isn't explicitly stated and there's no independent/hands-on corroboration of sync reliability. Missing for 10: explicit statement of daily sync frequency, independent verification of import reliability.

   • [claimed-docs] “"All data transmitted to and from Kick is encrypted in transit using TLS. Data at rest is encrypted using AES-256... Kick connects to your f…”
   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”
   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”

   proof ↗⚑ flag

Categorization

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

   weight 2 · round to Kick
   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

   Kick✓fullclaimed8/10

   Kick's docs explicitly state AI auto-categorizes ~97% of transactions on first pass, learns from user corrections, and lets users create Rules that override AI categorization permanently for future matching transactions — directly matching the story's requirement for learning-based categorization suggestions. Confidence gating (low-confidence transactions left uncategorized) further supports a learning/feedback loop. Missing for 10: no independent/hands-on verification of the learning accuracy or how quickly corrections propagate, and no detail on the mechanism (per-vendor vs. global learning).

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”

   proof ↗⚑ flag

Reconciliation

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

   weight 3 · round drawn
   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

   Kick~partialclaimed6/10

   Kick's docs describe reconciliation as comparing ledger transactions against bank/credit statements to confirm amounts, dates, and flag missing or duplicate transactions, which aligns with the matched/unmatched/duplicate framing in the story. However, there's no detailed evidence of a dedicated UI that explicitly buckets transactions into 'matched,' 'unmatched,' and 'duplicate' categories for accountant review, nor screenshots or workflow steps showing how discrepancies are resolved. Missing for 10: explicit UI/workflow evidence of distinct matched/unmatched/duplicate views, reconciliation report exports, and independent/hands-on confirmation of the review process.

   • [claimed-docs] “Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythin…”
   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”

   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

   Kick~partialclaimed3/10

   Kick can 'view and manage' bills synced in real time from Ramp or BILL, but the docs explicitly note Kick does not capture bills natively or execute vendor payments itself — it relies on synced data from external AP tools, and there is no documented approval-routing workflow within Kick. Missing for 10: native bill capture/OCR intake, an in-app approval-routing step, and evidence of Kick itself scheduling/executing payments (currently pass-through from Ramp/BILL).

   • [claimed-docs] “View and manage your bills in Kick, with real-time sync from Ramp or BILL.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

Payables

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

   weight 2 · round to Kick
   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

   Kick~partialclaimed4/10

   Kick supports AP-adjacent features — viewing and managing bills with real-time sync from Ramp/BILL (kick-docs-13, kick-supp-invoicing-billpay), a real double-entry ledger (kick-supp-journal-entries), and locked periods that keep historical reports stable so numbers can be trusted 'at any point in time' (kick-supp-locks, kick-docs-14). However, there is no explicit documentation of an AP aging report (e.g., 30/60/90-day buckets) or a vendor-balance summary view — only bill list/sync visibility is evidenced. Missing for 10: dedicated AP aging report, vendor balance summary/report, and evidence of historical point-in-time AP snapshots beyond generic locked-period stability.

   • [claimed-docs] “View and manage your bills in Kick, with real-time sync from Ramp or BILL.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”
   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “Reports for locked periods remain accurate and stable.”

   proof ↗⚑ flag

Close process

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

   weight 2 · round to Kick
   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

   Kick✓fullclaimed9/10

   Kick documents explicit period locking: an accountant locks a period after review, which 'protects the finalized books for that period from being changed - by anyone, including you,' and locked-period reports 'remain accurate and stable,' implying reopening is required for changes. This directly matches the accountant story of preventing prior-period edits without explicit reopening. Missing for 10: explicit documentation of the reopening workflow/permissions and independent/hands-on confirmation beyond vendor docs.

   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “Reports for locked periods remain accurate and stable.”

   proof ↗⚑ flag

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

   weight 3 · round to Kick
   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

   Kick~partialclaimed5/10

   Kick documents core close primitives — reconciliation against bank statements, period locks that finalize books, an audit trail of activity/AI actions, and rules/categorization workflows — which together support month-end close discipline. However, there is no evidence of a dedicated checklist feature tracking accruals as discrete tasks, formal review sign-off workflows, or a consolidated close-status dashboard for accountants. Missing for 10: a documented month-end checklist UI, explicit accrual task tracking, and formal sign-off/approval steps beyond simple period locking.

   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”

   proof ↗⚑ flag

Collaboration

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

   weight 3 · round to Kick
   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

   Kick✓fullclaimed8/10

   Kick explicitly supports role-based access control ('you decide exactly who can see and do what'), lock periods where an accountant can finalize and lock books against changes, a full audit trail of workspace activity, and a dedicated Tax Package/accountant workflow with a marketed accountants page — together enabling a founder to invite an external accountant with scoped access to review/adjust books. Missing for 10: no explicit documentation of granular invite flow or specific role types (e.g., 'accountant' vs 'bookkeeper' role names) and no independent/hands-on confirmation of the invite UX.

   • [claimed-docs] “Kick uses role-based access control so you decide exactly who can see and do what in your workspace.”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “The Tax Package generates a single Excel file with everything your accountant or tax preparer needs to file your taxes - no manual exports, …”
   • [claimed-docs] “We pivoted off QBO completely, and our team now outputs 10x what we used to without adding a single headcount.”
   • [claimed-docs] “Reports for locked periods remain accurate and stable.”

   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

   Kick—none0/10

   Kick documents a real double-entry ledger, chart of accounts, and journal entries, but there is no evidence of a documented API for exporting the general ledger or trial balance in open formats — the openapi probe returned 404s on all candidate endpoints, and the only 'API'-like surfaces found are a GitBook docs-search MCP server and Google Sheets AI integration, neither of which expose ledger/GL data programmatically.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   proof ↗⚑ flag

Integrations

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

   weight 2 · round to Kick
   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

   Kick✓fullclaimed8/10

   Kick connects banking via Plaid (with manual PDF/CSV backfill for unsupported institutions), syncs payment/invoicing data from Stripe, Mercury, Ramp, and BILL, and posts payroll runs directly as journal entries into a real double-entry ledger with automated AI categorization. missing for 10: explicit named payroll provider integrations (e.g., Gusto/Rippling) beyond the generic 'payroll run' mention, and independent third-party corroboration beyond Kick's own docs.

   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”
   • [claimed-docs] “View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.”
   • [claimed-docs] “View and manage your bills in Kick, with real-time sync from Ramp or BILL.”
   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

Migration

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

   weight 1 · round drawn
   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

   Kick~partialclaimed5/10

   Kick documents CSV/PDF backfill for historical data and offers a paid 'Advanced' tier with dedicated 'migration support,' plus a customer testimonial about switching off QBO — suggesting migration is a supported workflow. However, there's no documentation of how transaction-level detail, historical journal entries, or opening balances are preserved during a full accounting-system migration. Missing for 10: detailed migration/import methodology, evidence of transaction-level fidelity (e.g., historical journal entries, categorization history) surviving migration, and independent corroboration beyond one testimonial.

   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”
   • [claimed-docs] “We pivoted off QBO completely, and our team now outputs 10x what we used to without adding a single headcount.”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   proof ↗⚑ flag

Invoicing

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

   weight 3 · round to Xero
   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

   Kick~partialclaimed5/10

   Kick lets founders create and send invoices directly and also view invoices synced from Stripe, Mercury, and BILL, giving AR visibility; but the docs describe invoicing as largely a sync/view layer for AR (no native online payment collection is documented, and there's no mention of payment-status tracking like 'viewed' or 'paid' timestamps within Kick itself — that likely happens on the connected platform, not in Kick). missing for 10: documented online payment collection built into Kick-issued invoices, and explicit view/paid status tracking or notifications within Kick's own invoicing UI.

   • [claimed-docs] “View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Kick—none0/10

   Kick's docs confirm basic invoicing (viewing synced invoices from Stripe/Mercury/BILL, and creating/sending invoices directly from Kick) but there is no mention anywhere in the evidence of recurring/repeating invoice schedules or automated overdue-payment reminders. missing for 10: recurring invoice scheduling, automatic overdue payment reminder/dunning workflow.

   • [claimed-docs] “View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

Receivables

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

   weight 2 · round to Kick
   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

   Kick~partialclaimed5/10

   Kick supports AR via invoices synced from Stripe/Mercury/BILL and native invoice creation (kick-docs-12, kick-supp-invoicing-billpay), and the Plus plan advertises 'AR & AP' as a feature (kick-supp-pricing), implying some balance tracking exists. However, there is no documented aging report, no explicit per-customer balance/statement view, and AR appears to depend on synced platforms rather than a dedicated native AR module. Missing for 10: documented aging reports (30/60/90-day buckets), per-customer balance ledger or statement view, and any hands-on/independent confirmation of AR reporting depth.

   • [claimed-docs] “View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   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

   Kick—none0/10

   Kick documents journal entries, categorization confidence-gating, rules, and period locks, but there is no evidence of a public API/SDK for agents to draft or post journal entries programmatically, nor any 'review queue' workflow exposed via API. The only discovered API-like surface is a GitBook docs-search MCP endpoint (docs only, not ledger actions), and explicit probes for an OpenAPI spec returned 404s.

   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”

   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 Kick
   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

   Kick~partialclaimed6/10

   Docs confirm a standard Chart of Accounts that accountants can add/rename/restructure, and pricing explicitly lists 'classes' as a Plus-tier dimension feature, supporting class-based tagging. However there is no explicit documentation of sub-account/parent-child hierarchies or generic 'tag' dimensions beyond classes, and account-type customization is only implied by 'restructuring' rather than detailed. Missing for 10: explicit sub-account nesting support, explicit account-type editing controls, and tag (non-class) dimension documentation.

   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   proof ↗⚑ flag

Journal entries

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

   weight 3 · round to Kick
   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

   Kick~partialclaimed5/10

   Kick documents a genuine double-entry ledger where every transaction generates a journal entry with debit/credit sides, plus a chart of accounts accountants can adjust, supporting the underlying ledger mechanics. However, the evidence describes journal entries as system-generated from transactions/payroll/bills, not explicit manual entry creation by an accountant with supporting memos. Missing for 10: explicit documentation of manually creating/posting a journal entry, memo/description fields on manual entries, and confirmation entries must balance before posting.

   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”

   proof ↗⚑ flag

Ai audit

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

   weight 3 · round drawn
   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

   Kick~partialclaimed5/10

   Kick's reconciliation workflow explicitly checks for missing/duplicate transactions before close, and AI categorization has confidence-gating that flags low-confidence transactions for manual review, with all actions logged in a full audit trail — covering pieces of anomaly detection. However, there's no documented feature where an agent proactively/continuously monitors the ledger and surfaces anomaly or duplicate alerts ahead of close; the AI-agent angle is limited to external LLMs reasoning over exported Sheets report data, not a native monitoring agent. Missing for 10: a dedicated automated agent/alerting workflow for anomaly and duplicate detection tied to close, and evidence of proactive (vs. manual/scheduled) flagging.

   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “Your Kick reports land as live spreadsheet data in your workbook, so Gemini, Claude, or ChatGPT can read and reason over them.”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   proof ↗⚑ flag

Audit trail

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

   weight 3 · round to Kick
   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

   Kick✓fullclaimed8/10

   Kick documents a full Activity tab audit trail logging every transaction change, categorization update, and sync event with timestamp and actor (including AI agent actions), plus period locks that prevent retroactive changes to closed periods and RBAC to control who can act. This directly covers who-changed-what-when across the ledger, including multi-entity workspaces. Missing for 10: no independent/hands-on corroboration of the audit trail in practice, no detail on exporting/filtering audit logs for compliance review, and no explicit confirmation the trail spans across all entities in a multi-entity workspace simultaneously.

   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “The Activity tab is a full audit trail of everything that's happened in your workspace.”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “Reports for locked periods remain accurate and stable.”
   • [claimed-docs] “Kick uses role-based access control so you decide exactly who can see and do what in your workspace.”
   • [claimed-docs] “If you own more than one business, or have a holding company structure, Kick lets you manage all your entities from a single workspace.”

   proof ↗⚑ flag

Multi entity

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

   weight 2 · round to Kick
   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

   Kick~partialclaimed5/10

   Kick documents multi-entity management from a single workspace, including cross-entity expense splitting (kick-docs-5, kick-docs-6), and pricing tiers explicitly support 'unlimited entities' (kick-supp-pricing). However, there is no explicit documentation of consolidated financial statements or roll-up reporting across entities—only per-entity management and transaction splitting are described. Missing for 10: explicit consolidated P&L/Balance Sheet reporting across entities, evidence of a consolidation feature or combined financial statement output.

   • [claimed-docs] “If you own more than one business, or have a holding company structure, Kick lets you manage all your entities from a single workspace.”
   • [claimed-docs] “For expenses shared across businesses - like rent, software, or insurance - you can split a single transaction across multiple entities by a…”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   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

   Kick—none0/10

   Evidence shows no general Kick API: OpenAPI/swagger probes all 404'd, the only MCP endpoint found is a GitBook docs-search server explicitly noted to serve documentation, not Kick account data or ledger actions, and the AI workflow route is one-directional Google Sheets report export (with limited spreadsheet write-back, not writing into Kick). There is no evidence of programmatic access to core UI actions like categorization, reconciliation, invoicing, or entity management.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   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

   Kick~partialclaimed3/10

   Kick offers some export surfaces — a Tax Package that bundles reports into a single Excel file and live Google Sheets sync of reports for AI tools to read — but there is no documented capability to export the full ledger/transactions/journal entries in bulk open formats (CSV/JSON) or a documented account-closure/migration export process; 'migration support' is only mentioned as a paid Advanced-tier perk with no detail. missing for 10: full-data export (transactions, journal entries, chart of accounts) in open formats, documented account closure/migration workflow, evidence of independent/hands-on export testing.

   • [claimed-docs] “The Tax Package generates a single Excel file with everything your accountant or tax preparer needs to file your taxes - no manual exports, …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”
   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”

   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

   Kick—none0/10

   Kick's evidence pack (security, pricing, integrations, multi-entity docs) never mentions data residency options, regional storage selection, or geographic data controls; only generic encryption-in-transit/at-rest claims are documented.

   • [claimed-docs] “"All data transmitted to and from Kick is encrypted in transit using TLS. Data at rest is encrypted using AES-256... Kick connects to your f…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Xero—none0/10

   No evidence pack item mentions AI-training data opt-out, data usage policies for model training, or any privacy controls addressing this specific concern; all evidence covers product features, SDKs, and MCP integration rather than data-training privacy controls.

   ⚑ flag

   Kick—none0/10

   Kick's evidence covers security (encryption, RBAC, audit trail) and AI-based categorization, but there is no documentation of an opt-out for AI/model training on user data, no privacy policy excerpt, and no data-usage/training statement of any kind.

   ⚑ flag

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

   Kick—none0/10

   The evidence covers encryption, RBAC, and audit trails but contains no mention of data retention policies, data export, or account/data deletion controls that a user could invoke. Nothing addresses this axis at all, so it applies but is unaddressed.

   ⚑ flag

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

   Kick—none0/10

   Kick is an accounting/bookkeeping SaaS product, and no evidence pack item addresses telemetry/usage-tracking opt-out settings, a privacy control panel, or any documented data-collection preferences for the product itself. The security doc only covers encryption and Plaid credential handling, not telemetry opt-out.

   ⚑ 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

   Kick~partialprobed4/10

   Kick documents an AI workflow where live report data lands in Google Sheets so Gemini/Claude/ChatGPT can read and reason over it, which could support a question like "can we afford X?", but this runs through a spreadsheet bridge, not a genuine public ledger API — probes show openapi/swagger endpoints all 404, and the only live MCP endpoint found serves GitBook documentation search, not ledger data or account actions. Missing for 10: a documented public API or account-scoped MCP server exposing live ledger data directly to agents, and any evidence of natural-language affordability Q&A being answered from it.

   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [claimed-docs] “Your Kick reports land as live spreadsheet data in your workbook, so Gemini, Claude, or ChatGPT can read and reason over them.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”

   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

   Kick—none0/10

   Evidence only shows that the Plus plan includes 'classes' as a feature label in pricing (kick-supp-pricing), but there is no documentation of a report builder that lets users filter/group by class, location, or tag dimensions, nor any mention of 'location' or 'tag' dimensions at all. Missing for 10: documented custom report builder UI, filter/group-by controls, evidence of location dimension, evidence of tag dimension.

   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   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

   Kick~partialclaimed6/10

   Kick's docs show a real double-entry ledger with live P&L and Balance Sheet organized by Chart of Accounts, updating in real time as transactions are categorized, plus period locking that keeps historical reports accurate for any locked period (kick-supp-coa, kick-supp-categorization, kick-supp-journal-entries, kick-supp-locks). However, no evidence explicitly confirms a cash-flow statement report or an 'any period on demand' report generator UI — missing for 10: explicit cash-flow statement documentation, evidence of arbitrary custom date-range reporting on demand, and independent/hands-on verification of statement accuracy.

   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “The Tax Package generates a single Excel file with everything your accountant or tax preparer needs to file your taxes - no manual exports, …”

   proof ↗⚑ flag