Puzzle vs Wave

Agent access

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

   weight 2 · round to Puzzle
   Puzzle✓fullprobed8/10

   A live probe confirms Puzzle's help center serves a valid llms.txt file at help.puzzle.io/llms.txt (HTTP 200) with structured markdown links to docs, directly satisfying the ability to point an agent at agent-oriented docs. Missing for 10: independent/community confirmation of agents successfully consuming this file, and broader agent-doc formats (e.g., per-page .md mirrors, which probes show 404).

   • [probe] “PROBE llms.txt: HTTP 200 at https://help.puzzle.io/llms.txt # Puzzle Help Center > Help center for Puzzle ## Puzzle Overview - [Quick Sta…”
   • [probe] “PROBE docs-md: HTTP 404 at https://help.puzzle.io/en/.md”

   proof ↗⚑ flag

   Wave—none0/10

   A direct probe found no llms.txt file (404) and no agent-oriented docs surface; Wave's marketing pages contain no mention of llms.txt or agent-consumable documentation, and its developer portal is blocked to crawlers.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Puzzle—none0/10

   Puzzle's evidence only shows marketing language about an 'API' for embedding accounting into platforms and an MCP integration for Claude chat — neither documents headless CLI operation, CI pipeline usage, or automation-oriented tooling. No SDK, auth flow, or CI examples are present, so there's no evidence of headless/CI automation support.

   • [claimed-docs] “With Puzzle's Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “With Puzzle’s Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “your platform gets automated AI bookkeeping, real-time financial insights, and a clean data foundation built to scale”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.puzzle.io/openapi.json, https://help.puzzle.io/swagger.json, https://help.puzzle.io/api…”

   proof ↗⚑ flag

   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS with no evidence of a CLI, headless mode, or CI-friendly automation surface; llms.txt and OpenAPI probes both 404, and the developer/API portal is walled off with no documented programmatic interface. Nothing suggests Wave can be run headlessly or scripted in a CI pipeline.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Puzzle—none0/10

   Evidence shows Puzzle exposes its own MCP server so external AI clients (e.g., Claude) can pull Puzzle's financial data — the reverse of the story's ask. There is no evidence that Puzzle itself can consume or plug in external MCP servers to gain their tools.

   • [claimed-docs] “Puzzle's MCP (Model Context Protocol) integration lets you connect your Puzzle account directly to Claude, giving you instant access to your…”
   • [claimed-docs] “lets you connect your Puzzle account directly to Claude, giving you instant access to your financial data through natural conversation — no …”
   • [claimed-docs] “How to setup your Puzzle MCP”

   proof ↗⚑ flag

   Wave—none0/10

   Wave is small-business accounting/invoicing SaaS; no evidence of an MCP server or ability to plug MCP tools in. llms.txt and OpenAPI probes both 404, and the developer portal is inaccessible/undocumented on public pages, so the applicable axis (as a SaaS product could plausibly expose an MCP integration) has no supporting evidence.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 3 · round to Puzzle
   Puzzle✓fullclaimed7/10

   Puzzle documents an official MCP server integration that connects Puzzle accounts to Claude for natural-language access to financial data, with a dedicated setup guide (puzzle-docs-2, puzzle-docs-22, puzzle-docs-33). This is a first-party, product-level MCP server offering, fitting the axis for a non-agent SaaS product. Missing for 10: independent/hands-on confirmation that the MCP server works as documented, and technical details on supported tool calls/scopes.

   • [claimed-docs] “How to setup your Puzzle MCP”
   • [claimed-docs] “Puzzle's MCP (Model Context Protocol) integration lets you connect your Puzzle account directly to Claude, giving you instant access to your…”
   • [claimed-docs] “lets you connect your Puzzle account directly to Claude, giving you instant access to your financial data through natural conversation — no …”

   proof ↗⚑ flag

   Wave—none0/10

   Wave is an accounting SaaS product, so an official MCP server is a plausible axis, but there is no evidence of any MCP server, API docs accessible, or agent integration; probes for llms.txt and OpenAPI both 404, and the developer portal is walled off from crawling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Puzzle—none0/10

   Puzzle's evidence pack documents an API, an MCP integration, and various in-app AI features, but there is no mention of an official CLI tool anywhere in the docs or probes. Missing for 10: any CLI documentation, CLI installation instructions, or CLI command reference.

   ⚑ flag

   Wave—none0/10

   No evidence of any official CLI for Wave; probes for llms.txt and API docs both 404/403, and marketing pages document no CLI, API, or agent tooling surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 3 · round to Puzzle
   Puzzle~partialprobed4/10

   Puzzle markets an 'Embedded Accounting' API and has a help article on 'API Access in Puzzle' describing platform-to-platform integration intent, suggesting a documented public API exists. However, probes for actual API reference material (OpenAPI/swagger specs, docs-md) returned 404s, and no evidence pack item shows endpoint-level documentation, auth flow, or SDKs. Missing for 10: a public API reference/spec, authentication and endpoint documentation, and independent confirmation that AI-native users can programmatically drive the product via this API.

   • [claimed-docs] “With Puzzle's Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “With Puzzle’s Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.puzzle.io/openapi.json, https://help.puzzle.io/swagger.json, https://help.puzzle.io/api…”

   proof ↗⚑ flag

   Wave—none0/10

   Marketing pages document no public API, and direct probes for llms.txt/OpenAPI both 404; the developer portal exists but is blocked to crawlers so no documented, accessible API surface is evidenced.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Puzzle—none0/10

   Evidence shows Puzzle has an API and MCP integration for connecting agents (e.g., Claude) to account data, but there is no mention of issuing scoped, least-privilege API credentials, permission scopes, or granular token controls for agents. missing for 10: scoped API key/token generation, permission/role-based credential scoping, documentation of least-privilege access controls for agent integrations.

   • [claimed-docs] “Puzzle's MCP (Model Context Protocol) integration lets you connect your Puzzle account directly to Claude, giving you instant access to your…”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”
   • [claimed-docs] “lets you connect your Puzzle account directly to Claude, giving you instant access to your financial data through natural conversation — no …”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of any API credential system, scoped tokens, or agent-oriented access controls; Wave's role-based access is for human collaborators (admin/editor/viewer), and its developer/API portal could not even be crawled to confirm any credentialing mechanism exists.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Puzzle
   Puzzle~partialprobed5/10

   Puzzle offers a documented API for embedded accounting and an MCP integration for Claude, showing some official developer surfaces, but there's no evidence of a formal SDK (client libraries, language bindings) or OpenAPI spec — probes for openapi.json all returned 404. missing for 10: official SDK/client libraries in specific languages, published OpenAPI/API reference spec, independent developer corroboration of building against the API.

   • [claimed-docs] “With Puzzle's Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “With Puzzle’s Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”
   • [claimed-docs] “Puzzle's MCP (Model Context Protocol) integration lets you connect your Puzzle account directly to Claude, giving you instant access to your…”
   • [claimed-docs] “lets you connect your Puzzle account directly to Claude, giving you instant access to your financial data through natural conversation — no …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.puzzle.io/openapi.json, https://help.puzzle.io/swagger.json, https://help.puzzle.io/api…”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of official SDKs for AI-native/programmatic use; llms.txt and OpenAPI probes both 404, and the developer/GraphQL API portal is walled off from crawling with no documentation surfaced. Marketing pages describe only end-user accounting features, not SDKs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Puzzle—none0/10

   No evidence of webhook subscription capability anywhere in the pack; Puzzle offers an API and MCP integration for querying data, but nothing about event-driven webhooks.

   ⚑ flag

   Wave—none0/10

   No evidence of webhook support anywhere in Wave's marketing pages or developer portal; the developer portal itself couldn't be crawled and is described as documenting no webhook surface, and llms.txt/openapi probes both returned 404.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Puzzle
   Puzzle✓fullclaimed8/10

   Puzzle offers a conversational 'ask anything' insights feature (cash trending, profitability, fundraising readiness) plus AI Close agents that surface discrepancies, AI-driven categorization suggestions, and MCP integration for natural-language querying of financial data via Claude — all directly delivering AI-generated insights/suggestions from the user's own data. Missing for 10: independent hands-on verification of insight accuracy/quality beyond marketing copy and only one general community mention unrelated to this specific feature.

   • [claimed-docs] “Ask anything about your business, instantly, in plain English. "How's my cash trending?" "Am I ready to raise?" "Which months am I actually …”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “A user can click on a button and “ask AI” for help in categorizing a transaction —without context switching between tools.”
   • [claimed-docs] “Puzzle's MCP (Model Context Protocol) integration lets you connect your Puzzle account directly to Claude, giving you instant access to your…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “Hand off the busywork. Finding software subscriptions, matching invoices to payments, pulling together what your accountant needs — describe…”

   proof ↗⚑ flag

   Wave—none0/10

   Evidence shows OCR data extraction and automation (auto-categorize, reminders) but no AI-generated insights, analysis, or suggestions surfaced to users; reports are static comparisons, not AI-driven recommendations. No mention of AI/ML-based insight generation anywhere in the pack.

   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

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

   weight 2 · round to Puzzle
   Puzzle~partialclaimed6/10

   Puzzle documents concrete background automations — 'AI Close' agents that autonomously reconcile accounts, review transactions and surface discrepancies during month-end, plus custom categorization rules and batch auto-categorization (up to 98%) that run without manual triggering. However these are fixed, accounting-specific automations rather than a general-purpose 'set up your own automation' framework, and there's no independent/hands-on evidence confirming reliability of unattended runs. Missing for 10: user-configurable triggers/schedules for arbitrary automations, evidence of true autonomy without review gates, and independent verification of background execution.

   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “Creating custom rules”
   • [claimed-docs] “Batch Categorize Transactions”
   • [claimed-docs] “Up to 98% auto-categorization”

   proof ↗⚑ flag

   Wave~partialprobed4/10

   Wave ships several fixed, always-on background automations (auto bank import/categorization, recurring invoices with auto payment reminders, auto payroll tax filing) that run without manual triggering, per wave-docs-2, wave-docs-5, wave-docs-10, wave-docs-14. However these are hard-coded product features, not a general-purpose automation/agent framework the user can configure, and there is no API, webhook, or MCP surface documented for building custom autonomous workflows (wave-probe-1, wave-probe-2, wave-supp-dev-portal-wall). Missing for 10: a configurable automation builder, any AI-agent/orchestration capability, and a documented API/webhook layer for extending automations.

   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 3 · round to Puzzle
   Puzzle✓fullclaimed8/10

   Puzzle ships built-in AI features (AI Close, Accounting AI) described as using 'AI agents to reconcile accounts, review transactions, and surface discrepancies,' plus an 'Ask AI' button for categorization help and natural-language financial queries — all within the product itself, not an external agent. Missing for 10: independent/hands-on verification of these AI features actually completing delegated tasks, and clearer detail on autonomy vs human-review boundaries.

   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “A user can click on a button and “ask AI” for help in categorizing a transaction —without context switching between tools.”
   • [claimed-docs] “Accounting AI runs prompts on top of your general ledger. The output reflects your existing accounts and categories.”
   • [claimed-docs] “How to import a PDF or CSV using Accounting AI”
   • [claimed-docs] “Ask anything about your business, instantly, in plain English. "How's my cash trending?" "Am I ready to raise?" "Which months am I actually …”
   • [claimed-docs] “Hand off the busywork. Finding software subscriptions, matching invoices to payments, pulling together what your accountant needs — describe…”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence anywhere in the pack of a built-in AI assistant or agentic feature; Wave's docs describe automation (auto-import, OCR, reminders) but nothing about delegating tasks to an AI assistant, and the developer portal is inaccessible with no API/AI mention on marketing pages.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”

   proof ↗⚑ flag

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

   weight 2 · round to Puzzle
   Puzzle✓fullclaimed7/10

   Puzzle documents natural-language interaction via its MCP integration with Claude ('instant access to your financial data through natural conversation') and multiple AI features letting users 'ask anything about your business in plain English' or 'ask AI' to categorize transactions, plus AI Close agents automating close tasks from natural prompts. Missing for 10: independent/hands-on verification that NL commands can trigger broader actions (not just queries) and third-party corroboration of the MCP/Claude workflow in practice.

   • [claimed-docs] “Puzzle's MCP (Model Context Protocol) integration lets you connect your Puzzle account directly to Claude, giving you instant access to your…”
   • [claimed-docs] “lets you connect your Puzzle account directly to Claude, giving you instant access to your financial data through natural conversation — no …”
   • [claimed-docs] “Ask anything about your business, instantly, in plain English. "How's my cash trending?" "Am I ready to raise?" "Which months am I actually …”
   • [claimed-docs] “A user can click on a button and “ask AI” for help in categorizing a transaction —without context switching between tools.”
   • [claimed-docs] “Accounting AI runs prompts on top of your general ledger. The output reflects your existing accounts and categories.”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of any natural-language command interface, chat assistant, or AI-native control surface; Wave's marketing pages describe only manual UI-based accounting/invoicing features, and probes for llms.txt/openapi found nothing, with the developer portal walled off from crawling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Puzzle—none0/10

   Puzzle documents an API (puzzle.io/api) and an MCP integration, but there is no evidence of an interactive API reference or runnable examples; probes for OpenAPI/Swagger specs at expected paths all returned 404, suggesting no such interactive reference exists.

   • [claimed-docs] “With Puzzle's Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.puzzle.io/openapi.json, https://help.puzzle.io/swagger.json, https://help.puzzle.io/api…”
   • [probe] “PROBE docs-md: HTTP 404 at https://help.puzzle.io/en/.md”

   proof ↗⚑ flag

   Wave—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes for openapi/llms.txt returned 404s, and the developer portal itself is blocked from crawling with no documented API surface accessible.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Puzzle—none0/10

   Puzzle has an API and mentions API access docs, but the probe explicitly found no OpenAPI/swagger spec at any candidate path, and no evidence pack item references a downloadable machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://help.puzzle.io/openapi.json, https://help.puzzle.io/swagger.json, https://help.puzzle.io/api…”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”

   proof ↗⚑ flag

   Wave—none0/10

   Direct probes for OpenAPI/swagger specs and llms.txt returned 404s, and Wave's developer portal (GraphQL API) is blocked to crawlers with no machine-readable spec surfaced; marketing pages document no API spec at all.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Puzzle—none0/10

   No evidence in the pack mentions a sandbox, test, or staging environment for Puzzle's API or product that would let a user test without touching production financial data; only production-focused API and bookkeeping features are documented.

   ⚑ flag

   Wave—none0/10

   No evidence of any sandbox, staging, test-mode, or dev environment for Wave; the developer portal is inaccessible and marketing pages document no API/test environment for isolating data from production.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Puzzle—none0/10

   The evidence pack shows Puzzle has an API and MCP integration (puzzle-docs-42, puzzle-docs-21) but contains no mention of API versioning scheme or a documented deprecation policy; probes for OpenAPI specs all returned 404. Missing for 10: any versioning scheme documentation, changelog, or deprecation/sunset policy.

   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”
   • [claimed-docs] “With Puzzle’s Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.puzzle.io/openapi.json, https://help.puzzle.io/swagger.json, https://help.puzzle.io/api…”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of versioned APIs or a documented deprecation policy; the developer/API portal is inaccessible for crawling and Wave's public marketing pages document no API surface at all, with llms.txt and OpenAPI probes both returning 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 2 · round to Puzzle
   Puzzle~partialclaimed6/10

   Puzzle documents concrete bulk-operation features—batch categorizing transactions, bulk CSV import of manual journal entries, and bulk CSV upload of the Chart of Accounts—plus rule-based automation for categorization, all first-party docs. However, these bulk mechanisms are CSV/rule-based rather than explicitly exposed through the AI/API/MCP layer for an 'AI-native' agent to invoke programmatically at scale. Missing for 10: explicit evidence that the API or MCP integration itself supports issuing bulk operations (not just UI/CSV uploads), and independent/hands-on confirmation of bulk-op reliability at scale.

   • [claimed-docs] “Batch Categorize Transactions”
   • [claimed-docs] “Need to post more than one manual journal entry at a time? Instead of adding them one by one, you can upload a batch of entries all at once …”
   • [claimed-docs] “If you need to bulk add or edit your Chart of Accounts in Puzzle, you can do so by uploading a CSV file directly from your Company Settings.”
   • [claimed-docs] “Creating custom rules”
   • [claimed-docs] “Puzzle's MCP (Model Context Protocol) integration lets you connect your Puzzle account directly to Claude, giving you instant access to your…”

   proof ↗⚑ flag

   Wave~partialprobed2/10

   Wave documents a narrow bulk feature (uploading up to 10 receipts at once with OCR), but there is no evidence of broader bulk operations (e.g., bulk invoice creation/edits, bulk transaction updates) or any API/CLI/MCP surface an AI-native user could script against — the developer portal is crawl-walled and no OpenAPI/llms.txt exists. missing for 10: bulk invoice/transaction/customer operations, programmatic API or CLI access for scripted bulk actions, evidence beyond the 10-item receipt cap.

   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

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

   weight 3 · round to Puzzle
   Puzzle~partialclaimed5/10

   Puzzle documents 'Creating custom rules' for transaction categorization, letting users define rules that automatically trigger categorization when transactions occur, and AI Close agents that automate reconciliation on close events — concrete evidence of rule-based automation tied to events. However, this is scoped narrowly to bookkeeping categorization/close workflows rather than a general-purpose rules engine spanning arbitrary triggers and actions. Missing for 10: evidence of a broader, user-configurable trigger-action framework beyond categorization/close (e.g., custom webhooks, conditional workflows across modules), and independent confirmation of rule behavior in practice.

   • [claimed-docs] “Creating custom rules”
   • [claimed-docs] “Batch Categorize Transactions”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”

   proof ↗⚑ flag

   Wave—none0/10

   Wave offers only a handful of fixed, vendor-built automations (recurring invoices, overdue reminders, auto payroll tax filing, bank auto-categorization) — none of these let a user define custom rules or trigger-action logic on arbitrary events. No evidence of a rules engine, webhooks, or conditional automation builder; the developer/API surface is walled off (403) and marketing pages document no such capability.

   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Wave
   Puzzle—none0/10

   Puzzle documents AI-driven automation for close, categorization, and reconciliation, but there is no evidence of any capability to schedule recurring jobs or workflows (e.g., recurring invoices, scheduled reports, or timed automation triggers).

   ⚑ flag

   Wave~partialprobed3/10

   Wave supports one narrow recurring automation — recurring invoices and payment reminders (wave-docs-10, wave-docs-2) — but there is no evidence of a general-purpose scheduler, API-triggered jobs, or workflow automation platform that an AI-native user could hook into; its developer/API surface is walled off from public documentation (wave-supp-dev-portal-wall, wave-probe-1, wave-probe-2). Missing for 10: programmable/scriptable recurring jobs beyond invoicing, API or webhook-based scheduling, and any AI/automation-platform integration evidence.

   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Puzzle—none0/10

   Puzzle documents automation features (custom categorization rules, AI Close, batch categorization) but no evidence describes versioning, reviewing, or rolling back these automations themselves — the only 'rollback' mentioned is voiding a manual journal entry, not an automation rule change. Missing for 10: version history for rules/automations, review/approval workflow for automation changes, and a documented rollback mechanism for automations.

   • [claimed-docs] “Creating custom rules”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “Puzzle automatically creates a voiding (reversing) journal entry for the original and posts a new entry reflecting your changes”

   proof ↗⚑ flag

   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS with no evidence of automation version control, review workflows, or rollback capabilities for AI-driven automations; the evidence pack shows only accounting features (invoicing, payroll, receipts) and confirms no API/developer docs were accessible.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

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

   Puzzle's AI Close feature explicitly uses AI agents to reconcile accounts, review transactions, and surface discrepancies for month-end close, directly matching the story's core ask (puzzle-docs-24, puzzle-docs-39, puzzle-docs-5). However, evidence doesn't confirm full end-to-end autonomy or explicit 'preparation for human review' handoff workflow beyond general review-before-final claims, and there's no independent/hands-on validation of the AI Close agent's reconciliation accuracy or exception-flagging in practice. missing for 10: independent/hands-on verification of AI Close performance, detailed documentation of exception-flagging logic, explicit human-review handoff/approval workflow, and evidence of full end-to-end (not just partial/batch) reconciliation coverage.

   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “Month-End close with AI Close”
   • [claimed-docs] “Hand off the busywork. Finding software subscriptions, matching invoices to payments, pulling together what your accountant needs — describe…”
   • [claimed-docs] “performing a reconciliation is the best way to ensure every single transaction is accounted for and matches your bank statement exactly—givi…”

   proof ↗⚑ flag

   Wave—none0/10

   Wave's evidence covers auto-import/categorization, invoicing, payroll, and receipts, but there is no mention of an AI agent performing end-to-end reconciliation, flagging exceptions, or preparing a close for human review; no automation/agent framework or API for such orchestration is documented, and the developer portal is a crawl wall with no public API/agent hooks shown.

   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

Bank feeds

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

   weight 3 · round to Wave
   Puzzle✓fullclaimed7/10

   Puzzle's docs describe connecting bank/credit-card accounts and third-party sources (Brex, Ramp, Stripe) with automated categorization (98% categorized) and reconciliation workflows, which directly supports the daily-import banking-reconciliation story (puzzle-docs-29, -15, -14, -13, -18, -19). However, there's no explicit statement about daily import cadence or independent verification of reliability. Missing for 10: explicit 'daily auto-sync' language, third-party/hands-on confirmation of import frequency and accuracy.

   • [claimed-docs] “performing a reconciliation is the best way to ensure every single transaction is accounted for and matches your bank statement exactly—givi…”
   • [claimed-docs] “98% transactions categorized When you connect Brex with Puzzle”
   • [claimed-docs] “2x faster to close books When you connect Ramp with Puzzle”
   • [claimed-docs] “3 min to reconcile revenue When you connect Stripe with Puzzle”
   • [claimed-docs] “Up to 98% auto-categorization”
   • [claimed-docs] “Puzzle customers who fully onboard and connect supported integrations can reduce the time required to complete their monthly close by 50% or…”

   proof ↗⚑ flag

   Wave✓fullclaimed8/10

   Wave's Pro Plan explicitly documents automatic daily bank/credit-card feed import with auto-merge and categorization, directly matching the story, and this is corroborated across multiple marketing pages. Missing for 10: independent/hands-on verification (e.g., user reviews confirming daily reliability) beyond vendor claims, and no detail on credit-card-specific connection flow distinct from bank accounts.

   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”

   proof ↗⚑ flag

Categorization

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

   weight 2 · round to Puzzle
   Puzzle~partialclaimed6/10

   Puzzle clearly ships automatic transaction categorization with high accuracy claims (up to 98%), custom rules, batch categorization, and an 'ask AI' assist button, showing an active categorization engine tied to user-configurable rules. However, there is no explicit documentation describing a feedback loop where the AI model learns from user corrections over time (as opposed to static rules the user manually creates). missing for 10: explicit description of ML/AI learning from user corrections, evidence of improved suggestion accuracy after corrections, independent confirmation of this adaptive behavior.

   • [claimed-docs] “Creating custom rules”
   • [claimed-docs] “Batch Categorize Transactions”
   • [claimed-docs] “Up to 98% auto-categorization”
   • [claimed-docs] “A user can click on a button and “ask AI” for help in categorizing a transaction —without context switching between tools.”
   • [claimed-docs] “98% transactions categorized When you connect Brex with Puzzle”

   proof ↗⚑ flag

   Wave~partialclaimed4/10

   Wave documents automatic bank transaction import and categorization on the Pro Plan (auto-merge/categorize), but no evidence anywhere describes the system learning from user corrections over time — a core part of the story. Missing for 10: any documentation of a learning/adaptive categorization mechanism, evidence that manual recategorization improves future suggestions, and independent/hands-on confirmation of categorization accuracy improving.

   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”

   proof ↗⚑ flag

Reconciliation

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

   weight 3 · round to Puzzle
   Puzzle✓fullclaimed7/10

   Puzzle has a dedicated reconciliation feature for bank/credit card accounts explicitly designed to ensure every transaction is accounted for and matches the bank statement (puzzle-docs-29), plus AI Close automates reconciling accounts, reviewing transactions, and surfacing discrepancies (puzzle-docs-24, puzzle-docs-39). This covers the core reconcile-and-surface-for-review workflow an accountant needs. Missing for 10: explicit documentation of distinct 'matched/unmatched/duplicate' transaction states or UI surfacing terminology, and independent/hands-on validation beyond vendor docs.

   • [claimed-docs] “performing a reconciliation is the best way to ensure every single transaction is accounted for and matches your bank statement exactly—givi…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”

   proof ↗⚑ flag

   Wave~partialclaimed4/10

   Wave documents bank auto-import with auto-merge and categorization (implying some duplicate/match handling), but there is no evidence of a dedicated reconciliation view that explicitly surfaces matched, unmatched, and duplicate transactions for accountant review, nor of bank-to-ledger balance reconciliation reporting. Missing for 10: explicit unmatched-transaction review UI, duplicate-transaction flagging documentation, and a formal reconciliation/statement-balance-match report.

   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”

   proof ↗⚑ flag

Bill management

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

   weight 2 · round drawn
   Puzzle—none0/10

   The evidence pack covers bookkeeping, categorization, close automation, invoicing (AR), and reporting, but contains no mention of vendor bill capture, approval routing, or payment scheduling (AP workflow) anywhere in the docs or help center listings.

   ⚑ flag

   Wave—none0/10

   Evidence only shows Wave lets users 'create unlimited... bills' as a record type (wave-docs-7); there is no mention of vendor bill capture workflow, approval routing, or scheduled bill payments anywhere in the pack. Wave's payments feature is explicitly for receiving customer payments on invoices, not paying vendors (wave-supp-payments), and no AP-specific workflow is documented.

   • [claimed-docs] “Create unlimited estimates, invoices, bills, and bookkeeping records”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

Payables

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

   weight 2 · round drawn
   Puzzle—none0/10

   The evidence pack covers bookkeeping, categorization, month-end close, invoicing (AR), reconciliation, and reporting exports, but contains no mention of accounts payable, vendor bills, bill tracking, or AP aging reports. Missing for 10: any documentation of a bills/AP module, vendor balance tracking, or an AP aging report feature.

   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “Yes, you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “Puzzle's invoice editor lets you build a professional, branded invoice and see exactly how it will look as you go!”

   proof ↗⚑ flag

   Wave—none0/10

   Evidence confirms Wave supports creating bills and general accounting reports (month-to-month/year-to-year comparisons), but nothing documents an accounts-payable aging report or vendor balance tracking at a point in time. Missing for 10: AP aging report, vendor balance summary/statement, point-in-time vendor ledger view.

   • [claimed-docs] “Create unlimited estimates, invoices, bills, and bookkeeping records”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

Close process

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

   weight 2 · round drawn
   Puzzle—none0/10

   The evidence covers AI-assisted month-end close, reconciliation, and journal entry reversals, but nowhere mentions locking closed periods or requiring an explicit reopening step to prevent prior-period changes. This is a standard, applicable accounting-software axis, but no documentation or community evidence confirms it exists in Puzzle.

   ⚑ flag

   Wave—none0/10

   No evidence Wave offers period locking or close controls; docs mention role-based access and reports but nothing about locking closed periods or preventing prior-period edits without explicit reopening.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”

   proof ↗⚑ flag

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

   weight 3 · round to Puzzle
   Puzzle~partialclaimed5/10

   Puzzle's 'AI Close' explicitly automates month-end close by reconciling accounts, reviewing transactions, and surfacing discrepancies (puzzle-docs-24/39), and separate reconciliation docs describe matching bank/credit card transactions (puzzle-docs-29). Cash and accrual accounting are supported (puzzle-docs-20), but there's no evidence of a structured checklist UI, accrual-specific tasks, or multi-person review/sign-off workflow tracking. Missing for 10: explicit checklist/task-list feature, accrual entry tracking, and reviewer sign-off/approval workflow evidence.

   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “performing a reconciliation is the best way to ensure every single transaction is accounted for and matches your bank statement exactly—givi…”
   • [claimed-docs] “Cash **_and_** accrual accounting”
   • [claimed-docs] “Month-End close with AI Close”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of any month-end close checklist, reconciliation tracking, accrual management, or review sign-off workflow; Wave's evidence covers invoicing, payroll, receipts, and basic reports only, and it explicitly positions itself as built for small business owners rather than accountants performing formal close processes.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

Collaboration

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

   weight 3 · round to Wave
   Puzzle—none0/10

   Puzzle markets an accountant-facing page (migration, real-time reports, startup metrics) but no evidence describes actual user invitation, permission levels, or role-scoped access controls for external collaborators. Missing for 10: explicit invite flow, role/permission settings, and any documentation of accountant-specific access restrictions.

   • [claimed-docs] “Migrate from QuickBooks without lifting a finger or losing your client's data”
   • [claimed-docs] “Instantly see startup metrics like ARR, burn, & runway”
   • [claimed-docs] “Get real-time financial reports with one click”

   proof ↗⚑ flag

   Wave✓fullclaimed7/10

   Wave explicitly documents inviting an accountant/bookkeeper with role-scoped access (payroll manager, admin, editor, viewer on Pro, or free accountant/tax pro role), directly matching the story. Missing for 10: independent/hands-on verification of the invite/permissions flow and finer detail on what each role can/cannot edit.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

Data access

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

   weight 3 · round to Puzzle
   Puzzle~partialprobed4/10

   Puzzle documents that users can export a full general ledger and financial statements (cash or accrual) in Excel, CSV, and PDF (open formats), and separately references an API 'architected for deep platform-to-platform integrations,' but no evidence ties GL/trial-balance export specifically to the documented API — exports appear to be a UI feature, and probes for OpenAPI/API docs (openapi.json, swagger.json) all returned 404, suggesting no publicly discoverable API reference. Missing for 10: explicit API endpoint/documentation for pulling GL and trial balance, confirmation of trial balance as a report type, and a working/discoverable OpenAPI spec.

   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats”
   • [claimed-docs] “Yes, you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.puzzle.io/openapi.json, https://help.puzzle.io/swagger.json, https://help.puzzle.io/api…”

   proof ↗⚑ flag

   Wave—none0/10

   Evidence shows Wave's developer/GraphQL API portal exists but is crawl-walled and unverifiable, and explicit probes for llms.txt/openapi/swagger all return 404; no documentation confirms GL or trial balance export via API in open formats (CSV/JSON/XML). Marketing pages describe UI-based 'reports' but never reference an API endpoint for ledger/trial balance data.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

Integrations

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

   weight 2 · round drawn
   Puzzle~partialclaimed6/10

   Puzzle documents direct connections to banking/payment platforms like Stripe, Ramp, and Brex with concrete automation stats (transaction categorization, faster close, revenue reconciliation) and general bank/credit card reconciliation flows, showing banking and payments activity flows into the ledger automatically. However, no evidence names a payroll system integration (e.g., Gusto, Rippling) or shows payroll data flowing into the ledger. Missing for 10: explicit payroll system integrations, independent/hands-on confirmation of banking+payroll auto-sync working end-to-end.

   • [claimed-docs] “3 min to reconcile revenue When you connect Stripe with Puzzle”
   • [claimed-docs] “2x faster to close books When you connect Ramp with Puzzle”
   • [claimed-docs] “98% transactions categorized When you connect Brex with Puzzle”
   • [claimed-docs] “Is my revenue automatically ASC 606 compliant in Puzzle?”
   • [claimed-docs] “performing a reconciliation is the best way to ensure every single transaction is accounted for and matches your bank statement exactly—givi…”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”

   proof ↗⚑ flag

   Wave~partialclaimed6/10

   Wave clearly documents automatic bank-feed import/categorization (Pro plan) and integrated online payments that flow directly into invoicing/accounting records, so banking and payments activity does land in the ledger automatically. However, the payroll product's features (direct deposit, tax filing, employee portal) are described in isolation with no explicit statement that payroll transactions sync into the accounting ledger the way bank/payment data does, and there's no evidence of an API/webhook layer for connecting external banking, payment, or payroll systems beyond Wave's own native modules. Missing for 10: explicit documentation that payroll runs automatically post to the general ledger, and any API/integration surface for external banking or payroll systems.

   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”
   • [claimed-docs] “Run payroll in minutes”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [claimed-docs] “Deposit payments directly into your employees’ bank accounts. Less work for you, and your team will love it.”

   proof ↗⚑ flag

Migration

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

   weight 1 · round to Puzzle
   Puzzle✓fullclaimed6/10

   Puzzle explicitly markets QuickBooks migration ('Migrate from QuickBooks without lifting a finger or losing your client's data', 'Switch in minutes. Free migration.'), directly addressing historical books migration without data loss for founders switching accounting systems. Missing for 10: independent/hands-on verification of transaction-level fidelity during migration, detail on which source systems beyond QuickBooks are supported, and documented handling of complex historical data edge cases (multi-entity, custom categories).

   • [claimed-docs] “Migrate from QuickBooks without lifting a finger or losing your client's data”
   • [claimed-docs] “Switch in minutes. Free migration.”

   proof ↗⚑ flag

   Wave~partialclaimed3/10

   Wave mentions an 'onboarding' process for switching from other accounting software like Freshbooks, but this is a single glancing bullet point with no detail on how historical transactions, ledgers, or account balances are actually imported or whether transaction-level detail is preserved. missing for 10: documented import/migration tool, description of data mapping (chart of accounts, historical invoices, journal entries), evidence that no transaction detail is lost, and any independent user reports of successful bookkeeping migrations.

   • [claimed-docs] “Onboarding when switching from other accounting software, like Freshbooks”
   • [claimed-docs] “When you switch from another payroll software, migrating your data is simple.”

   proof ↗⚑ flag

Invoicing

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

   weight 3 · round to Wave
   Puzzle~partialclaimed4/10

   Puzzle has a documented invoice creation/customization feature with live preview and branded PDFs/emails (puzzle-docs-28, 40, 47), but there is no evidence of built-in online payment collection or of invoice view/paid status tracking, which are core parts of this story. Missing for 10: online payment processing integration for invoices, and view/paid status notifications or dashboards.

   • [claimed-docs] “The editor opens in a split view: the form on the left, a live preview on the right that updates as you type — so you always know what your …”
   • [claimed-docs] “Puzzle's invoice editor lets you build a professional, branded invoice and see exactly how it will look as you go!”
   • [claimed-docs] “Adding your logo and brand color takes just a few steps and applies everywhere your invoice appears — the live preview, downloaded PDFs, and…”

   proof ↗⚑ flag

   Wave✓fullclaimed9/10

   Wave's docs directly cover invoice creation, branded templates, online payment via 'Pay now' (credit card/bank/Apple Pay), and status tracking (viewed, due, paid) plus overdue reminders — exactly matching the story. Missing for 10: independent/hands-on corroboration beyond vendor marketing pages.

   • [claimed-docs] “Know when an invoice is viewed, becomes due, or gets paid, so you can take the right actions to manage your cash flow.”
   • [claimed-docs] “Customers can click a “Pay now” button on invoices and pay instantly by credit card or secure bank payment (ACH/EFT) for as little as 1%2 pe…”
   • [claimed-docs] “Add your logo and brand colors to our professional invoice templates. Drag-and-drop editing makes it easy to customize!”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”

   proof ↗⚑ flag

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

   weight 2 · round to Wave
   Puzzle—none0/10

   Evidence confirms Puzzle has an invoice creation/customization editor (branding, live preview) but no documentation mentions recurring/scheduled invoices or automatic overdue payment reminders. Missing for 10: any mention of recurring invoice scheduling, dunning/reminder automation, or overdue-tracking workflows.

   • [claimed-docs] “The editor opens in a split view: the form on the left, a live preview on the right that updates as you type — so you always know what your …”
   • [claimed-docs] “Puzzle's invoice editor lets you build a professional, branded invoice and see exactly how it will look as you go!”
   • [claimed-docs] “Adding your logo and brand color takes just a few steps and applies everywhere your invoice appears — the live preview, downloaded PDFs, and…”

   proof ↗⚑ flag

   Wave✓fullclaimed8/10

   Wave's documentation explicitly covers both halves of the story: recurring invoices with automatic credit card payments for repeat customers (wave-docs-10), and automatic overdue payment reminders scheduled at 3/7/14 days (wave-docs-2, wave-supp-invoicing). Missing for 10: independent/hands-on corroboration beyond vendor marketing pages, and detail on customizing reminder cadence beyond the fixed schedule.

   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

Receivables

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

   weight 2 · round to Puzzle
   Puzzle~partialclaimed3/10

   Puzzle documents invoice creation/customization (docs-28, docs-40, docs-47) and general ledger/financial statement exports (docs-26, docs-37, docs-45), which are adjacent to AR tracking, but no evidence explicitly describes an aging report or per-customer balance view. missing for 10: explicit AR aging report feature, per-customer balance/statement view, documentation tying invoicing to AR tracking workflows.

   • [claimed-docs] “The editor opens in a split view: the form on the left, a live preview on the right that updates as you type — so you always know what your …”
   • [claimed-docs] “Puzzle's invoice editor lets you build a professional, branded invoice and see exactly how it will look as you go!”
   • [claimed-docs] “Adding your logo and brand color takes just a few steps and applies everywhere your invoice appears — the live preview, downloaded PDFs, and…”
   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats”

   proof ↗⚑ flag

   Wave—none0/10

   Evidence describes general accounting reports (cash-flow trend comparisons) and per-invoice status tracking (viewed/due/paid), but nothing in the pack specifically documents an accounts-receivable aging report or a per-customer balance summary. Missing for 10: explicit AR aging report feature, per-customer balance/statement view, any documentation naming 'aging' or customer-level receivables tracking.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Know when an invoice is viewed, becomes due, or gets paid, so you can take the right actions to manage your cash flow.”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

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

   Puzzle's API supports platform-to-platform integration and journal entries can be created/edited/imported (docs-42, docs-43, docs-31/35), and AI Close uses agents to reconcile and 'review transactions' (docs-24/39), suggesting some agent-assisted, human-reviewed workflow exists. However, there is no documented API endpoint or feature specifically for an agent to draft a journal entry and place it into a distinct 'review queue' state pending accountant approval — the evidence only shows batch/manual entry creation and general AI-close reconciliation, not a draft-and-queue mechanism. Missing for 10: explicit API support for draft/pending journal entry status, a documented review-queue or approval workflow accessible to accountants, and confirmation that AI-drafted entries route through this queue rather than posting directly.

   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”
   • [claimed-docs] “Need to post more than one manual journal entry at a time? Instead of adding them one by one, you can upload a batch of entries all at once …”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “Puzzle automatically creates a voiding (reversing) journal entry for the original and posts a new entry reflecting your changes.”
   • [claimed-docs] “Puzzle automatically creates a voiding (reversing) journal entry for the original and posts a new entry reflecting your changes”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of an API for posting journal entries, nor any review-queue/approval workflow; the developer portal is inaccessible (403) and marketing pages document no API/MCP/CLI surface, and probes for llms.txt/openapi return 404s.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

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

   Puzzle docs confirm chart-of-accounts customization via bulk CSV upload/edit and a flexible Classes dimension with unlimited groups, supporting tag/class-based segmentation. However there's no explicit evidence of configuring account types or creating sub-accounts within the CoA structure. Missing for 10: explicit sub-account hierarchy support, account-type customization details, independent/hands-on corroboration.

   • [claimed-docs] “If you need to bulk add or edit your Chart of Accounts in Puzzle, you can do so by uploading a CSV file directly from your Company Settings.”
   • [claimed-docs] “a user can create an unlimited number of Groups for Classes”

   proof ↗⚑ flag

   Wave—none0/10

   The evidence pack contains no documentation of chart-of-accounts customization, account types, sub-accounts, or class/tag dimensions in Wave; it only vaguely mentions 'Tag it, track it' without describing COA structure, and positions Wave as built for non-accountants using standard double-entry books without customizable account hierarchies. missing for 10: any mention of account type management, sub-account creation, or class/tag dimension reporting.

   • [claimed-docs] “Tag it, track it, and see what's working for your business.”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

Journal entries

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

   weight 3 · round to Puzzle
   Puzzle~partialclaimed7/10

   Puzzle explicitly supports posting manual journal entries, including bulk CSV import for multiple entries and automatic reversing entries when editing an existing entry, indicating standard double-entry JE functionality with edit history. However, there is no explicit documentation confirming enforced debit/credit balancing validation or a dedicated memo/notes field on entries. missing for 10: explicit debit=credit validation, documented memo/description field support.

   • [claimed-docs] “Puzzle automatically creates a voiding (reversing) journal entry for the original and posts a new entry reflecting your changes.”
   • [claimed-docs] “Puzzle automatically creates a voiding (reversing) journal entry for the original and posts a new entry reflecting your changes”
   • [claimed-docs] “Need to post more than one manual journal entry at a time? Instead of adding them one by one, you can upload a batch of entries all at once …”
   • [claimed-docs] “If you need to bulk add or edit your Chart of Accounts in Puzzle, you can do so by uploading a CSV file directly from your Company Settings.”

   proof ↗⚑ flag

   Wave~partialclaimed3/10

   Wave explicitly markets itself as 'real, double-entry accounting software,' implying journal-entry mechanics under the hood, but no evidence pack item documents a manual journal-entry screen, debit/credit balancing UI, or memo field for such entries. Missing for 10: explicit manual journal entry feature documentation, debit/credit balance validation details, memo/note field support, and any independent or hands-on confirmation of this specific workflow.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

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

   Puzzle's AI Close feature explicitly uses AI agents to 'reconcile accounts, review transactions, and surface discrepancies' as part of the month-end close workflow, directly matching the anomaly-flagging story, and reconciliation docs confirm matching transactions against bank statements to catch mismatches. Missing for 10: explicit mention of duplicate-transaction detection specifically, and independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “AI Close helps you automate and accelerate your month-end process using AI agents to reconcile accounts, review transactions, and surface di…”
   • [claimed-docs] “Month-End close with AI Close”
   • [claimed-docs] “performing a reconciliation is the best way to ensure every single transaction is accounted for and matches your bank statement exactly—givi…”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of any AI agent, anomaly detection, duplicate transaction flagging, or automated audit monitoring capability; Wave's evidence covers manual/human-facing bookkeeping, invoicing, payroll and receipts features only, plus a note that its API/developer surface is not documented publicly.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

Audit trail

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

   weight 3 · round drawn
   Puzzle—none0/10

   No evidence describes an audit trail, change log, or user-attributed history of edits across the ledger. The closest related item (docs-31/35) only shows that editing a journal entry creates a reversing entry rather than in-place edits, which is not the same as a queryable audit trail of who changed what and when.

   ⚑ flag

   Wave—none0/10

   Evidence shows multi-user role access (admin/editor/viewer, accountant access) but nowhere documents an audit trail or change log tracking who edited what and when across the ledger. No mention of audit logs, version history, or edit tracking exists in the pack.

   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

Multi entity

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

   weight 2 · round to Puzzle
   Puzzle~partialclaimed5/10

   Puzzle explicitly supports managing multiple companies/entities under one login, and documents a Joiin integration specifically for 'Multi-Entity Reporting', showing entity management and a path to consolidated reporting exist. However, true consolidated financials appear to require a third-party integration (Joiin) rather than a native consolidation engine, and there's no evidence of native cross-entity elimination, intercompany accounting, or a built-in consolidated financial statement generator. Missing for 10: native consolidation/elimination features, evidence of intercompany transaction handling, and independent confirmation the Joiin integration fully satisfies audit-grade consolidated reporting.

   • [claimed-docs] “Puzzle supports managing multiple companies (entities) under one login.”
   • [claimed-docs] “Puzzle supports managing **multiple companies (entities)** under one login.”
   • [claimed-docs] “Puzzle + Joiin Integration: Multi-Entity Reporting”

   proof ↗⚑ flag

   Wave—none0/10

   Wave's pricing is explicitly per-business (subscribe and pay separately for each business), with no mention of consolidation, inter-entity eliminations, or a multi-entity reporting view; evidence explicitly frames Wave as built for individual small business owners, not multi-entity accounting.

   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

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

   weight 2 · round to Puzzle
   Puzzle~partialprobed3/10

   Puzzle exposes an API for embedded accounting and bookkeeping data (puzzle-docs-1, puzzle-docs-42) plus CSV/journal bulk import tools, but there is no documentation claiming or demonstrating that every UI action (invoicing, reconciliation, categorization rules, AI Close workflows) is exposed via the API, and a probe for an OpenAPI/swagger spec returned 404s, suggesting the API surface is not fully public or documented. missing for 10: explicit API-UI parity documentation, public OpenAPI spec, evidence of invoice creation/reconciliation/AI Close being API-accessible.

   • [claimed-docs] “With Puzzle's Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”
   • [claimed-docs] “Need to post more than one manual journal entry at a time? Instead of adding them one by one, you can upload a batch of entries all at once …”
   • [claimed-docs] “If you need to bulk add or edit your Chart of Accounts in Puzzle, you can do so by uploading a CSV file directly from your Company Settings.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.puzzle.io/openapi.json, https://help.puzzle.io/swagger.json, https://help.puzzle.io/api…”

   proof ↗⚑ flag

   Wave—none0/10

   Evidence shows no accessible API documentation (developer portal returns 403, no OpenAPI/llms.txt found), and marketing pages document no API/CLI surface that would let users mirror UI actions programmatically. There's no evidence of API parity with UI features like invoicing, payroll, or bank feeds.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 3 · round to Puzzle
   Puzzle~partialclaimed7/10

   Puzzle documents exporting a full general ledger and financial statements in open formats (Excel, CSV, PDF) for both cash and accrual basis, which supports the core 'export and leave' requirement for financial data. missing for 10: evidence of exporting full account configuration/rules/invoice templates/all metadata, independent user corroboration of the export process, and no explicit data-portability/deletion guarantee.

   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats”
   • [claimed-docs] “Yes, you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence anywhere in the pack of a data export feature (e.g., CSV/QIF export, open-format backups) or data portability tooling; marketing pages focus on invoicing, payroll, receipts, and payments with no mention of exporting or leaving with your data, and the developer/API surface is walled off (403) with no llms.txt or OpenAPI found. Missing for 10: any documented export-to-open-format feature, data portability docs, or migration-out tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Puzzle—none0/10

   No evidence pack item mentions data residency, regional storage options, or any control over where customer data is hosted; Puzzle is an accounting SaaS and this is a fair question for a data platform, but nothing documents such a capability.

   ⚑ flag

   Wave—none0/10

   No evidence anywhere in the pack mentions data residency, regional storage options, or compliance controls for choosing where data is stored; Wave's marketing pages focus entirely on accounting/invoicing/payroll features with no privacy-posture or data-location documentation.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Puzzle—none0/10

   No evidence pack items address data retention policies, deletion controls, or data lifecycle management for user/financial data; the evidence covers accounting features, AI Close, exports, and MCP integration but nothing on retention/deletion controls.

   ⚑ flag

   Wave—none0/10

   Wave is a small-business accounting/invoicing product with no evidence of any data retention or deletion controls, privacy dashboard, or export/erasure tooling in its marketing pages; the developer portal is inaccessible and no API/CLI/MCP docs exist to inspect further.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

3. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Puzzle—none0/10

   No evidence in the pack mentions telemetry, usage tracking, opt-out settings, or privacy controls of any kind — the pack is entirely about accounting features, AI bookkeeping, integrations, and pricing. This is a fair axis for any AI-native SaaS product, but there is no documentation to support it.

   ⚑ flag

   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS product with no evidence of any telemetry opt-out, privacy controls, or usage-tracking settings documented anywhere in its marketing pages; the developer portal is also inaccessible for verification. No mention of an AI-native usage context or telemetry controls exists in the pack.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

Ai insights

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

   weight 3 · round to Puzzle
   Puzzle✓fullclaimed7/10

   Puzzle's MCP integration explicitly connects an AI agent (Claude) to live financial data 'through natural conversation—no exports, no copy-pasting,' and Puzzle's broader API/AI messaging promotes asking plain-English questions like 'Am I ready to raise?' or 'Which months am I actually profitable?' grounded in the ledger. This directly matches the ai-native 'can we afford X' use case backed by live API data. Missing for 10: independent/hands-on verification of accuracy for financial affordability queries, and no explicit example matching the exact 'can we afford X' phrasing.

   • [claimed-docs] “Puzzle's MCP (Model Context Protocol) integration lets you connect your Puzzle account directly to Claude, giving you instant access to your…”
   • [claimed-docs] “lets you connect your Puzzle account directly to Claude, giving you instant access to your financial data through natural conversation — no …”
   • [claimed-docs] “Ask anything about your business, instantly, in plain English. "How's my cash trending?" "Am I ready to raise?" "Which months am I actually …”
   • [claimed-docs] “With Puzzle's Embedded Accounting—powered by our API, your platform gets automated AI bookkeeping, real-time financial insights, and a clean…”
   • [claimed-docs] “Our API was originally architected for deep platform-to-platform integrations.”

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of any AI agent, chat interface, or query capability grounded in live ledger data; the probes show no llms.txt/OpenAPI surface exposed on marketing domain, and the developer/GraphQL API portal is walled off from crawling with no documented AI integration. Marketing pages only describe reports/dashboards, not agent-accessible querying.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

Custom reports

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

   weight 2 · round to Puzzle
   Puzzle~partialclaimed5/10

   Puzzle supports Classes with Groups (puzzle-docs-36) and general ledger/financial statement export in cash or accrual basis (puzzle-docs-26/37/45), plus multi-entity management (puzzle-docs-38/44), but there is no direct evidence of a custom report builder that lets accountants filter/group specifically by class, location, or tag dimensions together. missing for 10: explicit custom report builder UI, evidence of 'location' and 'tag' dimensions (only 'class' is documented), and confirmation that reports can be filtered/grouped by these dimensions simultaneously.

   • [claimed-docs] “a user can create an unlimited number of Groups for Classes”
   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats”
   • [claimed-docs] “Yes, you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “Puzzle supports managing multiple companies (entities) under one login.”

   proof ↗⚑ flag

   Wave—none0/10

   Wave's evidence pack shows only basic month-to-month/year-to-year comparison reports; there is no mention of class, location, or tag-based report filtering/grouping, which is a QuickBooks/Xero-style feature Wave does not advertise (Wave is explicitly positioned as not built for accountants' advanced needs).

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

Statements

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

   weight 3 · round to Puzzle
   Puzzle✓fullclaimed7/10

   Puzzle explicitly supports generating and exporting full general ledger and financial statements (cash or accrual basis) in Excel/CSV/PDF on demand, plus real-time reporting and startup metrics like ARR/burn/runway, which directly serves the founder's need for on-demand P&L/balance sheet/cash-flow reporting. Missing for 10: explicit naming of 'balance sheet' and 'cash-flow statement' as distinct statement types, and independent/hands-on verification of statement accuracy beyond vendor docs.

   • [claimed-docs] “Get real-time financial reports with one click”
   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats”
   • [claimed-docs] “Yes, you can export a full general ledger and financial statements on either cash or accrual basis in excel, csv, and pdf formats.”
   • [claimed-docs] “Cash **_and_** accrual accounting”
   • [claimed-docs] “Instantly see startup metrics like ARR, burn, & runway”

   proof ↗⚑ flag

   Wave~partialclaimed6/10

   Wave uses real double-entry accounting and explicitly offers accounting reports with month-to-month/year-to-year comparisons to identify cash flow trends, implying core financial statements are generated from bookkeeping data. However, evidence never explicitly names or confirms a formal P&L, balance sheet, and cash-flow statement generated on-demand for any custom period — only general 'accounting reports' are described. Missing for 10: explicit documentation of P&L/balance sheet/cash-flow statement outputs, ability to select arbitrary custom date ranges, and independent/hands-on confirmation of statement accuracy.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag