Avalara AvaTax vs TaxJar

Agent access

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

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

   TaxJar—none0/10

   Direct probes show no llms.txt (404) and no discoverable OpenAPI spec, and no evidence of agent-oriented documentation exists anywhere in the pack.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   proof ↗⚑ flag

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

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

   TaxJar✓fullprobed6/10

   TaxJar exposes a full REST API with API-key auth and official client libraries in seven languages, which supports headless/CI automation for tax calculations, transaction uploads, and nexus tracking. Missing for 10: no published OpenAPI/Swagger spec or llms.txt (both probes 404), no explicit CI/CLI examples or independent hands-on automation reports.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “TaxJar uses API keys to allow access to the API.”
   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
   • [claimed-docs] “'x-api-version' must be specified in API call request headers.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   TaxJar—none0/10

   TaxJar is a SaaS tax API/service, so an official MCP server is a fair question, but evidence only shows a traditional REST API with language SDKs, no MCP server; probes for llms.txt and OpenAPI spec both returned 404s, indicating no AI-native integration surface.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   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

   TaxJar—none0/10

   No evidence of an official CLI tool; TaxJar offers API clients in several languages but nothing resembling a command-line interface, and probes for openapi/llms.txt failed, suggesting no such tooling exists.

   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   proof ↗⚑ flag

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

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

   TaxJar✓fullprobed7/10

   TaxJar documents a full public REST API with API-key auth, versioned headers, and official client libraries in seven languages, covering rate lookups, transaction upload, and tax code parameters — clearly a documented public API for programmatic/agentic use. missing for 10: no discoverable OpenAPI/Swagger spec or llms.txt (probes returned 404s), and no independent/hands-on corroboration of API usability beyond vendor docs.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “TaxJar uses API keys to allow access to the API.”
   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
   • [claimed-docs] “'x-api-version' must be specified in API call request headers.”
   • [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   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

   TaxJar—none0/10

   TaxJar's docs only describe a single API key mechanism with no mention of scoped, least-privilege, or per-agent credential issuance; no OAuth scopes, roles, or granular permission tokens are evidenced, and OpenAPI/llms.txt probes returned 404.

   • [claimed-docs] “TaxJar uses API keys to allow access to the API.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   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

   TaxJar✓fullprobed7/10

   TaxJar documents official API clients across seven languages (Ruby, Python, PHP, Node, C#/.NET, Java, Go) with API key auth and versioned headers, giving AI-native developers concrete official SDKs to build against. Missing for 10: no public OpenAPI spec or llms.txt (both probes 404), and no independent/hands-on corroboration of SDK quality or completeness.

   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
   • [claimed-docs] “TaxJar uses API keys to allow access to the API.”
   • [claimed-docs] “'x-api-version' must be specified in API call request headers.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   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

   TaxJar—none0/10

   No evidence of any webhook or event-subscription capability in TaxJar's API docs; only REST API key access, client libraries, and integrations are documented, with no mention of webhooks.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “TaxJar uses API keys to allow access to the API.”
   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”

   proof ↗⚑ flag

Agentic features

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

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

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

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

   proof ↗⚑ flag

   TaxJar—none0/10

   No evidence of AI-generated insights, recommendations, or in-product analytics powered by AI; the nexus threshold tracker (taxjar-docs-7/8) is rule-based reporting, not AI-generated. Missing for 10: any mention of AI/ML-driven insights, natural-language summaries, or suggestion features within TaxJar.

   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”

   proof ↗⚑ flag

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

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

   TaxJar~partialclaimed4/10

   TaxJar's AutoFile feature runs autonomously in the background to file and remit state tax returns without manual intervention, which is a genuine 'set-and-forget' automation. However, this is a single fixed built-in feature rather than a general automation framework letting AI-native users configure their own triggers/workflows, and there is no evidence of webhooks, scheduled jobs, or agent-friendly automation tooling beyond the core API. Missing for 10: general-purpose automation/trigger framework, webhook or event-driven automation support, evidence of AI-agent-configurable workflows beyond AutoFile.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”

   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

   TaxJar—none0/10

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

   ⚑ flag

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

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

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

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

   proof ↗⚑ flag

   TaxJar—none0/10

   No evidence of any natural-language interface, chatbot, or NL command layer; TaxJar exposes only a traditional REST API with SDKs, and probes for llms.txt/OpenAPI discovery artifacts returned 404s. Missing for 10: any NL command support, conversational interface, or agent-friendly API documentation.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “TaxJar uses API keys to allow access to the API.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   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

   TaxJar—none0/10

   No evidence of an interactive API reference with runnable examples; probes for llms.txt and OpenAPI spec both returned 404, and docs only describe static API reference content and client libraries.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”

   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

   TaxJar—none0/10

   Direct probes for llms.txt and common OpenAPI/Swagger spec paths all returned 404, and no documentation references a downloadable machine-readable API spec; only client libraries and reference docs are mentioned.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”

   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

   TaxJar—none0/10

   No evidence pack mentions a sandbox, test mode, or non-production environment for the TaxJar API; only production API usage, keys, and integrations are documented.

   ⚑ flag

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

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

   TaxJar~partialprobed3/10

   TaxJar's API requires an 'x-api-version' header, indicating some form of API versioning exists, but there is no documented deprecation policy, changelog, or sunset timeline evidenced anywhere in the pack. Probes for OpenAPI spec and llms.txt both failed (404), further limiting machine-readable API contract discovery for AI-native tooling. Missing for 10: documented deprecation/sunset policy, changelog of version changes, OpenAPI/machine-readable spec, and any evidence of long-term version support commitments.

   • [claimed-docs] “'x-api-version' must be specified in API call request headers.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   proof ↗⚑ flag

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

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

   TaxJar~partialclaimed3/10

   The API docs vaguely mention that you can "upload transactions" via the API, hinting at bulk transaction import, but there is no documented batch/bulk endpoint, CSV import spec, or rate-limit guidance for large-scale calls. Missing for 10: explicit bulk/batch API endpoint documentation, throughput/rate-limit specs for large batches, and any first-party or independent evidence of successful bulk operations at scale.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”

   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

   TaxJar—none0/10

   TaxJar offers fixed automated behaviors (AutoFile filing, nexus threshold tracking) but there is no evidence of a user-configurable rules/trigger system letting an AI-native user define custom event-based automations; no webhooks, event API, or rule engine documented.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Avalara AvaTax—none0/10

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

   ⚑ flag

   TaxJar—none0/10

   TaxJar's evidence covers API access, AutoFile, nexus tracking, and integrations, but there is no mention of scheduling recurring jobs/workflows or any workflow-automation/cron-like feature for AI-native users. AutoFile is a fixed filing automation, not a user-schedulable job system. missing for 10: any scheduler/cron API, workflow orchestration, or recurring job configuration capability.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”

   proof ↗⚑ flag

Certificate management

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

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

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

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

   proof ↗⚑ flag

   TaxJar—none0/10

   No evidence in the pack describes exemption/resale certificate collection, validation, expiry tracking, or automatic application at calculation time — the pack only covers tax rate/category APIs, AutoFile, nexus tracking, and integrations, none of which address certificate management.

   ⚑ 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 Avalara AvaTax
   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

   TaxJar—none0/10

   No evidence pack item mentions exemption certificates, exemption reasons, or marking customers/transactions exempt via the API — only generic API reference, product_tax_code, and AutoFile filing features are documented. Missing for 10: any mention of exemption_type/exemption_id parameters, exemption certificate storage/reporting, or exemption data flowing into filed returns.

   ⚑ 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 TaxJar
   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

   TaxJar~partialclaimed6/10

   TaxJar's AutoFile is explicitly documented to handle state tax returns and remittances with deadlines guaranteed, backed by a vendor guarantee (taxjar-docs-6), directly matching the core of the story. However, evidence doesn't clarify guarantee scope/terms (e.g., what penalties are covered, caps, exclusions), doesn't confirm coverage in every registered jurisdiction (state-only per wording), and there's no independent/hands-on corroboration of the guarantee being honored in practice. Missing for 10: detailed guarantee terms/limits, evidence of local/city jurisdiction filing beyond state level, and independent customer confirmation of guarantee payouts.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”

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

   TaxJar—none0/10

   Evidence confirms AutoFile handles filing/remittance and nexus tracking, but there is no mention of a filing calendar, per-filing status view, remitted-amount reporting, or downloadable confirmations for submitted returns. missing for 10: filing calendar UI, per-filing status tracking, remittance amount reporting, downloadable filing confirmations.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus 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

   TaxJar—none0/10

   TaxJar's evidence pack covers only US sales tax rates, categories, economic nexus tracking, and state tax return AutoFiling — there is no mention of VAT-specific fields, EU/international registration numbers, invoice generation, or locale-specific compliance rules for VAT jurisdictions. The axis is fair for a tax-compliance product, but no evidence shows TaxJar addresses VAT invoicing at all.

   • [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”

   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

   TaxJar—none0/10

   All evidence describes US sales tax nexus tracking, AutoFile for state returns, and US-centric integrations; nothing addresses EU OSS/IOSS, UK VAT, Canada GST/HST, Australia GST, foreign VAT registration thresholds, or international filing support.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”

   proof ↗⚑ flag

Vat validation

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

   weight 2 · round drawn
   Avalara AvaTax—none0/10

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

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

   proof ↗⚑ flag

   TaxJar—none0/10

   TaxJar's evidence is entirely focused on US sales tax (economic nexus, AutoFile state returns, US integrations) with no mention of VAT, EU/UK tax ID validation, official registry checks (e.g., VIES), or reverse charge mechanics for B2B cross-border sales. Nothing in the docs or community evidence addresses global VAT compliance.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”

   proof ↗⚑ flag

Exposure analysis

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

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

   TaxJar—none0/10

   Evidence shows TaxJar can track economic nexus thresholds and upload/import transactions via API, but nothing describes a backdated exposure analysis with estimated liability, penalties, and interest per jurisdiction. Missing for 10: any mention of historical liability calculation, penalty/interest estimation, or jurisdiction-level backdated exposure reporting.

   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”

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

   TaxJar~partialclaimed6/10

   TaxJar's economic nexus dashboard tracks sales/transaction counts against state thresholds and 'pinpoints states where you've met economic nexus thresholds' (taxjar-docs-7, taxjar-docs-8), showing real-time progress like '$90k of $100k' and '125 of 200' transactions. However, evidence does not confirm proactive alerting BEFORE crossing a threshold (vs. after), nor coverage of country-level (international) thresholds as the story specifies. missing for 10: explicit pre-crossing alert/notification mechanism, international/country threshold tracking, independent user confirmation of alert timing.

   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”

   proof ↗⚑ flag

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

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

   TaxJar~partialprobed5/10

   Docs show a real API for tax calculation, categories, and transaction uploads, but no evidence that UI-only features like AutoFile automated filing or the economic nexus threshold dashboard are exposed via API, and probes confirm no public OpenAPI spec or llms.txt exists. missing for 10: API coverage for AutoFile/state filing, API for nexus threshold tracking/dashboard, machine-readable OpenAPI spec for full API discoverability.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   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

   TaxJar—none0/10

   The evidence pack shows only API access for uploading/retrieving transaction and rate data, with no documented bulk data-export feature, open-format full account export, or data-portability tooling; probes for llms.txt and OpenAPI specs both failed (404s). Missing for 10: any documented full-account data export capability, open format (CSV/JSON) bulk export tool, or data portability/account closure export guarantee.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Avalara AvaTax—none0/10

   No evidence in the pack addresses data residency, regional data storage options, or data localization controls for AvaTax; the evidence only covers tax calculation, APIs, SDKs, and MCP tooling. This is a fair axis to ask about a SaaS product handling transaction data, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

   TaxJar—none0/10

   No evidence in the pack mentions data residency, regional data storage options, or any control over where TaxJar stores customer data; all documentation covers API usage, integrations, and tax filing features.

   ⚑ flag

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

   TaxJar—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy/data lifecycle management for TaxJar's API or platform; documentation focuses solely on tax calculation, filing, and integrations.

   ⚑ 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

   TaxJar—none0/10

   The evidence pack shows TaxJar tracks economic nexus thresholds and integrates with Amazon FBA, but there is no documentation describing how marketplace-facilitator-collected transactions are flagged, excluded from remittance, or reported separately for nexus purposes — the exact capability the story asks about is unaddressed.

   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”

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

   TaxJar—none0/10

   Evidence only shows a generic `product_tax_code` parameter for categorizing line items, with no documentation of specific SaaS-taxability rules by state, digital-goods nuances, bundled-offering logic, or any visible research/citations behind determinations.

   • [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”

   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

   TaxJar~partialclaimed6/10

   TaxJar's API supports a `product_tax_code` parameter per line item, which maps catalog items to tax categories (e.g., SaaS, digital goods, services, physical goods) so each is taxed correctly per jurisdiction — this is the core mechanism for the story. However, evidence lacks a published/detailed taxonomy list of category codes, guidance on how many categories exist or how granular they are, and no independent/hands-on confirmation of correct jurisdictional tax application per category. missing for 10: full published category taxonomy/reference list, hands-on validation of correct per-jurisdiction tax outcomes by category, documentation on default categorization behavior when no code is supplied.

   • [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”

   proof ↗⚑ flag

Agent operations

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

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

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

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

   proof ↗⚑ flag

   TaxJar~partialprobed3/10

   TaxJar has a documented REST API with API-key auth (docs-1,2,4) and a nexus-threshold tracking feature (docs-7,8), but evidence shows no API/agent access to registrations or accrued liability, no scoped/limited credentials beyond a flat API key, and no MCP surface — probes for llms.txt and OpenAPI discovery both failed (taxjar-probe-1, taxjar-probe-2). Missing for 10: API endpoints for registrations/accrued liability/filings, scoped/least-privilege credential model, any MCP server or agent-facing surface, independent confirmation of nexus data via API rather than dashboard-only.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “TaxJar uses API keys to allow access to the API.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   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

   TaxJar—none0/10

   No evidence of any AI/chatbot feature answering nexus or invoice-taxation questions with citations; evidence pack only covers API endpoints, AutoFile, nexus threshold tracking dashboards, and integrations. Probe results even show missing llms.txt/openapi discoverability artifacts, and there's no mention of an AI assistant anywhere in docs or community items.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

   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

   TaxJar—none0/10

   The only guarantee-related evidence concerns AutoFile ensuring filing deadlines are met, not calculation accuracy or audit support for erroneous tax calculations. No documentation in the pack describes a calculation-accuracy guarantee, indemnification, or audit-support commitment tied to TaxJar's tax rate/amount outputs.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”

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

   TaxJar~partialprobed5/10

   Docs confirm a REST API with API keys, multi-language clients, and line-item/product_tax_code support for tax calculation, implying real-time rate lookups suitable for checkout integration, but no evidence explicitly addresses rooftop/address-level accuracy claims or documented latency/performance suitable for checkout timing. Missing for 10: explicit documentation of rooftop-level address accuracy vs ZIP approximation, published latency/performance benchmarks, independent/hands-on corroboration of real-time checkout use, and a working OpenAPI spec (probes returned 404s).

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
   • [claimed-docs] “'x-api-version' must be specified in API call request headers.”
   • [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

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

   TaxJar✓fullclaimed7/10

   TaxJar documents pre-built integrations for major commerce/payment platforms (Amazon FBA, BigCommerce, eBay, Magento 2, NetSuite, PayPal, Shopify, Square, Stripe, WooCommerce) plus official API client libraries in seven languages, directly addressing the plug-and-play revenue-stack integration story. Missing for 10: no independent/hands-on verification that these integrations are actively maintained/up-to-date, no evidence of a public integrations marketplace or update changelog, and no OpenAPI spec available (probe returned 404s) to assess developer experience depth.

   • [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”
   • [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”

   proof ↗⚑ flag

Rate maintenance

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

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

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

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

   proof ↗⚑ flag

   TaxJar~partialclaimed4/10

   TaxJar's API model implies rates are served dynamically (docs-1, docs-4 x-api-version header) so calculations don't require client redeploys, and nexus/AutoFile features suggest ongoing compliance handling, but there's no explicit documentation of a rate/rule change log, update cadence, or effective-date notices for jurisdiction changes. Missing for 10: explicit changelog/documentation of when rate/rule updates take effect, confirmation of automatic jurisdiction coverage updates, and independent verification that no client-side action is ever needed.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “'x-api-version' must be specified in API call request headers.”
   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”

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

   TaxJar—none0/10

   Evidence only covers TaxJar's AutoFile service for filing state tax returns and remittances, and nexus threshold tracking — nothing about registering for sales tax permits (state/local registration filing) or per-registration pricing/status tracking. Missing for 10: any mention of permit registration service, registration pricing, or registration status tracking.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”

   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

   TaxJar—none0/10

   Evidence covers nexus tracking, AutoFile remittance, and API/integrations, but nothing addresses voluntary disclosure agreements (VDAs) or back-filing/remediation support for past-due, uncollected jurisdictions. Absence of evidence for this applicable capability means it is not shown to be delivered.

   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”

   proof ↗⚑ flag

Adjustments

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

   weight 2 · round drawn
   Avalara AvaTax—none0/10

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

   ⚑ flag

   TaxJar—none0/10

   No evidence pack item addresses refunds or credit notes, how negative amounts propagate through liability/reporting, or whether they auto-reconcile into the next filing without manual fixes. Evidence only covers general API usage, tax codes, AutoFile filing, and nexus tracking — none of which speaks to refund-specific tax adjustment. missing for 10: any documentation of a refund/credit-note API or workflow, confirmation that negative line items reduce liability correctly, and evidence that refunds are reflected in AutoFile filings without manual journal entries.

   ⚑ flag

Audit trail

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

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

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

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

   proof ↗⚑ flag

   TaxJar—none0/10

   The evidence pack shows TaxJar's API can return rates, categories, and accept product_tax_code parameters, but there is no documentation of a stored, exportable audit record showing the exact rate, rule, address resolution, and category used for each historical transaction's calculation. Nothing addresses retention or export of calculation provenance for audit purposes.

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”

   proof ↗⚑ flag

Channel imports

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

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

   TaxJar✓fullprobed7/10

   TaxJar's API supports uploading transactions and backfilling data programmatically, and its documented integrations list covers major storefronts and processors (Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce), enabling multi-channel data consolidation for filings. This directly supports the developer story of importing transactions from multiple sources into one nexus/filing view. Missing for 10: no independent/hands-on verification of connector sync reliability across all listed platforms, no detail on how conflicting/duplicate transactions from multiple sources are reconciled, and no OpenAPI spec confirming full API backfill capabilities (probe endpoints 404).

   • [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
   • [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”
   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”

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

   TaxJar~partialclaimed3/10

   Evidence shows nexus threshold tracking and AutoFile remittance/filing automation, which implies some jurisdiction-level tax handling, but there is no documentation of a liability report showing collected-vs-owed by jurisdiction, no mention of filing-ready detail views, and no export formats designed for accountants or GL consumption. missing for 10: collected-vs-owed liability dashboard, jurisdiction-level accrued liability reporting, GL/accountant-ready export formats, evidence of real-time 'at any moment' visibility.

   • [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
   • [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
   • [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”

   proof ↗⚑ flag