Anrok vs TaxJar

Agent access

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar✓fullprobed6/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

4. ai-native userUse an official CLI

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar✓fullprobed7/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

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

   TaxJar✓fullprobed7/10

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

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

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Agentic features

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar—none0/10

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

   ⚑ flag

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Api quality

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

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

   TaxJar—none0/10

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

   ⚑ flag

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

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

   TaxJar~partialprobed3/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Certificate management

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

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

   TaxJar—none0/10

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

   ⚑ flag

Exempt customers

1. developerMark a customer or transaction exempt through the API — with the exemption reason carried through calculation, reporting, and the filed return

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

   TaxJar—none0/10

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

   ⚑ flag

Autofile

1. finance leadReturns are prepared, filed, and remitted automatically in every registered jurisdiction — on time, with the vendor's guarantee covering penalties if it files late

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

   TaxJar~partialclaimed6/10

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

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

   proof ↗⚑ flag

Filing visibility

1. ops userSee the whole filing picture — a calendar of upcoming returns, per-filing status, the amounts remitted, and downloadable confirmations for every return submitted

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Invoice compliance

1. ops userInvoices come out compliant where I sell — required VAT fields, registration numbers, and locale rules flow through to my invoicing system or are generated by the product itself

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Vat coverage

1. founder selling internationallyVAT and GST are covered like US sales tax — EU OSS/IOSS, UK, Canada, Australia and beyond, with foreign registration thresholds tracked and filings supported

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Vat validation

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Exposure analysis

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Threshold tracking

1. founderThe product watches my economic nexus exposure — tracking sales and transaction counts against every state and country threshold and alerting me before I cross one, not after

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

   TaxJar~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar~partialprobed5/10

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

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

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

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

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

   TaxJar—none0/10

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

   ⚑ flag

2. ai-native userControl data retention and deletion

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

   TaxJar—none0/10

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

   ⚑ flag

Marketplace rules

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Saas rules

1. founder selling softwareThe product gets the hard cases right — SaaS taxability that differs by state, digital-goods rules, and bundled offerings — with the research behind each determination visible

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Tax codes

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

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

   TaxJar~partialclaimed6/10

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

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

   proof ↗⚑ flag

Agent operations

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

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

   TaxJar~partialprobed3/10

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

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

   proof ↗⚑ flag

Builtin ai

1. founderThe product ships its own AI for tax questions — is this product taxable in this state, why did this invoice tax this way — answering from its rule base with citations, not a generic chatbot

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Accuracy guarantee

1. finance leadThe vendor stands behind its numbers — a documented accuracy guarantee or audit support commitment if a calculation it produced turns out wrong

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Calculation api

1. developerCalculate the right sales tax for a transaction through an API in real time — address-level (rooftop) accuracy, not ZIP-code approximations — fast enough to sit inside checkout

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

   TaxJar~partialprobed5/10

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

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

   proof ↗⚑ flag

Integrations

1. developerThere are maintained integrations for my revenue stack — billing systems, payment processors, and commerce platforms feed transactions in without me building the plumbing

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

   TaxJar✓fullclaimed7/10

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

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

   proof ↗⚑ flag

Rate maintenance

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

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

   TaxJar~partialclaimed4/10

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

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

   proof ↗⚑ flag

Registration filing

1. ops userRegistering for a sales tax permit is handled in-product — the vendor files state and local registrations on my behalf with transparent per-registration pricing and status tracking

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Remediation

1. finance leadPast-due exposure has a remediation path — voluntary disclosure agreements or back-filing support to clean up jurisdictions where I should have been collecting

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Adjustments

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

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

   TaxJar—none0/10

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

   ⚑ flag

Audit trail

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

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

   TaxJar—none0/10

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

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

   proof ↗⚑ flag

Channel imports

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

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

   TaxJar✓fullprobed7/10

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

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

   proof ↗⚑ flag

Liability reports

1. finance leadSee accrued liability by jurisdiction at any moment — collected versus owed, filing-ready detail, and exports my accountant and GL can consume

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

   TaxJar~partialclaimed3/10

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

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

   proof ↗⚑ flag