Stripe Tax vs Numeral

Agent access

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

   weight 2 · round to Numeral
   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

   Numeral✓fullprobed9/10

   A 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…”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe Tax
   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

   Numeral~partialprobed4/10

   Numeral 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…”

   proof ↗⚑ flag

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

   weight 3 · round to Numeral
   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

   Numeral✓fullprobed8/10

   Numeral 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”

   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

   Numeral—none0/10

   Evidence covers a REST API, MCP server, and Claude skills, but no official CLI tool is mentioned anywhere in the docs or probes.

   ⚑ 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

   Numeral✓fullprobed8/10

   Numeral 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…”

   proof ↗⚑ flag

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

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

   Numeral—none0/10

   No 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 …”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Numeral
   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

   Numeral~partialprobed6/10

   Numeral 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…”

   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

   Numeral—none0/10

   Evidence 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.

   ⚑ flag

Agentic features

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

   weight 2 · round to Numeral
   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

   Numeral~partialclaimed5/10

   Numeral'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 …”

   proof ↗⚑ flag

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

   weight 2 · round to Numeral
   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

   Numeral~partialclaimed5/10

   Numeral'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”

   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

   Numeral—none0/10

   Numeral 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?"”

   proof ↗⚑ flag

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

   weight 2 · round to Numeral
   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

   Numeral~partialprobed6/10

   Numeral 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”

   proof ↗⚑ flag

Api quality

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

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

   Numeral—none0/10

   Docs 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…”

   proof ↗⚑ flag

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

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

   Numeral—none0/10

   Probes 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…”

   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

   Numeral—none0/10

   No 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.

   ⚑ flag

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

   weight 2 · round to Numeral
   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

   Numeral~partialclaimed4/10

   Numeral'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`”

   proof ↗⚑ flag

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

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

   Numeral—none0/10

   Evidence 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.”

   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 Numeral
   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

   Numeral~partialclaimed7/10

   Numeral'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”

   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 Numeral
   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

   Numeral~partialclaimed4/10

   Numeral'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”

   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 Numeral
   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

   Numeral~partialclaimed6/10

   Numeral'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 …”

   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 Numeral
   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

   Numeral~partialclaimed4/10

   Numeral'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 …”

   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

   Numeral—none0/10

   Numeral'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.”

   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 Numeral
   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

   Numeral~partialclaimed4/10

   Numeral 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”

   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 Numeral
   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

   Numeral~partialclaimed3/10

   Numeral'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”

   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 drawn
   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

   Numeral~partialclaimed3/10

   Numeral 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.”

   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 Numeral
   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

   Numeral~partialclaimed6/10

   Numeral 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…”

   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

   Numeral~partialprobed6/10

   Numeral'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…”

   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

   Numeral—none0/10

   No 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.

   ⚑ 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

   Numeral—none0/10

   The 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.

   ⚑ 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 Stripe Tax
   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

   Numeral—none0/10

   Evidence 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`”

   proof ↗⚑ flag

Tax codes

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

   weight 2 · round to Stripe Tax
   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

   Numeral~partialclaimed4/10

   Numeral'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`”

   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 Numeral
   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

   Numeral✓fullprobed8/10

   Numeral 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”

   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

   Numeral—none0/10

   Numeral 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.”

   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

   Numeral—none0/10

   No 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.

   ⚑ 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

   Numeral~partialprobed6/10

   Docs 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…”

   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 Numeral
   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

   Numeral~partialclaimed6/10

   Numeral 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.”

   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

   Numeral~partialclaimed5/10

   Numeral'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.”

   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 Numeral
   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

   Numeral~partialclaimed6/10

   Numeral 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.”

   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 Stripe Tax
   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

   Numeral—none0/10

   Evidence 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.

   ⚑ 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

   Numeral—none0/10

   The 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.”

   proof ↗⚑ 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

   Numeral~partialclaimed5/10

   Numeral'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`”

   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 Numeral
   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

   Numeral~partialclaimed5/10

   Numeral 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.”

   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 Stripe Tax
   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

   Numeral~partialclaimed4/10

   Numeral 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…”

   proof ↗⚑ flag