Digits vs Kick

Agent access

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

   weight 2 · round to Digits
   Digits✓fullprobed9/10

   Digits publishes both a top-level llms.txt (digits.com/llms.txt) and a developer-docs llms.txt (developer.digits.com/llms.txt), confirmed live via probe with HTTP 200, plus .md mirrors of every doc page — exactly the agent-oriented docs format the story asks for. missing for 10: independent third-party confirmation that an agent successfully consumed the llms.txt end-to-end (only first-party probes and docs are available).

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.digits.com/llms.txt # Digits Connect API Documentation > Documentation for Digits Connect API…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.digits.com/docs/overview.md --- updatedAt: 2026-08-31T23:35:53.000Z --- Fetch the complete doc…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”

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

   Digits exposes a full programmatic REST API (OAuth 2.0, OpenAPI spec, batch sync with idempotent writes, webhooks) and a resettable developer sandbox, which supports scripted/automated use outside a GUI, and the MCP server is also a headless, auth-gated JSON-RPC endpoint. However, there is no explicit CI/CD documentation, no service-to-service (client-credentials) auth flow described, and OAuth authorization-code grant typically requires an initial interactive login step, so pure unattended CI automation isn't directly documented. Missing for 10: explicit CI/headless-automation guide, client-credentials or machine-to-machine auth flow, and independent confirmation of unattended pipeline use.

   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Digits—none0/10

   All MCP evidence describes Digits exposing itself AS an MCP server (api.digits.com/mcp) so that other AI tools like Claude, ChatGPT, or Cursor can pull Digits' financial data — the opposite direction from this story, which asks whether a user can plug external MCP servers INTO Digits so Digits' own AI (e.g. Ask Digits) can call their tools. No evidence shows Digits acting as an MCP client or supporting user-added MCP server connections.

   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”
   • [probe] “official MCP server documented at https://help.digits.com/firms-connections/digits-mcp”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Digits
   Digits✓fullprobed9/10

   Digits ships a documented, hosted official MCP server at https://api.digits.com/mcp with OAuth against a user's own account, listed setup steps for Claude Desktop/Code, ChatGPT, Cursor, and Perplexity, and this is independently confirmed live via a probe showing a proper auth-gated JSON-RPC endpoint with RFC 9728 metadata. Missing for 10: broader independent third-party hands-on usage reports beyond the vendor docs and one live probe.

   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”
   • [probe] “official MCP server documented at https://help.digits.com/firms-connections/digits-mcp”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Digits—none0/10

   Digits ships an OpenAPI spec, SDG codegen, and an MCP server, but nothing in the evidence pack documents an official Digits CLI tool for developers; the only CLI mentioned is Claude's own 'claude mcp add' command, which is a third-party client CLI, not Digits'.

   ⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Digits
   Digits✓fullprobed9/10

   Digits publishes a full public REST API (Connect API) with OAuth2 authorization-code flow, versioned routes, OpenAPI 3.0 spec, generated SDKs across 50+ languages, a free resettable developer sandbox, and documented read/write endpoints (ledger, statements, bills workflow, webhooks) — this is a comprehensive, documented, programmatically-drivable API confirmed live by independent probes. missing for 10: the raw openapi.json file itself 404'd on direct probe (docs reference it at /openapi rather than the paths tried), so full spec accessibility wasn't independently verified end-to-end.

   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”
   • [claimed-docs] “"The Digits Connect API uses route-based versioning with the version number as a URL path prefix" — a published versioning policy on the dev…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.digits.com/docs/overview.md --- updatedAt: 2026-08-31T23:35:53.000Z --- Fetch the complete doc…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Digits
   Digits~partialprobed6/10

   The Connect API documents granular OAuth 2.0 scopes (e.g., 'source:sync ledger:read documents:write', 'bills:manage') that a developer/agent app can request, and the MCP server is fixed to read-only scope with its own OAuth flow, which together support least-privilege credential issuance. However there is no documented feature for a user to self-issue named, revocable API keys per-agent with custom scope selection (only the developer OAuth app flow, and the MCP server's scope is fixed read-only, not user-configurable). Missing for 10: dedicated 'create scoped API key for this agent' UI/API, per-agent revocation/audit trail, and evidence of narrower-than-read-only or custom scope combinations being selectable for MCP/agent use.

   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Digits
   Digits~partialprobed5/10

   Digits documents a full OpenAPI 3.0 spec and offers OpenAPI-Generator based codegen for 50+ languages/frameworks, plus a developer sandbox and OAuth flow — enabling AI-native developers to build integrations — but there is no evidence of dedicated, first-party maintained SDK packages (e.g., official Python/Node/Go client libraries), and a probe for the raw OpenAPI file at common paths returned 404s, casting some doubt on spec accessibility. missing for 10: dedicated first-party SDK repositories/packages, confirmed live OpenAPI spec file, independent corroboration of codegen usage.

   • [claimed-docs] “The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response sc…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Digits
   Digits~partialclaimed6/10

   Digits' API reference documents webhook event delivery — "Digits sends this JSON request body to your configured webhook endpoint" — confirming a webhook mechanism exists for event notifications, which supports agentic/event-driven integration alongside the OAuth API and MCP server. However, evidence lacks detail on how a user subscribes/manages webhook endpoints (create/list/delete subscription endpoints), the catalog of event types, retry/signing/security details, or independent confirmation of reliability. Missing for 10: webhook subscription management API details, event type catalog, delivery guarantees/signing docs, and independent/hands-on verification.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   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 Digits
   Digits✓fullprobed8/10

   Digits ships 'Ask Digits' as an in-product AI assistant that answers financial questions and completes tasks ('Ask questions. Complete tasks. Understand your business'), plus AI-driven trend insights, exception surfacing, and quality-control checks embedded in dashboards and the Agentic Close workflow. This is corroborated by a live, auth-gated MCP server exposing the same ledger data for AI-generated insights externally, reinforcing the product's AI-native insight capability. Missing for 10: independent/hands-on user reviews validating the quality of Ask Digits' insights beyond vendor claims.

   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “Digits Dashboards provide real-time, customizable views of revenue, expenses, cash, and other key metrics so founders and finance teams alwa…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

   Kick~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Digits
   Digits~partialclaimed7/10

   Digits documents strong built-in autonomous background processing: auto-booking 95%+ of transactions in real time, automated reconciliations, and an 'Agentic Close' workflow that continuously collects activity, books transactions, starts reconciliation, generates schedules, runs QC, and surfaces exceptions without user intervention. It also supports webhook event delivery and an 'Ask Digits' task mode. However, there's no evidence of user-configurable automation rules, triggers, or a workflow builder that an AI-native user could set up themselves — the automation is largely pre-built rather than user-defined. Missing for 10: user-configurable automation/trigger setup, scheduling controls, or evidence of custom rule-based automations beyond the fixed AGL pipeline.

   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”
   • [claimed-docs] “an AI-native month-end close workflow that collects financial activity continuously, books transactions inside the ledger, starts reconcilia…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

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

   Digits ships 'Ask Digits', a built-in AI assistant that answers financial questions and has a documented 'task mode' to 'Get it Done', which supports delegation of tasks within the product itself. However, evidence for the task-execution side is thin — only a marketing blurb, with no detailed docs, workflow examples, or independent/hands-on confirmation of what tasks it can actually complete autonomously. missing for 10: detailed documentation or hands-on evidence of the range/reliability of tasks Ask Digits can execute, independent corroboration of agentic task completion, and any limits/guardrails on delegated actions.

   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “Ask Digits Your AI financial assistant”

   proof ↗⚑ flag

   Kick~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Digits
   Digits✓fullprobed7/10

   Digits ships "Ask Digits", an in-product AI assistant that lets users ask natural-language questions about financials and invoke a documented task mode ("Ask Digits to Get it Done") to complete actions, and additionally exposes an MCP server so natural-language agents in Claude/ChatGPT/Cursor can query live ledger data. Missing for 10: independent/hands-on verification that Ask Digits' task execution actually works as described, and clarification of how far natural-language commands can go given the MCP server is documented as read-only.

   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “Ask Digits Your AI financial assistant”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

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

   Digits publishes a full OpenAPI 3.0 spec, an interactive-friendly llms.txt/markdown mirror of docs, and a free resettable developer sandbox with demo data, which together support exploring the API with real requests; however, the probe found no hosted interactive reference UI (openapi.json/swagger.json paths 404'd) and no evidence of embedded runnable code examples within the docs themselves. missing for 10: a live interactive API-reference UI (e.g., Swagger/Redoc/Stoplight) with clickable 'try it' runnable examples, and confirmation that the OpenAPI spec is actually renderable/explorable rather than just downloadable.

   • [claimed-docs] “The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response sc…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.digits.com/docs/overview.md --- updatedAt: 2026-08-31T23:35:53.000Z --- Fetch the complete doc…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Digits
   Digits✓fullprobed8/10

   Digits explicitly documents a 'complete OpenAPI 3.0 specification' covering all endpoints/params/schemas, hosted at a stated URL and paired with OpenAPI Generator codegen support for 50+ languages, plus a parallel llms.txt and per-page .md mirrors for machine-readable docs (digits-supp-openapi-llms, digits-docs-5, digits-probe-1, digits-probe-2). A probe attempting to fetch the spec failed, but it only tried guessed generic paths (openapi.json, swagger.json, etc.) rather than the actually documented '/openapi' URL, so this is not a concrete contradiction. Missing for 10: independent verification that the documented '/openapi' URL itself returns a valid spec live.

   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response sc…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.digits.com/llms.txt # Digits Connect API Documentation > Documentation for Digits Connect API…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.digits.com/docs/overview.md --- updatedAt: 2026-08-31T23:35:53.000Z --- Fetch the complete doc…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”

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

   Digits documents a dedicated developer sandbox with a resettable demo instance pre-loaded with realistic data, entirely separate from production, and free/self-serve access via Development API keys that auto-select the demo client in OAuth. This directly satisfies testing without touching production data. Missing for 10: independent/hands-on confirmation that the sandbox behaves identically to production and covers write endpoints (e.g., bills workflow) without side effects.

   • [claimed-docs] “Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo …”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”

   proof ↗⚑ flag

   Kick—none0/10

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

   ⚑ flag

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

   weight 2 · round to Digits
   Digits~partialclaimed5/10

   Digits documents route-based API versioning (version number as URL path prefix) on a dedicated versioning docs page, showing intentional version management for AI/agent consumers of its Connect API and MCP server. However, no evidence describes an explicit deprecation policy (timelines, sunset notices, migration guidance for old versions) — missing for 10: documented deprecation timeline/process, evidence of past version sunsets, and confirmation this policy also covers the MCP server surface.

   • [claimed-docs] “The Digits Connect API uses route-based versioning with the version number as a URL path prefix.”
   • [claimed-docs] “"The Digits Connect API uses route-based versioning with the version number as a URL path prefix" — a published versioning policy on the dev…”

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

   The Connect API documents batch transaction sync with external-ID idempotence ("Idempotence and deduplication is handled via the external_id field") and auto-books 95%+ of transactions in real time, showing the platform can process many items at once programmatically. However there's no documented bulk-edit UI, bulk categorization/reclassification endpoint, or explicit multi-item action beyond transaction sync and bill workflows. Missing for 10: dedicated bulk-update/bulk-edit endpoints or UI, evidence of bulk operations across other object types (invoices, reports, vendors) beyond transactions, and independent confirmation of batch scale limits.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

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

   Digits offers webhook event delivery (JSON payloads on ledger events) and internal automated actions like auto-booking, flagging, and quality checks, but these are pre-built automations rather than a user-facing rule engine where an AI-native user can define custom 'if event X then action Y' triggers. Missing for 10: a documented rule-builder/automation configuration UI or API, examples of user-defined trigger-action pairs, and evidence of arbitrary custom actions being executed on arbitrary events beyond fixed webhook notifications.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”

   proof ↗⚑ flag

   Kick~partialclaimed6/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Digits—none0/10

   Digits offers webhooks, background auto-booking, and month-end close automation, but there is no evidence of a user-facing scheduler for recurring jobs/workflows (e.g., cron-like triggers, scheduled report generation, or workflow automation builder) that an AI-native user could configure. missing for 10: any documented scheduling/cron API or UI, recurring job configuration, or workflow trigger system.

   ⚑ flag

   Kick—none0/10

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

   ⚑ flag

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

   weight 1 · round drawn
   Digits—none0/10

   Digits documents automated bookkeeping, auto-booking, agentic close, and exception surfacing, but nothing in the evidence describes versioning, reviewing change history, or rolling back automations/rules themselves — no changelog, rule-versioning, or undo mechanism for its automated workflows is documented.

   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “an AI-native month-end close workflow that collects financial activity continuously, books transactions inside the ledger, starts reconcilia…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

Ai reconciliation

1. ai-native userHave an agent reconcile a month end-to-end, matching transactions, flagging exceptions, and preparing the close for human review

   weight 3 · round to Digits
   Digits~partialclaimed6/10

   Digits documents an 'Agentic Close' workflow that continuously books transactions, starts reconciliation before month-end, generates schedules, surfaces exceptions with context, and produces reports from the live ledger, plus 95%+ auto-booking and quality-control checks — strong first-party alignment with the story. However, this is all vendor-authored marketing/docs with no independent or hands-on verification of end-to-end autonomous execution, no example of an agent actually running a full close via API/MCP, and the MCP server is explicitly read-only (cannot book, flag, or take reconciliation actions itself), meaning the 'agent-driven' close is only demonstrated through the closed first-party product, not via the agent-facing surfaces. missing for 10: independent/hands-on evidence of an agent executing the full reconciliation-to-close workflow, and MCP/API write access enabling an external agent to perform booking/exception-flagging rather than just read data.

   • [claimed-docs] “an AI-native month-end close workflow that collects financial activity continuously, books transactions inside the ledger, starts reconcilia…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “Digits adds 11 new quality checks to make closing the books that much easier!”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

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

   Digits documents real-time bank/credit-card connectivity across 12,000+ financial institutions with auto-booking of 95%+ of transactions in real time, and help docs describe adding new connections, positioning daily automatic import as a core feature. missing for 10: independent/hands-on confirmation of daily import reliability beyond vendor claims.

   • [claimed-docs] “"Digits Connect API seamlessly integrates with 12,000+ financial institutions, giving you real-time visibility into the metrics that matter—…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “Real-time Integrations 12,000+ financial institutions”
   • [claimed-docs] “Where do I add a new connection?”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”

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

   Digits documents AI-native auto-categorization (AGL trained on 170M+ transactions, 95%+ auto-booking) and 'transaction flagging & smart reviews' suggesting a learning/correction loop, but there is no explicit documentation of a feedback mechanism where founder corrections are captured and used to retrain or adjust future suggestions. missing for 10: explicit description of a correction-feedback loop showing suggestions improve from user edits, independent/hands-on verification of accuracy improving over time, and details on how manual overrides are ingested by the categorization model.

   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “The AGL is a purpose-trained model suite: "Proprietary AI models trained on over 170 Million transactions totaling $875 Billion", doing "Rea…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”

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

   Digits documents automated reconciliation, transaction flagging/smart reviews, and exception surfacing as part of its AI-driven bookkeeping and 'Agentic Close' workflow, which implies reconciliation review happens, but duplicates are described as being prevented via idempotent writes rather than surfaced as a reviewable duplicate queue. Missing for 10: explicit documentation of a per-bank-account reconciliation view distinguishing matched, unmatched, and duplicate transactions, and any hands-on/independent confirmation of this UI.

   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”
   • [claimed-docs] “Digits adds 11 new quality checks to make closing the books that much easier!”

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

   Digits documents a dedicated 'Bill Pay' feature (drag/drop/approve/pay) and a full bills workflow API covering ingest, query, submit, approve, pay, reject, and void gated by a bills:manage scope, which maps directly to capture, approval routing, and payment. However, evidence doesn't detail payment scheduling specifics (e.g., future-dated batch runs, approval chains/rules) or provide independent/hands-on confirmation the workflow works end-to-end. Missing for 10: explicit payment-scheduling mechanics, multi-step approval routing configuration details, and third-party corroboration.

   • [claimed-docs] “Bill Pay Drag. Drop. Approve. Pay.”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

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

   The developer API reference explicitly lists an 'accounts payable aging report' generator and a full bills workflow (ingest, query, submit, approve, pay, reject, void) gated by a bills:manage scope, implying vendor balance tracking within the AGL ledger. However, evidence doesn't explicitly confirm as-of-date/historical point-in-time snapshots for AP aging, and there's no independent/hands-on corroboration of the report's accuracy or usability. Missing for 10: explicit historical/point-in-time date parameter documentation, independent user validation of AP aging accuracy.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “Bill Pay Drag. Drop. Approve. Pay.”

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

   The evidence pack covers AGL categorization, the Agentic Close workflow, quality checks, and reporting, but nothing describes a period-lock or reopening-approval mechanism that prevents prior-period figures from changing. This is a reasonable axis for close-collaboration accounting software, so absence of evidence yields 'none'.

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

   Digits documents an 'Agentic Close' workflow that starts reconciliation before month-end, generates accrual/depreciation schedules from ledger activity, runs quality-control checks, and surfaces exceptions with context, plus 11 dedicated closing quality checks — covering reconciliations, accruals, and QC review. However, there is no explicit documentation of a checklist UI or formal review/sign-off tracking (who approved what, sign-off status) as the story specifies. Missing for 10: an explicit close checklist artifact and documented sign-off/approval tracking mechanism.

   • [claimed-docs] “an AI-native month-end close workflow that collects financial activity continuously, books transactions inside the ledger, starts reconcilia…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “Digits adds 11 new quality checks to make closing the books that much easier!”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”

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

   Digits documents collaboration features letting 'business owners, finance teams, and accountants review and share financials' (digits-docs-11) and firm-tier plans that add 'roles and permissions' and 'flexible client-level plans' (digits-supp-pricing), indicating some support for external accountant access. However, there is no concrete documentation of an invite flow, specific role scopes (e.g., view-only vs. edit/adjust), or how a founder specifically grants an external bookkeeper adjust-level access. missing for 10: detailed invite/role-management UI docs, granular permission levels for external accountants, and independent confirmation of the collaboration workflow.

   • [claimed-docs] “Digits Financials generates real-time, customizable financial statements and reports directly from the AGL with collaboration features that …”
   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”

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

   Digits documents a full OpenAPI 3.0 spec, ledger endpoints including trial balance, balance sheet, P&L, and full chart of accounts retrieval, plus sandbox/dev environment access — satisfying most of the story. However, a live probe found the OpenAPI spec file itself returning 404 at all standard paths, and there's no explicit mention of exporting data in open/portable formats (e.g., CSV/JSON export of GL) beyond API JSON responses. missing for 10: working/reachable OpenAPI spec file (probe returned 404), explicit open-format export (CSV/JSON bulk export) of GL and trial balance, independent third-party confirmation of API completeness.

   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”

   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 drawn
   Digits✓fullclaimed8/10

   Digits documents real-time connections to 12,000+ financial institutions with named payments/payroll connectors (Stripe, Gusto, Ramp), auto-booking 95%+ of transactions via the AGL, and idempotent sync with deduplication so activity flows automatically into the ledger. missing for 10: independent/third-party corroboration of actual bank/payroll sync reliability and no explicit named banking connector list beyond generic '12,000+ institutions' claim.

   • [claimed-docs] “"Digits Connect API seamlessly integrates with 12,000+ financial institutions, giving you real-time visibility into the metrics that matter—…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”

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

   Digits has a help-center entry titled 'How do I migrate to Digits from Quickbooks?' and the Connect API supports idempotent, deduplicated transaction sync and chart-of-accounts fetch, suggesting some migration tooling exists, but no evidence details how historical transaction-level detail, account balances, or attachments are actually preserved during a full migration from another system. missing for 10: actual migration walkthrough/content beyond the FAQ title, evidence of historical balance/opening-balance handling, support for non-QuickBooks source systems, and independent confirmation that no transaction detail is lost.

   • [claimed-docs] “How do I migrate to Digits from Quickbooks?”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

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

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

   proof ↗⚑ flag

Invoicing

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

   weight 3 · round to Kick
   Digits~partialclaimed3/10

   Digits' product page lists an 'Invoicing — Get paid faster' feature, confirming the axis applies, but there is no documentation describing invoice creation workflow, online payment integration, or read/paid status tracking. missing for 10: details on invoice creation UI, supported payment methods/gateways, view-tracking or paid notifications, and any independent confirmation of the feature working.

   • [claimed-docs] “Invoicing Get paid faster”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Digits
   Digits~partialclaimed2/10

   Digits' product page lists an 'Invoicing — Get paid faster' feature and the Connect API exposes A/R aging reports, but there is no documentation of recurring invoice scheduling or automatic overdue-payment reminders. missing for 10: documented recurring invoice setup, automated reminder/dunning workflow, any hands-on or independent confirmation of these AR automation features.

   • [claimed-docs] “Invoicing Get paid faster”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

   Kick—none0/10

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

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

   proof ↗⚑ flag

Receivables

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

   weight 2 · round to Digits
   Digits~partialclaimed6/10

   Docs confirm an accounts payable aging report and A/R aging generation via the API ('Generate an accounts payable aging report', A/R aging) plus per-customer/vendor ledger queries and chart of accounts access, and Digits Financials/Dashboards surface real-time reports; but there is no dedicated UI walkthrough or independent confirmation of a per-customer AR balance view or dunning/aging workflow in the product itself, only API-level mentions in the developer llms.txt. missing for 10: hands-on/UI evidence of an AR aging report screen, per-customer balance breakdown in the app UI, independent verification of accuracy/usability.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “Digits Financials generates real-time, customizable financial statements and reports directly from the AGL with collaboration features that …”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

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

   The Connect API documents write/batch transaction sync with external_id idempotence and a bills workflow with submit/approve/reject/void steps (a review-queue-like pattern), and OAuth scopes include ledger:write-style scopes, showing agents can post financial data programmatically. However, there is no explicit documentation of a 'draft journal entry' state or an accountant-facing review queue specifically for journal entries (as opposed to bills), and the MCP server—the more natural agent surface—is explicitly read-only, so agentic posting must go through the raw Connect API rather than a documented review workflow. Missing for 10: explicit journal-entry draft/pending state, an accountant review-queue UI/API for entries, and confirmation that MCP or agent tooling can trigger this flow.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

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

   Digits documents the ability to fetch the full chart of accounts via the Connect API and mentions 'dimensional accounting'/'dimensional reporting' as a paid-tier feature, suggesting some support for class/tag dimensions, but there is no documentation of an accountant-facing workflow for creating account types or sub-accounts — indeed Digits' messaging emphasizes that its AI 'replaces' manual chart-of-accounts mapping rather than supporting granular manual customization. Missing for 10: explicit UI/API support for defining account types, creating/nesting sub-accounts, and configuring custom class or tag dimensions beyond the vague 'dimensional accounting' mention.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

   proof ↗⚑ flag

   Kick~partialclaimed6/10

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

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

   proof ↗⚑ flag

Journal entries

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

   weight 3 · round to Kick
   Digits—none0/10

   Digits' evidence describes AI-driven auto-booking, categorization, reconciliation, and an API for batch transaction sync/ledger queries, but nowhere documents a manual journal-entry workflow with debit/credit balancing and memo fields — the product's own framing explicitly positions itself as replacing manual entry/mapping rather than supporting it.

   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “The AGL is a purpose-trained model suite: "Proprietary AI models trained on over 170 Million transactions totaling $875 Billion", doing "Rea…”

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

   Digits documents built-in anomaly/duplicate handling (idempotent writes with external_id dedup, 11 quality checks before close, 'Agentic Close' that 'surfaces exceptions with context', and 24/7 bookkeeping with 'transaction flagging & smart reviews'), and its MCP server lets an AI agent query the live ledger. However this is largely automated system-level checking rather than a user-directed agent actively monitoring and proactively flagging anomalies/duplicates during the close cycle, and the MCP server is explicitly read-only so an agent cannot act on or resolve flagged items. Missing for 10: independent/hands-on evidence that an AI agent can be configured to continuously monitor and alert on spend anomalies or duplicates specifically before close, and confirmation the flagging pipeline is agent-driven rather than purely rule/ML-based backend automation.

   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “Digits adds 11 new quality checks to make closing the books that much easier!”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”

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

   No evidence exists of a change-log, version history, or 'who changed what and when' audit trail feature across the ledger; the pack covers categorization, APIs, MCP, security-at-rest, and pricing but nothing about audit trails or user-action logging.

   ⚑ flag

   Kick✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Multi entity

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

   weight 2 · round to Kick
   Digits—none0/10

   Evidence shows Digits is built around a single AI-native general ledger (AGL) per business, with firm plans offering multi-client seats/permissions but no documented feature for combining multiple legal entities into consolidated financial statements. Nothing in the docs, API reference, or product pages mentions inter-entity eliminations, consolidated reporting, or multi-entity ledger structures.

   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

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

   The Connect API exposes substantial read/write ledger functionality (financial statements, chart of accounts, bills workflow with submit/approve/pay, batch transaction sync, webhooks) matching much of the UI's bookkeeping/reporting features, and the MCP server extends programmatic access to AI tools. However, the MCP server is explicitly read-only, and several UI-surfaced features (Ask Digits AI assistant, Invoicing, Bill Pay drag-and-drop UI, Dashboards customization, mobile app features) have no documented API/MCP equivalent for full parity — missing for 10: write access via MCP, API coverage for Ask Digits conversational tasks, invoicing endpoints, dashboard customization API, and independent confirmation that all UI actions map to API calls.

   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “Bill Pay Drag. Drop. Approve. Pay.”
   • [claimed-docs] “Invoicing Get paid faster”

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

   Digits' Connect API exposes read endpoints for financial statements, chart of accounts, ledger entries, and transactions via a documented OpenAPI spec, which could be used to pull data out into open formats. However, there is no documented bulk 'export all your data' feature, no CSV/GDPR-style data portability statement, and no mention of account closure or migrating away from Digits (only migration into Digits from QuickBooks is documented). missing for 10: a dedicated full-account data export/download feature, explicit open-format (CSV/JSON) bulk export tooling, and any documentation addressing leaving/closing an account with full data portability.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “How do I migrate to Digits from Quickbooks?”

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

   No evidence anywhere in the pack mentions data residency, regional data storage options, or geographic controls for where financial data is hosted; security page only discusses encryption and SOC 2, not location choice.

   ⚑ 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 userControl data retention and deletion

   weight 2 · round drawn
   Digits—none0/10

   The evidence pack covers OAuth authentication, encryption at rest/in transit, and general security posture, but nothing addresses data retention policies or user-initiated deletion of financial data/records. For a financial ledger handling sensitive data, this is a fair and applicable privacy axis, but no documentation, help-center article, or API endpoint for retention settings or deletion requests is cited.

   ⚑ 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

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

   Digits ships both a documented Connect API (OAuth, OpenAPI, live ledger endpoints for statements, balances, cash flow) and an official read-only MCP server exposing the 'live, auto-booked' AGL data to Claude, ChatGPT, Cursor etc., independently confirmed live via a working OAuth-gated MCP probe — enabling an agent to query real-time financial data to answer affordability-style questions grounded in the ledger. The Ask Digits assistant further demonstrates first-party natural-language grounding against live financials. Missing for 10: no independent third-party example of a real 'can we afford X' query/answer being run end-to-end through the API or MCP.

   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”

   proof ↗⚑ flag

   Kick~partialprobed4/10

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

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

   proof ↗⚑ flag

Custom reports

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

   weight 2 · round to Digits
   Digits~partialclaimed5/10

   Digits explicitly advertises 'dimensional reporting' and 'dimensional accounting' as a feature (gated to Core/Pro plans) and has a help doc titled 'How do I create a custom report?', suggesting some custom, dimension-based reporting capability exists. However, no evidence specifies filtering/grouping by class, location, or tag dimensions specifically, nor shows a UI walkthrough or hands-on confirmation of this granularity. Missing for 10: explicit documentation naming class/location/tag as filterable/groupable dimensions, a hands-on or independent demonstration of building such a custom report, and detail on how grouping/filtering works in the report builder.

   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”
   • [claimed-docs] “How do I create a custom report?”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”

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

   Digits explicitly generates P&L, balance sheet, and cash-flow statements on demand from its live AGL ledger, with API endpoints for 'Generate a balance sheet statement', cash flow, and P&L, plus dashboards and custom reports (help.digits.com custom report doc). Pricing page confirms 'real-time financial statements—profit & loss, balance sheet, and cash flow' updating automatically. Missing for 10: independent/hands-on verification of statement accuracy for arbitrary custom periods, and no third-party review confirming report correctness beyond vendor claims.

   • [claimed-docs] “Digits Financials generates real-time, customizable financial statements and reports directly from the AGL with collaboration features that …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”
   • [claimed-docs] “How do I create a custom report?”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

   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