Pilot vs Digits

Agent access

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

   weight 2 · round to Digits
   Pilot~partialprobed4/10

   A probe confirms Pilot serves an llms.txt file at HTTP 200, so an agent can indeed be pointed at it — but the content shown is minimal (just entity/category metadata, no structured docs or API references), and other agent-doc formats (docs-md, openapi) return 404. Missing for 10: substantive llms.txt content beyond basic metadata, markdown docs mirror, and any first-party statement about agent-oriented documentation strategy.

   • [probe] “PROBE llms.txt: HTTP 200 at https://pilot.com/llms.txt # Pilot [Entity: Pilot] [Category: Professional Services] [Subcategory: Acco…”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Digits
   Pilot—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

   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

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

   weight 3 · round to Digits
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any MCP server offering; docs mention integrations (Bill.com, Stripe, Gusto) but nothing about AI agent connectivity via MCP, and API/openapi probes returned 404s.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Digits
   Pilot—none0/10

   No evidence of a public API for Pilot; OpenAPI/swagger probes all returned 404 and no docs mention an API for driving the product programmatically. Pilot is a human-service accounting/bookkeeping product with integrations, not an API-driven platform.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Digits
   Pilot—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

   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

6. ai-native userBuild against official SDKs

   weight 2 · round to Digits
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any official SDKs; probes for API/OpenAPI specs returned 404s, and no docs mention developer SDKs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

7. ai-native userSubscribe to events via webhooks

   weight 2 · round to Digits
   Pilot—none0/10

   No evidence of any webhook subscription capability or event API; Pilot is an accounting/bookkeeping service and probes show no OpenAPI or developer API surface exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Digits
   Pilot~partialclaimed4/10

   Pilot's marketing mentions 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead' (pilot-docs-7), which points to some AI-generated insight capability inside the product, and scenario/cash-flow modeling features (pilot-docs-8, pilot-docs-21) suggest similar analytical output, though these are framed as human CFO-delivered rather than explicitly AI-driven. There is no independent/hands-on corroboration of the AI feature actually working, and community reviews focus on bookkeeping accuracy/time savings rather than AI insights. Missing for 10: detailed documentation of the AI feature's scope/accuracy, independent user testimony specifically about the AI insights, and clarity on whether insights are AI-generated vs. human-analyst-generated.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Model cash flow scenarios Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Track company expenses in real time Find the $2,000/month you didn't know you were wasting.”
   • [claimed-docs] “Find the $2,000/month you didn't know you were wasting.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Digits
   Pilot—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

   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

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

   weight 3 · round to Digits
   Pilot~partialclaimed3/10

   Pilot's pricing page mentions an AI feature offering 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' which is a thin, single-mention hint of an in-product AI assistant capable of some task-like actions (scenario modeling). There's no further documentation on scope, autonomy, or how tasks are delegated to it, and community evidence focuses on human bookkeepers/CFOs rather than the AI assistant. Missing for 10: detailed documentation of the AI assistant's task-delegation capabilities, independent/hands-on corroboration of it actually performing delegated tasks, and clarity on its scope beyond Q&A.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Digits
   Pilot~partialclaimed3/10

   Pilot's marketing mentions 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' implying some natural-language Q&A interface, but there's no evidence of broader natural-language command execution (e.g., initiating actions, workflows) or any API/CLI to support it. missing for 10: evidence of NL commands beyond Q&A, independent/hands-on corroboration, technical documentation of the AI interface, API or programmatic access.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round to Digits
   Pilot—none0/10

   Pilot is an accounting/bookkeeping service with no evidence of any developer API reference or runnable examples; probes for OpenAPI/docs-md all returned 404, and no evidence pack items mention an API reference.

   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Digits
   Pilot—none0/10

   Probe explicitly checked common OpenAPI/swagger endpoints and all returned 404, and no documentation mentions a machine-readable API spec. Missing for 10: any published OpenAPI/Swagger spec, API documentation, or developer portal.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Digits
   Pilot—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

   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

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

   weight 2 · round to Digits
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI specs all returned 404s. missing for 10: any public API documentation, versioning scheme, deprecation policy, or developer-facing API references.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Digits
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service; no evidence describes any bulk-operation or batch-processing capability across items (transactions, invoices, etc.) for AI-native automation. Missing for 10: any mention of bulk edit/import/export tools, batch API operations, or automation-scale item processing.

   ⚑ flag

   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

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

   weight 3 · round to Digits
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with dedicated human experts and integrations, but there is no evidence of a rules engine or automation-trigger system letting users define event-based automated actions; features described are AI Q&A and integrations, not user-defined trigger/action rules.

   ⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

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

   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

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
   Pilot~partialcommunity3/10

   Pilot's evidence shows human bookkeepers finalize monthly books with integration-driven transaction classification (pilot-comm-1, pilot-docs-18, pilot-docs-26), which is directionally toward automated reconciliation, but there is no evidence of an autonomous agent matching transactions, flagging exceptions, and preparing a close package end-to-end without human bookkeeper involvement. Missing for 10: explicit agentic exception-flagging workflow, evidence of AI (not human staff) doing the matching/reconciliation, and documentation of an automated close-prep output for review.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Bank feeds

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

   weight 3 · round to Digits
   Pilot✓fullcommunity7/10

   Pilot's docs and a first-hand customer testimonial confirm bank/credit-card/expense integrations automatically feed transaction data for classification, with real-time account data in the portal, eliminating manual founder bookkeeping work. missing for 10: no explicit list of supported banks, no detail on daily-sync frequency or setup flow, and no independent technical documentation beyond marketing/community claims.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Categorization

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

   weight 2 · round to Digits
   Pilot—none0/10

   Evidence shows Pilot's transaction classification is handled by integrations plus human bookkeepers/accountants (pilot-comm-1, pilot-docs-17), not by an AI categorization engine that learns from founder corrections. No documentation describes a self-serve ML suggestion-and-correction loop. Missing for 10: any mention of an AI/ML categorization suggestion feature, evidence of a correction/feedback loop, or founder-facing UI for adjusting categorizations.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Reconciliation

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

   weight 3 · round to Digits
   Pilot—none0/10

   Pilot's evidence describes bank/tool integrations and automated transaction classification (pilot-comm-1, pilot-docs-17) but never describes a reconciliation workflow that surfaces matched, unmatched, and duplicate transactions for accountant review. Missing for 10: any documentation or user report of a reconciliation screen or matched/unmatched/duplicate transaction handling.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Bill management

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

   weight 2 · round to Digits
   Pilot~partialclaimed3/10

   Pilot's pricing page lists 'Full accounts payable' as a service line item and mentions integration with Bill.com, implying vendor bill handling, but there is no documented detail on bill capture, approval routing, or payment scheduling mechanics within a single workflow — AP appears to be a done-for-you service rather than a described self-serve workflow. Missing for 10: bill capture/OCR details, approval routing configuration, payment scheduling functionality, and any hands-on/independent confirmation of the AP workflow.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”

   proof ↗⚑ flag

   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

Payables

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

   weight 2 · round to Digits
   Pilot~partialclaimed4/10

   Pilot advertises 'Full accounts payable' as a service feature and real-time account data access via its portal, implying some visibility into AP status, but there is no specific mention of AP aging reports or vendor balance tracking at a point in time. missing for 10: explicit AP aging report feature, vendor balance detail/history, point-in-time reporting capability, screenshots or hands-on evidence of AP aging views.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Close process

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

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack mentions period locking, closing periods, or preventing retroactive changes to prior-period financials; the evidence only covers bookkeeping, tax, CFO, and integration features. Missing for 10: any mention of period-lock/close controls, reopening workflow, or audit trail preventing prior-period edits.

   ⚑ flag

   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

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

   weight 3 · round to Digits
   Pilot~partialclaimed3/10

   Pilot's monthly bookkeeping service closes books and lets customers communicate on 'outstanding items needed to finalize your books every month' via a portal, implying some close-tracking process, but there is no evidence of an actual checklist artifact tracking reconciliations, accruals, and review sign-offs as distinct trackable steps. missing for 10: explicit reconciliation checklist UI, accrual tracking, and sign-off/approval workflow evidence.

   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Collaboration

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

   weight 3 · round to Digits
   Pilot—none0/10

   Pilot's evidence describes its own bookkeeping team communicating with the founder via a portal (docs-18, docs-26) and lets customers keep QuickBooks data so any tax preparer can access it (docs-24), but there is no evidence of a feature to invite an external accountant/bookkeeper into Pilot's own system with role-scoped permissions to review or adjust books. missing for 10: any documentation of user/role invitation, permission scoping, or external collaborator access controls within Pilot's platform.

   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Data access

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

   weight 3 · round to Digits
   Pilot—none0/10

   No evidence of a documented API for pulling general ledger or trial balance data; probes for OpenAPI/docs endpoints returned 404s and no API documentation is mentioned anywhere in the evidence pack.

   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

Integrations

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

   weight 2 · round drawn
   Pilot✓fullcommunity8/10

   Pilot explicitly integrates with banking, payments, and payroll systems (e.g. Bill.com, Stripe, Gusto, 10k+ integrations) to feed real-time transaction data into the ledger, and community testimonials confirm bank/card/payment integrations auto-handle transaction classification with minimal founder effort. missing for 10: no explicit first-party detail on the breadth/setup process of bank feed connections beyond named partners, no independent audit of integration reliability at scale.

   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “10k+ Integrations”
   • [claimed-docs] “If you use Gusto, we’ve partnered with Gusto to automatically apply the credit, saving you time.”
   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Migration

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

   weight 1 · round to Pilot
   Pilot~partialclaimed5/10

   Pilot markets that switching providers is supported and mentions keeping existing QuickBooks account and historical data, implying migration support, but there's no detail on how historical transaction-level detail is preserved or migrated from other systems (e.g., Xero, Wave, spreadsheets) beyond QuickBooks. missing for 10: documented migration process, evidence of no data/detail loss, support for non-QuickBooks source systems, independent confirmation of successful migrations.

   • [claimed-docs] “Whether you’re starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding, underst…”
   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Whether you're starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding, underst…”
   • [claimed-docs] “Whether you’re starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding”

   proof ↗⚑ flag

   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

Invoicing

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

   weight 3 · round to Digits
   Pilot—none0/10

   Evidence only shows Pilot offers 'full accounts receivable' as a bookkeeping service item, but there is no mention of self-serve invoice creation, online payment collection, or view/paid tracking features for founders—Pilot is a done-for-you bookkeeping service, not an invoicing tool. Missing for 10: invoice creation UI, online payment processing, read-receipt/paid-status tracking evidence.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Digits
   Pilot—none0/10

   Evidence mentions 'Full accounts receivable' as a service but nothing about recurring invoicing or automated overdue payment reminders specifically. Pilot is positioned as a bookkeeping/accounting service, not an invoicing tool with these automation features documented anywhere in the pack.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

Receivables

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

   weight 2 · round to Digits
   Pilot~partialclaimed4/10

   Pilot's pricing page lists 'Full accounts receivable' as a service offering, confirming AR management is part of the product, but there is no evidence of specific features like aging reports or per-customer balance tracking/reporting in the evidence pack. missing for 10: documentation of aging reports, per-customer balance views, AR-specific dashboards or reports, and independent/hands-on confirmation of these features.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

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

   No evidence of any API, agent integration, or journal entry review queue functionality; Pilot is a human-service bookkeeping/accounting company with no documented API (openapi probes 404). Missing for 10: any API existence, journal entry draft/post capability, review queue workflow, agent-facing endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE llms.txt: HTTP 200 at https://pilot.com/llms.txt # Pilot [Entity: Pilot] [Category: Professional Services] [Subcategory: Acco…”

   proof ↗⚑ flag

   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

Chart of accounts

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

   weight 3 · round to Digits
   Pilot—none0/10

   Pilot is a done-for-you bookkeeping/accounting service, so ledger customization is a fair question, but the evidence pack only mentions generic 'custom workflows and reporting' with no mention of chart of accounts structure, account types, sub-accounts, or class/tag dimensions. Missing for 10: any documentation of COA setup, account type hierarchy, sub-account creation, or class/tag dimension tagging controlled by the accountant.

   • [claimed-docs] “Custom workflows and reporting”

   proof ↗⚑ flag

   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

Journal entries

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

   weight 3 · round drawn
   Pilot—none0/10

   Pilot's evidence describes a done-for-you bookkeeping/CFO service built on QuickBooks with dedicated experts handling books, but there is no mention of any interface for accountants to post manual journal entries with debits/credits and memos. Missing for 10: any UI or workflow for manual JE creation, debit/credit balancing, or memo attachment.

   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”

   proof ↗⚑ flag

   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

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

   Pilot's evidence covers bookkeeping, tax, CFO services, and AI Q&A on transactions, but there is no mention of an autonomous agent that monitors the ledger, flags spend anomalies, or detects duplicate transactions before close. missing for 10: anomaly-detection feature, duplicate-transaction flagging, any agentic monitoring capability, pre-close audit workflow evidence.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Track company expenses in real time Find the $2,000/month you didn't know you were wasting.”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”

   proof ↗⚑ flag

   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

Audit trail

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

   weight 3 · round drawn
   Pilot—none0/10

   No evidence in the pack describes any audit trail, change history, or user-activity logging feature within Pilot's platform; the material focuses on bookkeeping services, integrations, CFO advisory, and tax credits. Missing for 10: any mention of audit logs, change tracking, user attribution, or timestamped edit history across the ledger.

   ⚑ flag

   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

Multi entity

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

   weight 2 · round to Pilot
   Pilot~partialclaimed4/10

   Pilot's FAQ mentions it can provide consolidated reporting for US entities with foreign subsidiaries, but there is no evidence of multi-entity management for domestic entities, no detail on consolidation methodology, and no independent/hands-on corroboration of this feature. missing for 10: multi-entity dashboard/management capability, domestic multi-entity consolidation support, detailed consolidation workflow, independent verification.

   • [claimed-docs] “We can also provide US entities with foreign subsidiaries with consolidated reporting.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Digits
   Pilot—none0/10

   No evidence of any public API for Pilot; probes for OpenAPI/swagger endpoints all returned 404, and all documentation describes only the human portal/UI and service offerings. missing for 10: any documented API, API parity claims, or developer endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Digits
   Pilot—none0/10

   While Pilot mentions QuickBooks compatibility and tax-preparer portability, there is no evidence of a dedicated data export feature, open-format export (CSV/JSON/API), or a documented process to fully extract and leave with all financial data; probes even show no public API/OpenAPI spec.

   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack addresses data residency, region selection, or storage location controls; Pilot is an accounting/bookkeeping service with no mention of infrastructure or data-residency options. Missing for 10: any documentation of data storage regions, residency guarantees, or configurable data location.

   ⚑ flag

   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

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for Pilot's AI features or data; the pack only covers accounting, bookkeeping, and tax service offerings. Missing for 10: any documentation of data retention/deletion controls, privacy settings, or data handling policies for AI or customer data.

   ⚑ flag

   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

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

   Pilot advertises an in-app AI feature offering 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' which aligns with the 'can we afford X' query use case, but there is no evidence this is exposed via an API for external agents to query — the openapi probe returned 404s and no API/agent-integration docs exist. missing for 10: evidence of a public API/endpoint an external AI agent could call, documentation of grounding in live ledger data via API, and any independent confirmation the AI answer feature works as described.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Model cash flow scenarios Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Know if you can afford new hires well before you make the offers.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

Custom reports

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

   weight 2 · round to Digits
   Pilot—none0/10

   Evidence only mentions generic 'custom workflows and reporting' (pilot-docs-10) with no mention of class, location, or tag dimension filtering/grouping capabilities typical of QuickBooks-style reports; missing for 10: any documentation of dimension-based (class/location/tag) filtering or grouping in reports.

   • [claimed-docs] “Custom workflows and reporting”

   proof ↗⚑ flag

   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

Statements

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

   weight 3 · round to Digits
   Pilot~partialcommunity5/10

   Pilot's bookkeeping and CFO service pages reference real-time account data, custom workflows/reporting, and budget-vs-actuals/scenario planning, implying standard financial statements are produced as part of monthly bookkeeping, and community reviews confirm books are kept accurate and up to date. However, no evidence explicitly confirms generation of a P&L, balance sheet, and cash-flow statement for any arbitrary period on demand. Missing for 10: explicit documentation of the three core statements, confirmation of on-demand/any-period generation (vs. standard monthly close), and independent verification of statement accuracy/timeliness.

   • [claimed-docs] “Custom workflows and reporting”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Custom financial model with strategic insights Budget vs actuals variance analysis Scenario planning model”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”
   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [community] “Pilot customer here; they are amazing. It's pretty different from a regular bookkeeper largely in that Pilot is super accurate and timely. M…”

   proof ↗⚑ flag

   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