Kick vs Bench

Agent access

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

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

   Bench—none0/10

   Bench is a bookkeeping service, not a dev tool/platform, but the axis still applies since any web product could publish agent-oriented docs; probes explicitly show llms.txt returns 404, docs-as-markdown 404, and no OpenAPI spec found. There is no evidence of any agent-oriented documentation surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

   Bench—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

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

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

   Bench—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 userDrive the product through a documented public API

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

   Bench—none0/10

   Bench is a bookkeeping/accounting service with no evidence of a documented public API; direct probes for llms.txt, docs.md, and OpenAPI/swagger endpoints all returned 404, and no docs mention an API for AI-native integration.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

   Bench—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

6. ai-native userBuild against official SDKs

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

   Bench—none0/10

   Bench is a bookkeeping/tax service with no evidence of any public SDK, API, or developer library; probes for llms.txt, docs-md, and OpenAPI specs all returned 404. Missing for 10: any official SDK, API documentation, or developer integration surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

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

   Bench—none0/10

   No evidence of any webhook subscription mechanism, API, or event system; probes for llms.txt, docs-md, and OpenAPI specs all return 404, and Bench is a human-plus-software bookkeeping service with no developer/webhook offering documented.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

Agentic features

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

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

   Bench—none0/10

   Bench's evidence describes automation (data entry, categorization) and human bookkeeper support, but nothing describes AI-generated insights, recommendations, or suggestions surfaced to the user from their data — 'smart automation' refers to categorization mechanics, not generative analysis or advisory insights. Missing for 10: any mention of AI-generated commentary, anomaly detection, forecasting, or proactive suggestions derived from financial data.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”

   proof ↗⚑ flag

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

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

   Bench—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

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

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

   Bench—none0/10

   Bench offers human bookkeepers plus automation for data entry and categorization, but there is no evidence of a built-in AI assistant that a user can delegate tasks to conversationally — communication is described as messaging with a human team, not an AI agent. Missing for 10: any mention of an AI assistant/chat feature, agentic task delegation, or AI-driven interaction surface within the product.

   • [claimed-docs] “Effortless messaging with your Bench team for unlimited support or advice, anytime, anywhere”
   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   Bench offers human-support messaging and a client dashboard, but there is no evidence of a natural-language command interface (chat-driven actions, NL query of financial data, etc.); probes for llms.txt, docs-md, and OpenAPI all 404, indicating no AI-native interface layer. missing for 10: any natural-language command/chat-to-action capability, NL query support, or API/agent interface evidence.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”
   • [claimed-docs] “Effortless messaging with your Bench team for unlimited support or advice, anytime, anywhere”

   proof ↗⚑ flag

Api quality

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

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

   Bench—none0/10

   Bench is a bookkeeping/accounting service with no API, no interactive API reference, and no runnable examples; probes for llms.txt, docs.md, and OpenAPI specs all returned 404. missing for 10: any API reference, interactive docs, runnable code examples.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   Probes explicitly show llms.txt, docs.md, and all openapi/swagger candidate paths return 404, and no docs mention any API spec; Bench is a bookkeeping service with no evidence of a machine-readable API for AI agents.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

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

   Bench—none0/10

   Bench is a bookkeeping/tax service with no evidence of a public API at all — probes for OpenAPI specs, docs, and llms.txt all returned 404. No mention of versioning or a deprecation policy anywhere in the evidence pack. Missing for 10: any public API, version numbers, changelog, or deprecation policy documentation.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   Bench is a human-plus-software bookkeeping service focused on categorization, reporting, and tax filing for individual accounts; no evidence describes any bulk/batch operation capability across many items (e.g., bulk transaction edits, bulk uploads, batch API operations) for AI-native or power users. Probes also show no API/docs surface for programmatic bulk actions.

   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   Bench is a bookkeeping/accounting service with backend automation for categorization and reminders, but there is no evidence of a user-facing rule engine where AI-native users can define custom triggers/actions on events; the automation described is fixed internal workflow, not configurable rules.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

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

   Bench—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

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

   Bench—none0/10

   Bench's evidence describes automated data entry/categorization plus human bookkeepers preparing reports, not an autonomous agent that reconciles a month end-to-end, flags exceptions, and stages a close for human review. No documentation of exception-flagging logic, agent-driven reconciliation workflow, or AI-native interface exists in the pack. Missing for 10: evidence of automated exception detection, an agentic reconciliation workflow, and any API/agent interface for month-end close.

   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Bank feeds

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

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

   Bench✓fullclaimed7/10

   Bench's docs explicitly describe connecting all financial accounts to automate daily data entry and transaction categorization, which directly matches the story of automatic daily import via connected bank/credit card accounts. Missing for 10: no independent/hands-on corroboration of connection reliability, no detail on supported bank list or sync frequency specifics beyond marketing copy.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”

   proof ↗⚑ flag

Categorization

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

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

   Bench~partialclaimed4/10

   Bench documents automated, 'smart automation' transaction categorization with 'instant guidance' (bench-docs-4, bench-supp-automation), which covers the core categorization-suggestion capability, but since Bench is a human-plus-software bookkeeping service, human bookkeepers—not the software—typically apply corrections, and there is no evidence describing a feedback loop where the system learns from founder corrections. Missing for 10: any documentation of a correction-learning mechanism, founder-facing feedback UI, or improvement in suggestion accuracy over time.

   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Reconciliation

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

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

   Bench—none0/10

   Bench's evidence covers account connection, automated categorization, and reporting, but no citation describes a reconciliation workflow that surfaces matched, unmatched, and duplicate transactions for accountant review. missing for 10: explicit reconciliation UI/workflow, matched/unmatched transaction views, duplicate detection and review surface.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Bill management

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

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

   Bench—none0/10

   Bench is a bookkeeping/tax service focused on categorization, reporting, and human bookkeeper support; no evidence of bill capture (AP inbox/OCR), approval routing, or scheduled bill payment workflows anywhere in the docs, pricing, or banking pages.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “"Banking by Mainstreet — Get dedicated business accounts, debit cards, and automated financial management tools that integrate seamlessly wi…”
   • [claimed-docs] “Published service pricing: Bookkeeping Grow from $199/month ("An accessible, lighter-touch plan—built for lean businesses seeking financial …”

   proof ↗⚑ flag

Payables

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

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

   Bench—none0/10

   Bench's evidence covers bookkeeping automation, categorization, income statement/balance sheet reporting, banking and tax prep, but nowhere mentions accounts payable aging, vendor balances, or bill-tracking reports at a point in time. Bench appears to focus on income statement/balance sheet reporting rather than AP-specific aging reports.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”

   proof ↗⚑ flag

Close process

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

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

   Bench—none0/10

   No evidence describes period locking, close controls, or reopening workflows; Bench is presented as a human-plus-software bookkeeping service with reporting/downloads, not a ledger system with period-lock controls exposed to the accountant/customer. missing for 10: any mention of period closing, locking prior periods, or explicit reopening controls.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   Bench markets itself as a done-for-you bookkeeping/tax service with messaging, document upload, categorization, and real-time reports, but nothing in the evidence describes a month-end close checklist tracking reconciliations, accruals, or review sign-offs — only generic 'timely reminders' are mentioned, which is not the same as a structured close workflow.

   • [claimed-docs] “Get timely reminders to stay on top of your financial tasks and deadlines”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

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

   Bench—none0/10

   Bench's evidence describes a done-for-you bookkeeping service where Bench's own staff manage the books and communicate with the founder, with no mention of inviting an external accountant/bookkeeper as a role-scoped collaborator with adjustable permissions inside a shared ledger. The 'Add a bookkeeper to your team' claim refers to Bench's own hire-a-bookkeeper offering working inside the founder's existing systems, not the founder granting scoped access to their own outside accountant.

   • [claimed-docs] “Add a bookkeeper to your team who works with your existing systems”
   • [claimed-docs] “Published service pricing: Bookkeeping Grow from $199/month ("An accessible, lighter-touch plan—built for lean businesses seeking financial …”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Data access

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

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

   Bench—none0/10

   Bench only offers report viewing/downloads (income statement, balance sheet) via its web app; there is no documented API, no OpenAPI/Swagger spec, and probes for llms.txt, markdown docs, and OpenAPI endpoints all returned 404s, so developers have no documented way to pull the GL or trial balance in open formats.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Integrations

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

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

   Bench~partialclaimed6/10

   Bench's docs claim customers can 'connect all your financial accounts to automate data entry' and offers integrated banking (Banking by Bench/Mainstreet), which supports bank/payment account linking flowing into bookkeeping. However, payroll integration is never explicitly mentioned, and the ledger itself is not customer-facing/editable — it's a human-plus-software service producing reports rather than a live self-serve ledger. missing for 10: explicit payroll system integration, technical detail on connection breadth (which banks/payment processors), independent/hands-on confirmation of automated data flow reliability.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Get dedicated business accounts, debit cards, and automated financial management tools that integrate seamlessly with your bookkeeping opera…”
   • [claimed-docs] “"Banking by Mainstreet — Get dedicated business accounts, debit cards, and automated financial management tools that integrate seamlessly wi…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Migration

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

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

   Bench~partialclaimed5/10

   Bench explicitly offers 'Catch Up Bookkeeping' for businesses behind on their books, implying it can reconstruct/backfill historical transaction data, and its human-bookkeeper model suggests manual handling of past records. However, there is no explicit documentation of migrating data from another accounting system (e.g., QuickBooks, Xero) with transaction-level fidelity preserved, no import tooling, and no evidence addressing loss/retention of transaction detail during migration. Missing for 10: explicit migration/import process from other platforms, evidence of transaction-level data preservation, any tooling or API for historical data transfer.

   • [claimed-docs] “Catch up bookkeeping services for small businesses, no matter how far behind they are”
   • [claimed-docs] “Add a bookkeeper to your team who works with your existing systems”
   • [claimed-docs] “The buying motion is demo-led for service fit: "Book a demo with our friendly team of experts. Not sure where to start or which accounting s…”

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

   Bench—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

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

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

   Bench—none0/10

   Bench is a bookkeeping/tax service focused on categorization, reporting, and tax filing; there is no mention of invoicing, accounts receivable, recurring invoices, or customer payment reminders anywhere in the evidence pack.

   ⚑ flag

Receivables

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

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

   Bench—none0/10

   Bench's evidence covers reporting (income statement, balance sheet), categorization, and banking, but there is no mention of accounts receivable aging reports or per-customer balance tracking anywhere in the docs or probes. Missing for 10: any AR aging report feature, per-customer balance tracking, invoicing/AR module documentation.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Ai ledger

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

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

   Bench—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

Chart of accounts

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

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

   Bench—none0/10

   Bench is a done-for-you bookkeeping service where a human bookkeeper manages the books; the evidence pack shows no self-serve chart-of-accounts customization, account types, sub-accounts, or class/tag dimension configuration exposed to the accountant/customer. The client-facing surface is reports and downloads, not ledger/CoA editing. Missing for 10: any mention of CoA management, account type/sub-account creation, or class/tag dimension tagging capability.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Journal entries

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

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

   Bench—none0/10

   Bench is a done-for-you bookkeeping service where Bench's own staff (not the customer) manage the books; evidence explicitly states the client-facing surface is reports/downloads, 'not a ledger the customer posts to' (bench-supp-reporting), with no mention of a journal-entry interface, debit/credit balancing, or memo fields for accountant users. Missing for 10: any UI or workflow for entering/posting journal entries, debit/credit validation, and memo/supporting-documentation attachment on entries.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

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

   Bench—none0/10

   Bench is a human-plus-software bookkeeping service with automated categorization and real-time reporting, but there is no evidence of an AI agent that actively monitors the ledger for anomalies or duplicate transactions ahead of close; the closest capability is human bookkeeper review and periodic reminders. missing for 10: agent-based anomaly detection, duplicate-transaction flagging, any pre-close audit automation.

   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

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

   Bench—none0/10

   Bench is a service where a human bookkeeper does the books, and the client-facing surface is reports/downloads rather than a ledger with visible change history; no evidence of any audit-trail, version history, or user-attribution feature is present anywhere in the pack, and probes confirm no docs/API surfacing such capability. missing for 10: any mention of audit logs, change tracking, user attribution, or timestamped edit history across the ledger.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

Multi entity

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

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

   Bench—none0/10

   Bench is a single-entity small-business bookkeeping/tax service; nothing in the evidence mentions multi-entity management, consolidation, or intercompany eliminations. Missing for 10: multi-entity account structure, consolidated financial statements across entities, intercompany reconciliation/eliminations.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   No API, OpenAPI spec, or developer documentation exists; probes for llms.txt, docs.md, and openapi.json all return 404s, and all evidence describes a UI/human-service product with no programmatic access surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   No evidence of data export in open/portable formats or account portability; reporting is limited to viewing/downloading income statements or balance sheets, not a full data export mechanism, and probes for llms.txt/openapi/docs all 404. missing for 10: explicit data export feature (CSV/QBO/API), documented data portability policy, evidence of ability to leave with full underlying data.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls; Bench's marketing focuses on bookkeeping automation, tax, and banking, with no data-residency documentation and 404s on technical/API probes that might have revealed such settings.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

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

   Bench—none0/10

   Bench is a bookkeeping/accounting service and no evidence pack item mentions AI training data usage, opt-out controls, or any privacy policy addressing model training; this is an applicable privacy-posture axis for any modern SaaS handling customer data, but no supporting or contradicting evidence exists. Missing for 10: any privacy policy statement, opt-out mechanism, or terms-of-service language regarding AI/ML training on customer data.

   ⚑ flag

3. ai-native userControl data retention and deletion

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

   Bench—none0/10

   Bench is a human-plus-software bookkeeping service; no evidence in the pack addresses data retention policies, deletion controls, or export/delete-your-data mechanisms for AI-native users. Probes for docs/llms.txt/openapi all 404, and no privacy/retention page is cited. missing for 10: retention policy documentation, data deletion/export controls, privacy posture disclosures, any AI-specific data handling terms.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

Ai insights

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

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

   Bench—none0/10

   No evidence of any public API, MCP server, or AI-agent integration exposing ledger data; probes for llms.txt, docs-md, and OpenAPI all returned 404s, and reporting is described as human-facing downloads/dashboards, not programmatic access. missing for 10: any API/endpoint for ledger data, agent integration, documented query interface for financial questions.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Custom reports

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

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

   Bench—none0/10

   Evidence only shows basic reporting (income statement, balance sheet) delivered as static downloads/reports, with no mention of custom report building or filtering/grouping by class, location, or tag dimensions. Bench is positioned as a done-for-you bookkeeping service, not a self-serve reporting tool with dimensional tagging capabilities.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Statements

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

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

   Bench✓fullclaimed8/10

   Bench explicitly markets real-time reporting with income statement (P&L) and balance sheet access/download at all times, backed by automated categorization and human bookkeeper review for accuracy. Cash-flow statement generation is not explicitly named, and there's no independent/hands-on corroboration of accuracy beyond vendor claims. Missing for 10: explicit mention of cash-flow statement as a deliverable report, and third-party or user corroboration of report accuracy.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag