Zoho Books vs Kick

Agent access

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

   weight 2 · round to Kick
   Zoho Books~partialprobed5/10

   No llms.txt exists (confirmed 404) and the docs-in-markdown probe also 404s, so there's no dedicated agent-consumption doc format. However, Zoho does publish a downloadable OpenAPI spec (live-verified zip) and an explicit MCP integration page describing how to connect LLMs/agents to Zoho Books' APIs and actions, which serves a similar agent-onboarding purpose. Missing for 10: an actual llms.txt or markdown-native docs, and independent confirmation that agents can successfully parse/use the MCP or OpenAPI docs autonomously.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.zoho.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.zoho.com/books/api/v3/introduction/.md”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 Zoho Books
   Zoho Books~partialprobed6/10

   Zoho Books exposes a full REST API with OAuth2 tokens, documented rate limits, and a published OpenAPI spec, all of which support scripted/CI-driven automation without a UI, and MCP support adds agent-drivable actions. However, there is no evidence of a CLI, official SDK examples for CI pipelines, or headless/batch execution patterns beyond API calls, and OAuth token flow typically requires an initial interactive consent step not shown to be scriptable end-to-end. missing for 10: CLI tool, CI/headless-specific documentation or examples, fully non-interactive OAuth token provisioning, independent verification of automation in CI environments.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [claimed-docs] “Documented rate limits: "You can make 100 requests per minute per organization", per-plan daily call caps (the error payload for exceeding t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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
   Zoho Books—none0/10

   All MCP evidence describes Zoho positioning Books as an MCP *server* — external LLM agents (Claude, GPT) connect to Zoho's APIs and use Books' tools — the opposite direction from this story, which asks whether Zoho Books itself can act as an MCP client that plugs in and uses external MCP servers' tools. No evidence shows Books consuming outside MCP servers or its built-in Zia assistant connecting to third-party MCP tool providers.

   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “500+ integrations at your fingertips across Asana, Twilio, Zoho, and beyond.”

   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 Zoho Books
   Zoho Books✓fullclaimed8/10

   Zoho documents a Zoho MCP service (mcp.zoho.com) that explicitly connects LLMs like GPT/Claude to Zoho Books' APIs and actions, with customer quotes confirming real use for invoicing, bookkeeping, and reconciliation via Claude. This is an official first-party MCP server, not just client-side integration. Missing for 10: independent/hands-on verification of the MCP connection flow beyond vendor marketing quotes, and the hosted endpoint is sign-in-gated so behavior couldn't be directly probed.

   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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
   Zoho Books—none0/10

   Evidence covers a REST API, OAuth, OpenAPI spec, and an MCP server offering, but there is no mention of an official command-line interface (CLI) tool for Zoho Books; probes for llms.txt and doc-md endpoints also failed. This is a fair axis for an API-driven SaaS product, but no CLI evidence exists.

   ⚑ 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 Zoho Books
   Zoho Books✓fullprobed9/10

   Zoho Books ships a comprehensive, well-documented public REST API with OAuth2 auth, rate limits, extensive endpoint coverage (contacts, banking, reconciliation, orgs), and a live-verified downloadable OpenAPI spec confirming machine-readability. This directly satisfies an AI-native user's need to drive the product programmatically via documented public API. Missing for 10: independent third-party developer corroboration beyond vendor docs, and the llms.txt/openapi.json well-known probes returned 404 (though the actual OpenAPI zip works).

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [claimed-docs] “Documented rate limits: "You can make 100 requests per minute per organization", per-plan daily call caps (the error payload for exceeding t…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Step3: Generating Access and Refresh Tokens”

   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 Zoho Books
   Zoho Books~partialclaimed5/10

   Zoho Books documents OAuth 2.0 with a scopes catalog gating access per module, which provides a mechanism for issuing credentials with limited access rather than full account access, and MCP integration references agent-driven access. However, there is no evidence of fine-grained, per-action or per-record least-privilege scoping (e.g., read-only vs. write, or resource-level restriction) beyond module-level scopes, nor documentation of agent-specific credential issuance/revocation workflows distinct from human OAuth clients. missing for 10: granular least-privilege scope examples beyond module-level, agent-specific credential lifecycle management (issuance/rotation/revocation tailored to AI agents), independent/hands-on verification that scoped tokens restrict agent actions as claimed.

   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Step3: Generating Access and Refresh Tokens”

   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 drawn
   Zoho Books—none0/10

   The evidence pack documents a REST API, OAuth flow, rate limits, and a downloadable OpenAPI spec, but nowhere mentions official client SDKs (e.g., Python, Node, Java, PHP libraries) for Zoho Books; an OpenAPI zip is not itself an SDK. Missing for 10: any documentation of official language SDKs, package registry listings (npm/PyPI/Maven), or SDK usage guides.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”

   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
   Zoho Books—none0/10

   The evidence pack covers Zoho Books' REST API, OAuth, rate limits, OpenAPI spec, and MCP integration, but contains no mention of webhooks or event subscription mechanisms anywhere. Since webhook support is a plausible and common capability for an API-driven accounting platform, its complete absence from the evidence means the axis applies but is undocumented.

   ⚑ 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 Zoho Books
   Zoho Books✓fullclaimed7/10

   Zoho Books ships built-in AI (Zia) that gives plain-English queries, anomaly detection, and auto-suggested next actions on financial data, plus MCP-based agent access letting LLMs reason over and act on Books data. Evidence is vendor-sourced with some third-party customer quotes but lacks independent hands-on verification of insight quality. Missing for 10: independent/hands-on evaluation of Zia's insight accuracy, and concrete examples of specific AI-generated suggestions beyond marketing copy.

   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”

   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 to Zoho Books
   Zoho Books✓fullclaimed7/10

   Zoho Books documents native workflow automation (trigger workflows, bank rules, bulk categorization) and an MCP integration explicitly framed for 'fully autonomous agents [that] monitor, reason, and act without human input,' with customer quotes describing autonomous month-end closures and invoice handling via Claude/OpenClaw. This directly supports background, autonomous automation setups beyond simple manual triggers. missing for 10: independent/hands-on verification that MCP-driven agents persist and run unattended over time, and more detail on scheduling/triggers for background workflow execution beyond vendor marketing language.

   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 Zoho Books
   Zoho Books✓fullclaimed7/10

   Zoho Books documents a built-in AI assistant, Zia, that users can delegate tasks to in plain English — e.g. 'Ask Zia in plain English', sending bulk collection reminders, categorizing bank statements, and building workflow Blueprints automatically, all inside the product UI, distinct from the separate MCP-based external agent integration. This is first-party vendor documentation with concrete examples of task delegation. Missing for 10: independent or hands-on corroboration of Zia's task-delegation capability, and deeper documentation (e.g. feature list, screenshots) beyond a single marketing page's quotes.

   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 Zoho Books
   Zoho Books✓fullclaimed8/10

   Zoho Books ships an official MCP server connecting LLMs like GPT/Claude to its APIs so agents can act on natural instructions, plus built-in Zia AI for 'plain English' commands, with customer testimonials describing invoice/bill/bookkeeping tasks done via simple AI-driven instructions. Missing for 10: independent (non-vendor-quoted) hands-on verification of the MCP server's reliability and breadth of natural-language command coverage beyond the cited testimonials.

   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”

   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
   Zoho Books—none0/10

   Evidence shows static API docs, OAuth guides, and a downloadable OpenAPI zip, but nothing indicates an interactive reference with runnable/try-it-now examples; probes for machine-readable/live docs endpoints (llms.txt, docs.md, openapi.json paths) returned 404s, and there's no mention of a sandbox or 'try it' console.

   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.zoho.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.zoho.com/books/api/v3/introduction/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.zoho.com/openapi.json, https://www.zoho.com/swagger.json, https://www.zoho.com/api/opena…”

   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 Zoho Books
   Zoho Books✓fullprobed9/10

   Zoho Books publishes a downloadable OpenAPI document, live-verified via HEAD request returning HTTP 200 with a 349KB zip of the full API corpus, directly linked from the official API docs. missing for 10: no independent third-party confirmation of spec completeness/validity beyond the vendor-hosted file check.

   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”

   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
   Zoho Books—none0/10

   No evidence of a sandbox/test environment, demo org, or non-production API mode for AI agents to safely test against; the only isolation-like feature mentioned is a free plan with real financial thresholds, not a sandbox. There is also no mention of a 'test mode' flag or separate sandbox API endpoint distinct from the production organization_id-based API.

   ⚑ 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 Zoho Books
   Zoho Books~partialprobed4/10

   Zoho Books documents a versioned API (v3), OAuth 2.0 auth, rate limits, and a downloadable OpenAPI spec, but there is no evidence of a documented version-deprecation policy, sunset timeline, or changelog governing how v3 will be retired or migrated. missing for 10: explicit deprecation/sunset policy, versioning changelog, migration guides between API versions, and any stated support-lifecycle commitments.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Documented rate limits: "You can make 100 requests per minute per organization", per-plan daily call caps (the error payload for exceeding t…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”

   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 to Zoho Books
   Zoho Books✓fullclaimed8/10

   Zoho Books API documents explicit bulk endpoints (assign owner to multiple contacts, mark multiple contacts for 1099, bulk update/delete bank rules) and MCP integration lets AI agents drive these actions via natural instructions, with customer testimonials describing bulk workflows (month-end closures, bulk reminders) done via AI. Missing for 10: no independent hands-on verification of bulk operation limits/scale via MCP, and no explicit bulk invoice/expense creation endpoints documented.

   • [claimed-docs] “Assign an Owner to Multiple Contacts”
   • [claimed-docs] “Mark Multiple Contacts for 1099 Tracking”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 Zoho Books
   Zoho Books✓fullclaimed7/10

   Zoho Books documents genuine event/condition-based automation: 'Trigger workflow' rules to notify/update/validate on events, Bank Rules API for auto-categorizing transactions, and Zia AI turning data into automatic next steps (bulk reminders, categorization, Blueprints). MCP integration also lets AI agents trigger actions from natural instructions, corroborated by customer quotes. Missing for 10: independent hands-on verification of rule complexity/reliability, and detailed docs on the full workflow-rule builder (trigger types, conditions, action chaining) beyond marketing copy.

   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 to Zoho Books
   Zoho Books~partialclaimed4/10

   Zoho Books documents workflow automation ('Trigger workflow', Blueprints, AI-driven bulk reminders/categorization) and MCP-based agent actions, suggesting automation depth, but no evidence explicitly describes scheduling recurring jobs, cron-like triggers, or persistent recurring workflows for AI agents. Missing for 10: explicit recurring/scheduled job API or documentation, evidence of interval-based triggers, and independent confirmation that AI agents can set up recurring automations.

   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   proof ↗⚑ 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
   Zoho Books—none0/10

   Evidence shows workflow automation, AI/MCP integration, and audit trail for financial records, but there is no mention of versioning, reviewing, or rolling back automations/workflow definitions themselves. Missing for 10: automation version history, diff/review UI for workflow changes, rollback mechanism for automations.

   ⚑ 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 to Zoho Books
   Zoho Books~partialclaimed7/10

   Zoho Books exposes concrete reconciliation primitives (bank transaction categorization, bank reconciliation creation/listing, bank rules with match filters) plus Zia AI anomaly detection ('Spot anomalies before they become problems') and MCP access letting LLM agents act on Books data, with a customer testimonial claiming 'Month-end closures... reduced from hours to minutes' via Claude integration. However, there is no documented end-to-end orchestrated workflow that explicitly matches transactions, compiles an exception list, and stages a close for human sign-off as a single agent-driven process. Missing for 10: a documented structured exception-flagging/close-summary output, an explicit human-review handoff step, and independent (non-vendor-testimonial) verification of full month-end automation.

   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 to Zoho Books
   Zoho Books✓fullclaimed8/10

   Zoho Books explicitly documents connecting bank/credit-card accounts with automatic daily transaction import, categorization, and reconciliation workflows, backed by a full Bank Accounts/Bank Rules API for automation. Missing for 10: independent/hands-on user corroboration of daily-import reliability and any bank-feed coverage/outage caveats.

   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”

   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
   Zoho Books~partialclaimed5/10

   Zoho Books documents automatic bank feed import with categorization (Zia AI "categorizing bank statements") and an API/UI for categorizing transactions plus configurable Bank Rules for matching, but there is no evidence that suggestions adapt or improve specifically from user corrections (an explicit learning/feedback loop). Missing for 10: documented ML feedback loop showing suggestions improve after corrections, independent/hands-on confirmation of this adaptive behavior.

   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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
   Zoho Books~partialclaimed6/10

   Zoho Books documents bank feeds, transaction categorization, bank reconciliation creation/listing, bank statement summaries, and bank rules for matching, which together support surfacing matched/unmatched items during reconciliation; accountant collaboration is also documented. However, there is no explicit description of a duplicate-transaction detection/review UI or a dedicated reconciliation screen showing matched vs unmatched vs duplicate buckets. missing for 10: explicit documentation or hands-on evidence of duplicate-transaction flagging, a unified reconciliation review screen showing matched/unmatched/duplicate side-by-side, and independent (non-vendor) confirmation of the reconciliation workflow.

   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 Kick
   Zoho Books—none0/10

   The evidence pack shows generic Zoho Books workflow automation (trigger workflows, notifications), bank transaction categorization as 'vendor payment', and vague MCP-agent quotes about 'managing bills,' but nothing documents a specific bill-capture → approval-routing → payment-scheduling pipeline for accounts payable. Missing for 10: vendor bill entry/OCR capture docs, an approval-routing/Blueprint workflow specific to bills, and a scheduled/batch bill payment feature.

   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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
   Zoho Books~partialclaimed3/10

   Evidence shows generic 'custom reports' and accountant collaboration for 'generating reports', plus vendor-related bank transaction categorization, but nothing explicitly documents an accounts-payable aging report or vendor balance report as of a specific date. Missing for 10: explicit AP aging report documentation, vendor balance report screenshots/specs, point-in-time reporting capability evidence.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   proof ↗⚑ 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
   Zoho Books—none0/10

   No evidence of a period-locking/closing-books feature or explicit reopening workflow anywhere in the pack; mentions of month-end closing refer to reconciliation speed, not locking prior-period transactions from edits. missing for 10: documentation of a 'close books' or 'lock period' setting, permission controls around it, and an explicit 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
   Zoho Books~partialclaimed4/10

   Zoho Books documents strong reconciliation tooling (bank reconciliation API, auto-categorization, bank rules) and accountant collaboration access, plus a workflow-trigger engine and audit trail, and even a customer quote referencing faster 'month-end closures.' However, there is no evidence of a dedicated close checklist feature that explicitly tracks accrual entries or formal review/sign-off steps as a structured workflow. missing for 10: a named month-end close checklist UI, accrual-tracking/journal automation tied to close, and a documented sign-off/approval mechanism for reviewers.

   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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
   Zoho Books~partialclaimed7/10

   Zoho Books explicitly documents an accountant-invite feature: "Invite your accountant in Zoho Books to access real-time data... accountants can effortlessly manage your books from anywhere," covering journal entries, currency adjustments, reconciliation, and reports. However, the evidence does not detail granular role-scoping (custom permission levels, view-only vs edit controls) for that invited user. Missing for 10: explicit documentation of configurable role/permission scopes for accountant invites, and independent/hands-on confirmation of the invite flow in practice.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   proof ↗⚑ 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 Zoho Books
   Zoho Books~partialprobed4/10

   Zoho Books publishes a full REST API with an OpenAPI spec download and OAuth-based access, and states the API's goal is 'all the operations you do with our web client,' implying report access, but no evidence cites specific 'General Ledger' or 'Trial Balance' report endpoints or confirms these are exportable in open formats (JSON/CSV) via API. missing for 10: explicit GL/trial-balance report endpoint documentation, confirmed open-format export options, and independent verification of report API usage.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”

   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
   Zoho Books~partialclaimed6/10

   Bank feed automation is well documented (auto-import, categorization, reconciliation APIs) and general integration breadth (500+ apps, MCP) is claimed, but there is no explicit evidence of dedicated payments-gateway or payroll-system integrations feeding the ledger. Missing for 10: explicit payroll system connectors (e.g., Zoho Payroll or Gusto), explicit payment processor integrations (Stripe/PayPal) beyond generic '500+ integrations' claim, and independent confirmation these flows work end-to-end.

   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “500+ integrations at your fingertips across Asana, Twilio, Zoho, and beyond.”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 to Kick
   Zoho Books—none0/10

   The evidence pack shows general API/contact/organization creation endpoints, OAuth, banking reconciliation, and MCP/AI agent capabilities, but nothing addresses importing historical transactions, opening balances, or bulk migration from another accounting system (e.g., QuickBooks/Xero import tools, CSV bulk import, or a dedicated migration service) while preserving transaction-level detail.

   ⚑ 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 Kick
   Zoho Books~partialclaimed4/10

   Evidence confirms Zoho Books can 'generate invoices' and 'track payments' (via MCP/Zia docs), implying some invoicing and payment-tracking capability, but there is no explicit documentation of online payment gateway options embedded in invoices or of invoice 'viewed' status tracking. missing for 10: dedicated docs on online payment gateway/checkout options on invoices, evidence of 'viewed' status/read-receipt tracking, and any independent/hands-on confirmation of the payment/view workflow.

   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 to Zoho Books
   Zoho Books~partialclaimed5/10

   Evidence documents automated collection reminders ("sending bulk collection reminders") and workflow triggers that can notify customers, plus AI/MCP hooks for invoice tracking, but no citation explicitly describes a recurring-invoice scheduling feature. Missing for 10: explicit documentation of setting up recurring/repeating invoices, and independent/hands-on confirmation of the reminder automation working end-to-end.

   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”

   proof ↗⚑ 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
   Zoho Books~partialclaimed3/10

   Evidence confirms Zoho Books has contact/customer management and a customizable reporting engine ('generating reports... changing date range, adding columns, filters') that accountants can use, implying AR-related reporting capability, but no citation explicitly names an accounts-receivable aging report or per-customer balance view. missing for 10: explicit AR aging report documentation, explicit per-customer balance/statement feature, independent confirmation of these standard reports.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Create a Contact”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   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 Zoho Books
   Zoho Books~partialclaimed5/10

   Zoho Books has a documented Journal Entries-capable API, OAuth-based agent access, and MCP integration for agent-driven bookkeeping actions, plus accountant collaboration features, which together make agent-drafted journal entries plausible. However, there is no evidence of a dedicated 'draft/review queue' status or approval workflow for journal entries specifically, nor confirmation that journal entries can be created in a pending/unposted state for accountant review via API. missing for 10: explicit journal entry draft/pending status API field, a documented review-queue or approval workflow feature, and a hands-on example of an agent posting a journal entry that awaits accountant sign-off.

   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   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
   Zoho Books—none0/10

   The evidence pack contains no mention of chart of accounts customization, account types, sub-accounts, or class/tag dimensions—only unrelated docs on contacts, bank reconciliation, MCP, OAuth, and pricing. This is a core accounting feature that clearly applies to a bookkeeping product like Zoho Books, but no supporting evidence is provided.

   ⚑ 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 drawn
   Zoho Books~partialclaimed5/10

   Zoho Books documents accountant access to 'journal entries and base currency adjustments' via the accountant collaboration feature, confirming journal entry posting exists as a core feature, but there is no direct evidence of the journal entry UI/API showing debit/credit balancing enforcement or memo/attachment support. Missing for 10: explicit documentation of journal entry creation flow, balance validation, memo/notes fields, and attachment support for journal entries.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 to Zoho Books
   Zoho Books~partialclaimed6/10

   Zia AI is explicitly documented to 'Spot anomalies before they become problems' and Zoho MCP lets external agents (Claude, GPT) connect to Books data to 'monitor, reason, and act without human input,' with bank feed categorization and reconciliation APIs that an agent could use to review transactions before close. However, there is no explicit documentation of duplicate-transaction detection or a dedicated anomaly-flagging workflow across multiple entities/organizations, and evidence is vendor-marketing plus generic customer quotes rather than a demonstrated anomaly-detection feature spec. Missing for 10: explicit duplicate-transaction detection capability, documented multi-entity/cross-org anomaly rollup, and independent/hands-on verification of agent-driven anomaly flagging.

   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”

   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
   Zoho Books~partialclaimed3/10

   The features page briefly names an 'audit trail' as a Zoho Books capability, but the evidence pack gives no detail on what it captures (user, timestamp, field-level changes) or its coverage across the entire ledger/multi-entity setup — it's a single passing mention alongside unrelated features like custom reports. missing for 10: documentation of audit trail granularity (who/what/when), screenshots or hands-on verification, coverage confirmation across multiple organizations/entities, and independent corroboration.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   proof ↗⚑ 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
   Zoho Books~partialclaimed3/10

   Zoho Books supports creating multiple organizations and copying settings between them (zoho-books-docs-6, zoho-books-docs-7), which enables managing multiple legal entities separately, but there is no evidence of a consolidated financial reporting feature across organizations/entities. Missing for 10: documented consolidation/roll-up reporting across multiple organizations, inter-entity eliminations, or a unified consolidated financial statement feature.

   • [claimed-docs] “Create an organization”
   • [claimed-docs] “Copy settings to an organization”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 Zoho Books
   Zoho Books~partialprobed7/10

   Zoho explicitly states API parity as a design goal ('perform all the operations that you do with our web client'), backs it with a large, verified OpenAPI spec covering contacts, banking, reconciliation, rules, orgs, and 1099 workflows, plus documented OAuth scopes gating module access. However, there is no independent/hands-on verification confirming true 1:1 parity (e.g., UI-only settings, some organization-level admin actions), and the llms.txt/well-known OpenAPI discovery probes 404, showing openness/discoverability gaps for AI-native tooling. Missing for 10: independent confirmation of full UI-API parity with no exceptions, and standard machine-discoverable API metadata (llms.txt, well-known openapi.json) actually resolving.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.zoho.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.zoho.com/openapi.json, https://www.zoho.com/swagger.json, https://www.zoho.com/api/opena…”

   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 Zoho Books
   Zoho Books~partialprobed4/10

   Zoho Books never documents a dedicated 'export all data' or backup feature, but its REST API offers near-full parity with the web client ("perform all the operations that you do with our web client") plus a published OpenAPI spec, meaning a technical/AI-native user could programmatically pull out contacts, transactions, invoices, etc. in JSON via authenticated calls — a workaround path to open-format export rather than a first-class export/leave feature. Missing for 10: an explicit bulk-export or full-account-backup capability, documented standard export formats (CSV/Excel/JSON dump), and any migration/portability tooling or independent confirmation that a full data export actually works end-to-end.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”

   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 to Zoho Books
   Zoho Books~partialclaimed3/10

   The only relevant evidence is a brief mention that the API root documents "eight regional API domains," implying Zoho Books operates data centers in multiple regions — a proxy for data residency options — but there is no explicit documentation of a user-facing region/residency selection at signup or account level, nor any privacy-page confirmation of data locality guarantees. missing for 10: explicit account creation region-selection documentation, data residency/privacy policy statement, independent confirmation of regional data storage enforcement.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”

   proof ↗⚑ 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
   Zoho Books—none0/10

   No evidence in the pack addresses AI-training data usage policies, opt-outs, or data-privacy controls related to model training; the pack covers API docs, MCP integration, and features but nothing on training-data exclusion.

   ⚑ 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
   Zoho Books—none0/10

   The evidence pack covers API access, OAuth, MCP integration, and general accounting features, but contains no documentation of data retention policies, deletion controls, data export/purge APIs, or configurable retention periods for AI-native or any users. No mention of GDPR/CCPA deletion mechanisms, audit-trail retention settings, or account/data deletion workflows appears anywhere.

   ⚑ 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
   Zoho Books—none0/10

   No evidence in the pack addresses telemetry opt-out or usage tracking controls; the material covers API docs, OAuth, MCP integration, and accounting features but nothing about privacy settings or telemetry toggles.

   ⚑ 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 Zoho Books
   Zoho Books~partialclaimed6/10

   Zoho Books exposes live ledger data via a documented REST/OAuth API and OpenAPI spec, and Zoho MCP explicitly connects LLMs (GPT/Claude) to Books' data/actions with customer testimonials describing pulling reports and managing bookkeeping via natural-language agent instructions; Zia also markets 'pull reports just by asking'. However, there is no concrete evidence of an agent answering a specific affordability/cash-runway question grounded in live balances—no worked example, and MCP access is gated/unverified hands-on beyond vendor testimonials. Missing for 10: a demonstrated affordability-style query/answer flow, independent (non-vendor) confirmation of MCP grounding accuracy, and explicit cash-balance/afford-X reasoning support.

   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”

   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 to Zoho Books
   Zoho Books~partialclaimed4/10

   Evidence confirms Zoho Books supports custom reports with filters, columns, and date ranges (zoho-books-supp-accountant), but no citation explicitly documents reporting dimensions like class, location, or tags for grouping/filtering—only generic 'custom fields' and 'custom reports' are mentioned. Missing for 10: explicit documentation of class/location/tag tracking categories and their use as report filter/group dimensions, plus any hands-on or independent confirmation of this specific capability.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   proof ↗⚑ 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 to Kick
   Zoho Books~partialclaimed5/10

   Evidence confirms Zoho Books supports generating financial reports generally (custom reports with date-range/filter controls, MCP-enabled 'pull reports just by asking', accountant access to 'generating reports') but never explicitly names or documents P&L, balance sheet, or cash-flow statement generation specifically. Missing for 10: explicit documentation/screenshots of P&L, balance sheet, and cash-flow statement generation for arbitrary periods, and any independent/hands-on verification of their accuracy.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   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