Stripe Tax vs Anrok

Agent access

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

   weight 2 · round to Stripe Tax
   Stripe Tax✓fullprobed8/10

   Direct probe evidence confirms an llms.txt file exists at docs.stripe.com/llms.txt (HTTP 200) and per-page markdown docs (e.g. tax.md) are also served, allowing agents to fetch agent-oriented documentation directly. This is Stripe-wide infrastructure that applies to the Tax docs specifically (stripe-tax-docs-2 sourced from tax.md). Missing for 10: no evidence of a dedicated llms-full.txt or Tax-specific agent guide, and no independent/community confirmation of agents successfully using this in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/tax.md # Stripe Tax Automate sales tax, VAT, and GST compliance on all your transactions…”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”

   proof ↗⚑ flag

   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
   Stripe Tax~partialprobed6/10

   Stripe Tax is fully API-driven (tax calculation, sandbox testing, itemized exports) and Stripe provides a CLI and sandbox environment usable in CI/automation pipelines, supporting headless operation. However, the evidence is generic Stripe platform tooling rather than Stripe Tax-specific CI/automation documentation, and no CI examples, GitHub Actions, or automated testing pipeline integration specific to Tax are shown. missing for 10: Stripe Tax-specific CI/CD pipeline examples, automated testing workflows referencing Tax API, evidence of headless batch/report automation beyond manual sandbox testing.

   • [claimed-docs] “You can use Stripe Tax in a sandbox environment to preview automatic tax calculation behavior for different tax settings.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”

   proof ↗⚑ flag

   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 Stripe Tax
   Stripe Tax~partialprobed6/10

   Stripe (the platform Stripe Tax belongs to) documents an official MCP server at docs.stripe.com/mcp, evidencing agent connectivity, but the evidence pack has no Stripe Tax-specific MCP tooling details, hands-on agent usage, or independent corroboration of MCP functioning with Stripe Tax specifically. Missing for 10: Stripe Tax-specific MCP tool documentation, independent/hands-on validation of the MCP server working with tax operations, details on scope/coverage of tax-related MCP tools.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   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 to Stripe Tax
   Stripe Tax✓fullprobed7/10

   Stripe (the parent platform) documents an official CLI at docs.stripe.com/stripe-cli, which covers Stripe Tax API usage as part of the broader Stripe API surface. Missing for 10: no Stripe Tax-specific CLI commands or documentation, and no independent/community corroboration of CLI usage specifically for tax workflows.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   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
   Stripe Tax✓fullprobed8/10

   Stripe Tax is fully API-driven, with documented parameters (shipping_cost, IP geolocation, ship-from address), a sandbox/testing environment, and taxability_reason fields returned via API responses, plus a standalone Tax API doc. Community evidence confirms real-world programmatic integration (VAT/tax rate automation) though with operational gotchas unrelated to API documentation quality. Missing for 10: a discoverable OpenAPI spec (probe returned 404s) and independent hands-on confirmation of API robustness beyond docs.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “To calculate tax on shipping costs, use the `shipping_cost` parameter”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [claimed-docs] “You can use Stripe Tax in a sandbox environment to preview automatic tax calculation behavior for different tax settings.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/tax.md # Stripe Tax Automate sales tax, VAT, and GST compliance on all your transactions…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   No evidence of Stripe Tax (or Stripe's platform) offering scoped/least-privilege API credential issuance for agents; the pack discusses general API access (restricted keys) nowhere, only tax calculation features, CLI, and MCP server pointers. Missing for 10: any mention of restricted/scoped API keys, OAuth scopes, or agent-specific credential controls.

   ⚑ flag

   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 Stripe Tax
   Stripe Tax~partialprobed5/10

   Evidence shows Stripe's docs reference official npm packages/SDKs for integration (stripe-tax-probe-1) and Stripe Tax is built on the standard Stripe API with docs pages (stripe-tax-docs-1..14), implying SDK-based access, but the pack contains no explicit list of official language SDKs, code samples in multiple languages, or SDK-specific documentation for Tax endpoints. missing for 10: explicit official SDK list/pages for Stripe Tax, multi-language code samples, versioning/release notes for SDKs.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “To calculate tax on shipping costs, use the `shipping_cost` parameter”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   The evidence pack contains extensive Stripe Tax documentation on tax calculation, registration, filing, and reporting, but no mention of webhooks, event subscriptions, or any event-driven integration mechanism. Without evidence of webhook support for Stripe Tax events, this applicable axis cannot be credited.

   ⚑ flag

   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
   Stripe Tax—none0/10

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

   ⚑ flag

   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
   Stripe Tax~partialprobed3/10

   Stripe Tax's core value is automatic tax calculation on every transaction (docs-2, comm-1) and automated US filing via TaxJar integration (docs-10, comm-5), which are background automations that run without manual intervention. However there is no evidence of an AI-native workflow where a user configures agentic automations (e.g., via the general Stripe MCP server or CLI) specifically for tax tasks running autonomously. Missing for 10: explicit AI-agent-configurable automation/trigger setup for tax workflows, evidence of the MCP/CLI being used to orchestrate autonomous background tax processes, and independent confirmation that these automations run without ongoing manual oversight (comm-4 notes filing still requires manual paperwork/payment).

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”
   • [community] “This looks great. Implementing Avalara for tax calculation was a large pain across multiple dimensions. Stripe Tax integrates with TaxJar fo…”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

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

   ⚑ flag

   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 drawn
   Stripe Tax~partialprobed5/10

   Stripe (the platform) documents an official MCP server and CLI (stripe-tax-probe-4, stripe-tax-probe-5) plus an llms.txt for docs discovery, which are the building blocks for AI-agent/natural-language operation, but none of the evidence shows these specifically exposing Stripe Tax's calculation/filing/registration workflows via natural-language commands. Missing for 10: tax-specific MCP tool examples, natural-language usage documentation for Tax operations, and independent confirmation of AI-agent control over tax settings.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   The evidence pack includes Stripe Tax conceptual docs, an MCP server, and a CLI, but nothing describes an interactive API reference with runnable/try-it code examples; the openapi probe even returned 404s for all candidate spec locations, suggesting no discoverable machine-readable API spec for this evidence pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   The evidence pack includes an explicit probe for OpenAPI/Swagger spec files at all common locations, all returning 404, and no other citation points to a downloadable machine-readable API spec for Stripe Tax; only human-readable docs and an MCP/CLI mention exist.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   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 Stripe Tax
   Stripe Tax✓fullprobed8/10

   Docs explicitly confirm a sandbox environment can be used to preview automatic tax calculation for different tax settings without touching production, and Stripe's broader test-mode/sandbox architecture is documented via CLI/API tooling. Missing for 10: independent hands-on confirmation of sandbox parity with production data isolation, and no explicit mention of test API keys/test clocks specific to Tax.

   • [claimed-docs] “You can use Stripe Tax in a sandbox environment to preview automatic tax calculation behavior for different tax settings.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   No evidence in the pack discusses API versioning strategy or a documented deprecation policy for Stripe Tax's API; docs cover tax calculation features, CLI/MCP tooling, and community pricing/reliability complaints, none of which address versioning or deprecation commitments.

   ⚑ flag

   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
   Stripe Tax—none0/10

   Stripe Tax docs describe per-transaction tax calculation (including multi-line-item support via shipping_cost) and itemized exports/reports, but there is no evidence of a batch/bulk API endpoint or workflow that lets an AI-native user submit or calculate tax across many separate transactions/items in a single bulk operation. missing for 10: bulk/batch tax-calculation API, documented batch endpoints, evidence of processing many orders in one automated call.

   • [claimed-docs] “To calculate tax on shipping costs, use the `shipping_cost` parameter”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”

   proof ↗⚑ flag

   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

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
   Stripe Tax—none0/10

   No evidence in the pack describes collection, validation, storage, expiry tracking, or automatic application of exemption/resale certificates; the closest related item is VAT number validation (VIES), which is a different mechanism and explicitly noted as one-time only with no re-validation. This is a plausible axis for a tax compliance product, but nothing here shows Stripe Tax supports it end to end.

   • [community] “Note this big gotcha: Stripe's VIES validation only takes place once and there is no way to retrigger it. For compliance purposes you have t…”

   proof ↗⚑ flag

   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 to Anrok
   Stripe Tax—none0/10

   The evidence pack shows Stripe Tax can return a taxability_reason for a calculated tax result and supports itemized reporting, but nowhere does it document an API mechanism to mark a customer or transaction as tax-exempt with a specified exemption reason, nor any linkage of that reason through to the filed return. Missing for 10: exemption-marking API/parameter, exemption certificate storage, and evidence the exemption reason propagates into reports and filed returns.

   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”

   proof ↗⚑ flag

   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
   Stripe Tax!disputedcontradicted2/10

   Stripe Tax only offers automated filing via a TaxJar integration for US sales tax (stripe-tax-docs-10), not for 'every registered jurisdiction,' and there is no evidence of any penalty guarantee for late filing. Community evidence directly contradicts the 'automatic filing/remittance' claim: users report 'you still have to do everything yourself - filing the papers and wiring money' and recommend using a Merchant of Record instead specifically to avoid doing filing/remittance manually. missing for 10: global (non-US) automated filing coverage, any late-filing penalty guarantee, evidence that remittance itself is automated rather than manual.

   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [community] “This looks great. Implementing Avalara for tax calculation was a large pain across multiple dimensions. Stripe Tax integrates with TaxJar fo…”
   • [community] “Notes on Remitting Stripe Tax to the UK and EU: Unless you're doing something like 1mil ARR it's not worth the hassle, just use a Merchant o…”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   Evidence shows Stripe Tax offers filing automation via TaxJar integration (stripe-tax-docs-10) and itemized tax exports (stripe-tax-docs-11), but there is no mention of a filing calendar, per-filing status tracker, remitted-amount summaries, or downloadable filing confirmations. A community report even states that despite Stripe's tooling users 'still have to do everything yourself - filing the papers and wiring money' (stripe-tax-comm-4), reinforcing the absence of a consolidated filing dashboard. Missing for 10: filing calendar view, per-filing status indicators, remitted amount tracking, downloadable confirmation documents.

   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”

   proof ↗⚑ flag

   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 to Anrok
   Stripe Tax!disputedcontradicted5/10

   Stripe Tax calculates VAT/GST by locale, computes rates based on customer/business location, integrates with Invoicing/Checkout, and supports registration number handling and tax-code based rules (stripe-tax-docs-2,4,5,8,12,14), with a positive first-party account of it automating VAT rate/number syncing (stripe-tax-comm-1). However, concrete community evidence contradicts full 'compliant everywhere' delivery: VIES VAT-number validation only fires once with no re-trigger, requiring manual quarterly re-checks for compliance (stripe-tax-comm-2), a documented incident where Stripe Tax silently stopped billing many customers and left invoices stuck in Draft (stripe-tax-comm-6, acknowledged by a Stripe employee in stripe-tax-comm-7), and reports that international coverage is 'woefully incomplete' (stripe-tax-comm-10). Missing for 10: explicit documentation of which specific VAT fields/registration numbers are auto-populated on the invoice template itself, and independent confirmation that the Draft-invoice/VIES issues have been fully remediated.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Stripe Tax uses the preset product tax code for products that don’t have a PTC set directly.”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”
   • [community] “Note this big gotcha: Stripe's VIES validation only takes place once and there is no way to retrigger it. For compliance purposes you have t…”
   • [community] “I built out my Stripe Tax integration, made sure I had all the addresses I needed for my Canadian customers... deployed it... the same day t…”
   • [community] “(I work at Stripe.) This was a painful read. I'm sorry. We could have done a lot better. We're working on remediations now, and we're sendin…”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   proof ↗⚑ flag

   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 to Anrok
   Stripe Tax!disputedcontradicted4/10

   Stripe Tax's docs confirm VAT/GST calculation across EU, UK, Canada, Australia and registration-threshold monitoring (docs-2, docs-7, docs-8, docs-14), but the filing-support integration (TaxJar) is explicitly scoped to 'US sales tax' only (stripe-tax-docs-10), and community evidence directly contradicts broader filing/remittance support — one user notes 'you still have to do everything yourself - filing the papers and wiring money' and another says 'If you're selling internationally it's woefully incomplete, so often not that useful' (stripe-tax-comm-4, stripe-tax-comm-10), with a third suggesting a Merchant of Record instead for EU/UK remittance (stripe-tax-comm-11). missing for 10: automated filing/remittance support for VAT/GST jurisdictions beyond US sales tax, and evidence rebutting the community reports of incomplete international coverage.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”
   • [community] “Notes on Remitting Stripe Tax to the UK and EU: Unless you're doing something like 1mil ARR it's not worth the hassle, just use a Merchant o…”

   proof ↗⚑ flag

   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 to Stripe Tax
   Stripe Tax!disputedcontradicted4/10

   Stripe Tax docs confirm automated VAT/GST calculation based on customer/business location and tax codes, and a community report confirms VAT-number (VIES) validation exists, but that same first-hand account states validation only fires once and is never re-triggered — contradicting a true 'real-time' registry check — and no evidence anywhere documents explicit reverse-charge logic for B2B cross-border sales. Missing for 10: explicit reverse-charge documentation, continuous/real-time VIES re-validation, and independent confirmation of correct B2B cross-border handling beyond the disputed one-time check.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”
   • [community] “Note this big gotcha: Stripe's VIES validation only takes place once and there is no way to retrigger it. For compliance purposes you have t…”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   proof ↗⚑ flag

   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 to Stripe Tax
   Stripe Tax~partialclaimed3/10

   Stripe Tax docs mention identifying where you 'might need to register to collect tax based on past transactions' (nexus monitoring), but there is no evidence of importing historical transactions to produce an estimated liability, penalties, and interest per jurisdiction — the core of this backdated exposure-analysis story. missing for 10: historical transaction import, estimated back-tax liability calculation, penalty/interest estimation per jurisdiction, any hands-on or documented feature matching this workflow.

   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”

   proof ↗⚑ flag

   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
   Stripe Tax~partialclaimed5/10

   Stripe Tax docs mention identifying registration obligations based on past transactions and registering 'as soon as you start processing payments,' which implies some threshold-tracking capability, but there is no evidence of proactive, pre-crossing alerts or real-time dashboards tracking sales/transaction counts against every state and country threshold before they're exceeded. Community evidence focuses on calculation and filing integration, not nexus threshold alerting. Missing for 10: explicit alerting/notification mechanism before threshold crossing, real-time nexus dashboard evidence, and independent confirmation that monitoring is forward-looking rather than retrospective.

   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Calculate and report tax on all payments, even those that you process outside of Stripe.”

   proof ↗⚑ flag

   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
   Stripe Tax~partialprobed6/10

   Docs show deep API coverage for tax calculation (shipping cost, IP geolocation, ship-from address, sandbox testing, itemized reports, taxability_reason) mirroring UI capabilities, and a documented CLI/MCP exist for API-driven workflows. However, registration and filing—explicitly UI-flagged features (docs-7, docs-8, docs-14, docs-10)—appear to rely on Stripe performing them 'on your behalf' or via TaxJar integration rather than exposing full programmatic control, and no evidence confirms these can be fully driven via API alone. missing for 10: explicit API endpoints/parity for tax registration and filing workflows, independent confirmation of full UI-API parity.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “To calculate tax on shipping costs, use the `shipping_cost` parameter”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [claimed-docs] “You can use Stripe Tax in a sandbox environment to preview automatic tax calculation behavior for different tax settings.”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   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 to Stripe Tax
   Stripe Tax~partialclaimed3/10

   Stripe Tax offers itemized exports with line-item tax breakdowns per transaction, which is a data-export capability, but there is no evidence of a comprehensive 'export all data' feature, explicit open-format guarantees (e.g., CSV/JSON specification), or support for fully leaving the platform with your data. missing for 10: full data export scope beyond tax reports, explicit open-format documentation, independent confirmation of unrestricted data portability.

   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”

   proof ↗⚑ flag

   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

Marketplace rules

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

   weight 2 · round drawn
   Stripe Tax—none0/10

   No evidence in the pack addresses marketplace-facilitator tax collection (Amazon, app stores) or how Stripe Tax tracks facilitator-collected transactions for nexus/reporting purposes without double-remitting. All docs and community items focus on Stripe Tax's own calculation/filing for payments processed through Stripe, not on handling third-party facilitator-collected sales.

   ⚑ flag

   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 to Anrok
   Stripe Tax!disputedcontradicted4/10

   Stripe Tax docs show product tax codes (PTC) driving taxability determinations and a `taxability_reason` field exposing the rationale for a given tax result (docs-12, docs-13), which partially supports the 'visible research' ask, but there's no documentation specifically addressing state-by-state SaaS taxability nuances or bundled-offering treatment. Community evidence directly contradicts the completeness claim — practitioners call it 'vastly outgunned by its competitors' and 'woefully incomplete' for international/complex sales (comm-9, comm-10), undercutting confidence it reliably nails the hard cases. Missing for 10: documented state-specific SaaS/digital-goods taxability guidance, bundled-offering tax logic, and independent verification that edge-case determinations are correct.

   • [claimed-docs] “Stripe Tax uses the preset product tax code for products that don’t have a PTC set directly.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [community] “Humorously enough we needed a sales tax solution, and Stripe Tax is vastly outgunned by its competitors, possibly leading to the layoffs in …”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   proof ↗⚑ flag

   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 drawn
   Stripe Tax~partialcommunity6/10

   Stripe Tax documents product tax codes (PTCs) that determine tax rates based on product type (SaaS, digital goods, services, physical goods) and lets Stripe apply a preset PTC when none is set on a specific item, which is exactly the catalog-mapping mechanism the story asks for. However, community feedback specifically flags coverage gaps when selling internationally ('woefully incomplete' for international jurisdictions), and there's no independent verification that every category/jurisdiction combination is accurately handled. Missing for 10: independent/hands-on confirmation of correct taxability across all four category types and all jurisdictions, and clearer documentation addressing the international completeness gap raised by users.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “Stripe Tax uses the preset product tax code for products that don’t have a PTC set directly.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   proof ↗⚑ flag

   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 drawn
   Stripe Tax~partialprobed4/10

   Stripe Tax exposes API access to registrations, calculations, filings, and reports (docs-7,8,10,11,14), and Stripe has a documented MCP server (stripe-tax-probe-4), but there's no evidence the MCP surface exposes tax-specific read/act capabilities (nexus status, accrued liability, upcoming filings) or scoped credentials for an agent to autonomously act on tax posture. missing for 10: MCP server tool list showing tax-specific endpoints (nexus/liability/filings), scoped-credential/permission model for agentic access, and any hands-on/community confirmation of agent-driven tax actions via API or MCP.

   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   Evidence shows Stripe Tax provides rule-based calculation, reporting, and a taxability_reason field for API results, but there is no evidence of a conversational AI/chatbot answering ad-hoc questions like 'is this taxable in this state' with citations. This is a rules/API engine, not an AI-agent Q&A interface. Missing for 10: any AI chat/assistant interface, natural-language Q&A capability, citation-backed reasoning beyond a single API field.

   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   No evidence pack item mentions an accuracy guarantee, indemnification, or audit support commitment from Stripe if a tax calculation is wrong; documentation covers calculation mechanics, filing, and reporting only, and community threads discuss billing bugs and pricing complaints rather than any guarantee/warranty language. missing for 10: any documented accuracy guarantee, liability/indemnification clause, or audit-defense commitment.

   • [claimed-docs] “Calculate and report tax on all payments, even those that you process outside of Stripe.”
   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [community] “I built out my Stripe Tax integration, made sure I had all the addresses I needed for my Canadian customers... deployed it... the same day t…”
   • [community] “(I work at Stripe.) This was a painful read. I'm sorry. We could have done a lot better. We're working on remediations now, and we're sendin…”

   proof ↗⚑ flag

   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 Anrok
   Stripe Tax~partialcommunity6/10

   Stripe Tax docs confirm real-time API tax calculation based on full customer address, business location, product type, and even IP-based geolocation before an address is captured, which is well beyond ZIP-code-level approximation and is used inside checkout/payment flows (stripe-tax-docs-2, stripe-tax-docs-4, stripe-tax-docs-5, stripe-tax-comm-1). However, there's no explicit documentation of latency/performance guarantees for checkout-speed use, no explicit 'rooftop-accuracy' claim, and community feedback flags that international coverage is 'woefully incomplete' compared to competitors like Avalara (stripe-tax-comm-9, stripe-tax-comm-10), tempering confidence in universal address-level precision. Missing for 10: explicit rooftop/address-level accuracy documentation, published latency/performance benchmarks for checkout integration, and independent verification of accuracy claims across all jurisdictions.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”
   • [community] “Humorously enough we needed a sales tax solution, and Stripe Tax is vastly outgunned by its competitors, possibly leading to the layoffs in …”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   proof ↗⚑ flag

   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 drawn
   Stripe Tax~partialcommunity5/10

   Stripe Tax is deeply integrated with Stripe's own revenue products (Billing, Invoicing, Checkout, Payment Links) and offers a standalone Tax API that can calculate tax even on payments processed outside Stripe, plus a maintained TaxJar integration for automated US filing. However, there is no evidence of maintained, pre-built connectors to third-party billing systems, payment processors, or commerce platforms (e.g., Shopify, WooCommerce, other PSPs) — using it outside Stripe's own ecosystem still requires developers to build the API plumbing themselves, and community feedback notes it is 'woefully incomplete' for international sellers and inferior to dedicated tax platforms like Avalara that have broader integration ecosystems. missing for 10: documented third-party commerce/payment-processor integrations beyond Stripe's own products and TaxJar, independent confirmation these integrations are actively maintained and cover non-Stripe stacks.

   • [claimed-docs] “Calculate and report tax on all payments, even those that you process outside of Stripe.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “This looks great. Implementing Avalara for tax calculation was a large pain across multiple dimensions. Stripe Tax integrates with TaxJar fo…”
   • [community] “Humorously enough we needed a sales tax solution, and Stripe Tax is vastly outgunned by its competitors, possibly leading to the layoffs in …”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   proof ↗⚑ flag

   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 Stripe Tax
   Stripe Tax~partialcommunity7/10

   Docs and community evidence confirm Stripe Tax automatically calculates rates across jurisdictions worldwide based on location/product type without manual rate syncing, and a merchant explicitly notes it eliminated their need to manually sync VAT rates. However, the pack has no evidence of a changelog or documentation specifying exactly when rate/rule changes take effect, and no explicit statement guaranteeing zero-redeploy behavior beyond the general 'automatic' framing. Missing for 10: a public changelog/versioning of rate updates, explicit no-redeploy guarantee, and independent verification that rule updates propagate without any integration changes.

   • [claimed-docs] “Calculate sales tax, VAT, and GST for transactions worldwide, determining tax rates based on product type, customer location, and business l…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”
   • [community] “Especially as a EU business owner, I previously had to sync every VAT tax rate possible... Stripe tax does all of that automatically, based …”

   proof ↗⚑ flag

   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
   Stripe Tax!disputedcontradicted4/10

   Stripe docs claim Stripe can 'register on your behalf' for tax permits and that Stripe Tax 'integrates with TaxJar to automate filing for US sales tax,' but a hands-on community account explicitly contradicts the filing automation, stating 'you still have to do everything yourself - filing the papers and wiring money' after using Stripe's tax tools. No evidence anywhere shows per-registration pricing transparency or a status-tracking UI for registrations. missing for 10: documented per-registration pricing, in-product registration status tracker, evidence that state/local filings (beyond TaxJar's limited US sales tax scope) are actually filed by Stripe rather than the merchant.

   • [claimed-docs] “Register to collect tax as soon as you start processing payments.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [community] “This looks great. Implementing Avalara for tax calculation was a large pain across multiple dimensions. Stripe Tax integrates with TaxJar fo…”

   proof ↗⚑ flag

   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 to Stripe Tax
   Stripe Tax!disputedcontradicted4/10

   Stripe Tax docs claim to help identify where past transactions create registration exposure and can register on your behalf, but there's no evidence of voluntary disclosure agreement (VDA) support or back-filing assistance for cleaning up historical non-compliance. A community account (comm-4) directly contradicts any remediation narrative, stating that even with Stripe's new tools 'you still have to do everything yourself - filing the papers and wiring money,' undercutting the impression of an end-to-end remediation path. Missing for 10: explicit VDA/back-filing support, evidence of handling historical liability cleanup, and confirmation that registration assistance extends beyond forward-looking compliance.

   • [claimed-docs] “Identify where you might need to register to collect tax based on past transactions.”
   • [claimed-docs] “You can also use Stripe to register on your behalf.”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”

   proof ↗⚑ flag

   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
   Stripe Tax—none0/10

   The evidence pack covers tax calculation, registration, filing integration with TaxJar, and reporting exports, but nothing specifically addresses how refunds or credit notes adjust tax liability/reporting/filing, nor confirms negative amounts flow through without manual journal fixes. This is a reasonable axis for a tax product to be judged on, but no supporting evidence is present.

   ⚑ flag

   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 drawn
   Stripe Tax~partialclaimed6/10

   Docs show itemized exports with line-item tax breakdown, a taxability_reason field explaining the calculation logic, product tax codes, and address-resolution methods (IP geolocation, ship-from address), which together support reconstructing rate, category, and address logic per transaction. However there's no explicit documentation of data retention duration/policy, no audit-specific report bundling all these fields together, and no independent confirmation that exports satisfy audit requirements. Missing for 10: explicit retention/export lifecycle policy, a unified audit trail report combining rate+rules+address+category, and independent/hands-on verification of audit usability.

   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “The API returns the reason for a tax result in the taxability_reason field.”
   • [claimed-docs] “Stripe Tax uses the preset product tax code for products that don’t have a PTC set directly.”
   • [claimed-docs] “If you provide your customer’s IP address, we geolocate it and use that location as your customer’s location. Use this to show your customer…”
   • [claimed-docs] “If your business ships goods from locations other than your head office, you can provide a ship-from address to calculate tax based on the a…”

   proof ↗⚑ flag

   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
   Stripe Tax~partialprobed4/10

   Stripe Tax docs claim it can 'calculate and report tax on all payments, even those you process outside of Stripe,' suggesting some cross-channel coverage, but there is no evidence of concrete connector integrations with other processors/storefronts or of an API-based historical backfill mechanism for importing past transactions from other channels. Missing for 10: documented connectors/integrations for third-party processors or storefronts, API endpoints for bulk/backfill import of historical transactions, and independent confirmation these actually cover 'whole business' filings.

   • [claimed-docs] “Calculate and report tax on all payments, even those that you process outside of Stripe.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/tax.md # Stripe Tax Automate sales tax, VAT, and GST compliance on all your transactions…”

   proof ↗⚑ flag

   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 drawn
   Stripe Tax~partialcommunity5/10

   Stripe Tax provides itemized tax reports/exports and TaxJar-based US filing assistance, giving some filing-ready detail, but there is no documented dashboard showing accrued liability by jurisdiction (collected vs. owed) or GL-mapped exports for accountants, and community reports note filing/remittance still requires manual work and international coverage gaps. missing for 10: explicit collected-vs-owed liability view, GL/accounting-system export format, evidence of jurisdiction-level real-time liability tracking.

   • [claimed-docs] “Itemized exports contain a detailed view of the line item level tax breakdown for every transaction.”
   • [claimed-docs] “Stripe Tax integrates with TaxJar to automate filing for US sales tax, helping you file on time and avoid errors that can occur with manual …”
   • [community] “So. After 10 years in business and THOUSANDS of customer requests... Stripe has introduced... a calculator. And you still have to do everyth…”
   • [community] “Possibly only a small fraction use Stripe Tax to automatically calculate it. If you're selling internationally it's woefully incomplete, so …”

   proof ↗⚑ flag

   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