Avalara AvaTax vs Numeral

Agent access

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

   weight 2 · round to Numeral
   Avalara AvaTax✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 drawn
   Avalara AvaTax✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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 drawn
   Avalara AvaTax—none0/10

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

   ⚑ flag

   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
   Avalara AvaTax✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

   ⚑ flag

   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 Avalara AvaTax
   Avalara AvaTax✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

   ⚑ flag

   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 drawn
   Avalara AvaTax~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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 to Avalara AvaTax
   Avalara AvaTax~partialprobed3/10

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

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

   proof ↗⚑ flag

   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 drawn
   Avalara AvaTax~partialprobed6/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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 Avalara AvaTax
   Avalara AvaTax~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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 to Avalara AvaTax
   Avalara AvaTax~partialclaimed2/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   Numeral—none0/10

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

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Avalara AvaTax—none0/10

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

   ⚑ flag

   Numeral—none0/10

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

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Avalara AvaTax—none0/10

   No evidence of version control, review workflows, or rollback capabilities for AvaTax automations/configurations; the evidence covers tax calculation APIs, SDKs, and an MCP server but nothing about versioning or reverting automation logic.

   ⚑ flag

   Numeral—none0/10

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

   ⚑ 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
   Avalara AvaTax~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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 Avalara AvaTax
   Avalara AvaTax~partialcommunity5/10

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

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

   proof ↗⚑ flag

   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 Avalara AvaTax
   Avalara AvaTax~partialcommunity6/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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 to Numeral
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax~partialprobed6/10

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

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

   proof ↗⚑ flag

   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 drawn
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Avalara AvaTax—none0/10

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

   ⚑ flag

   Numeral—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out settings for AvaTax; the docs cover tax calculation, SDKs, MCP tools, and pricing but say nothing about data collection or privacy controls for AI-native usage.

   ⚑ flag

   Numeral—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for Numeral's product or its AI/MCP features.

   ⚑ flag

Marketplace rules

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

   weight 2 · round drawn
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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 Avalara AvaTax
   Avalara AvaTax~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax~partialprobed6/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

   ⚑ flag

   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 to Avalara AvaTax
   Avalara AvaTax✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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 drawn
   Avalara AvaTax~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   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 drawn
   Avalara AvaTax—none0/10

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

   ⚑ flag

   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
   Avalara AvaTax—none0/10

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

   ⚑ flag

   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 drawn
   Avalara AvaTax~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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 drawn
   Avalara AvaTax~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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 Numeral
   Avalara AvaTax~partialcommunity3/10

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

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

   proof ↗⚑ flag

   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