Stripe Tax vs Kintsugi

Agent access

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

   weight 2 · round drawn
   Stripe Tax✓fullprobed8/10

   Direct probe evidence confirms an llms.txt file exists at docs.stripe.com/llms.txt (HTTP 200) and per-page markdown docs (e.g. tax.md) are also served, allowing agents to fetch agent-oriented documentation directly. This is Stripe-wide infrastructure that applies to the Tax docs specifically (stripe-tax-docs-2 sourced from tax.md). Missing for 10: no evidence of a dedicated llms-full.txt or Tax-specific agent guide, and no independent/community confirmation of agents successfully using this in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/tax.md # Stripe Tax Automate sales tax, VAT, and GST compliance on all your transactions…”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”

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

   Stripe Tax is fully API-driven (tax calculation, sandbox testing, itemized exports) and Stripe provides a CLI and sandbox environment usable in CI/automation pipelines, supporting headless operation. However, the evidence is generic Stripe platform tooling rather than Stripe Tax-specific CI/automation documentation, and no CI examples, GitHub Actions, or automated testing pipeline integration specific to Tax are shown. missing for 10: Stripe Tax-specific CI/CD pipeline examples, automated testing workflows referencing Tax API, evidence of headless batch/report automation beyond manual sandbox testing.

   • [claimed-docs] “You can use Stripe Tax in a sandbox environment to preview automatic tax calculation behavior for different tax settings.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”

   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 drawn
   Stripe Tax~partialprobed6/10

   Stripe (the platform Stripe Tax belongs to) documents an official MCP server at docs.stripe.com/mcp, evidencing agent connectivity, but the evidence pack has no Stripe Tax-specific MCP tooling details, hands-on agent usage, or independent corroboration of MCP functioning with Stripe Tax specifically. Missing for 10: Stripe Tax-specific MCP tool documentation, independent/hands-on validation of the MCP server working with tax operations, details on scope/coverage of tax-related MCP tools.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   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 to Stripe Tax
   Stripe Tax✓fullprobed7/10

   Stripe (the parent platform) documents an official CLI at docs.stripe.com/stripe-cli, which covers Stripe Tax API usage as part of the broader Stripe API surface. Missing for 10: no Stripe Tax-specific CLI commands or documentation, and no independent/community corroboration of CLI usage specifically for tax workflows.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ 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
   Stripe Tax✓fullprobed8/10

   Stripe Tax is fully API-driven, with documented parameters (shipping_cost, IP geolocation, ship-from address), a sandbox/testing environment, and taxability_reason fields returned via API responses, plus a standalone Tax API doc. Community evidence confirms real-world programmatic integration (VAT/tax rate automation) though with operational gotchas unrelated to API documentation quality. Missing for 10: a discoverable OpenAPI spec (probe returned 404s) and independent hands-on confirmation of API robustness beyond docs.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “To calculate tax on shipping costs, use the `shipping_cost` parameter”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [claimed-docs] “You can use Stripe Tax in a sandbox environment to preview automatic tax calculation behavior for different tax settings.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/tax.md # Stripe Tax Automate sales tax, VAT, and GST compliance on all your transactions…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”

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

   No evidence of Stripe Tax (or Stripe's platform) offering scoped/least-privilege API credential issuance for agents; the pack discusses general API access (restricted keys) nowhere, only tax calculation features, CLI, and MCP server pointers. Missing for 10: any mention of restricted/scoped API keys, OAuth scopes, or agent-specific credential controls.

   ⚑ 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 to Kintsugi
   Stripe Tax~partialprobed5/10

   Evidence shows Stripe's docs reference official npm packages/SDKs for integration (stripe-tax-probe-1) and Stripe Tax is built on the standard Stripe API with docs pages (stripe-tax-docs-1..14), implying SDK-based access, but the pack contains no explicit list of official language SDKs, code samples in multiple languages, or SDK-specific documentation for Tax endpoints. missing for 10: explicit official SDK list/pages for Stripe Tax, multi-language code samples, versioning/release notes for SDKs.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “To calculate tax on shipping costs, use the `shipping_cost` parameter”

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

   The evidence pack contains extensive Stripe Tax documentation on tax calculation, registration, filing, and reporting, but no mention of webhooks, event subscriptions, or any event-driven integration mechanism. Without evidence of webhook support for Stripe Tax events, this applicable axis cannot be credited.

   ⚑ 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 drawn
   Stripe Tax—none0/10

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

   ⚑ flag

   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
   Stripe Tax~partialprobed3/10

   Stripe Tax's core value is automatic tax calculation on every transaction (docs-2, comm-1) and automated US filing via TaxJar integration (docs-10, comm-5), which are background automations that run without manual intervention. However there is no evidence of an AI-native workflow where a user configures agentic automations (e.g., via the general Stripe MCP server or CLI) specifically for tax tasks running autonomously. Missing for 10: explicit AI-agent-configurable automation/trigger setup for tax workflows, evidence of the MCP/CLI being used to orchestrate autonomous background tax processes, and independent confirmation that these automations run without ongoing manual oversight (comm-4 notes filing still requires manual paperwork/payment).

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”
   • [community] “This looks great. Implementing Avalara for tax calculation was a large pain across multiple dimensions. Stripe Tax integrates with TaxJar fo…”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

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

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

   ⚑ flag

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

   Stripe (the platform) documents an official MCP server and CLI (stripe-tax-probe-4, stripe-tax-probe-5) plus an llms.txt for docs discovery, which are the building blocks for AI-agent/natural-language operation, but none of the evidence shows these specifically exposing Stripe Tax's calculation/filing/registration workflows via natural-language commands. Missing for 10: tax-specific MCP tool examples, natural-language usage documentation for Tax operations, and independent confirmation of AI-agent control over tax settings.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”

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

   The evidence pack includes Stripe Tax conceptual docs, an MCP server, and a CLI, but nothing describes an interactive API reference with runnable/try-it code examples; the openapi probe even returned 404s for all candidate spec locations, suggesting no discoverable machine-readable API spec for this evidence pack.

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

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

   The evidence pack includes an explicit probe for OpenAPI/Swagger spec files at all common locations, all returning 404, and no other citation points to a downloadable machine-readable API spec for Stripe Tax; only human-readable docs and an MCP/CLI mention exist.

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

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

   Docs explicitly confirm a sandbox environment can be used to preview automatic tax calculation for different tax settings without touching production, and Stripe's broader test-mode/sandbox architecture is documented via CLI/API tooling. Missing for 10: independent hands-on confirmation of sandbox parity with production data isolation, and no explicit mention of test API keys/test clocks specific to Tax.

   • [claimed-docs] “You can use Stripe Tax in a sandbox environment to preview automatic tax calculation behavior for different tax settings.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

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

   No evidence in the pack discusses API versioning strategy or a documented deprecation policy for Stripe Tax's API; docs cover tax calculation features, CLI/MCP tooling, and community pricing/reliability complaints, none of which address versioning or deprecation commitments.

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

   Stripe Tax docs describe per-transaction tax calculation (including multi-line-item support via shipping_cost) and itemized exports/reports, but there is no evidence of a batch/bulk API endpoint or workflow that lets an AI-native user submit or calculate tax across many separate transactions/items in a single bulk operation. missing for 10: bulk/batch tax-calculation API, documented batch endpoints, evidence of processing many orders in one automated call.

   • [claimed-docs] “To calculate tax on shipping costs, use the `shipping_cost` parameter”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”

   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

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 Kintsugi
   Stripe Tax—none0/10

   No evidence in the pack describes collection, validation, storage, expiry tracking, or automatic application of exemption/resale certificates; the closest related item is VAT number validation (VIES), which is a different mechanism and explicitly noted as one-time only with no re-validation. This is a plausible axis for a tax compliance product, but nothing here shows Stripe Tax supports it end to end.

   • [community] “Note this big gotcha: Stripe's VIES validation only takes place once and there is no way to retrigger it. For compliance purposes you have t…”

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

   The evidence pack shows Stripe Tax can return a taxability_reason for a calculated tax result and supports itemized reporting, but nowhere does it document an API mechanism to mark a customer or transaction as tax-exempt with a specified exemption reason, nor any linkage of that reason through to the filed return. Missing for 10: exemption-marking API/parameter, exemption certificate storage, and evidence the exemption reason propagates into reports and filed returns.

   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”

   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
   Stripe Tax!disputedcontradicted2/10

   Stripe Tax only offers automated filing via a TaxJar integration for US sales tax (stripe-tax-docs-10), not for 'every registered jurisdiction,' and there is no evidence of any penalty guarantee for late filing. Community evidence directly contradicts the 'automatic filing/remittance' claim: users report 'you still have to do everything yourself - filing the papers and wiring money' and recommend using a Merchant of Record instead specifically to avoid doing filing/remittance manually. missing for 10: global (non-US) automated filing coverage, any late-filing penalty guarantee, evidence that remittance itself is automated rather than manual.

   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [community] “This looks great. Implementing Avalara for tax calculation was a large pain across multiple dimensions. Stripe Tax integrates with TaxJar fo…”
   • [community] “Notes on Remitting Stripe Tax to the UK and EU: Unless you're doing something like 1mil ARR it's not worth the hassle, just use a Merchant o…”

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

   Evidence shows Stripe Tax offers filing automation via TaxJar integration (stripe-tax-docs-10) and itemized tax exports (stripe-tax-docs-11), but there is no mention of a filing calendar, per-filing status tracker, remitted-amount summaries, or downloadable filing confirmations. A community report even states that despite Stripe's tooling users 'still have to do everything yourself - filing the papers and wiring money' (stripe-tax-comm-4), reinforcing the absence of a consolidated filing dashboard. Missing for 10: filing calendar view, per-filing status indicators, remitted amount tracking, downloadable confirmation documents.

   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”

   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 Stripe Tax
   Stripe Tax!disputedcontradicted5/10

   Stripe Tax calculates VAT/GST by locale, computes rates based on customer/business location, integrates with Invoicing/Checkout, and supports registration number handling and tax-code based rules (stripe-tax-docs-2,4,5,8,12,14), with a positive first-party account of it automating VAT rate/number syncing (stripe-tax-comm-1). However, concrete community evidence contradicts full 'compliant everywhere' delivery: VIES VAT-number validation only fires once with no re-trigger, requiring manual quarterly re-checks for compliance (stripe-tax-comm-2), a documented incident where Stripe Tax silently stopped billing many customers and left invoices stuck in Draft (stripe-tax-comm-6, acknowledged by a Stripe employee in stripe-tax-comm-7), and reports that international coverage is 'woefully incomplete' (stripe-tax-comm-10). Missing for 10: explicit documentation of which specific VAT fields/registration numbers are auto-populated on the invoice template itself, and independent confirmation that the Draft-invoice/VIES issues have been fully remediated.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Stripe Tax uses the preset product tax code for products that don’t have a PTC set directly.”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”
   • [community] “Note this big gotcha: Stripe's VIES validation only takes place once and there is no way to retrigger it. For compliance purposes you have t…”
   • [community] “I built out my Stripe Tax integration, made sure I had all the addresses I needed for my Canadian customers... deployed it... the same day t…”
   • [community] “(I work at Stripe.) This was a painful read. I'm sorry. We could have done a lot better. We're working on remediations now, and we're sendin…”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   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 Stripe Tax
   Stripe Tax!disputedcontradicted4/10

   Stripe Tax's docs confirm VAT/GST calculation across EU, UK, Canada, Australia and registration-threshold monitoring (docs-2, docs-7, docs-8, docs-14), but the filing-support integration (TaxJar) is explicitly scoped to 'US sales tax' only (stripe-tax-docs-10), and community evidence directly contradicts broader filing/remittance support — one user notes 'you still have to do everything yourself - filing the papers and wiring money' and another says 'If you're selling internationally it's woefully incomplete, so often not that useful' (stripe-tax-comm-4, stripe-tax-comm-10), with a third suggesting a Merchant of Record instead for EU/UK remittance (stripe-tax-comm-11). missing for 10: automated filing/remittance support for VAT/GST jurisdictions beyond US sales tax, and evidence rebutting the community reports of incomplete international coverage.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”
   • [community] “Notes on Remitting Stripe Tax to the UK and EU: Unless you're doing something like 1mil ARR it's not worth the hassle, just use a Merchant o…”

   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 to Stripe Tax
   Stripe Tax!disputedcontradicted4/10

   Stripe Tax docs confirm automated VAT/GST calculation based on customer/business location and tax codes, and a community report confirms VAT-number (VIES) validation exists, but that same first-hand account states validation only fires once and is never re-triggered — contradicting a true 'real-time' registry check — and no evidence anywhere documents explicit reverse-charge logic for B2B cross-border sales. Missing for 10: explicit reverse-charge documentation, continuous/real-time VIES re-validation, and independent confirmation of correct B2B cross-border handling beyond the disputed one-time check.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”
   • [community] “Note this big gotcha: Stripe's VIES validation only takes place once and there is no way to retrigger it. For compliance purposes you have t…”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

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

   Stripe Tax docs mention identifying where you 'might need to register to collect tax based on past transactions' (nexus monitoring), but there is no evidence of importing historical transactions to produce an estimated liability, penalties, and interest per jurisdiction — the core of this backdated exposure-analysis story. missing for 10: historical transaction import, estimated back-tax liability calculation, penalty/interest estimation per jurisdiction, any hands-on or documented feature matching this workflow.

   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”

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

   Stripe Tax docs mention identifying registration obligations based on past transactions and registering 'as soon as you start processing payments,' which implies some threshold-tracking capability, but there is no evidence of proactive, pre-crossing alerts or real-time dashboards tracking sales/transaction counts against every state and country threshold before they're exceeded. Community evidence focuses on calculation and filing integration, not nexus threshold alerting. Missing for 10: explicit alerting/notification mechanism before threshold crossing, real-time nexus dashboard evidence, and independent confirmation that monitoring is forward-looking rather than retrospective.

   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Calculate and report tax on all payments, even those that you process outside of Stripe.”

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

   Docs show deep API coverage for tax calculation (shipping cost, IP geolocation, ship-from address, sandbox testing, itemized reports, taxability_reason) mirroring UI capabilities, and a documented CLI/MCP exist for API-driven workflows. However, registration and filing—explicitly UI-flagged features (docs-7, docs-8, docs-14, docs-10)—appear to rely on Stripe performing them 'on your behalf' or via TaxJar integration rather than exposing full programmatic control, and no evidence confirms these can be fully driven via API alone. missing for 10: explicit API endpoints/parity for tax registration and filing workflows, independent confirmation of full UI-API parity.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “To calculate tax on shipping costs, use the `shipping_cost` parameter”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [claimed-docs] “You can use Stripe Tax in a sandbox environment to preview automatic tax calculation behavior for different tax settings.”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   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 to Stripe Tax
   Stripe Tax~partialclaimed3/10

   Stripe Tax offers itemized exports with line-item tax breakdowns per transaction, which is a data-export capability, but there is no evidence of a comprehensive 'export all data' feature, explicit open-format guarantees (e.g., CSV/JSON specification), or support for fully leaving the platform with your data. missing for 10: full data export scope beyond tax reports, explicit open-format documentation, independent confirmation of unrestricted data portability.

   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”

   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

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

   No evidence in the pack addresses marketplace-facilitator tax collection (Amazon, app stores) or how Stripe Tax tracks facilitator-collected transactions for nexus/reporting purposes without double-remitting. All docs and community items focus on Stripe Tax's own calculation/filing for payments processed through Stripe, not on handling third-party facilitator-collected sales.

   ⚑ 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 Kintsugi
   Stripe Tax!disputedcontradicted4/10

   Stripe Tax docs show product tax codes (PTC) driving taxability determinations and a `taxability_reason` field exposing the rationale for a given tax result (docs-12, docs-13), which partially supports the 'visible research' ask, but there's no documentation specifically addressing state-by-state SaaS taxability nuances or bundled-offering treatment. Community evidence directly contradicts the completeness claim — practitioners call it 'vastly outgunned by its competitors' and 'woefully incomplete' for international/complex sales (comm-9, comm-10), undercutting confidence it reliably nails the hard cases. Missing for 10: documented state-specific SaaS/digital-goods taxability guidance, bundled-offering tax logic, and independent verification that edge-case determinations are correct.

   • [claimed-docs] “Stripe Tax uses the preset product tax code for products that don’t have a PTC set directly.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [community] “Humorously enough we needed a sales tax solution, and Stripe Tax is vastly outgunned by its competitors, possibly leading to the layoffs in …”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   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 drawn
   Stripe Tax~partialcommunity6/10

   Stripe Tax documents product tax codes (PTCs) that determine tax rates based on product type (SaaS, digital goods, services, physical goods) and lets Stripe apply a preset PTC when none is set on a specific item, which is exactly the catalog-mapping mechanism the story asks for. However, community feedback specifically flags coverage gaps when selling internationally ('woefully incomplete' for international jurisdictions), and there's no independent verification that every category/jurisdiction combination is accurately handled. Missing for 10: independent/hands-on confirmation of correct taxability across all four category types and all jurisdictions, and clearer documentation addressing the international completeness gap raised by users.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “Stripe Tax uses the preset product tax code for products that don’t have a PTC set directly.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   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 Kintsugi
   Stripe Tax~partialprobed4/10

   Stripe Tax exposes API access to registrations, calculations, filings, and reports (docs-7,8,10,11,14), and Stripe has a documented MCP server (stripe-tax-probe-4), but there's no evidence the MCP surface exposes tax-specific read/act capabilities (nexus status, accrued liability, upcoming filings) or scoped credentials for an agent to autonomously act on tax posture. missing for 10: MCP server tool list showing tax-specific endpoints (nexus/liability/filings), scoped-credential/permission model for agentic access, and any hands-on/community confirmation of agent-driven tax actions via API or MCP.

   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

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

   Evidence shows Stripe Tax provides rule-based calculation, reporting, and a taxability_reason field for API results, but there is no evidence of a conversational AI/chatbot answering ad-hoc questions like 'is this taxable in this state' with citations. This is a rules/API engine, not an AI-agent Q&A interface. Missing for 10: any AI chat/assistant interface, natural-language Q&A capability, citation-backed reasoning beyond a single API field.

   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”

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

   No evidence pack item mentions an accuracy guarantee, indemnification, or audit support commitment from Stripe if a tax calculation is wrong; documentation covers calculation mechanics, filing, and reporting only, and community threads discuss billing bugs and pricing complaints rather than any guarantee/warranty language. missing for 10: any documented accuracy guarantee, liability/indemnification clause, or audit-defense commitment.

   • [claimed-docs] “Calculate and report tax on all payments, even those that you process outside of Stripe.”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [community] “I built out my Stripe Tax integration, made sure I had all the addresses I needed for my Canadian customers... deployed it... the same day t…”
   • [community] “(I work at Stripe.) This was a painful read. I'm sorry. We could have done a lot better. We're working on remediations now, and we're sendin…”

   proof ↗⚑ 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 drawn
   Stripe Tax~partialcommunity6/10

   Stripe Tax docs confirm real-time API tax calculation based on full customer address, business location, product type, and even IP-based geolocation before an address is captured, which is well beyond ZIP-code-level approximation and is used inside checkout/payment flows (stripe-tax-docs-2, stripe-tax-docs-4, stripe-tax-docs-5, stripe-tax-comm-1). However, there's no explicit documentation of latency/performance guarantees for checkout-speed use, no explicit 'rooftop-accuracy' claim, and community feedback flags that international coverage is 'woefully incomplete' compared to competitors like Avalara (stripe-tax-comm-9, stripe-tax-comm-10), tempering confidence in universal address-level precision. Missing for 10: explicit rooftop/address-level accuracy documentation, published latency/performance benchmarks for checkout integration, and independent verification of accuracy claims across all jurisdictions.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”
   • [community] “Humorously enough we needed a sales tax solution, and Stripe Tax is vastly outgunned by its competitors, possibly leading to the layoffs in …”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   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
   Stripe Tax~partialcommunity5/10

   Stripe Tax is deeply integrated with Stripe's own revenue products (Billing, Invoicing, Checkout, Payment Links) and offers a standalone Tax API that can calculate tax even on payments processed outside Stripe, plus a maintained TaxJar integration for automated US filing. However, there is no evidence of maintained, pre-built connectors to third-party billing systems, payment processors, or commerce platforms (e.g., Shopify, WooCommerce, other PSPs) — using it outside Stripe's own ecosystem still requires developers to build the API plumbing themselves, and community feedback notes it is 'woefully incomplete' for international sellers and inferior to dedicated tax platforms like Avalara that have broader integration ecosystems. missing for 10: documented third-party commerce/payment-processor integrations beyond Stripe's own products and TaxJar, independent confirmation these integrations are actively maintained and cover non-Stripe stacks.

   • [claimed-docs] “Calculate and report tax on all payments, even those that you process outside of Stripe.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “This looks great. Implementing Avalara for tax calculation was a large pain across multiple dimensions. Stripe Tax integrates with TaxJar fo…”
   • [community] “Humorously enough we needed a sales tax solution, and Stripe Tax is vastly outgunned by its competitors, possibly leading to the layoffs in …”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   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 Stripe Tax
   Stripe Tax~partialcommunity7/10

   Docs and community evidence confirm Stripe Tax automatically calculates rates across jurisdictions worldwide based on location/product type without manual rate syncing, and a merchant explicitly notes it eliminated their need to manually sync VAT rates. However, the pack has no evidence of a changelog or documentation specifying exactly when rate/rule changes take effect, and no explicit statement guaranteeing zero-redeploy behavior beyond the general 'automatic' framing. Missing for 10: a public changelog/versioning of rate updates, explicit no-redeploy guarantee, and independent verification that rule updates propagate without any integration changes.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”

   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
   Stripe Tax!disputedcontradicted4/10

   Stripe docs claim Stripe can 'register on your behalf' for tax permits and that Stripe Tax 'integrates with TaxJar to automate filing for US sales tax,' but a hands-on community account explicitly contradicts the filing automation, stating 'you still have to do everything yourself - filing the papers and wiring money' after using Stripe's tax tools. No evidence anywhere shows per-registration pricing transparency or a status-tracking UI for registrations. missing for 10: documented per-registration pricing, in-product registration status tracker, evidence that state/local filings (beyond TaxJar's limited US sales tax scope) are actually filed by Stripe rather than the merchant.

   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [community] “This looks great. Implementing Avalara for tax calculation was a large pain across multiple dimensions. Stripe Tax integrates with TaxJar fo…”

   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
   Stripe Tax!disputedcontradicted4/10

   Stripe Tax docs claim to help identify where past transactions create registration exposure and can register on your behalf, but there's no evidence of voluntary disclosure agreement (VDA) support or back-filing assistance for cleaning up historical non-compliance. A community account (comm-4) directly contradicts any remediation narrative, stating that even with Stripe's new tools 'you still have to do everything yourself - filing the papers and wiring money,' undercutting the impression of an end-to-end remediation path. Missing for 10: explicit VDA/back-filing support, evidence of handling historical liability cleanup, and confirmation that registration assistance extends beyond forward-looking compliance.

   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”

   proof ↗⚑ 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
   Stripe Tax—none0/10

   The evidence pack covers tax calculation, registration, filing integration with TaxJar, and reporting exports, but nothing specifically addresses how refunds or credit notes adjust tax liability/reporting/filing, nor confirms negative amounts flow through without manual journal fixes. This is a reasonable axis for a tax product to be judged on, but no supporting evidence is present.

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

   Docs show itemized exports with line-item tax breakdown, a taxability_reason field explaining the calculation logic, product tax codes, and address-resolution methods (IP geolocation, ship-from address), which together support reconstructing rate, category, and address logic per transaction. However there's no explicit documentation of data retention duration/policy, no audit-specific report bundling all these fields together, and no independent confirmation that exports satisfy audit requirements. Missing for 10: explicit retention/export lifecycle policy, a unified audit trail report combining rate+rules+address+category, and independent/hands-on verification of audit usability.

   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [claimed-docs] “Stripe Tax uses the preset product tax code for products that don’t have a PTC set directly.”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”

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

   Stripe Tax docs claim it can 'calculate and report tax on all payments, even those you process outside of Stripe,' suggesting some cross-channel coverage, but there is no evidence of concrete connector integrations with other processors/storefronts or of an API-based historical backfill mechanism for importing past transactions from other channels. Missing for 10: documented connectors/integrations for third-party processors or storefronts, API endpoints for bulk/backfill import of historical transactions, and independent confirmation these actually cover 'whole business' filings.

   • [claimed-docs] “Calculate and report tax on all payments, even those that you process outside of Stripe.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/tax.md # Stripe Tax Automate sales tax, VAT, and GST compliance on all your transactions…”

   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
   Stripe Tax~partialcommunity5/10

   Stripe Tax provides itemized tax reports/exports and TaxJar-based US filing assistance, giving some filing-ready detail, but there is no documented dashboard showing accrued liability by jurisdiction (collected vs. owed) or GL-mapped exports for accountants, and community reports note filing/remittance still requires manual work and international coverage gaps. missing for 10: explicit collected-vs-owed liability view, GL/accounting-system export format, evidence of jurisdiction-level real-time liability tracking.

   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   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