Avalara AvaTax vs Kintsugi

Agent access

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

   weight 2 · round drawn
   Avalara AvaTax✓fullprobed8/10

   Direct probe confirms llms.txt returns HTTP 200 at developer.avalara.com/llms.txt, and docs reference agent-oriented .md pages (e.g. avatax.md, mcp.md) plus a dedicated mcp-servers.md, showing an AI-agent-friendly documentation surface. Missing for 10: independent/community confirmation of an agent successfully consuming llms.txt in practice, and no OpenAPI machine-readable spec found (404s on probe).

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.avalara.com/llms.txt # Avalara Developer > Avalara Developer (developer.avalara.com) is the o…”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [probe] “official MCP server documented at https://developer.avalara.com/mcp-servers.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.avalara.com/openapi.json, https://developer.avalara.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Kintsugi✓fullprobed8/10

   A probe confirms llms.txt is live and served (HTTP 200) with a clear description of the docs, and Kintsugi also documents an official MCP server that gives AI assistants direct access to its API documentation. Together these show agent-oriented docs access is explicitly supported. missing for 10: no independent third-party confirmation of agent usage/quality beyond the vendor's own probe and docs, and no evidence of a machine-readable openapi.json to complement llms.txt (404s on candidate paths).

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.trykintsugi.com/llms.txt # Kintsugi Developer Docs > Automated sales tax compliance, by API. Calcu…”
   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trykintsugi.com/openapi.json, https://docs.trykintsugi.com/swagger.json, https://docs.t…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Avalara AvaTax~partialclaimed6/10

   AvaTax exposes REST v2 APIs and SDKs in multiple languages (C#, Java, JS, Python, PHP, Ruby) that can be scripted headlessly for CI/automation, and API endpoints like CreateTransaction/CreateNexus are clearly designed for programmatic, non-interactive use. However, there is no explicit CI/automation documentation, no CLI tool, and no discussion of authentication patterns, rate limits, or idempotency for automated pipelines. missing for 10: explicit CI/headless usage docs or examples, a dedicated CLI, and evidence of automation-friendly auth/rate-limit handling for unattended pipelines.

   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “90-day AvaTax free trial. Get access to AvaTax APIs and SDKs ... No credit card needed. All you have to do is create an account”

   proof ↗⚑ flag

   Kintsugi~partialprobed6/10

   Kintsugi is API-first: it exposes a REST API and five official SDKs plus configurable API keys, making it straightforward to call from scripts or CI pipelines without a UI. However, there is no explicit CLI, headless-mode documentation, or CI-specific guidance (e.g., GitHub Actions examples) confirming automated pipeline use. Missing for 10: dedicated CLI/headless tooling, CI/CD integration examples, and explicit 'automation' framing beyond generic API/SDK access.

   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
   • [claimed-docs] “Choose when the key should expire: Never, One Month, Six Month, or One Year.”
   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.trykintsugi.com/llms.txt # Kintsugi Developer Docs > Automated sales tax compliance, by API. Calcu…”

   proof ↗⚑ flag

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

   weight 3 · round to Avalara AvaTax
   Avalara AvaTax✓fullprobed8/10

   Avalara documents an official MCP server (mcp.md, mcp-servers.md) exposing AvaTax capabilities—tax calculation, transaction management, nexus handling, AI-powered tax code recommendations—directly usable by AI agents, and a probe confirms the server documentation is live. Missing for 10: independent/hands-on third-party confirmation of the MCP server working in practice and details on transport/auth setup.

   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [probe] “official MCP server documented at https://developer.avalara.com/mcp-servers.md”

   proof ↗⚑ flag

   Kintsugi~partialprobed6/10

   Kintsugi documents an official MCP server that gives AI assistants direct access to its API documentation for building integrations, confirmed by both docs and a probe hit. However, the described purpose is limited to documentation/code-example access rather than full agentic action (e.g., invoking tax calculations, registrations, filings via MCP), and there's no independent/hands-on corroboration of its use. Missing for 10: evidence of MCP-driven actions beyond docs lookup, independent verification of setup/usage, and details on tool/action coverage via the server.

   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   No evidence of an official CLI tool for AvaTax; the ecosystem offers REST SDKs (C#, Java, JS, Python, PHP, Ruby) and an MCP server, but nothing about a command-line interface for AI-native workflows.

   ⚑ flag

   Kintsugi—none0/10

   Kintsugi offers SDKs, REST API, and an MCP server for docs access, but no evidence of an official CLI tool being published or documented anywhere in the evidence pack.

   ⚑ flag

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

   weight 3 · round drawn
   Avalara AvaTax✓fullprobed8/10

   Avalara provides a well-documented public REST v2 API with SDKs in six languages, detailed method-level docs (CreateTransaction, CreateNexus), a free trial for API access, and even an MCP server exposing tax calculation, transaction, and nexus endpoints for AI-driven use. missing for 10: no discoverable OpenAPI/swagger spec at standard endpoints (404s), and no independent/hands-on developer corroboration beyond vendor docs.

   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “90-day AvaTax free trial. Get access to AvaTax APIs and SDKs ... No credit card needed. All you have to do is create an account”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.avalara.com/llms.txt # Avalara Developer > Avalara Developer (developer.avalara.com) is the o…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.avalara.com/openapi.json, https://developer.avalara.com/swagger.json, https://deve…”
   • [probe] “official MCP server documented at https://developer.avalara.com/mcp-servers.md”

   proof ↗⚑ flag

   Kintsugi✓fullprobed8/10

   Kintsugi documents a REST API with numerous endpoints (nexus, registrations, filings, exemptions, tax estimate), five official SDKs generated from an OpenAPI spec, API key management, and an llms.txt for AI-native discovery, plus an MCP server exposing docs to AI assistants. Missing for 10: a publicly reachable OpenAPI/swagger spec (probe found all candidate paths 404) and independent third-party corroboration of API robustness.

   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”
   • [claimed-docs] “Choose when the key should expire: Never, One Month, Six Month, or One Year.”
   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.trykintsugi.com/llms.txt # Kintsugi Developer Docs > Automated sales tax compliance, by API. Calcu…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trykintsugi.com/openapi.json, https://docs.trykintsugi.com/swagger.json, https://docs.t…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

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

   weight 2 · round to Kintsugi
   Avalara AvaTax—none0/10

   No evidence of scoped/least-privilege API credentialing (e.g., API keys limited to specific permissions or agent-scoped tokens); documentation covers general API/SDK access, account keys, and MCP server capabilities but nothing about issuing restricted-scope credentials for agents.

   ⚑ flag

   Kintsugi~partialclaimed4/10

   Kintsugi lets users create API keys with configurable expiration windows (Never/1mo/6mo/1yr), which supports time-boxing credentials, but there's no evidence of scoped/permission-based least-privilege controls (e.g., read-only vs write, endpoint-level restrictions) for issuing to an agent specifically. The MCP server only exposes API docs to assistants, not credential-scoping. Missing for 10: permission/role-based scoping of API keys, agent-specific credential issuance workflow, and documentation tying key creation to least-privilege agent use cases.

   • [claimed-docs] “Choose when the key should expire: Never, One Month, Six Month, or One Year.”
   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Avalara AvaTax✓fullprobed8/10

   Avalara officially documents SDKs for REST v2 APIs across six languages (C#, Java, JavaScript, Python, PHP, Ruby), with clear API method docs and a free trial for building against them. Missing for 10: independent/hands-on developer corroboration of SDK quality and no public OpenAPI spec discoverable (probe returned 404s).

   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”
   • [claimed-docs] “90-day AvaTax free trial. Get access to AvaTax APIs and SDKs ... No credit card needed. All you have to do is create an account”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.avalara.com/openapi.json, https://developer.avalara.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Kintsugi✓fullprobed8/10

   Docs explicitly confirm five official SDKs (Python, TypeScript, Java, PHP, Ruby) generated from a shared OpenAPI spec, plus REST API docs and an official MCP server for AI-assisted integration. Missing for 10: independent/hands-on corroboration of SDK quality and a publicly reachable OpenAPI spec (probe found 404s on candidate URLs).

   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”
   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trykintsugi.com/openapi.json, https://docs.trykintsugi.com/swagger.json, https://docs.t…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   No evidence anywhere in the pack of a webhook/event subscription mechanism for AvaTax; the API/MCP surface described is request-response (transactions, nexus, tax code recommendations) with no push/event notification feature documented.

   ⚑ flag

   Kintsugi—none0/10

   No evidence pack item mentions webhooks, event subscriptions, or push notifications; Kintsugi's documented integration model is REST API/SDK polling and connector sync, not event-driven webhooks.

   ⚑ flag

Agentic features

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

   weight 2 · round to Avalara AvaTax
   Avalara AvaTax~partialclaimed5/10

   Docs mention AI-powered tax code recommendations with confidence levels (avalara-docs-7) and conversational-query analytics for spotting transaction patterns/anomalies (avalara-docs-12), which are AI-generated insight/suggestion features embedded in the product. However, these are narrow (tax-code classification, basic query analytics) rather than broad, proactive insight generation across the product's data, and there's no independent/hands-on evidence validating quality or scope. Missing for 10: evidence of broader analytical dashboards or proactive anomaly/insight surfacing beyond tax-code suggestions, and independent corroboration of the conversational analytics feature's real-world performance.

   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Analyze accounts faster with conversational queries. Explore transactions in detail to spot patterns or anomalies”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”

   proof ↗⚑ flag

   Kintsugi—none0/10

   Kintsugi's evidence shows nexus/threshold determination logic and an MCP server aimed at helping developers build integrations with accurate API docs, not AI-generated insights or suggestions surfaced to end users from their own data. No feature is described that analyzes user data and proactively generates recommendations or insights within the product UI.

   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”
   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

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

   weight 2 · round to Kintsugi
   Avalara AvaTax—none0/10

   AvaTax's evidence shows API/MCP integration for on-demand tax calculation and lookups (transactions, nexus, tax-code suggestions), but nothing describes a scheduling, workflow, or trigger mechanism that lets an AI-native user configure automations that run autonomously in the background without a calling system initiating each request. missing for 10: evidence of scheduled/triggered background jobs, webhooks, or an autonomous workflow engine.

   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”

   proof ↗⚑ flag

   Kintsugi~partialprobed5/10

   Kintsugi's connectors auto-sync transactions and its tax engine autonomously computes nexus, tracks exposure, and can register/file across jurisdictions once configured (kintsugi-docs-1, kintsugi-docs-15), which is background automation, but this is standard SaaS integration behavior rather than a user-defined 'automation' or agentic workflow builder, and the MCP server is scoped only to serving API docs to coding assistants, not orchestrating autonomous tasks (kintsugi-docs-6, kintsugi-probe-3). Missing for 10: evidence of a configurable automation/workflow engine, scheduling or trigger-based agent tasks, and any AI-agent-driven autonomous execution beyond passive data sync.

   • [claimed-docs] “Dozens of prebuilt connectors cover shopping carts, billing systems, ERPs, and accounting platforms. Pick your platform, authorize it once, …”
   • [claimed-docs] “Kintsugi finds the exposure you didn’t know you had, registers you, and files everywhere you sell with real people to support you whenever n…”
   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

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

   weight 3 · round to Avalara AvaTax
   Avalara AvaTax~partialprobed3/10

   Evidence only hints at AI features (AI-powered tax code recommendations, and 'conversational queries' for analyzing accounts) rather than a documented built-in assistant a user can delegate broader tasks to; the MCP server (docs-6/7/8/13, probe-3) is framed as an API surface for external AI agents to call into AvaTax, not an assistant embedded in the product for the user. Missing for 10: a documented in-product chat/assistant UI, description of delegable task scope, and evidence of user-facing conversational workflows beyond a single marketing line.

   • [claimed-docs] “Analyze accounts faster with conversational queries. Explore transactions in detail to spot patterns or anomalies”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [probe] “official MCP server documented at https://developer.avalara.com/mcp-servers.md”

   proof ↗⚑ flag

   Kintsugi—none0/10

   Kintsugi's evidence only describes an MCP server that lets external AI assistants read its API documentation for developers building integrations (kintsugi-docs-6, kintsugi-probe-3) — this is not a built-in assistant inside the product that end users can delegate tasks to. No feature resembling an in-app AI assistant, chat, or task-delegation UI is documented anywhere in the pack.

   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

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

   weight 2 · round to Avalara AvaTax
   Avalara AvaTax~partialprobed6/10

   Avalara ships an official MCP server exposing tax calculation, transaction, and nexus tools that an AI agent can invoke via natural-language requests, plus an AI-powered tax-code recommendation feature that accepts free-text product descriptions and a mention of 'conversational queries' for account analysis. However, there's no first-party chat/NL interface for end users and no independent/hands-on evidence of natural-language command execution in practice. Missing for 10: end-user natural-language UI evidence, independent verification of MCP/NL command reliability, broader NL coverage beyond tax-code suggestion and conversational analytics.

   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Analyze accounts faster with conversational queries. Explore transactions in detail to spot patterns or anomalies”
   • [probe] “official MCP server documented at https://developer.avalara.com/mcp-servers.md”

   proof ↗⚑ flag

   Kintsugi~partialprobed3/10

   Kintsugi ships an official MCP server, but per its own docs it only gives AI assistants access to API documentation/code examples for building integrations—it does not let a user perform actual operations (sync transactions, create registrations, file exemptions) via natural-language commands. Missing for 10: an MCP/agent interface that executes real product actions (nexus checks, filings, registrations) via natural language, evidence of end-to-end task completion through NL commands, independent corroboration of agentic use.

   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Kintsugi
   Avalara AvaTax—none0/10

   The evidence shows only static API method documentation pages (e.g., CreateTransaction, CreateNexus) and SDK lists, with no mention of an interactive 'try it' console or runnable code examples. A probe for OpenAPI/Swagger specs (which typically power interactive references) returned 404s across all candidate paths, and no other evidence points to an interactive explorer.

   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.avalara.com/openapi.json, https://developer.avalara.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   Kintsugi~partialprobed4/10

   Kintsugi has structured API reference pages (get-nexus-for-org, create-registration, get-filings, create-exemption) and SDKs generated from an OpenAPI spec, suggesting a formal reference exists, but no evidence explicitly confirms an interactive 'try it out' console or runnable code examples, and probes for a public openapi.json spec returned 404s. missing for 10: explicit confirmation of in-browser runnable/try-it examples, working public OpenAPI spec endpoint, independent corroboration of interactivity.

   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trykintsugi.com/openapi.json, https://docs.trykintsugi.com/swagger.json, https://docs.t…”

   proof ↗⚑ flag

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

   weight 2 · round to Kintsugi
   Avalara AvaTax—none0/10

   The evidence pack shows explicit probing for common OpenAPI/Swagger spec locations (openapi.json, swagger.json, etc.) all returning 404, and no documentation item claims a downloadable OpenAPI/Swagger file for the REST v2 API; only SDKs and API method docs are mentioned.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.avalara.com/openapi.json, https://developer.avalara.com/swagger.json, https://deve…”
   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”

   proof ↗⚑ flag

   Kintsugi!disputedcontradicted3/10

   Docs assert an OpenAPI spec underlies the SDKs and API reference (kintsugi-docs-10), but a direct probe for standard OpenAPI/Swagger download endpoints (openapi.json, swagger.json, etc.) returned 404 everywhere (kintsugi-probe-2), so no machine-readable spec is actually downloadable. Missing for 10: a working, publicly downloadable OpenAPI/Swagger file or documented export endpoint, and independent confirmation of successful spec retrieval.

   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trykintsugi.com/openapi.json, https://docs.trykintsugi.com/swagger.json, https://docs.t…”

   proof ↗⚑ flag

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

   weight 1 · round to Avalara AvaTax
   Avalara AvaTax~partialclaimed5/10

   Avalara offers a 90-day free trial with API/SDK access without a credit card, which functions as a sandbox for testing without touching production billing data, and the MCP server exposes transaction/nexus endpoints that could be used against trial accounts. However, there's no explicit documentation of a dedicated 'sandbox' environment/endpoint distinct from trial accounts, no mention of sandbox-specific flags or test-mode transaction handling, and no independent confirmation of how cleanly sandbox/trial data is isolated from production. missing for 10: explicit sandbox environment documentation, test-mode API parameters, independent verification of production/sandbox data isolation.

   • [claimed-docs] “90-day AvaTax free trial. Get access to AvaTax APIs and SDKs ... No credit card needed. All you have to do is create an account”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”

   proof ↗⚑ flag

   Kintsugi—none0/10

   No evidence pack mention of a sandbox/test environment, test API keys, or staging mode distinct from production; docs cover connectors, SDKs, nexus, and MCP for docs access but nothing about isolated testing without touching production data.

   ⚑ flag

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

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   Evidence confirms AvaTax exposes versioned REST APIs (e.g., 'REST v2 APIs') but nowhere in the pack is there a documented deprecation policy, versioning changelog, or sunset timeline for API versions. missing for 10: explicit deprecation/versioning policy documentation, changelog of API version lifecycle, sunset notice process.

   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”

   proof ↗⚑ flag

   Kintsugi—none0/10

   Evidence shows a REST API, SDKs generated from an OpenAPI spec, and API key management, but no mention anywhere of API versioning scheme or a documented deprecation policy; the OpenAPI spec itself couldn't even be located via probing. missing for 10: explicit API version numbering/headers, a deprecation/sunset policy document, changelog or migration guidance for breaking changes.

   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trykintsugi.com/openapi.json, https://docs.trykintsugi.com/swagger.json, https://docs.t…”

   proof ↗⚑ flag

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

   weight 2 · round to Kintsugi
   Avalara AvaTax~partialclaimed2/10

   The only hint of multi-item processing is the Nexus API supporting creation of 'one or more' declarations in a call; the MCP and REST docs otherwise describe single-transaction creation and per-item tax-code suggestions (1-3 per query), with no documented batch/bulk transaction, bulk calculation, or bulk import endpoint for AI-native workflows. Missing for 10: a dedicated batch/bulk transaction API, bulk calculation across many line items, and evidence of AI agents invoking such bulk operations via MCP.

   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”

   proof ↗⚑ flag

   Kintsugi~partialclaimed3/10

   Kintsugi's API supports syncing large volumes of transaction data (a full year's worth) and offers paginated list endpoints (e.g., Get Filings, Get Nexus for Org), which implies handling many records, but there is no documented bulk/batch endpoint for creating or updating multiple exemptions, registrations, or other items in a single call. Missing for 10: explicit bulk-create/bulk-update API endpoints, batch operation examples, and evidence of an AI agent orchestrating multi-item actions via MCP or SDK.

   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Avalara AvaTax—none0/10

   The evidence shows AvaTax as an API/MCP-driven tax calculation, transaction, and nexus system, but there is no evidence of a user-facing rules engine where AI-native users can define custom event-triggered automations beyond calling discrete API/MCP endpoints. missing for 10: evidence of a rule-definition interface, event-trigger configuration, or workflow automation engine tied to conditions and actions.

   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”

   proof ↗⚑ flag

   Kintsugi—none0/10

   Kintsugi is a sales-tax compliance API with connectors, SDKs, and an MCP server for documentation access, but there is no evidence of a rules engine or event-triggered automation system where users define conditional actions on events. The MCP server only exposes API docs, not workflow/rule automation.

   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   The evidence pack covers tax calculation, transaction APIs, nexus, SDKs, and an MCP server, but nothing describes scheduling recurring jobs/workflows or any automation/orchestration scheduler capability. Missing for 10: any documentation of recurring job scheduling, workflow automation triggers, or cron-like execution features.

   ⚑ flag

   Kintsugi—none0/10

   Kintsugi's docs describe automatic background transaction syncing and filing, but there is no evidence of an API, SDK, or MCP capability that lets an AI-native user explicitly schedule or configure recurring jobs/workflows (e.g., cron-like triggers, webhook-based automation, or workflow orchestration). The MCP server only exposes documentation access, not job scheduling. Missing for 10: any documented scheduling/automation API, recurring job configuration options, or workflow-orchestration tooling for AI agents.

   • [claimed-docs] “Dozens of prebuilt connectors cover shopping carts, billing systems, ERPs, and accounting platforms. Pick your platform, authorize it once, …”
   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

Certificate management

1. ops userExemption and resale certificates are managed end to end — collected from customers, validated, stored with expiry tracking, and applied automatically at calculation time

   weight 2 · round to Avalara AvaTax
   Avalara AvaTax~partialclaimed5/10

   Avalara's Exemption Certificate Management (ECM/CertCapture) is documented to collect, validate, and store exemption certificates in one place, and AvaTax's tax calculation API is the natural integration point, but the evidence pack never explicitly documents expiry tracking or automatic application of stored certificates at calculation time. missing for 10: explicit documentation of certificate expiry/renewal tracking, and explicit evidence that AvaTax calculation automatically applies stored certificate exemptions without manual steps.

   • [claimed-docs] “Exemption Certificate Management (ECM), also known as CertCapture, helps you collect, validate, and store exemption certificates in one plac…”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules a…”

   proof ↗⚑ flag

   Kintsugi~partialclaimed4/10

   Kintsugi has a Create Exemption API allowing exemption records with type, jurisdiction, and validity dates to be stored (kintsugi-docs-14), but there is no evidence of a customer-facing collection workflow (e.g., certificate upload portal), automated validation of certificate authenticity, expiry-based alerting, or documented automatic application of exemptions at tax-calculation time. missing for 10: customer-facing certificate collection/upload flow, validation logic against jurisdiction rules, expiry tracking/alerts, and documented automatic application of stored exemptions during tax calculation.

   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”
   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”

   proof ↗⚑ flag

Exempt customers

1. developerMark a customer or transaction exempt through the API — with the exemption reason carried through calculation, reporting, and the filed return

   weight 2 · round to Kintsugi
   Avalara AvaTax~partialclaimed3/10

   AvaTax's CreateTransaction API supports recording transactions and Exemption Certificate Management (ECM/CertCapture) exists to collect/validate/store certificates, suggesting the capability exists, but the evidence never shows an explicit exemption/exemptCertNo parameter on the transaction API nor documents how the exemption reason flows through to reporting and filed returns. missing for 10: explicit exemption-reason field/parameter in the transaction API, documented linkage between ECM certificates and CreateTransaction, and evidence the reason appears in filed-return output.

   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Exemption Certificate Management (ECM), also known as CertCapture, helps you collect, validate, and store exemption certificates in one plac…”

   proof ↗⚑ flag

   Kintsugi~partialclaimed5/10

   Kintsugi documents a Create Exemption API that lets developers define exemption type, jurisdiction, and validity dates via the API (kintsugi-docs-14), and the tax estimate/calculation endpoint exists separately (kintsugi-docs-9), implying exemptions feed into tax calc. However there is no explicit documentation showing the exemption reason is carried through calculation, reporting dashboards, and the actual filed return — the pack never ties exemption records to reporting or filing outputs. Missing for 10: evidence that exemption reason propagates into tax reports and filed returns, and confirmation it applies per-transaction or per-customer at calculation time.

   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”
   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”

   proof ↗⚑ flag

Autofile

1. finance leadReturns are prepared, filed, and remitted automatically in every registered jurisdiction — on time, with the vendor's guarantee covering penalties if it files late

   weight 3 · round to Kintsugi
   Avalara AvaTax—none0/10

   The evidence pack covers tax calculation, nexus determination, transaction recording, and exemption certificate management, but contains no documentation of Avalara's actual returns-filing/remittance service or its on-time filing guarantee. A community comment even notes that per-jurisdiction registration and filing remain separate manual work outside of tax calculation tools like Avalara, reinforcing the absence of evidence for automated filing.

   • [community] “Avalara is wildly expensive for what it does, mentioned as an option (along with Stripe Tax, Quaderno) for collecting tax properly, though i…”

   proof ↗⚑ flag

   Kintsugi~partialclaimed5/10

   Docs confirm registration creation, filings retrieval, and marketing copy claiming Kintsugi 'registers you and files everywhere you sell,' indicating automated filing/remittance across jurisdictions. However, there is no explicit documentation of an on-time filing guarantee or penalty-coverage commitment, nor independent evidence corroborating the claim. missing for 10: explicit vendor guarantee/penalty-coverage terms, evidence of remittance execution (not just filing), independent/hands-on confirmation of on-time filing performance.

   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “Kintsugi finds the exposure you didn’t know you had, registers you, and files everywhere you sell with real people to support you whenever n…”

   proof ↗⚑ flag

Filing visibility

1. ops userSee the whole filing picture — a calendar of upcoming returns, per-filing status, the amounts remitted, and downloadable confirmations for every return submitted

   weight 2 · round to Kintsugi
   Avalara AvaTax—none0/10

   The evidence pack covers AvaTax's calculation, transaction recording, nexus, and MCP tooling, but contains no mention of a filing calendar, per-filing status tracking, remitted amounts, or downloadable filing confirmations. A community comment even notes that per-jurisdiction registration and filing remain separate work outside core AvaTax, reinforcing that this dashboard-style filing visibility isn't evidenced here.

   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [community] “Avalara is wildly expensive for what it does, mentioned as an option (along with Stripe Tax, Quaderno) for collecting tax properly, though i…”

   proof ↗⚑ flag

   Kintsugi~partialclaimed3/10

   Kintsugi's Get Filings API supports listing filings with status/date/jurisdiction filters, and Create Registration tracks filings across jurisdictions, giving some per-filing status visibility, but there is no evidence of a calendar view of upcoming returns, remitted amounts, or downloadable filing confirmations. missing for 10: calendar UI for upcoming returns, remittance amount tracking, downloadable confirmation documents for filed returns.

   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”

   proof ↗⚑ flag

Invoice compliance

1. ops userInvoices come out compliant where I sell — required VAT fields, registration numbers, and locale rules flow through to my invoicing system or are generated by the product itself

   weight 2 · round to Avalara AvaTax
   Avalara AvaTax~partialcommunity5/10

   AvaTax calculates jurisdiction-aware tax, validates addresses, and returns transaction-level tax data (avalara-docs-1, avalara-docs-2, avalara-docs-4) that a system could use to populate invoice fields, and nexus data ties to registration obligations (avalara-docs-5, avalara-docs-13). However there is no evidence of AvaTax itself generating compliant invoice documents with required VAT fields/registration numbers or locale-specific invoice formatting — it's positioned as a calculation/transaction API, and community commentary notes registration/filing remain separate manual work (avalara-comm-1). Missing for 10: evidence of actual invoice document generation or field mapping guidance for VAT-compliant invoices, registration number placement on invoices, and locale-specific invoice templates.

   • [claimed-docs] “Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules a…”
   • [claimed-docs] “Validate addresses and map transactions to the correct tax jurisdictions to reduce errors caused by incomplete or inaccurate location data.”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [community] “Avalara is wildly expensive for what it does, mentioned as an option (along with Stripe Tax, Quaderno) for collecting tax properly, though i…”

   proof ↗⚑ flag

   Kintsugi—none0/10

   Evidence describes Kintsugi as a sales-tax/nexus compliance API (calculating tax, tracking nexus, registrations, filings, exemptions) but never mentions VAT-specific invoice requirements, required VAT fields, registration-number formatting, or locale invoicing rules for non-US jurisdictions.

   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”

   proof ↗⚑ flag

Vat coverage

1. founder selling internationallyVAT and GST are covered like US sales tax — EU OSS/IOSS, UK, Canada, Australia and beyond, with foreign registration thresholds tracked and filings supported

   weight 3 · round to Avalara AvaTax
   Avalara AvaTax~partialcommunity6/10

   Avalara's docs confirm global coverage (200+ countries/jurisdictions) and jurisdiction-aware tax calculation, nexus tracking, and transaction management APIs, which supports VAT/GST scenarios beyond US sales tax. However, the evidence pack doesn't explicitly confirm EU OSS/IOSS scheme support, UK-specific VAT filing, or automated foreign registration threshold monitoring/alerts, and a community source notes that registration and filing remain separate manual work even when tax calculation is handled. missing for 10: explicit EU OSS/IOSS scheme documentation, UK/Canada/Australia-specific filing support details, automated foreign registration threshold tracking/alerts, and independent confirmation that filings are actually supported end-to-end rather than requiring separate manual registration/filing work.

   • [claimed-docs] “Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules a…”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Global coverage. Access tax rates and rules for 200+ countries and jurisdictions”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [community] “Avalara is wildly expensive for what it does, mentioned as an option (along with Stripe Tax, Quaderno) for collecting tax properly, though i…”

   proof ↗⚑ flag

   Kintsugi—none0/10

   The evidence pack only describes US-style sales tax nexus, registration, and filing APIs (with generic "Country" fields) but never mentions VAT, GST, EU OSS/IOSS, or specific UK/Canada/Australia regimes, so there is no proof Kintsugi extends its compliance engine to international VAT/GST obligations.

   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”

   proof ↗⚑ flag

Vat validation

1. developerB2B cross-border sales are handled correctly — VAT and tax IDs validated against official registries in real time, reverse charge applied when it should be

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   The evidence pack shows general tax calculation, jurisdiction mapping, nexus handling, and 200+ country coverage, but nothing documents real-time validation of VAT/tax IDs against official registries (e.g., VIES) or automatic application of reverse-charge logic for B2B cross-border transactions. Missing for 10: VAT ID/registry validation API, reverse-charge determination logic, B2B cross-border specific documentation or examples.

   • [claimed-docs] “Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules a…”
   • [claimed-docs] “Validate addresses and map transactions to the correct tax jurisdictions to reduce errors caused by incomplete or inaccurate location data.”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Global coverage. Access tax rates and rules for 200+ countries and jurisdictions”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”

   proof ↗⚑ flag

   Kintsugi—none0/10

   The evidence pack shows Kintsugi handling US-style sales tax, nexus determination, exemptions, and filings, but contains no mention of VAT ID validation against official registries (e.g., VIES), reverse-charge mechanism handling, or any EU/cross-border B2B VAT-specific logic. This is an applicable axis for a tax-compliance product, but no evidence demonstrates it.

   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”
   • [claimed-docs] “Tell Kintsugi where you have: Offices, stores, or warehouses, Employees or contractors, including remote staff working from home, Inventory …”
   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”

   proof ↗⚑ flag

Exposure analysis

1. finance leadImport my historical transactions and see where I already owe — a backdated exposure analysis with estimated liability, penalties, and interest per jurisdiction

   weight 2 · round to Kintsugi
   Avalara AvaTax—none0/10

   Evidence shows nexus determination, transaction creation/retrieval, and tax calculation APIs, but nothing about importing historical transactions to produce a backdated exposure report with estimated liability, penalties, and interest per jurisdiction. missing for 10: historical transaction import/backfill tooling, exposure/liability estimation engine, penalty and interest calculation, jurisdiction-level backdated exposure reporting.

   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”

   proof ↗⚑ flag

   Kintsugi~partialclaimed5/10

   Kintsugi documents historical transaction import spanning the prior calendar year plus current, explicitly for nexus/threshold backdating (kintsugi-docs-3), and markets 'finds the exposure you didn't know you had' with nexus tracking APIs (kintsugi-docs-11, kintsugi-docs-15). However, no evidence describes computing estimated liability, penalties, or interest amounts per jurisdiction — only nexus/threshold detection and registration/filing tracking are documented. Missing for 10: explicit liability/penalty/interest calculation methodology, per-jurisdiction dollar exposure reporting, and any UI/report showing a backdated liability summary.

   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “Kintsugi finds the exposure you didn’t know you had, registers you, and files everywhere you sell with real people to support you whenever n…”
   • [claimed-docs] “Tell Kintsugi where you have: Offices, stores, or warehouses, Employees or contractors, including remote staff working from home, Inventory …”

   proof ↗⚑ flag

Threshold tracking

1. founderThe product watches my economic nexus exposure — tracking sales and transaction counts against every state and country threshold and alerting me before I cross one, not after

   weight 3 · round to Kintsugi
   Avalara AvaTax—none0/10

   Evidence covers nexus declaration (CreateNexus), retrieving existing nexus definitions, and transaction recording/calculation, but nothing shows AvaTax proactively tracking sales/transaction counts against state/country thresholds or alerting a founder before a threshold is crossed. CreateNexus appears to be for declaring nexus you've already determined, not predictive monitoring. Missing for full/partial: any documented threshold-tracking dashboard, automated alerts, or predictive nexus-crossing notifications.

   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”

   proof ↗⚑ flag

   Kintsugi~partialclaimed6/10

   Kintsugi syncs transactions and computes nexus by looking back across the trailing year, and exposes a nexus list endpoint, supporting economic nexus tracking against thresholds — but this evidence is entirely first-party docs with no independent/hands-on corroboration, and none of the pack explicitly describes proactive pre-crossing alerts (only that it 'determines nexus' and 'finds exposure you didn't know you had,' which reads more retrospective than predictive). missing for 10: explicit documentation of real-time threshold alerts/notifications before a crossing occurs, per-state/country threshold configuration detail, and independent confirmation the monitoring works as claimed.

   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “Kintsugi finds the exposure you didn’t know you had, registers you, and files everywhere you sell with real people to support you whenever n…”
   • [claimed-docs] “Dozens of prebuilt connectors cover shopping carts, billing systems, ERPs, and accounting platforms. Pick your platform, authorize it once, …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Avalara AvaTax~partialprobed6/10

   AvaTax exposes broad API/SDK coverage for core functions (tax calculation, transactions, nexus, exemption certs) and even an MCP server with AI-oriented tools like tax code recommendations, suggesting most UI functionality is API-accessible. However, there's no evidence confirming full parity with the UI (e.g., account administration, reporting/dashboards, user management) and no public OpenAPI spec was found via probe, limiting verifiable completeness. missing for 10: explicit UI-to-API parity confirmation, published OpenAPI/spec for full endpoint coverage, evidence covering admin/reporting UI features, independent verification of parity claims.

   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”
   • [claimed-docs] “Exemption Certificate Management (ECM), also known as CertCapture, helps you collect, validate, and store exemption certificates in one plac…”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.avalara.com/openapi.json, https://developer.avalara.com/swagger.json, https://deve…”
   • [probe] “official MCP server documented at https://developer.avalara.com/mcp-servers.md”

   proof ↗⚑ flag

   Kintsugi~partialprobed6/10

   Kintsugi's REST API/SDKs expose most core tax-compliance actions—nexus lookup, registrations, filings, exemptions, transaction sync, tax estimation, product categorization—that mirror the platform's main UI workflows, and it ships 5 official SDKs plus an MCP server for developer docs access. However there is no explicit documentation claiming full UI/API parity, no accessible OpenAPI spec (probe returned 404s), and management-type UI features (account/user settings, dashboard reporting, filing status changes) are not evidenced via API. Missing for 10: explicit parity statement, public OpenAPI spec, evidence covering all UI-only settings/admin functions.

   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trykintsugi.com/openapi.json, https://docs.trykintsugi.com/swagger.json, https://docs.t…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Avalara AvaTax—none0/10

   AvaTax exposes APIs to retrieve individual transactions and nexus records, but the evidence pack contains no mention of bulk/full data export, open-format dumps, or any documented data-portability/exit path for exemption certificates, transaction history, or nexus configurations.

   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [claimed-docs] “Exemption Certificate Management (ECM), also known as CertCapture, helps you collect, validate, and store exemption certificates in one plac…”

   proof ↗⚑ flag

   Kintsugi—none0/10

   No evidence of any data export feature, open-format export, or account portability tooling; the only migration-related content describes importing from Avalara/TaxJar into Kintsugi, not exporting out. This axis is plausible for a SaaS compliance platform, but no supporting evidence exists.

   ⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   No evidence describes data retention controls, deletion APIs, or privacy/compliance settings for AvaTax data; the pack only covers tax calculation, nexus, transactions, and MCP tool access. Missing for 10: any documentation of data retention policy, deletion/right-to-be-forgotten API, or configurable data lifecycle controls.

   ⚑ flag

   Kintsugi—none0/10

   Kintsugi is a sales-tax compliance API; the evidence pack covers connectors, SDKs, nexus tracking, API keys, and MCP docs, but contains no mention of data retention policies, deletion controls, or privacy/data lifecycle settings for AI-native users.

   ⚑ flag

Marketplace rules

1. finance leadMarketplace sales are modeled correctly — transactions where a facilitator (Amazon, app stores) collected the tax are tracked for nexus and reporting without being double-remitted

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   The evidence pack covers general tax calculation, transaction recording, nexus declarations, and jurisdiction mapping, but nothing addresses marketplace facilitator scenarios specifically — e.g., flagging transactions where Amazon or an app store already collected/remitted tax so they count toward nexus thresholds without being taxed/remitted again. This is a standard, fair axis for a tax compliance product, but no documentation, API method, or feature description in the pack mentions facilitator-collected tax, marketplace facilitator laws, or non-remittance flags.

   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”

   proof ↗⚑ flag

   Kintsugi—none0/10

   No evidence describes handling of marketplace-facilitator-collected transactions (e.g., Amazon, app stores) for nexus tracking without double-remittance; docs cover general nexus threshold tracking, transaction sync, and filings but never mention facilitator tax collection status or how it's flagged/excluded from remittance while still counted toward nexus. Missing for 10: any mention of marketplace facilitator flag/field, guidance on excluding facilitator-collected sales from filings, or documentation of nexus counting facilitator sales without double remittance.

   ⚑ flag

Saas rules

1. founder selling softwareThe product gets the hard cases right — SaaS taxability that differs by state, digital-goods rules, and bundled offerings — with the research behind each determination visible

   weight 3 · round to Avalara AvaTax
   Avalara AvaTax~partialclaimed5/10

   AvaTax provides jurisdiction-aware tax calculation, tax code recommendations, and nexus data via API/MCP, which supports differentiated SaaS/digital-goods taxability determinations, but there is no evidence of visible research/rationale behind each determination, no documented handling of bundled-offering taxability logic, and no SaaS-specific taxability guidance. missing for 10: transparent research/citations behind each taxability determination, explicit bundled-offering taxability rules, SaaS-specific taxability examples, independent validation of accuracy on hard cases.

   • [claimed-docs] “Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules a…”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [claimed-docs] “Global coverage. Access tax rates and rules for 200+ countries and jurisdictions”

   proof ↗⚑ flag

   Kintsugi~partialclaimed3/10

   Kintsugi documents product-category/subcategory classification that determines tax treatment across jurisdictions, implying it handles SaaS/digital-goods taxability differences, but there is no evidence of bundled-offering handling or of visible research/citations backing each determination. missing for 10: bundled-offering tax logic, state-by-state SaaS taxability rules detail, visible research/sourcing behind each determination.

   • [claimed-docs] “Kintsugi classifies every product into a category and subcategory, which together determine how it is taxed across jurisdictions.”

   proof ↗⚑ flag

Tax codes

1. developerMap my catalog to the vendor's tax categories — SaaS, digital goods, services, physical products — so each line item is taxed by what it is, in every jurisdiction it sells

   weight 2 · round to Avalara AvaTax
   Avalara AvaTax✓fullclaimed7/10

   AvaTax's core tax-code system lets developers assign a taxability classification (SaaS, digital goods, services, physical goods, etc.) to each catalog item, and the docs show an AI-powered tax-code recommendation tool that returns ranked tax code suggestions from product description/category/itemType, plus transaction creation APIs that use these codes for jurisdiction-aware calculation across 200+ countries. Missing for 10: no explicit documentation of the full tax-code taxonomy/category list or a bulk catalog-mapping workflow example, and no independent/hands-on validation of mapping accuracy.

   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules a…”
   • [claimed-docs] “Global coverage. Access tax rates and rules for 200+ countries and jurisdictions”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”

   proof ↗⚑ flag

   Kintsugi~partialclaimed6/10

   Kintsugi documents a product categorization system (category + subcategory) that determines tax treatment across jurisdictions, which directly addresses mapping catalog items to tax categories, and this feeds into its estimate/calculation endpoints. However, the evidence pack lacks detail on the actual taxonomy (whether SaaS, digital goods, services, physical goods are explicitly distinct built-in categories), how granular the mapping API is, or independent confirmation of jurisdictional accuracy. Missing for 10: explicit list/taxonomy of category types (SaaS/digital/services/physical), API reference for assigning categories per line item, and independent/hands-on validation of correct jurisdictional taxation.

   • [claimed-docs] “Kintsugi classifies every product into a category and subcategory, which together determine how it is taxed across jurisdictions.”
   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”

   proof ↗⚑ flag

Agent operations

1. ai-native userAn agent can read my tax posture — nexus status, registrations, accrued liability, upcoming filings — and act on it through the API or an MCP surface with scoped credentials

   weight 3 · round to Avalara AvaTax
   Avalara AvaTax~partialprobed6/10

   Avalara ships an official MCP server exposing nexus definitions, transaction retrieval, tax code recommendations, and general compliance data (avalara-docs-6,7,8,13; avalara-probe-3), plus REST APIs/SDKs for creating nexus and transactions (avalara-docs-4,5,3) — a real agent-accessible surface. However the evidence never shows endpoints for 'accrued liability' summaries or 'upcoming filings' schedules, nor details on scoped/least-privilege credential issuance for agents. Missing for 10: accrued liability reporting endpoint, filing calendar/upcoming filings API or MCP tool, explicit scoped-credential/auth-scoping documentation for agent use.

   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [probe] “official MCP server documented at https://developer.avalara.com/mcp-servers.md”

   proof ↗⚑ flag

   Kintsugi~partialprobed5/10

   The REST API and SDKs expose real tax-posture endpoints an agent could call — nexus list, registrations, filings, exemptions, tax estimates — and API keys support expiration-based scoping, so the API half of the story is solidly evidenced. However, Kintsugi's actual MCP server is documented as giving AI assistants access to API documentation for building integrations, not as an interface for reading or acting on live nexus/registration/filing data — so the 'MCP surface' part of the story is not delivered as described, only a docs-lookup MCP exists. Missing for 10: an MCP server (or API scope) that lets an agent directly read/act on nexus, registrations, accrued liability and filings rather than just fetch documentation; fine-grained credential scopes beyond key expiration; independent/hands-on confirmation of agentic use.

   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “Choose when the key should expire: Never, One Month, Six Month, or One Year.”
   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

Builtin ai

1. founderThe product ships its own AI for tax questions — is this product taxable in this state, why did this invoice tax this way — answering from its rule base with citations, not a generic chatbot

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   Evidence shows AvaTax exposes APIs/MCP tools for tax calculation, nexus lookup, and AI-powered tax-code suggestions, plus a generic 'conversational queries' feature for transaction analytics — but nothing describes a first-party AI assistant that answers 'is this taxable in this state' or 'why did this invoice tax this way' with citations to its rule base. The MCP/API surface is designed for external agents/integrations to consume, not a built-in citation-grounded tax Q&A product.

   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “Provides AI-powered tax code recommendations for products. Returns 1 to 3 ranked tax code suggestions with confidence levels based on produc…”
   • [claimed-docs] “Analyze accounts faster with conversational queries. Explore transactions in detail to spot patterns or anomalies”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”

   proof ↗⚑ flag

   Kintsugi—none0/10

   Evidence shows Kintsugi's MCP server exposes API documentation for developers building integrations, not an AI agent answering founder-facing tax questions like nexus or invoice-taxation rationale with citations to a rule base. No docs describe a conversational/Q&A tax-explanation feature.

   • [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
   • [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”

   proof ↗⚑ flag

Accuracy guarantee

1. finance leadThe vendor stands behind its numbers — a documented accuracy guarantee or audit support commitment if a calculation it produced turns out wrong

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   No evidence in the pack mentions an accuracy guarantee, indemnification, or audit-defense commitment for calculations produced by AvaTax; documentation focuses on API/SDK capabilities and coverage, not financial/legal backing of results.

   ⚑ flag

   Kintsugi—none0/10

   No evidence of an accuracy guarantee, audit support commitment, or liability coverage for incorrect tax calculations anywhere in the docs; the pack covers integrations, API endpoints, and connectors but nothing about accuracy warranties or audit defense.

   ⚑ flag

Calculation api

1. developerCalculate the right sales tax for a transaction through an API in real time — address-level (rooftop) accuracy, not ZIP-code approximations — fast enough to sit inside checkout

   weight 3 · round to Avalara AvaTax
   Avalara AvaTax✓fullclaimed7/10

   Docs explicitly describe real-time tax calculation during checkout via the CreateTransaction API, with address validation and jurisdiction mapping for rooftop-level accuracy, plus multi-language SDKs for integration into checkout flows. Missing for 10: independent benchmark or hands-on evidence of sub-checkout-latency performance, and explicit confirmation of 'rooftop' (parcel-level) precision versus jurisdiction-level rounding.

   • [claimed-docs] “Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules a…”
   • [claimed-docs] “Validate addresses and map transactions to the correct tax jurisdictions to reduce errors caused by incomplete or inaccurate location data.”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”
   • [claimed-docs] “Global coverage. Access tax rates and rules for 200+ countries and jurisdictions”

   proof ↗⚑ flag

   Kintsugi~partialprobed6/10

   Docs confirm a REST API (tax estimate endpoint POST /v1/tax/estimate) plus SDKs for real-time tax pricing before payment, and product categorization drives jurisdiction-specific taxation — supporting the core 'calculate tax via API' story. However, there is no explicit evidence of address-level (rooftop) precision versus ZIP-level approximation, and no documented latency/performance benchmarks confirming it's fast enough for checkout. missing for 10: explicit rooftop/address-level accuracy claims, latency/performance guarantees for checkout-speed use, independent verification of calculation accuracy.

   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “Kintsugi classifies every product into a category and subcategory, which together determine how it is taxed across jurisdictions.”
   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.trykintsugi.com/llms.txt # Kintsugi Developer Docs > Automated sales tax compliance, by API. Calcu…”

   proof ↗⚑ flag

Integrations

1. developerThere are maintained integrations for my revenue stack — billing systems, payment processors, and commerce platforms feed transactions in without me building the plumbing

   weight 2 · round to Kintsugi
   Avalara AvaTax~partialclaimed3/10

   Evidence shows Avalara exposes REST APIs, SDKs in multiple languages, and a CreateTransaction endpoint that a developer could use to build tax integration into a billing or commerce system, but there is no evidence of maintained, pre-built connectors for specific payment processors, billing systems, or commerce platforms (e.g., Shopify, Stripe, NetSuite plugins) that would let transactions flow in without custom plumbing. Missing for 10: named pre-built platform/plugin integrations, connector marketplace, or documentation of maintained third-party connectors for billing/payment/commerce systems.

   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”
   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [claimed-docs] “90-day AvaTax free trial. Get access to AvaTax APIs and SDKs ... No credit card needed. All you have to do is create an account”

   proof ↗⚑ flag

   Kintsugi~partialclaimed6/10

   Kintsugi advertises dozens of prebuilt connectors for shopping carts, billing systems, ERPs, and accounting platforms, plus REST API/SDKs for custom integrations, which supports the 'no plumbing' claim. However, the evidence pack lacks a named list of specific maintained integrations (e.g., Stripe, Shopify) or independent confirmation of connector reliability/maintenance status. Missing for 10: a documented list of specific named connectors with maintenance status, and independent/hands-on validation that these prebuilt integrations work as advertised.

   • [claimed-docs] “Dozens of prebuilt connectors cover shopping carts, billing systems, ERPs, and accounting platforms. Pick your platform, authorize it once, …”
   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
   • [claimed-docs] “Five official SDKs. Python, TypeScript, Java, PHP and Ruby, each published to its language's package registry and generated from the same Op…”

   proof ↗⚑ flag

Rate maintenance

1. ops userRate and rule changes across thousands of jurisdictions are the vendor's job — updates land automatically, are documented when they take effect, and never require me to redeploy

   weight 2 · round to Avalara AvaTax
   Avalara AvaTax~partialclaimed5/10

   Docs confirm AvaTax is a cloud API that calculates tax using 'current tax rules and boundaries' across 200+ jurisdictions, implying vendor-managed rate/rule updates without client redeploys (avalara-docs-1, avalara-docs-10). However, there's no explicit documentation of an update changelog, notification cadence, or effective-date tracking for jurisdiction rule changes. Missing for 10: documented release notes/changelog for rate changes, explicit statement of update frequency, and confirmation of no-redeploy guarantee beyond implication of being an API service.

   • [claimed-docs] “Calculate sales and use tax during checkout, invoicing, or order processing using jurisdiction-aware logic that reflects current tax rules a…”
   • [claimed-docs] “Global coverage. Access tax rates and rules for 200+ countries and jurisdictions”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”

   proof ↗⚑ flag

   Kintsugi~partialclaimed4/10

   Kintsugi's architecture is API-based (tax estimate endpoint, product categorization engine) which implies tax logic lives server-side and calls always reflect the vendor's current rules without requiring integrator redeploys, but there is no explicit documentation about how often rates/rules are updated or how such changes are communicated/dated to customers. Missing for 10: a documented update cadence or changelog for jurisdiction rate/rule changes, and any statement that changes take effect with a timestamp/notice to ops users.

   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “Kintsugi classifies every product into a category and subcategory, which together determine how it is taxed across jurisdictions.”
   • [claimed-docs] “Kintsugi finds the exposure you didn’t know you had, registers you, and files everywhere you sell with real people to support you whenever n…”

   proof ↗⚑ flag

Registration filing

1. ops userRegistering for a sales tax permit is handled in-product — the vendor files state and local registrations on my behalf with transparent per-registration pricing and status tracking

   weight 2 · round to Kintsugi
   Avalara AvaTax—none0/10

   The evidence pack only covers AvaTax's tax calculation, transaction recording, nexus tracking, and MCP/API capabilities — none of it describes an in-product service where Avalara files state/local sales tax permit registrations on the customer's behalf with per-registration pricing or status tracking. The nexus API merely tracks declared nexus, it does not file registrations. Community evidence (avalara-comm-1) explicitly notes that per-jurisdiction tax registration and filing remains separate work even when using tools like Avalara, reinforcing that this capability is not delivered in-product.

   • [claimed-docs] “Creates one or more new nexus declarations attached to this company... The concept of Nexus indicates a place where your company is legally …”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [community] “Avalara is wildly expensive for what it does, mentioned as an option (along with Stripe Tax, Quaderno) for collecting tax properly, though i…”

   proof ↗⚑ flag

   Kintsugi~partialclaimed5/10

   Kintsugi's marketing copy explicitly claims it 'registers you' for sales tax and files everywhere you sell, and the API exposes a Create Registration endpoint for tracking/managing registrations across jurisdictions, showing in-product registration handling exists. However there is no evidence of transparent per-registration pricing, and status tracking is only inferred from a generic API endpoint rather than documented UI/status flow. Missing for 10: per-registration pricing disclosure, detailed status-tracking workflow/UI evidence, and independent confirmation that Kintsugi actually files the registrations rather than just tracking them.

   • [claimed-docs] “Kintsugi finds the exposure you didn’t know you had, registers you, and files everywhere you sell with real people to support you whenever n…”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”

   proof ↗⚑ flag

Remediation

1. finance leadPast-due exposure has a remediation path — voluntary disclosure agreements or back-filing support to clean up jurisdictions where I should have been collecting

   weight 2 · round to Kintsugi
   Avalara AvaTax—none0/10

   The evidence pack covers nexus tracking, tax calculation, exemption certificates, and transaction APIs, but contains no mention of voluntary disclosure agreements, back-filing, or remediation services for past-due jurisdictions. This is a plausible axis for a tax compliance vendor, but nothing in the pack substantiates it.

   ⚑ flag

   Kintsugi~partialclaimed4/10

   Kintsugi's marketing claims it 'finds the exposure you didn't know you had, registers you, and files everywhere you sell,' and nexus lookback plus registration APIs support identifying past-due exposure and creating registrations, but there is no explicit mention of voluntary disclosure agreements (VDAs) or back-filing of historical periods to clean up past liability. missing for 10: explicit VDA program or negotiation support, back-filing of historical/past-due returns, penalty/interest abatement guidance, any case study or documentation describing remediation of already-accrued exposure rather than just prospective registration and filing.

   • [claimed-docs] “Kintsugi finds the exposure you didn’t know you had, registers you, and files everywhere you sell with real people to support you whenever n…”
   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “Get a list of all nexuses for the organization.”

   proof ↗⚑ flag

Adjustments

1. developerRefunds and credit notes adjust tax correctly — negative amounts flow through liability, reporting, and the next filing without manual journal fixes

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   The evidence pack covers transaction creation, nexus, address validation, and MCP tools, but nothing describes refund/credit-note transaction types, negative-amount handling, or how such adjustments flow into liability reporting or subsequent filings. Missing for 10: documentation of refund/credit-note transaction codes (e.g., ReturnInvoice), negative-amount liability adjustment logic, and evidence that filings/reports automatically reconcile these without manual journal entries.

   ⚑ flag

   Kintsugi—none0/10

   The evidence pack covers transaction syncing, nexus tracking, filings, exemptions, and product categorization, but nothing addresses how refunds or credit notes with negative amounts are processed through liability, reporting, or filings. This is a fair question for a tax compliance API, so the axis applies, but no supporting evidence exists.

   ⚑ flag

Audit trail

1. ops userEvery calculation is reconstructable — the rate, rules, address resolution, and product category that produced each transaction's tax, retained and exportable for an audit

   weight 2 · round to Avalara AvaTax
   Avalara AvaTax~partialclaimed5/10

   AvaTax's CreateTransaction and GetTransactions APIs record and retrieve individual transaction details (address, tax amount, presumably jurisdiction) and nexus/tax-code data can be queried, suggesting some reconstructability, but there is no explicit documentation of a consolidated audit trail showing the exact rate, rule, and product-category reasoning per transaction, nor an export mechanism for audit purposes. Missing for 10: explicit audit-log/export feature documentation, evidence of rule/rate versioning retained per transaction, and independent confirmation of audit usability.

   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [claimed-docs] “Validate addresses and map transactions to the correct tax jurisdictions to reduce errors caused by incomplete or inaccurate location data.”

   proof ↗⚑ flag

   Kintsugi~partialclaimed3/10

   Kintsugi documents product-category classification and a tax estimate/calculation endpoint, plus nexus, registration, exemption and filings APIs, but there is no evidence of a retained, per-transaction breakdown of rate/rules/address resolution or an export mechanism for audit reconstruction. missing for 10: documented storage of calculation inputs (rate, rule, address resolution) per transaction, an audit-log or export feature, and any mention of reconstructability for compliance audits.

   • [claimed-docs] “Kintsugi classifies every product into a category and subcategory, which together determine how it is taxed across jurisdictions.”
   • [claimed-docs] “The tax estimate endpoint (POST /v1/tax/estimate) prices sales tax before you take payment.”
   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”

   proof ↗⚑ flag

Channel imports

1. developerTransactions from every channel can be imported — API backfills and connector syncs from other processors and storefronts — so filings cover my whole business, not just one integration

   weight 2 · round to Kintsugi
   Avalara AvaTax~partialclaimed5/10

   AvaTax exposes a transaction API (CreateTransaction, transaction retrieval/filtering via MCP) and multi-language SDKs, which let developers push or backfill transactions programmatically from any custom integration. However, the evidence pack contains no mention of pre-built connectors or native sync integrations with specific storefronts/processors (e.g., Shopify, Stripe, marketplaces) that would let non-developers or bulk imports cover 'every channel' without custom API work. missing for 10: documented connector/integration marketplace, batch/backfill import tooling, evidence of multi-source reconciliation for filings.

   • [claimed-docs] “Records a new transaction in AvaTax. A transaction represents a unique potentially taxable action that your company has recorded”
   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”
   • [claimed-docs] “Avalara provides SDKs for the REST v2 APIs in the following languages: C#, Java, JavaScript, Python, PHP, Ruby”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”

   proof ↗⚑ flag

   Kintsugi~partialprobed6/10

   Docs confirm prebuilt connectors for carts, billing, ERPs, and accounting platforms plus a REST API/SDKs for backfilling historical transactions (previous full calendar year through today), which supports multi-channel coverage. However, there's no independent/hands-on corroboration of connector breadth or reliability, and OpenAPI spec probes 404, leaving API completeness unverified. Missing for 10: independent verification of connector list/reliability, working public OpenAPI spec, evidence of successful multi-source reconciliation in practice.

   • [claimed-docs] “Dozens of prebuilt connectors cover shopping carts, billing systems, ERPs, and accounting platforms. Pick your platform, authorize it once, …”
   • [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trykintsugi.com/openapi.json, https://docs.trykintsugi.com/swagger.json, https://docs.t…”

   proof ↗⚑ flag

Liability reports

1. finance leadSee accrued liability by jurisdiction at any moment — collected versus owed, filing-ready detail, and exports my accountant and GL can consume

   weight 2 · round to Kintsugi
   Avalara AvaTax~partialcommunity3/10

   AvaTax exposes transaction and nexus data via API/MCP that could underpin liability tracking, but there is no direct evidence of a jurisdiction-level accrued liability report (collected vs owed), filing-ready summaries, or GL/accountant-ready export formats. Community input even notes that filing/registration remains separate manual work outside the core tax calc engine. missing for 10: dedicated liability/reconciliation report, GL export format documentation, collected-vs-owed dashboard evidence.

   • [claimed-docs] “Retrieves a list of transactions for a specific company, using filters to search.”
   • [claimed-docs] “Retrieves nexus definitions so you can determine tax obligations across jurisdictions.”
   • [claimed-docs] “Provides access to the Avalara AvaTax API for tax calculation, transaction management, nexus handling, and compliance data.”
   • [community] “Avalara is wildly expensive for what it does, mentioned as an option (along with Stripe Tax, Quaderno) for collecting tax properly, though i…”

   proof ↗⚑ flag

   Kintsugi~partialclaimed6/10

   Kintsugi provides nexus tracking, filings, registrations, and exemption APIs (get-filings, create-registration, get-nexus-for-org) that could surface liability by jurisdiction, and product categorization determines taxability, but there's no explicit documentation of a 'collected vs owed' liability dashboard or accountant/GL-ready export format. missing for 10: explicit accrued-liability-by-jurisdiction view/report, collected-vs-owed reconciliation feature, documented GL/accountant export formats (e.g. CSV/QBO/NetSuite journal entries), independent confirmation of filing-ready detail accuracy.

   • [claimed-docs] “Get a list of all nexuses for the organization.”
   • [claimed-docs] “The Create Registration API allows users to create a new registration for tracking and managing tax filings efficiently across multiple juri…”
   • [claimed-docs] “The Get Filings API retrieves a paginated list of filings based on filters such as dates, jurisdiction, Country, status, etc.”
   • [claimed-docs] “The Create Exemption API allows you to create a new exemption record. This includes defining details such as exemption type, jurisdiction, C…”
   • [claimed-docs] “Kintsugi classifies every product into a category and subcategory, which together determine how it is taxed across jurisdictions.”
   • [claimed-docs] “Send transactions covering the previous full calendar year through today. Kintsugi determines nexus by looking back across that window, so w…”

   proof ↗⚑ flag