FreshBooks vs Kick

Agent access

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

   weight 2 · round to Kick
   FreshBooks—none0/10

   Direct probes show no llms.txt (404) and no markdown-based docs (404), and no evidence exists of an agent-oriented documentation format; only standard human-facing API docs are present.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   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 FreshBooks
   FreshBooks~partialclaimed4/10

   FreshBooks exposes a full REST API (invoices, expenses, journal entries, reports) with OAuth2 auth and an official Node.js SDK, which lets scripts/services call it headlessly outside the UI. However there is no CLI, Docker image, or explicit CI/CD integration guidance, and no evidence anyone has run FreshBooks automation in a pipeline context. missing for 10: CLI or headless runner, CI/CD-specific documentation or examples, independent evidence of CI usage.

   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [github] “Get/set data from FreshBooks using the REST API.”
   • [claimed-docs] “Authentication - FreshBooks”

   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 userConnect an agent via an official MCP server

   weight 3 · round drawn
   FreshBooks—none0/10

   FreshBooks offers a REST API, webhooks, and SDKs, but there is no evidence of an official MCP server for agent connectivity; probes for llms.txt and docs.md both returned 404. Since FreshBooks is a SaaS platform (not itself an agent), an official MCP server is a plausible offering, so its absence is 'none' rather than 'na'.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”

   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

4. ai-native userUse an official CLI

   weight 2 · round drawn
   FreshBooks—none0/10

   No evidence of an official CLI tool; FreshBooks only offers a REST API, SDKs (Node.js), and Postman collection, with no mention of a command-line interface. Probes for llms.txt and docs.md also returned 404s.

   • [github] “Get/set data from FreshBooks using the REST API.”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   proof ↗⚑ 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

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

   weight 3 · round to FreshBooks
   FreshBooks✓fullclaimed8/10

   FreshBooks publishes a well-documented public REST API covering invoices, expenses, payments, journal entries, reports, and webhooks, with OAuth 2.0 authentication, scopes, pagination, error handling, an official Node.js SDK, and a Postman collection — enabling programmatic/agentic control of core accounting workflows. Missing for 10: no llms.txt or machine-readable docs endpoint (probe 404s) and no independent third-party corroboration of API robustness beyond first-party docs.

   • [claimed-docs] “Authentication - FreshBooks”
   • [claimed-docs] “Search, Paging and Includes - FreshBooks”
   • [claimed-docs] “Webhook Callbacks - FreshBooks”
   • [claimed-docs] “Invoices - FreshBooks”
   • [claimed-docs] “Expenses - FreshBooks”
   • [claimed-docs] “Journal Entries - FreshBooks”
   • [claimed-docs] “Other Reports - FreshBooks”
   • [claimed-docs] “Errors - FreshBooks”
   • [claimed-docs] “Postman Collection”
   • [github] “Get/set data from FreshBooks using the REST API.”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”

   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

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

   weight 2 · round to FreshBooks
   FreshBooks~partialclaimed6/10

   FreshBooks documents OAuth 2.0 authentication with per-endpoint scopes and a dedicated tutorial for finding the right scopes for an app, which supports issuing least-privilege credentials to any third-party client including an agent. However, there is no explicit mention of AI-agent use cases, no granular API-key/service-account model beyond OAuth scopes, and no guidance on revocation or monitoring specifically for autonomous agents. Missing for 10: agent-specific credential guidance, fine-grained scope examples beyond a generic tutorial reference, and independent confirmation of scope enforcement in practice.

   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “Authentication - FreshBooks”

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to FreshBooks
   FreshBooks~partialprobed6/10

   FreshBooks publishes an official Node.js SDK on GitHub with REST API bindings and pre-configured auth, backed by extensive REST API docs (auth, webhooks, invoices, expenses, payments, journal entries, reports) and a Postman collection/'Tools and Libraries' page for building integrations. However, evidence only shows one official SDK (Node.js) with no other languages, no AI-native docs formats (llms.txt and docs.md both return 404), and no independent developer corroboration of SDK quality or maintenance. Missing for 10: multi-language official SDKs, machine-readable/agent-friendly docs, and third-party validation of the SDK's reliability.

   • [github] “Get/set data from FreshBooks using the REST API.”
   • [github] “Pre-configured [ExpressJS](https://expressjs.com/) app. Includes authentication via [PassportJS](http://www.passportjs.org/).”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “Postman Collection”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to FreshBooks
   FreshBooks✓fullclaimed8/10

   FreshBooks documents a real webhook subscription system: registering callbacks (e.g. invoice.create), a verification handshake, and HMAC-based signature verification, with an explicit caveat about delivery latency. This directly satisfies the story of subscribing to events via webhooks. Missing for 10: independent/hands-on developer confirmation of webhook reliability and no evidence of a broader event catalog beyond a few examples.

   • [claimed-docs] “Webhook Callbacks - FreshBooks”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”

   proof ↗⚑ 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 Kick
   FreshBooks—none0/10

   No evidence of AI-generated insights, suggestions, or analytics features anywhere in the docs, API surface, or community mentions; the product focuses on invoicing, expense tracking, and reporting without any AI/ML layer mentioned. Missing for 10: any mention of AI-driven insights, anomaly detection, predictive suggestions, or natural-language analysis of financial data.

   ⚑ flag

   Kick~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   FreshBooks~partialclaimed4/10

   FreshBooks offers building blocks—webhooks, journal entry/reports APIs, bank reconciliation automation, and Bill Pay automated scheduling—that could support autonomous background workflows, but there is no evidence of a native automation/agent framework, scheduled triggers, or persistent background jobs configurable by an AI-native user. missing for 10: a documented automation/rules engine or agent-runnable scheduler, evidence of autonomous multi-step workflows beyond webhooks+bill pay, and independent confirmation of reliability for unattended background operation.

   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

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

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

   No evidence of a natural-language interface, chatbot, or AI assistant for operating FreshBooks; only a developer REST/OAuth API and webhooks are documented, which require code, not NL commands. Probes for llms.txt and machine-readable docs both returned 404, further suggesting no AI-native interaction layer.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”

   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 to FreshBooks
   FreshBooks~partialprobed3/10

   FreshBooks publishes a full REST API reference (auth, endpoints, errors, webhooks) and offers a Postman Collection that lets developers run example requests, which partially satisfies 'runnable examples,' but there's no evidence of an embedded interactive console (e.g., try-it-now code snippets) in the docs themselves, and llms.txt/docs-md probes returned 404s indicating no AI-native doc tooling. missing for 10: an in-browser interactive API console with live runnable requests, AI-readable doc formats (llms.txt/markdown), and independent confirmation of the Postman collection's usability.

   • [claimed-docs] “Postman Collection”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

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

   FreshBooks documents a REST API with a Postman collection and SDKs, but nothing in the evidence indicates an OpenAPI/Swagger spec or other machine-readable API description is published or downloadable; explicit probes for llms.txt and a machine-readable docs endpoint both returned 404.

   • [claimed-docs] “Postman Collection”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

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

   No evidence of a sandbox/test environment, test-mode API keys, or demo accounts; the API docs cover authentication, endpoints, and webhooks but nothing about non-production testing.

   ⚑ flag

   Kick—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   FreshBooks—none0/10

   FreshBooks publishes a REST API with docs, authentication, webhooks, and an API changelog note about swapping legacy bearer tokens for JWTs, but there is no evidence of a versioning scheme (e.g., v1/v2 endpoints) or a documented deprecation policy/timeline for API changes. The changelog mention shows change happened but not a stated deprecation process, and llms.txt/docs-md probes 404, showing no AI-native API governance documentation.

   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

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

   The API docs cover single-resource CRUD endpoints (invoices, expenses, payments, journal entries) plus search/paging/webhooks, but no evidence describes batch or bulk-operation endpoints (e.g., bulk invoice creation, bulk expense updates) that would let an AI agent act on many items in one call.

   • [claimed-docs] “Search, Paging and Includes - FreshBooks”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “Invoices - FreshBooks”
   • [claimed-docs] “Expenses - FreshBooks”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Kick
   FreshBooks~partialclaimed4/10

   FreshBooks exposes webhooks for real-time event notifications (e.g., invoice.create) that could be wired to external actions, but there is no evidence of a native rules/automation engine where users define conditional triggers and actions inside the product itself; webhooks require external code to act on events. Missing for 10: in-app rule builder, conditional logic UI, natively triggered actions without custom integration, and evidence of AI-native automation workflows.

   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “Webhook Callbacks - FreshBooks”

   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 FreshBooks
   FreshBooks~partialclaimed4/10

   FreshBooks Bill Pay documents scheduled/recurring vendor payments ("schedule payments" and "executes your scheduled payments so nothing slips"), and webhooks provide event-driven sync, but there is no evidence of a general-purpose recurring job/workflow scheduler exposed via API for AI-native automation (e.g., recurring invoices, scheduled reports, or cron-like triggers callable by an agent). Missing for 10: API endpoint or docs for recurring invoice/report scheduling, evidence of programmatic (not just UI) recurring workflow setup, and confirmation this extends beyond bill payments to general automation.

   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “FreshBooks Bill Pay* makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check.”
   • [claimed-docs] “Forward your bills to your FreshBooks account, schedule vendor payments, and watch each payment move from created to paid.”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”

   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

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

   FreshBooks documents automated bank-reconciliation workflows and a rich API (journal entries, reports, payments, expenses) that a third party could use to build an agent, but there is no evidence of an AI agent that autonomously matches transactions, flags exceptions, and prepares a month-end close for review — reconciliation here is rule-based software automation, not an agentic capability.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”

   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 Kick
   FreshBooks✓fullclaimed6/10

   FreshBooks' own accounting page explicitly states you can 'link your bank account and create automated workflows for bank reconciliation and transaction management' and lists bank reconciliation among its 100+ automations, directly matching the founder's need for automatic daily transaction import. Missing for 10: independent/hands-on confirmation of daily import cadence, credit-card-specific linking details, and any troubleshooting/reliability reports beyond the vendor's own claim.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”

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

   FreshBooks evidence mentions bank account linking and 'automated workflows for bank reconciliation and transaction management' but contains no mention of a categorization engine that suggests categories for imported transactions or that improves from user corrections. Missing for 10: any documentation of transaction categorization suggestions, machine-learning/rules-based category prediction, or confirmation that the system learns from user corrections.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”

   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 to Kick
   FreshBooks~partialclaimed4/10

   FreshBooks documents bank account linking and 'automated workflows for bank reconciliation and transaction management' plus a chart of accounts and accountant collaboration, but there's no evidence of the specific UI/workflow for surfacing matched, unmatched, and duplicate transactions for review. missing for 10: explicit documentation of matched/unmatched/duplicate transaction states, reconciliation review screen, independent or hands-on confirmation of the reconciliation workflow.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”

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

   FreshBooks Bill Pay documents bill capture ('Upload a file or snap a photo; Bill Pay reads the details and recreates the bill') and payment scheduling/execution by ACH or check, covering capture-to-payment scheduling in one workflow. However, there is no evidence of a distinct approval-routing step (multi-user sign-off before payment) — missing for 10: documented approval workflow/routing feature, evidence of multi-step sign-off controls, and independent/hands-on confirmation of the Bill Pay flow.

   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “FreshBooks Bill Pay* makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check.”
   • [claimed-docs] “Forward your bills to your FreshBooks account, schedule vendor payments, and watch each payment move from created to paid.”

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

   FreshBooks Bill Pay lets you manage and schedule vendor bill payments, and the Reports API exposes seven report types, but none of the evidence mentions an accounts-payable aging report or point-in-time vendor balance report — only due-date tracking and payment status. missing for 10: AP aging report, vendor balance/statement report, point-in-time historical AP view.

   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “FreshBooks Bill Pay* makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check.”

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

   No evidence pack item mentions period locking, closing periods, or preventing edits to prior-period transactions without explicit reopening; FreshBooks docs cover invoicing, journal entries, reports, and API access but nothing about close controls.

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

   FreshBooks documents bank reconciliation automation, journal entries, and accountant collaboration, but there is no evidence of a structured month-end close checklist that tracks reconciliations, accruals, and review sign-offs as a workflow feature — no mention of accrual entries, close tasks, or approval/sign-off tracking. missing for 10: close checklist/task tracking, accrual entry workflows, review sign-off or approval features.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

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

   FreshBooks explicitly documents accountant collaboration: "Grant your accountant access to real-time data in one central location" and accountants can "update your journal entries and chart of accounts... run reports, file taxes", alongside a paid Team Members role add-on for scoped user access. This directly matches the founder story of inviting an external accountant with role-based access to adjust books. Missing for 10: independent/hands-on confirmation of the granularity of role-scoping (what an accountant role can/cannot see or edit) and details of the actual invite UX flow.

   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “Team Members ($11/mo per user)”
   • [claimed-docs] “FreshBooks gives you the tools you need for tasks like invoicing, billing your clients, preparing detailed financial reports, and making inf…”

   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 FreshBooks
   FreshBooks~partialclaimed4/10

   FreshBooks documents a REST API with Journal Entries and 'Other Reports' endpoints (including Manual Journal Entry and Payments Collected reports) that expose ledger-level data in JSON via OAuth2, giving developers programmatic access to accounting data. However, no evidence names a dedicated 'General Ledger' or 'Trial Balance' report/endpoint, nor confirms export in open formats like CSV/OFX beyond JSON API responses. Missing for 10: explicit General Ledger and Trial Balance report endpoints, confirmation of open-format exports (CSV/OFX), independent developer confirmation of pulling these specific reports.

   • [claimed-docs] “Journal Entries - FreshBooks”
   • [claimed-docs] “Other Reports - FreshBooks”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”

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

   FreshBooks documents linking bank accounts for automated reconciliation, embedded payroll as part of its 100+ integrations, online payment collection (cards/ACH/etc.), and a dedicated Bill Pay product for vendor payments that syncs into the ledger — collectively covering banking, payments, and payroll flowing into the books automatically. Missing for 10: independent/hands-on confirmation that bank feeds and payroll sync work reliably in practice, and more detail on which specific bank/payroll providers are supported.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “Get paid with credit and debit cards, ACH bank transfer, Apple Pay, Google Pay, and Buy Now, Pay Later”
   • [claimed-docs] “FreshBooks Payroll ($40/mo plus $6/mo per user)”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”

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

   No evidence in the pack mentions data migration, import tools, historical transaction import, or conversion from other accounting systems (e.g., QuickBooks). The API surface (invoices, expenses, journal entries) could theoretically support a custom migration, but there's no documented migration feature, import wizard, or third-party migration tool referenced.

   ⚑ 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 FreshBooks
   FreshBooks✓fullclaimed8/10

   FreshBooks docs confirm invoice creation with customizable payment options, multiple online payment methods (cards, ACH, Apple/Google Pay, BNPL), and a Payments API with webhook notifications (e.g., invoice.create) enabling read status/paid tracking. This directly covers create/send invoices, online payment, and view/paid visibility. Missing for 10: explicit documentation or screenshot of an invoice 'viewed' read-receipt status in the UI, and independent/hands-on confirmation of the view-tracking feature beyond API/webhook inference.

   • [claimed-docs] “Create professional invoices in minutes. Automatically add tracked time and expenses, calculate taxes, and customize your payment options.”
   • [claimed-docs] “Get paid with credit and debit cards, ACH bank transfer, Apple Pay, Google Pay, and Buy Now, Pay Later”
   • [claimed-docs] “Invoices - FreshBooks”
   • [claimed-docs] “Payments - FreshBooks”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   FreshBooks—none0/10

   The evidence pack covers general invoicing, payment methods, expense tracking, bill pay (for outgoing vendor bills), and API endpoints, but nowhere mentions recurring invoice scheduling or automated reminders to customers for overdue invoices. This is a core, plausible capability for an invoicing/AR product, so the axis applies, but no citation confirms it. missing for 10: explicit documentation of recurring invoice setup, automatic overdue payment reminder configuration.

   ⚑ 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
   FreshBooks~partialclaimed4/10

   FreshBooks documents invoicing, per-client entities (Clients API), and a Reports API with 'seven types of reports' including Invoice Details and Payments Collected, implying customer-level transaction data is queryable, but no evidence explicitly names an accounts-receivable aging report or a dedicated per-customer balance view. Missing for 10: explicit aging-report feature documentation, explicit per-customer outstanding-balance report, and any UI/API confirmation of AR-specific terminology.

   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “Invoices - FreshBooks”

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

   FreshBooks' API documents a Create Adjustment Journal Entry endpoint with required fields (account_uuid, debit/credit), OAuth2 authentication, and webhooks for real-time sync, which together could let an agent draft and post journal entries programmatically. However, there is no evidence of a native 'review queue' or draft/approval workflow before posting — entries appear to post directly rather than sit pending accountant review, and no accountant-approval or draft-state mechanism is documented. missing for 10: a documented draft/pending state or approval workflow for journal entries, evidence of an accountant-facing review queue, and any hands-on/independent confirmation of agent-driven posting.

   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”

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

   FreshBooks docs mention a 'customizable chart of accounts' and journal entries referencing account_uuid via the Get Accounts endpoint, showing basic COA existence and editability, but there is no evidence of account type configuration, sub-account hierarchies, or class/tag dimensions for transaction tagging. missing for 10: account type customization, sub-account/hierarchy support, class or tag dimension tracking, independent corroboration of these features.

   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

   proof ↗⚑ flag

   Kick~partialclaimed6/10

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

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

   proof ↗⚑ flag

Journal entries

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

   weight 3 · round to FreshBooks
   FreshBooks~partialclaimed6/10

   FreshBooks documents a Journal Entries API/UI supporting double-entry postings that require account_uuid plus debit or credit amounts, and it exposes a 'Manual Journal Entry' report, confirming balanced-entry posting is possible alongside accountant collaboration on the chart of accounts. However, evidence does not show a memo/description field for supporting notes, nor explicit validation that entries must balance, nor first-party UI walkthroughs (only API-level docs) confirming this journal entry flow end-to-end. Missing for 10: explicit memo/note field support, explicit balance-validation behavior, and independent/hands-on confirmation of the manual journal entry UI workflow.

   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Journal Entries - FreshBooks”

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

   FreshBooks exposes API access to expenses, journal entries, and reports plus webhooks (freshbooks-supp-journal-entries, freshbooks-supp-reports-api, freshbooks-supp-webhooks), which a third party could use to build an external monitoring agent, but there is no evidence of any native AI/agent-based anomaly detection, duplicate-transaction flagging, or pre-close audit capability shipped by FreshBooks itself.

   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”

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

   No evidence pack item mentions an audit log, change history, user attribution for edits, or timestamped audit trail across the ledger; only journal entries, reports, and accountant access are documented without any change-tracking feature. This is a plausible axis for accounting software, so absence of evidence yields 'none' rather than 'na'.

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

   FreshBooks is designed for single-business invoicing/bookkeeping (per-account chart of accounts, journal entries, reports) and no evidence pack item mentions multi-entity management, inter-company eliminations, or consolidated financial statements across separate legal entities. This is a fair question for an accounting product to ask, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

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

   FreshBooks documents a broad REST API (invoices, expenses, payments, journal entries, reports, clients, taxes, bills-beta) with OAuth, webhooks, and an official SDK, covering most core accounting workflows an AI agent could drive. However, several UI-surfaced features (Bill Pay automation, Payroll, Team member management, human Bookkeeping service tier) are only described as product/marketing features with no corresponding API endpoints in the evidence, and there's no independent confirmation of full UI-API parity. Missing for 10: API coverage confirmation for Bill Pay, Payroll, Team Members, and Bookkeeping service; independent/hands-on verification of parity claims.

   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “FreshBooks Payroll ($40/mo plus $6/mo per user)”
   • [claimed-docs] “Team Members ($11/mo per user)”
   • [claimed-docs] “A human bookkeeping tier sits alongside the software: "Get tax-ready with professional bookkeeping services for small business" with "Dedica…”

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

   FreshBooks exposes a full REST API (invoices, expenses, payments, journal entries, reports) with an official SDK, letting AI-native users programmatically extract virtually all their data in JSON, which is a reasonably open format. However there is no documented bulk export-to-open-format (CSV/JSON dump) feature, no data portability/GDPR export tool, and probes show no llms.txt or markdown docs, suggesting export is only via manual API integration rather than a one-click 'leave with your data' path. missing for 10: a native bulk data export/download feature, documented data portability guarantees, and independent evidence of successful full-account export via the API.

   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [github] “Get/set data from FreshBooks using the REST API.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   proof ↗⚑ flag

   Kick~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   FreshBooks—none0/10

   No evidence in the pack addresses data residency, region selection, or storage location options for FreshBooks; the docs cover invoicing, API, and accounting features but never mention data-center location or residency controls.

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

   No evidence pack item addresses AI training data usage, opt-outs, or any privacy policy language about AI model training; FreshBooks materials focus solely on invoicing/accounting features and API docs.

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

   No evidence pack items address AI data retention, deletion controls, or privacy policies specific to AI-native usage; the docs focus on invoicing, API endpoints, and pricing with no mention of data retention/deletion controls or AI data handling policies.

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

   No evidence exists of any telemetry/usage-tracking opt-out control, privacy settings, or documentation addressing AI-native data collection preferences; FreshBooks' docs cover invoicing, accounting, and API surfaces only, with no privacy-posture disclosures.

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

   FreshBooks exposes a REST API with Reports, Journal Entries, Expenses, Invoices and Payments endpoints that could be queried by a third-party agent to ground a 'can we afford X' answer in live ledger data, and OAuth2/webhooks are documented for secure, real-time access. However there is no first-party AI agent, natural-language Q&A layer, or MCP server, and llms.txt/docs.md probes both 404, meaning any such experience would have to be built entirely by the developer rather than delivered out of the box. Missing for 10: a native conversational/agent interface over the ledger data, evidence of LLM-specific integration, and a working llms.txt or agent-discovery endpoint.

   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   proof ↗⚑ flag

   Kick~partialprobed4/10

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

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

   proof ↗⚑ flag

Custom reports

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

   weight 2 · round drawn
   FreshBooks—none0/10

   FreshBooks' Reports API documents only seven fixed report types (e.g., Invoice Details, Manual Journal Entry, Payments Collected) with no mention of class, location, or tag dimensions, nor any custom report builder with grouping/filtering by these attributes. This is a fair axis for accounting software but no evidence shows FreshBooks supports it.

   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Other Reports - FreshBooks”

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

   FreshBooks documents core accounting infrastructure that would support these statements — double-entry chart of accounts, journal entries, accountant collaboration to 'run reports', and a Reports API exposing 'seven types of reports' (though only Invoice Details, Manual Journal Entry, and Payments Collected are named) plus generic 'tax-time reports' and 'detailed financial reports' claims. However, no evidence explicitly confirms dedicated Profit & Loss, Balance Sheet, or Cash Flow statement reports or on-demand period selection for them. Missing for 10: explicit documentation naming P&L/balance sheet/cash-flow reports, evidence of on-demand period customization, and independent/hands-on confirmation of report accuracy.

   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “Generate tax-time reports”
   • [claimed-docs] “FreshBooks gives you the tools you need for tasks like invoicing, billing your clients, preparing detailed financial reports, and making inf…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions 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