Avalara AvaTax vs Anrok

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

   Anrok—none0/10

   A direct probe for llms.txt returned 404, and no agent-oriented docs endpoint was found; OpenAPI probes also failed. No evidence supports pointing an agent at machine-readable docs.

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

   proof ↗⚑ flag

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

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

   Anrok✓fullprobed7/10

   Anrok is explicitly headless/API-first ('Run tax through Anrok's APIs, or hand it to your agents') with a full REST API covering customers, transactions, certificates, filings, and tax calculation that can be scripted for automation/CI pipelines. Missing for 10: explicit CI/CD pipeline examples, official SDKs/CLI tooling, and a working machine-readable openapi.json/llms.txt (probes show 404s) that would make automated integration turnkey.

   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”
   • [claimed-docs] “Retrieves a customer by its ID.”
   • [claimed-docs] “Lists the customers on your seller account, in ascending customer ID order.”
   • [claimed-docs] “this endpoint also saves the transaction in Anrok and associates it with the appropriate tax return”
   • [claimed-docs] “Certificates can be uploaded to Anrok via the Anrok UI as well as via the API.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://apidocs.anrok.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”

   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

   Anrok—none0/10

   Anrok exposes a REST API and mentions 'hand it to your agents' but there is no evidence of an official MCP server for connecting AI agents; llms.txt and openapi probes both 404.

   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”
   • [probe] “PROBE llms.txt: HTTP 404 at https://apidocs.anrok.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”

   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

   Anrok—none0/10

   Anrok offers an API and headless tax product, but no evidence of an official CLI tool; probes for llms.txt and openapi endpoints both returned 404s, and no docs mention a CLI.

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

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

   Anrok✓fullprobed8/10

   Anrok exposes a well-documented public API covering customers, certificates, tax calculation, transactions, filings, and product mappings, with a dedicated tutorials/integration overview and OpenAPI spec referenced, plus explicit messaging that agents can be handed the API ("Run tax through Anrok's APIs, or hand it to your agents"). Missing for 10: independent third-party corroboration of API usage and confirmation of a discoverable machine-readable spec (probe found openapi.json/llms.txt 404s despite an openapi.yaml reference).

   • [claimed-docs] “Retrieves a customer by its ID.”
   • [claimed-docs] “Lists the customers on your seller account, in ascending customer ID order.”
   • [claimed-docs] “This tax amount can be estimated using Anrok's createEphemeral endpoint and should be refreshed any time the customer changes something”
   • [claimed-docs] “this endpoint also saves the transaction in Anrok and associates it with the appropriate tax return”
   • [claimed-docs] “Anrok responds with the list of customer tax IDs to collect... Anrok provides a list of valid tax IDs for each applicable jurisdiction.”
   • [claimed-docs] “The Anrok Address Resolution endpoint resolves a customer address to its normalized form, suitable for sales tax calculations, as well as ta…”
   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”
   • [claimed-docs] “you can use this API endpoint to create many-to-1 mappings to associate various products in your billing system with equivalent products tha…”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”

   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

   Anrok—none0/10

   No evidence of API key scoping, permission levels, or credential issuance mechanisms for agents; docs describe tax API endpoints but nothing about least-privilege or scoped credential issuance.

   ⚑ 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

   Anrok—none0/10

   Evidence shows Anrok has a REST API with OpenAPI schema references, but there is no mention of official client SDKs (e.g., Python, Node, Java libraries) for developers to build against; probes even show openapi.json/llms.txt discovery paths returning 404, suggesting no packaged SDK or machine-readable spec artifact is publicly distributed. missing for 10: named official SDK packages, language-specific client libraries, SDK installation/quickstart docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://apidocs.anrok.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”
   • [claimed-docs] “Certificates can be uploaded to Anrok via the Anrok UI as well as via the API.”

   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

   Anrok—none0/10

   No evidence of any webhook subscription mechanism; all documented capabilities are REST endpoints for customers, transactions, filings, and certificates, with no mention of webhooks or event subscriptions.

   ⚑ flag

Agentic features

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

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

   Anrok✓fullclaimed7/10

   Anrok's AI Atlas feature explicitly lets users ask natural-language questions about their sales tax and receive AI-generated answers with reasoning, grounded in their own transactions, registrations, filings, and certificates. This directly matches the story of getting AI-generated insights from within the product's own data. Missing for 10: independent/hands-on corroboration of AI Atlas quality, and more detail on the range/depth of insights or suggestions beyond Q&A.

   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”

   proof ↗⚑ flag

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

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

   Anrok~partialclaimed4/10

   Anrok's marketing mentions background automations like automatic jurisdiction registration completion, early tax-obligation alerts, and a headless API that can be 'handed to your agents,' implying some autonomous background processing (tax calc, filings, registrations). However there's no evidence of a user-configurable automation builder or explicit agentic scheduling system that an AI-native user could set up themselves. Missing for 10: documentation of a user-facing automation/workflow builder, evidence of agent-triggered autonomous tasks beyond marketing claims, and independent confirmation these run without manual oversight.

   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”
   • [claimed-docs] “Two dashboard screens showing tax obligations in 13 countries and automatic registration completion in 13 jurisdictions.”
   • [claimed-docs] “Early alerts before you owe anywhere”
   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

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

   Anrok~partialclaimed5/10

   Anrok's 'Atlas' feature is described as a built-in AI assistant that lets users 'ask it anything about your sales tax' with reasoning grounded in the customer's own transactions, registrations, filings, and certificates, and the 'headless-tax' page mentions handing tax work 'to your agents.' However, evidence is limited to marketing copy about answering questions and general agent-friendliness, without documentation of the assistant executing multi-step tasks (e.g., filing, remediation) autonomously. Missing for 10: concrete examples of the assistant taking action (not just Q&A), technical/architecture docs on the assistant's task-execution scope, and independent/hands-on verification of its capabilities.

   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”

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

   Anrok~partialclaimed5/10

   Anrok's AI Atlas feature lets users 'ask it anything about your sales tax' and get grounded answers, showing a natural-language query interface, and headless-tax mentions handing tax operations to agents. However, evidence only shows NL-based Q&A/insight retrieval, not full operational control (e.g., creating transactions, managing filings) via natural language commands. missing for 10: evidence of NL commands executing actions (not just queries), documentation of command syntax/scope, independent verification of AI Atlas performance.

   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”

   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

   Anrok—none0/10

   The evidence pack shows Anrok's API docs describe endpoints (customers, tax IDs, address resolution, etc.) and reference an openapi.yaml spec, but nothing indicates an interactive reference with runnable/try-it examples; probes even show that common interactive-doc artifacts (openapi.json, swagger.json, llms.txt) return 404. Missing for 10: any mention of a 'try it' console, code sandbox, or runnable request builder in the docs.

   • [claimed-docs] “Retrieves a customer by its ID.”
   • [claimed-docs] “Lists the customers on your seller account, in ascending customer ID order.”
   • [claimed-docs] “Certificates can be uploaded to Anrok via the Anrok UI as well as via the API.”
   • [claimed-docs] “Anrok responds with the list of customer tax IDs to collect... Anrok provides a list of valid tax IDs for each applicable jurisdiction.”
   • [claimed-docs] “The Anrok Address Resolution endpoint resolves a customer address to its normalized form, suitable for sales tax calculations, as well as ta…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://apidocs.anrok.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”

   proof ↗⚑ flag

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

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

   Anrok~partialprobed6/10

   Anrok's docs repeatedly reference a live openapi.yaml file (e.g., anrok-docs-4, anrok-docs-10-13) suggesting a machine-readable OpenAPI spec exists, but probes for common JSON/well-known OpenAPI paths and llms.txt all 404, and no direct confirmation of a downloadable spec file was found. Missing for 10: a verified working download link for openapi.yaml, an llms.txt or AI-friendly spec index, and independent confirmation the spec is complete/machine-consumable.

   • [claimed-docs] “Certificates can be uploaded to Anrok via the Anrok UI as well as via the API.”
   • [claimed-docs] “Anrok responds with the list of customer tax IDs to collect... Anrok provides a list of valid tax IDs for each applicable jurisdiction.”
   • [claimed-docs] “The Anrok Address Resolution endpoint resolves a customer address to its normalized form, suitable for sales tax calculations, as well as ta…”
   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”
   • [claimed-docs] “you can use this API endpoint to create many-to-1 mappings to associate various products in your billing system with equivalent products tha…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://apidocs.anrok.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”

   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

   Anrok—none0/10

   No evidence pack item mentions a sandbox, test mode, or non-production environment for testing API integrations; the createEphemeral endpoint is described as a tax estimation tool, not a sandbox for isolating test data from production. Missing for 10: any mention of sandbox/test environment, test API keys, or documented separation between test and live data.

   ⚑ flag

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

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

   Anrok—none0/10

   No evidence of API versioning scheme or a documented deprecation policy anywhere in the docs pack; probes even show standard OpenAPI/discovery files returning 404. missing for 10: versioning scheme documentation, explicit deprecation policy, changelog or migration guides.

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

   proof ↗⚑ flag

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

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

   Anrok~partialclaimed4/10

   Anrok's API supports listing customers and creating many-to-1 product mappings across a catalog, which implies some bulk-style operations, but there is no explicit documentation of batch create/update/delete endpoints or bulk transaction processing across many items at once. missing for 10: dedicated bulk/batch API endpoints, evidence of bulk certificate or transaction processing, and independent confirmation of scale handling.

   • [claimed-docs] “Lists the customers on your seller account, in ascending customer ID order.”
   • [claimed-docs] “you can use this API endpoint to create many-to-1 mappings to associate various products in your billing system with equivalent products tha…”
   • [claimed-docs] “Anrok sellers only need to create product IDs for each unique tax category, not every single product in the catalog.”

   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

   Anrok—none0/10

   Anrok's evidence covers tax calculation APIs, certificate/registration tracking, and an AI Q&A assistant (AI Atlas), but nothing describes a user-defined rules engine that automatically triggers actions on events (e.g., 'if nexus threshold crossed, auto-register' as a configurable rule). 'Early alerts' and 'automatic registration completion' are pre-built product features, not user-definable trigger/action rules.

   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”
   • [claimed-docs] “Early alerts before you owe anywhere”

   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

   Anrok—none0/10

   Anrok is a tax compliance/API platform; no evidence describes any scheduling of recurring jobs or workflows (cron-like automation, scheduled syncs, recurring filings automation via API). Filings, registrations, and calculations are described as on-demand API calls or automatic processes, not user-schedulable recurring jobs.

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

   Anrok~partialclaimed5/10

   Anrok supports certificate collection and storage via UI/API, and pricing page states certificates are "collected, verified, and stored," with customer search enabling pre-billing certificate upload. However, there is no evidence of expiry tracking or explicit automatic application of certificates at tax-calculation time within the evidence pack. missing for 10: expiry tracking/alerting on certificates, explicit description of certificates being auto-applied during tax calculation, independent verification of the certificate workflow.

   • [claimed-docs] “creating it ahead of time makes the customer searchable by name in Anrok - for example, when uploading a tax exemption certificate before th…”
   • [claimed-docs] “Certificates can be uploaded to Anrok via the Anrok UI as well as via the API.”
   • [claimed-docs] “Certificates collected, verified, and stored”

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

   Anrok~partialclaimed3/10

   Docs confirm certificates (which typically carry exemption reasons) can be uploaded via API alongside the calculation/transaction/return endpoints, implying exemption data could flow into the tax engine, but there is no explicit documentation of an API field to mark a customer/transaction exempt with a reason, nor confirmation that this reason is surfaced in reporting or on the filed return. Missing for 10: explicit API parameter/endpoint for setting exemption status+reason, and evidence that the reason appears in reports and filed returns.

   • [claimed-docs] “Certificates can be uploaded to Anrok via the Anrok UI as well as via the API.”
   • [claimed-docs] “Certificates collected, verified, and stored”
   • [claimed-docs] “this endpoint also saves the transaction in Anrok and associates it with the appropriate tax return”
   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”

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

   Anrok~partialclaimed3/10

   Evidence shows Anrok can fetch filings and supports automatic registration across jurisdictions, implying some filing automation, but there is no mention of remittance, on-time guarantee, or penalty coverage anywhere in the pack. missing for 10: explicit description of end-to-end return preparation/remittance workflow, guarantee language covering late-filing penalties, evidence of on-time filing across all registered jurisdictions.

   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”
   • [claimed-docs] “Two dashboard screens showing tax obligations in 13 countries and automatic registration completion in 13 jurisdictions.”

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

   Anrok~partialclaimed3/10

   Evidence only shows a generic API endpoint to 'fetch filings' from Anrok, implying some filing-tracking capability, but there is no documentation of a calendar of upcoming returns, per-filing status detail, remitted amounts, or downloadable confirmations for submitted returns. Missing for 10: calendar view of upcoming filings, per-filing status detail, remitted amount reporting, downloadable filing confirmations.

   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”

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

   Anrok~partialclaimed5/10

   Anrok computes tax amounts, resolves jurisdictions/addresses, and collects/validates customer tax IDs per jurisdiction (docs-10, docs-11), which supports registration-number and locale-rule inputs into billing systems, but there is no evidence it generates or validates full compliant invoice documents (e.g., specific required VAT invoice fields, reverse-charge notices, locale formatting) itself. missing for 10: evidence of actual invoice-field/template compliance output, confirmation that generated invoices meet locale-specific legal requirements, and any hands-on/independent verification of this.

   • [claimed-docs] “Anrok responds with the list of customer tax IDs to collect... Anrok provides a list of valid tax IDs for each applicable jurisdiction.”
   • [claimed-docs] “The Anrok Address Resolution endpoint resolves a customer address to its normalized form, suitable for sales tax calculations, as well as ta…”
   • [claimed-docs] “Dashboard showing a world exposure map with sales data by jurisdiction and a UK registration threshold tracker.”
   • [claimed-docs] “Two dashboard screens showing tax obligations in 13 countries and automatic registration completion in 13 jurisdictions.”

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

   Anrok~partialclaimed6/10

   Evidence shows global exposure tracking (world exposure map, UK registration threshold tracker, tax obligations tracked across 13 countries, automatic registration in 13 jurisdictions) and filings API support, indicating international VAT/GST coverage beyond US sales tax. However, there's no explicit mention of EU OSS/IOSS schemes, Canada or Australia specifically, or detail on how foreign registration thresholds are tracked/filed beyond the UK example and generic '13 jurisdictions.' Missing for 10: explicit EU OSS/IOSS support, named coverage of Canada/Australia, and detailed foreign filing mechanics beyond dashboard alerts.

   • [claimed-docs] “Dashboard showing a world exposure map with sales data by jurisdiction and a UK registration threshold tracker.”
   • [claimed-docs] “Two dashboard screens showing tax obligations in 13 countries and automatic registration completion in 13 jurisdictions.”
   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”
   • [claimed-docs] “Early alerts before you owe anywhere”

   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

   Anrok—none0/10

   Evidence shows Anrok collects and validates customer tax IDs for applicable jurisdictions (anrok-docs-10) and tracks global VAT obligations (anrok-docs-17, anrok-docs-18), but there is no evidence of real-time validation against official government registries (e.g., VIES) or of reverse-charge mechanics being automatically applied to B2B cross-border transactions.

   • [claimed-docs] “Anrok responds with the list of customer tax IDs to collect... Anrok provides a list of valid tax IDs for each applicable jurisdiction.”
   • [claimed-docs] “Dashboard showing a world exposure map with sales data by jurisdiction and a UK registration threshold tracker.”
   • [claimed-docs] “Two dashboard screens showing tax obligations in 13 countries and automatic registration completion in 13 jurisdictions.”

   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

   Anrok—none0/10

   Evidence shows Anrok tracks nexus/exposure prospectively (world exposure map, registration threshold tracker, early alerts) but nothing describes importing historical transactions to backdate exposure or calculate estimated liability, penalties, and interest per jurisdiction. missing for 10: historical transaction import/backfill feature, backdated exposure calculation, penalty and interest estimation per jurisdiction.

   • [claimed-docs] “Dashboard showing a world exposure map with sales data by jurisdiction and a UK registration threshold tracker.”
   • [claimed-docs] “Early alerts before you owe anywhere”

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

   Anrok~partialclaimed6/10

   Anrok's marketing docs explicitly claim 'Early alerts before you owe anywhere' and show a world exposure map with a UK registration threshold tracker, indicating nexus monitoring across jurisdictions with proactive alerting. However, there is no detailed documentation of how thresholds are tracked per state/country, alert timing/mechanics, or transaction-count-based nexus logic. missing for 10: technical detail on threshold-tracking logic per state/country, transaction-count thresholds (not just revenue), alert delivery mechanics/timing, and independent/hands-on verification that alerts fire before crossing thresholds.

   • [claimed-docs] “Dashboard showing a world exposure map with sales data by jurisdiction and a UK registration threshold tracker.”
   • [claimed-docs] “Early alerts before you owe anywhere”
   • [claimed-docs] “Two dashboard screens showing tax obligations in 13 countries and automatic registration completion in 13 jurisdictions.”

   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

   Anrok~partialprobed6/10

   Anrok's API documentation covers most core operations (customers, certificates, transactions, tax IDs, address resolution, filings, product mappings) and it markets itself as 'headless tax' with 'one engine' powering both UI and API/agent workflows, suggesting strong parity. However, dashboard-style features (world exposure map, registration threshold tracker, AI Atlas natural-language assistant) are only described as UI experiences with no documented API equivalent, and probes show no discoverable OpenAPI spec or llms.txt for full API surface verification. Missing for 10: explicit statement/documentation of full UI-API parity, API access to dashboard/exposure-map and AI Atlas features, and a verifiable machine-readable API spec.

   • [claimed-docs] “Certificates can be uploaded to Anrok via the Anrok UI as well as via the API.”
   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”
   • [claimed-docs] “Dashboard showing a world exposure map with sales data by jurisdiction and a UK registration threshold tracker.”
   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://apidocs.anrok.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”

   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

   Anrok—none0/10

   There is no evidence of a bulk data export feature or open-format data portability (e.g., CSV/JSON export of all transactions, certificates, filings) for users to leave with their data; API endpoints only support fetching individual records via calls, not a full export mechanism, and probes for llms.txt/openapi.json artifacts returned 404s.

   • [probe] “PROBE llms.txt: HTTP 404 at https://apidocs.anrok.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”
   • [claimed-docs] “Retrieves a customer by its ID.”
   • [claimed-docs] “Lists the customers on your seller account, in ascending customer ID order.”

   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

   Anrok—none0/10

   No evidence in the pack addresses data residency, regional storage options, or data location controls for Anrok's platform; all evidence concerns tax calculation, filings, and API endpoints unrelated to data residency.

   ⚑ 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

   Anrok—none0/10

   The evidence pack covers Anrok's tax calculation, filing, and certificate APIs but contains no mention of data retention policies, data deletion controls, or privacy/data lifecycle management features for AI-native users. No documentation addresses how users can control or delete stored data.

   ⚑ flag

Marketplace rules

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

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

   Anrok—none0/10

   No evidence pack items mention marketplace facilitator transactions, facilitator-collected tax tracking, or logic to avoid double-remittance on marketplace sales — the docs cover general transaction/refund/certificate APIs but nothing specific to marketplace facilitator nexus handling.

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

   Anrok~partialclaimed5/10

   Anrok's product-category mapping (docs-13, docs-14) shows it classifies products into tax categories, and AI Atlas (docs-15) lets users 'ask anything about sales tax' with reasoning shown, grounded in transactions/registrations/filings/certificates — suggesting visible research behind determinations. However, there's no direct evidence addressing the specific hard cases named (state-by-state SaaS taxability differences, digital-goods nuances, or bundled-offering treatment) or how the reasoning trail covers those scenarios. Missing for 10: explicit documentation of SaaS taxability variance by state, digital-goods rule handling, bundled-offering tax logic, and independent verification that Atlas's 'reasoning shown' actually resolves these edge cases correctly.

   • [claimed-docs] “you can use this API endpoint to create many-to-1 mappings to associate various products in your billing system with equivalent products tha…”
   • [claimed-docs] “Anrok sellers only need to create product IDs for each unique tax category, not every single product in the catalog.”
   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”

   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

   Anrok~partialclaimed6/10

   Anrok's API supports mapping catalog products to tax categories via product IDs and many-to-1 mappings (each unique tax category needs only one product ID), and jurisdiction-aware tax calculation/address resolution is documented. However, there's no explicit documentation showing the specific vendor tax category taxonomy (SaaS, digital goods, services, physical products) or a UI/API walkthrough of assigning each of those category types across jurisdictions. missing for 10: explicit list/definition of tax category taxonomy (SaaS vs digital goods vs services vs physical goods), concrete UI/API example mapping catalog items to these categories, independent corroboration of category-based jurisdictional taxation accuracy.

   • [claimed-docs] “you can use this API endpoint to create many-to-1 mappings to associate various products in your billing system with equivalent products tha…”
   • [claimed-docs] “Anrok sellers only need to create product IDs for each unique tax category, not every single product in the catalog.”
   • [claimed-docs] “The Anrok Address Resolution endpoint resolves a customer address to its normalized form, suitable for sales tax calculations, as well as ta…”
   • [claimed-docs] “Anrok responds with the list of customer tax IDs to collect... Anrok provides a list of valid tax IDs for each applicable jurisdiction.”

   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

   Anrok~partialprobed4/10

   Anrok's API exposes some relevant read/act endpoints (filings, tax-ID/registration lists, address resolution, transaction create/void/refund) and marketing for 'headless-tax' explicitly says you can 'hand it to your agents', plus AI Atlas offers grounded Q&A over transactions/registrations/filings/certificates. However there is no evidence of an MCP surface, no mention of scoped/limited API credentials, no explicit nexus-status or accrued-liability endpoint, and probes show llms.txt and openapi discovery endpoints 404ing, undercutting easy machine/agent onboarding. Missing for 10: MCP server or endpoint, scoped-credential/OAuth support, explicit nexus-status and accrued-liability read endpoints, working machine-readable API discovery (llms.txt/openapi).

   • [claimed-docs] “Anrok responds with the list of customer tax IDs to collect... Anrok provides a list of valid tax IDs for each applicable jurisdiction.”
   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”
   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”
   • [probe] “PROBE llms.txt: HTTP 404 at https://apidocs.anrok.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://apidocs.anrok.com/openapi.json, https://apidocs.anrok.com/swagger.json, https://apidocs.anro…”

   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 to Anrok
   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

   Anrok✓fullclaimed7/10

   Anrok's 'AI Atlas' is explicitly described as answering sales-tax questions 'with the reasoning shown, grounded in your own transactions, registrations, filings, and certificates' — a purpose-built tax AI over its own rule/data base rather than a generic chatbot. Missing for 10: independent/hands-on validation of answer accuracy, detail on invoice-level 'why did this tax this way' explanations, and citation format specifics.

   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”

   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

   Anrok—none0/10

   No evidence pack item mentions an accuracy guarantee, indemnification, warranty, or audit-defense/support commitment tied to Anrok's tax calculations; all citations cover API mechanics, product features, and dashboards. Absence of any documented guarantee for this applicable finance/tax axis yields 'none'.

   ⚑ 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

   Anrok~partialclaimed7/10

   Anrok's API docs describe a createEphemeral endpoint for real-time tax estimation during checkout and a dedicated Address Resolution endpoint that normalizes a customer address to determine taxable jurisdiction(s), supporting rooftop-level (not ZIP-only) accuracy. However, there is no explicit performance/latency benchmark or independent hands-on confirmation that calls are fast enough for checkout-critical paths. Missing for 10: documented latency/SLA numbers for checkout use, independent/third-party verification of real-time performance, and explicit comparison against ZIP-code-level competitors.

   • [claimed-docs] “This tax amount can be estimated using Anrok's createEphemeral endpoint and should be refreshed any time the customer changes something”
   • [claimed-docs] “The Anrok Address Resolution endpoint resolves a customer address to its normalized form, suitable for sales tax calculations, as well as ta…”
   • [claimed-docs] “this endpoint also saves the transaction in Anrok and associates it with the appropriate tax return”

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

   Anrok~partialclaimed5/10

   Anrok documents a Shopify integration (verifying Shopify's own tax calc) and a general API for transactions, customers, and product mappings, but the mapping endpoint (many-to-1 product mapping) and createOrUpdate/negation flows show developers still must build the plumbing to sync billing-system data rather than plugging into a pre-built connector library covering multiple billing/payment/commerce platforms. Missing for 10: a documented catalog of maintained native integrations (e.g., Stripe, Chargebee, Recurly, other commerce platforms) beyond Shopify, and evidence that these connectors sync automatically without developer-built API glue.

   • [claimed-docs] “Tax calculation through Shopify requires Shopify tax. Anrok recalculates and verifies Shopify's calculations to ensure accuracy.”
   • [claimed-docs] “you can use this API endpoint to create many-to-1 mappings to associate various products in your billing system with equivalent products tha…”
   • [claimed-docs] “this endpoint also saves the transaction in Anrok and associates it with the appropriate tax return”
   • [claimed-docs] “Use createOrUpdate endpoint to create a negative transaction representing the refund.”
   • [claimed-docs] “Use createNegation endpoint to negate the original transaction. Use createOrUpdate endpoint to create a new version of the partially refunde…”
   • [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”

   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

   Anrok—none0/10

   The evidence pack covers API endpoints, certificates, filings, and dashboards, but contains no claims about automatic rate/rule updates across jurisdictions, no changelog or effective-date documentation, and no statement that customers never need to redeploy for rate changes. This is a fair and central axis for a tax-calculation vendor, but no supporting evidence exists.

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

   Anrok~partialclaimed4/10

   Anrok's marketing claims 'automatic registration completion in 13 jurisdictions' and an exposure/threshold tracker, suggesting some in-product registration handling, but there is no evidence of per-registration pricing transparency or a dedicated status-tracking workflow for permit filings. missing for 10: per-registration pricing disclosure, explicit status tracking UI/API for registrations, confirmation of full state/local filing scope.

   • [claimed-docs] “Dashboard showing a world exposure map with sales data by jurisdiction and a UK registration threshold tracker.”
   • [claimed-docs] “Two dashboard screens showing tax obligations in 13 countries and automatic registration completion in 13 jurisdictions.”
   • [claimed-docs] “Early alerts before you owe anywhere”

   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

   Anrok—none0/10

   Evidence shows Anrok tracks exposure, thresholds, and sends early alerts before liability accrues, but nothing in the pack mentions voluntary disclosure agreements, back-filing support, or any remediation path for past-due/uncollected tax periods.

   ⚑ 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 to Anrok
   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

   Anrok~partialclaimed6/10

   Anrok's API docs explicitly cover refund/credit-note workflows: createOrUpdate for negative transactions, createNegation for full negation plus a new corrected transaction for partial refunds, and each saved transaction is tied to the appropriate tax return, implying downstream liability and filing effects. However, there's no explicit evidence describing how these adjustments flow through reporting dashboards or that manual journal fixes are entirely eliminated across all reporting/filing steps. Missing for 10: explicit documentation or independent confirmation that negative amounts automatically reconcile in liability reports and filings without any manual reconciliation, and real-world/hands-on validation of this flow.

   • [claimed-docs] “this endpoint also saves the transaction in Anrok and associates it with the appropriate tax return”
   • [claimed-docs] “Use createOrUpdate endpoint to create a negative transaction representing the refund.”
   • [claimed-docs] “Use createNegation endpoint to negate the original transaction. Use createOrUpdate endpoint to create a new version of the partially refunde…”
   • [claimed-docs] “Void can be used in cases where a customer transaction payment was unsuccessful or when the invoice needs to be canceled”

   proof ↗⚑ flag

Audit trail

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

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

   Anrok~partialclaimed6/10

   Anrok's API retains transaction data (createOrUpdate/createNegation saved and tied to filings), address resolution is a distinct queryable endpoint, and product category mapping is stored per tax category; AI Atlas explicitly says answers are grounded in transactions, registrations, filings, and certificates, implying underlying data is retrievable. However, there's no explicit documentation of a per-transaction audit trail showing the exact rate and rule set applied, nor a dedicated export/audit report feature. Missing for 10: explicit rate/rule audit trail per transaction, a documented export function for audit purposes, and independent confirmation of reconstructability beyond docs claims.

   • [claimed-docs] “this endpoint also saves the transaction in Anrok and associates it with the appropriate tax return”
   • [claimed-docs] “The Anrok Address Resolution endpoint resolves a customer address to its normalized form, suitable for sales tax calculations, as well as ta…”
   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”
   • [claimed-docs] “you can use this API endpoint to create many-to-1 mappings to associate various products in your billing system with equivalent products tha…”
   • [claimed-docs] “Anrok sellers only need to create product IDs for each unique tax category, not every single product in the catalog.”
   • [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”

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

   Anrok~partialclaimed6/10

   Anrok's API clearly supports transaction ingestion (createOrUpdate, void, refund/negation endpoints) and product mapping across billing systems (anrok-docs-6,7,8,9,13), and it explicitly recalculates/verifies Shopify tax data (anrok-docs-19), showing at least one storefront connector beyond the core API. However, evidence does not show a broader library of connectors to other processors/storefronts (e.g., Stripe, other marketplaces) or explicit historical-data backfill tooling. missing for 10: documented connectors to multiple processors/storefronts beyond Shopify, explicit bulk/historical backfill API or import tool, independent confirmation of multi-source coverage.

   • [claimed-docs] “this endpoint also saves the transaction in Anrok and associates it with the appropriate tax return”
   • [claimed-docs] “Void can be used in cases where a customer transaction payment was unsuccessful or when the invoice needs to be canceled”
   • [claimed-docs] “Use createOrUpdate endpoint to create a negative transaction representing the refund.”
   • [claimed-docs] “Use createNegation endpoint to negate the original transaction. Use createOrUpdate endpoint to create a new version of the partially refunde…”
   • [claimed-docs] “you can use this API endpoint to create many-to-1 mappings to associate various products in your billing system with equivalent products tha…”
   • [claimed-docs] “Tax calculation through Shopify requires Shopify tax. Anrok recalculates and verifies Shopify's calculations to ensure accuracy.”

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

   Anrok~partialclaimed5/10

   Anrok's docs show jurisdiction-level exposure dashboards and a filings-fetch API, implying some accrued/owed visibility and filing-ready data, but there is no explicit evidence of a collected-vs-owed liability view, GL-formatted exports, or accountant-consumable outputs. missing for 10: explicit collected vs owed liability breakdown, GL/accounting export formats, accountant-facing report examples.

   • [claimed-docs] “This endpoint can be used to fetch filings from Anrok.”
   • [claimed-docs] “Dashboard showing a world exposure map with sales data by jurisdiction and a UK registration threshold tracker.”
   • [claimed-docs] “Two dashboard screens showing tax obligations in 13 countries and automatic registration completion in 13 jurisdictions.”
   • [claimed-docs] “Early alerts before you owe anywhere”

   proof ↗⚑ flag