Numeral vs Kintsugi
Numeral
Numeral Two, Inc.
Numeral wins · 14–13 (19 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to NumeralA live probe confirms llms.txt returns HTTP 200 with a structured doc index at docs.numeral.com/llms.txt, and Numeral also documents agent-oriented resources like Claude skills and an MCP server for AI agents to consult its docs/API. Missing for 10: independent third-party confirmation of an agent successfully using llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
- [claimed-docs] “Claude skills that teach an AI coding agent how to integrate the Numeral tax API correctly.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
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…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to KintsugiNumeral is fundamentally a REST API (create products, calculations, transactions via POST calls) which is inherently callable headlessly from any automation pipeline including CI, and there's also an MCP server exposing account operations as callable tools. However, there is no explicit documentation of CI integration, headless CLI, or automated testing/deployment workflows. missing for 10: explicit CI/CD examples or guidance, a CLI tool for scripted/headless runs, and confirmation of non-interactive auth flows suitable for automation.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
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…”
ai-native userConnect an agent via an official MCP server
weight 3 · round to NumeralNumeral documents an official MCP server exposing nexus, filings, registrations, transactions, sales, products, and exemption certificates as tools an AI agent can call directly, with specific tool documentation and example use cases. Missing for 10: independent/hands-on corroboration beyond first-party docs, and details on authentication/rate limits for the MCP endpoint.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [probe] “official MCP server documented at https://docs.numeral.com/mcp/overview”
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”
ai-native userUse an official CLI
weight 2 · round drawnNumeralnone0/10Evidence covers a REST API, MCP server, and Claude skills, but no official CLI tool is mentioned anywhere in the docs or probes.
ai-native userDrive the product through a documented public API
weight 3 · round drawnNumeral publishes a versioned REST API with documented endpoints (products, transactions, calculations, exemption certificates) and a quickstart guide, plus an llms.txt confirming machine-readable API docs are live (HTTP 200). This is a genuine documented public API an AI-native user could drive directly. Missing for 10: a discoverable OpenAPI/Swagger spec (all candidate paths 404), independent third-party corroboration of API usage.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can now pass `customer.ip` instead of (or in addition to) `customer.address`”
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
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”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to KintsugiNumeralnone0/10No evidence Numeral offers scoped or least-privilege API key/credential issuance for agents; the docs mention a general MCP server exposing the whole account (nexus, filings, transactions, etc.) but nothing about restricting agent permissions or issuing limited-scope tokens. Missing for 10: any mention of API key scopes, role-based permissions, or agent-specific credential issuance.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
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…”
ai-native userBuild against official SDKs
weight 2 · round to KintsugiNumeral offers a documented REST API with detailed object/endpoint docs, an MCP server, and Claude skills for AI agent integration, but there's no evidence of official language-specific SDKs (e.g., Python/JS/Ruby client libraries) — only raw API/docs and an OpenAPI probe that 404s. missing for 10: official multi-language SDK packages, published OpenAPI spec confirming SDK generation, independent developer corroboration of SDK usage.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “Claude skills that teach an AI coding agent how to integrate the Numeral tax API correctly.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
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…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnNumeralnone0/10Evidence covers MCP server, REST API objects, and integrations, but there is no mention of webhooks or event subscriptions anywhere in the docs pack. This is a plausible axis for an API-driven tax platform, but absence of evidence means it must be marked none.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to NumeralNumeral's MCP server exposes nexus, filings, and transaction data as callable tools, enabling an external AI agent to answer questions like 'which states have I triggered nexus in' — a form of AI-derived insight from the data. However, this requires a separate AI agent/client to consume the MCP tools rather than a built-in, native in-product insights/suggestions feature. Missing for 10: evidence of insights or suggestions generated natively within Numeral's own UI/dashboard without requiring an external agent, and any proactive suggestion capability (vs. query-response only).
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
Kintsuginone0/10Kintsugi'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”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnNumeral's core product is autonomous background compliance automation (nexus monitoring, filing, remittance, mail handling, certificate tracking) rather than a user-configurable automation builder, and the MCP server lets an AI agent query/act on nexus, filings, and transactions autonomously. However there's no explicit evidence of scheduled/triggered 'set it and forget it' automations that a user configures themselves via the MCP or API (e.g., recurring jobs, webhooks, or event-driven triggers) — missing for 10: documented scheduling/trigger mechanism for autonomous runs, user-configurable automation workflows, and independent confirmation the MCP tools can run unattended in production.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “We scan, read, and respond to all your sales tax mail from state and local governments.”
- [claimed-docs] “Automatically validate each uploaded certificate * Expiration tracking, renewals, and compliance monitoring”
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”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnNumeralnone0/10Numeral exposes an MCP server so external AI agents (e.g., Claude) can query its tax data, and offers Claude skills for coding agents integrating its API — but this is exposing Numeral as a tool for outside agents, not a built-in AI assistant living inside Numeral's own product UI that a user delegates tasks to. No evidence of an in-product chat/assistant experience is provided.
- [claimed-docs] “Claude skills that teach an AI coding agent how to integrate the Numeral tax API correctly.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
Kintsuginone0/10Kintsugi'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”
ai-native userOperate the product with natural-language commands
weight 2 · round to NumeralNumeral ships a documented MCP server exposing nexus, filings, transactions, and exemption certificates as tools an AI agent can call, explicitly enabling natural-language queries like 'which states have I triggered nexus in' — this is the core enabler for NL-driven operation. However, this is agent-mediated (via MCP tool calls) rather than a native NL command interface within Numeral's own product UI, and there's no evidence of a built-in chat/command box or independent hands-on validation of the NL experience. Missing for 10: first-party NL interface within the product itself, broader coverage of all actions via NL, independent corroboration of real-world usage.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [probe] “official MCP server documented at https://docs.numeral.com/mcp/overview”
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”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to KintsugiNumeralnone0/10Docs describe API endpoints and objects (products, transactions, certificates) but there is no evidence of an interactive reference with runnable/try-it examples; the openapi probe found no spec at standard locations, suggesting no Swagger/Postman-style interactive console.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
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…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to KintsugiNumeralnone0/10Probes explicitly show all common OpenAPI/swagger spec paths return 404, and no evidence pack item links to a downloadable machine-readable spec; only human-readable docs and an llms.txt are found.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
Kintsugidisputedcontradicted3/10Docs 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…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnNumeralnone0/10No evidence of a sandbox/test-mode environment or test API keys distinct from production; docs cover product/tax objects, MCP server, and integrations but never mention sandbox or test-vs-live data separation.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to NumeralNumeral's docs show clear API versioning via dated version paths (e.g., v2026-03-01) in multiple endpoints, indicating a versioning scheme, but no evidence describes a documented deprecation policy, sunset timeline, or migration guidance for older versions. Missing for 10: explicit deprecation policy documentation, version sunset/migration guides, changelog of breaking changes.
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can now pass `customer.ip` instead of (or in addition to) `customer.address`”
Kintsuginone0/10Evidence 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…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to KintsugiNumeralnone0/10Evidence only shows single-item API operations (create one product, one transaction, one certificate_request) with no documented batch/bulk endpoints for processing many items in one call. Bulk operations across many items is a plausible axis for a tax compliance API but no evidence supports it.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
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…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round drawnNumeralnone0/10Evidence shows built-in system behaviors (nexus threshold triggering, certificate expiration tracking, automatic validation) but no capability for an AI-native user to author custom rules that trigger arbitrary actions on events — no rules engine, webhook/trigger configuration, or conditional automation framework is documented.
Kintsuginone0/10Kintsugi is a sales-tax compliance API with connectors, SDKs, and an MCP server for documentation access, but there is no evidence of a rules engine or event-triggered automation system where users define conditional actions on events. The MCP server only exposes API docs, not workflow/rule automation.
- [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
- [claimed-docs] “Build against the REST API or an official SDK. Start with Planning an Integration to choose your integration level, then Syncing Transaction…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnNumeralnone0/10Numeral's docs describe automated recurring compliance processes (auto-filing, remittance, certificate renewal tracking) as built-in product behavior, but there's no evidence that an AI-native user can programmatically schedule or configure recurring jobs/workflows via the API or MCP server — the MCP tools expose read/trigger actions (nexus status, certificate requests) rather than a scheduling primitive. missing for 10: any API/MCP capability to create, list, or manage recurring/scheduled jobs or workflows initiated by the user or agent.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “Automatically validate each uploaded certificate * Expiration tracking, renewals, and compliance monitoring”
Kintsuginone0/10Kintsugi's docs describe automatic background transaction syncing and filing, but there is no evidence of an API, SDK, or MCP capability that lets an AI-native user explicitly schedule or configure recurring jobs/workflows (e.g., cron-like triggers, webhook-based automation, or workflow orchestration). The MCP server only exposes documentation access, not job scheduling. Missing for 10: any documented scheduling/automation API, recurring job configuration options, or workflow-orchestration tooling for AI agents.
- [claimed-docs] “Dozens of prebuilt connectors cover shopping carts, billing systems, ERPs, and accounting platforms. Pick your platform, authorize it once, …”
- [claimed-docs] “Kintsugi's MCP server gives AI assistants direct access to our API documentation, making it easier for developers to build integrations with…”
- [probe] “official MCP server documented at https://docs.trykintsugi.com/docs/mcp/getting-started”
Exemption certificates — stories about exemption certificates in this arenaExemption certificates
Stories about exemption certificates in this arena
Certificate management
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 NumeralNumeral's docs describe a full certificate_request object lifecycle (trigger, read state, cancel) and pricing page confirms automatic validation of uploaded certificates plus expiration tracking, renewals, and compliance monitoring, covering collection, validation, and storage/expiry well. However, there is no explicit evidence that certificates are automatically applied at tax calculation time to exempt a transaction. Missing for 10: direct documentation of certificate application/exemption logic during the calculation API call, and independent/hands-on confirmation of the end-to-end flow.
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [claimed-docs] “Automatically validate each uploaded certificate * Expiration tracking, renewals, and compliance monitoring”
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.”
Exempt customers
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 KintsugiNumeral's docs confirm an `exemption-certificates` object and `certificate_request` workflow (trigger/read/cancel) plus certificate validation and expiration tracking, showing exemption handling exists at the API level. However, there's no evidence of explicitly marking a customer or transaction exempt with a specific exemption reason field, nor documentation showing that reason flows through tax calculation, reporting, and the filed return itself. Missing for 10: explicit API fields/endpoint for setting exemption reason on customer/transaction, documentation of reason propagation into calculation logic, and confirmation it appears in reporting/filed returns.
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [claimed-docs] “Automatically validate each uploaded certificate * Expiration tracking, renewals, and compliance monitoring”
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.”
Filing remittance — stories about filing remittance in this arenaFiling remittance
Stories about filing remittance in this arena
Autofile
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 NumeralNumeral's marketing claims automatic registration, filing, and remittance across jurisdictions 'on time, every time' and handles related mail from tax authorities, showing strong first-party support for the filing/remittance workflow. However, the evidence pack contains no mention of a specific late-filing penalty guarantee or indemnification, which is a core part of the story. Missing for 10: explicit vendor guarantee/indemnification language covering penalties for late filings, independent verification of on-time filing performance.
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “We scan, read, and respond to all your sales tax mail from state and local governments.”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
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…”
Filing visibility
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 NumeralNumeral's docs confirm it manages filings and remittance end-to-end ("Register, file, and remit... on time, every time", MCP tools surfacing filings and nexus status) but there is no evidence of a calendar-style upcoming-returns view, no mention of remitted amounts display, and no mention of downloadable confirmations for submitted returns. missing for 10: calendar view of upcoming filings, remitted-amount reporting per filing, downloadable filing confirmations.
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
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.”
Global vat — stories about global vat in this arenaGlobal vat
Stories about global vat in this arena
Invoice compliance
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 drawnNumeralnone0/10Numeral's docs show tax calculation, transaction/calculation objects, VAT ID validation and nexus/filing management, but there is no evidence of the product generating or feeding compliant invoice documents themselves — no mention of VAT registration numbers on invoices, required invoice line-item fields, or locale-specific invoice formatting rules flowing to an invoicing system.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “Validate customer VAT IDs live”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
Kintsuginone0/10Evidence 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…”
Vat coverage
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 NumeralNumeral markets itself as covering 'US and global jurisdictions' and offers live VAT ID validation, suggesting some non-US tax support, but there is no evidence of specific OSS/IOSS registration, UK/Canada/Australia threshold tracking, or global filing workflows described in the docs. Missing for 10: explicit OSS/IOSS scheme support, per-country (UK, Canada, Australia) registration threshold tracking, and documented global filing/remittance processes beyond the generic 'global jurisdictions' claim.
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “Validate customer VAT IDs live”
Kintsuginone0/10The 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…”
Vat validation
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 NumeralNumeral's pricing page claims 'Validate customer VAT IDs live' (numeral-docs-16), suggesting some real-time VAT ID validation capability, but there is no documentation of reverse charge mechanics, official registry (e.g., VIES) integration, or B2B cross-border transaction logic anywhere in the evidence pack — the product's core narrative is US sales tax nexus/filing, not EU VAT compliance. Missing for 10: reverse charge application logic, explicit official-registry validation (VIES or equivalent), B2B cross-border transaction handling, and any independent corroboration of the VAT ID validation claim.
- [claimed-docs] “Validate customer VAT IDs live”
Kintsuginone0/10The 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…”
Nexus monitoring — stories about nexus monitoring in this arenaNexus monitoring
Stories about nexus monitoring in this arena
Exposure analysis
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 KintsugiNumeral offers a nexus study and MCP tools that report current nexus position per jurisdiction (thresholds, sales/transaction counts), which partially supports exposure monitoring, but there is no evidence of importing historical transactions to back-calculate liability, or of penalty/interest estimation per jurisdiction. missing for 10: historical transaction import for backdated analysis, estimated liability calculation, penalty and interest estimation per jurisdiction.
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “You can connect your sales channels and receive a free nexus study with no contract or upfront commitment required.”
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 …”
Threshold tracking
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 drawnNumeral explicitly tracks nexus position per jurisdiction with live economic thresholds and current sales/transaction counts (numeral-docs-10), offers a free nexus study (numeral-docs-14), and surfaces nexus status via MCP queries (numeral-docs-9). However, there is no explicit evidence of proactive threshold-crossing alerts/notifications sent before a limit is hit — the docs describe on-demand querying of current status rather than an automated pre-crossing warning system. Missing for 10: documented proactive alert/notification mechanism triggered before threshold breach, evidence of alert delivery channels (email/dashboard push), and any independent confirmation of alert timing accuracy.
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “You can connect your sales channels and receive a free nexus study with no contract or upfront commitment required.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
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, …”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnNumeral's docs show broad API coverage of core dashboard functions—products, transactions, calculations, exemption certificates, nexus, filings, registrations—and the MCP server exposes these same objects as agent-callable tools, suggesting strong parity between UI and API/agent access. However, there is no explicit statement that 100% of UI functionality is API-accessible, and a probe for a canonical OpenAPI spec returned 404s, leaving completeness unverified. Missing for 10: an explicit UI-to-API feature parity statement, a confirmed complete OpenAPI/API reference, and independent verification that all dashboard actions (e.g., billing, certificate uploads) are API-reachable.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
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…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnNumeralnone0/10No evidence of any data export feature or open-format data portability for user data (transactions, filings, certificates, etc.); evidence covers API usage, MCP tools, and integrations but nothing about exporting/leaving with data.
Kintsuginone0/10No 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.
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userControl data retention and deletion
weight 2 · round drawnNumeralnone0/10Numeral is a sales-tax compliance platform whose evidence pack covers tax calculation, filings, MCP access, and integrations, but contains no mention of data retention policies, deletion controls, or privacy/data-lifecycle settings that an AI-native user could configure.
Product taxability — stories about product taxability in this arenaProduct taxability
Stories about product taxability in this arena
Marketplace rules
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 drawnNumeralnone0/10The evidence pack details Numeral's nexus tracking, tax calculation, transactions, and filings features, but nowhere mentions marketplace facilitator sales (e.g., Amazon, app stores) or the specific handling needed to track such sales for nexus purposes without double-remitting tax already collected by the facilitator. This is a real and applicable capability for sales tax compliance software, but no evidence addresses it.
Kintsuginone0/10No 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.
Saas rules
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 KintsugiNumeralnone0/10Evidence shows only generic tax calculation via address+product lookup (numeral-docs-1) and certificate/nexus tracking, but nothing about SaaS-specific state-by-state taxability nuances, digital-goods rules, bundled-offering treatment, or visible research/rationale behind determinations.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “Create a product with a POST to `/tax/products`”
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.”
Tax codes
developerMap my catalog to the vendor's tax categories — SaaS, digital goods, services, physical products — so each line item is taxed by what it is, in every jurisdiction it sells
weight 2 · round to KintsugiNumeral's docs confirm a product-taxability model (creating `product` objects via POST /tax/products and computing tax based on address + product set), implying category-based tax logic, but the evidence never surfaces the actual taxonomy (SaaS, digital goods, services, physical goods) or a way for developers to map their catalog into it. missing for 10: explicit tax category list/taxonomy, documented mapping workflow from SKU to category, jurisdiction-specific category rules, and independent verification of correctness.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “Create a product with a POST to `/tax/products`”
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…”
Tax agent access — stories about tax agent access in this arenaTax agent access
Stories about tax agent access in this arena
Agent operations
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 NumeralNumeral documents a dedicated MCP server exposing nexus status, filings, registrations, transactions, and exemption certificates as agent-callable tools, plus a full REST API for programmatic access to tax posture and actions (calculations, transactions, certificates). This directly matches the story of an agent reading and acting on tax posture via API/MCP. missing for 10: no explicit documentation of scoped/least-privilege credential support for the MCP endpoint or API keys, and no independent/hands-on corroboration of the MCP server's real-world reliability.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [probe] “official MCP server documented at https://docs.numeral.com/mcp/overview”
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”
Builtin ai
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 drawnNumeralnone0/10Numeral ships an MCP server that lets external AI agents query raw account data (nexus status, filings, transactions) — e.g. 'which states have I triggered nexus' — but this is infrastructure for connecting third-party/generic AI agents, not a first-party built-in tax-Q&A assistant that answers 'is this taxable' or 'why did this invoice tax this way' from its own rule base with citations. No evidence of a native chatbot or rule-cited answer engine exists in the pack.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Claude skills that teach an AI coding agent how to integrate the Numeral tax API correctly.”
Kintsuginone0/10Evidence 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”
Tax calculation — stories about tax calculation in this arenaTax calculation
Stories about tax calculation in this arena
Accuracy guarantee
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 drawnNumeralnone0/10No evidence of any accuracy guarantee, indemnification, warranty, or audit-support commitment for erroneous tax calculations—only feature descriptions of the API, MCP server, and pricing terms.
Calculation api
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 drawnDocs confirm an API-based flow where you submit an address and products and get back an accurate tax amount, with a create-calculation step before transactions, supporting real-time per-address tax logic (numeral-docs-1, numeral-docs-3, numeral-docs-4). However, there's no explicit claim of rooftop-level (vs ZIP) precision or checkout-speed/latency guarantees, and no independent benchmarking. missing for 10: explicit rooftop-level accuracy claims, latency/performance benchmarks for checkout use, independent verification of real-time speed.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can now pass `customer.ip` instead of (or in addition to) `customer.address`”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
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…”
Integrations
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 drawnNumeral claims 'native integrations for the platforms your business already runs on' and supports connecting sales channels for nexus studies, indicating maintained connections to commerce/billing platforms feed data in without custom plumbing. However, evidence lacks specifics on which billing systems, payment processors, or commerce platforms are actually supported, how they're maintained, or independent confirmation of integration depth/reliability. Missing for 10: named list of specific integrations (Stripe, Shopify, etc.), documentation of integration setup/maintenance process, and independent/hands-on verification that these integrations work reliably.
- [claimed-docs] “Numeral provides native integrations for the platforms your business already runs on.”
- [claimed-docs] “You can connect your sales channels and receive a free nexus study with no contract or upfront commitment required.”
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…”
Rate maintenance
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 NumeralNumeral's core pitch is that it handles tax calculation and returns accurate rates automatically via API (numeral-docs-1), and it manages filings/registrations across jurisdictions (numeral-docs-11), implying rate/rule maintenance is vendor-managed rather than requiring customer redeployment. However, there is no explicit documentation describing how rate/rule changes are tracked, versioned, or communicated to customers, nor any changelog or notice mechanism for jurisdiction rule updates. missing for 10: explicit documentation of automatic rate/rule update process, a changelog or notification system for jurisdiction changes, and confirmation that no client-side redeploy/config change is ever needed when rules change.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
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…”
Tax registrations — stories about tax registrations in this arenaTax registrations
Stories about tax registrations in this arena
Registration filing
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 NumeralNumeral explicitly claims to 'Register, file, and remit across US and global jurisdictions' on the customer's behalf, and its MCP/API surface exposes 'registrations' as an object with status data (nexus position, filing review status), supporting in-product tracking. However, there is no evidence of transparent per-registration pricing — the pricing docs describe billing tied to filings generally, not itemized registration costs. Missing for 10: explicit per-registration price disclosure, and independent/hands-on confirmation that registrations are actually filed (not just claimed).
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Standard accounts run month-to-month with no required contract; you are only billed as filings occur.”
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.”
Remediation
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 KintsugiNumeralnone0/10Evidence covers nexus tracking, registration, filing, remittance, and mail handling, but nothing mentions voluntary disclosure agreements (VDAs) or back-filing/back-tax remediation support for past-due exposure in jurisdictions where the company should have registered earlier.
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.”
Tax reporting — stories about tax reporting in this arenaTax reporting
Stories about tax reporting in this arena
Adjustments
developerRefunds and credit notes adjust tax correctly — negative amounts flow through liability, reporting, and the next filing without manual journal fixes
weight 2 · round drawnNumeralnone0/10The evidence pack covers tax calculation, transactions, exemption certificates, nexus tracking, and filing/remittance, but nowhere mentions refunds, credit notes, or negative-amount adjustments flowing through liability and reporting. This is a fair axis for a tax compliance product, but no documentation addresses it.
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
Kintsuginone0/10The 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.
Audit trail
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 NumeralNumeral's API models a `calculation` object tied to each `transaction`, uses address/IP for resolution, and ties products to tax categories, suggesting the underlying data needed for reconstruction exists (numeral-docs-1,2,3,4). However, there is no evidence of an audit-export feature, a persisted rate/rule breakdown, or a UI/API for retrieving historical calculation detail for audit purposes. missing for 10: explicit audit-trail/export functionality, documentation of retained rate and rule detail per transaction, and any mention of long-term storage/retrieval of calculation inputs for compliance review.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can now pass `customer.ip` instead of (or in addition to) `customer.address`”
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.”
Channel imports
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 KintsugiNumeral documents native integrations for existing sales/business platforms and an API for creating transactions/calculations, suggesting multi-channel ingestion, but the evidence never specifies which connectors exist (e.g., specific processors/storefronts) or confirms historical backfill/import of past transactions rather than just live transaction creation. Missing for 10: named connector list, explicit backfill/historical-import capability, and confirmation multiple channels roll into a unified filing dataset.
- [claimed-docs] “Numeral provides native integrations for the platforms your business already runs on.”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can connect your sales channels and receive a free nexus study with no contract or upfront commitment required.”
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…”
Liability reports
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 KintsugiNumeral tracks nexus position and thresholds per jurisdiction and manages filings/registrations, and its API/MCP exposes transactions, sales, and calculations that could underpin liability tracking, but there is no explicit documentation of a 'collected vs owed' liability view or accountant/GL-ready exports. missing for 10: explicit accrued liability by jurisdiction report, collected-vs-owed breakdown, documented GL/accountant export formats (e.g., CSV/QBO sync).
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
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…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableNumeraln/aNumeral is a tax-compliance SaaS/API product that exposes its own data as an MCP server for external AI agents to call (docs-7, docs-9, probe-3) — it is not itself an agent or agent-runtime that would consume other MCP servers' tools. The 'plug MCP servers into this product' framing is a category error for a backend compliance platform; no evidence pack item describes Numeral acting as an MCP client.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [probe] “official MCP server documented at https://docs.numeral.com/mcp/overview”
Kintsugin/aKintsugi is a tax-compliance SaaS/API platform, not an AI agent; the only MCP-related evidence shows Kintsugi providing its own MCP server for AI assistants to access its API docs (the server role), not Kintsugi acting as a client that plugs in external MCP servers to use their tools. This client-consumption axis is a category mismatch for a compliance API product.
- [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”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableNumeralnone0/10No evidence of versioning, review, or rollback of automations/workflows in Numeral's docs; the product focuses on tax calculation, filing, and MCP-based querying, with no mention of automation history, diffing, or revert capabilities.
ai-native userRead the product's source under an open license
weight 2 · not comparableNumeraln/aNumeral is a closed SaaS tax-compliance product/API, not open-source software; source-code openness is a category error for this type of product.
ai-native userSelf-host the core product
weight 3 · not comparableNumeraln/aNumeral is a hosted sales-tax compliance SaaS (calculations, filings, registrations, MCP/API access), not a product designed to be self-hosted; the axis is a category error for this kind of managed compliance service.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableNumeraln/aNumeral is a sales-tax compliance/API product, not infrastructure with data residency controls; no evidence pack content addresses region/residency choice, and this is a category mismatch rather than a gap in an applicable axis.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableNumeraln/aNumeral is a sales tax compliance/filing product, not an AI model provider or platform with a data-training policy relevant to this axis; no evidence pack content addresses AI training data usage at all.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableNumeralnone0/10No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for Numeral's product or its AI/MCP features.