Anrok vs Numeral
Anrok
Anrok, Inc.
Numeral wins · 15–16 (15 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to NumeralAnroknone0/10A 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.
A live probe confirms llms.txt returns HTTP 200 with a structured doc index at docs.numeral.com/llms.txt, and Numeral also documents agent-oriented resources like Claude skills and an MCP server for AI agents to consult its docs/API. Missing for 10: independent third-party confirmation of an agent successfully using llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
- [claimed-docs] “Claude skills that teach an AI coding agent how to integrate the Numeral tax API correctly.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to AnrokAnrok 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…”
Numeral is fundamentally a REST API (create products, calculations, transactions via POST calls) which is inherently callable headlessly from any automation pipeline including CI, and there's also an MCP server exposing account operations as callable tools. However, there is no explicit documentation of CI integration, headless CLI, or automated testing/deployment workflows. missing for 10: explicit CI/CD examples or guidance, a CLI tool for scripted/headless runs, and confirmation of non-interactive auth flows suitable for automation.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
ai-native userConnect an agent via an official MCP server
weight 3 · round to NumeralAnroknone0/10Anrok 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…”
Numeral documents an official MCP server exposing nexus, filings, registrations, transactions, sales, products, and exemption certificates as tools an AI agent can call directly, with specific tool documentation and example use cases. Missing for 10: independent/hands-on corroboration beyond first-party docs, and details on authentication/rate limits for the MCP endpoint.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [probe] “official MCP server documented at https://docs.numeral.com/mcp/overview”
ai-native userUse an official CLI
weight 2 · round drawnAnroknone0/10Anrok 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.
ai-native userDrive the product through a documented public API
weight 3 · round drawnAnrok 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…”
Numeral publishes a versioned REST API with documented endpoints (products, transactions, calculations, exemption certificates) and a quickstart guide, plus an llms.txt confirming machine-readable API docs are live (HTTP 200). This is a genuine documented public API an AI-native user could drive directly. Missing for 10: a discoverable OpenAPI/Swagger spec (all candidate paths 404), independent third-party corroboration of API usage.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can now pass `customer.ip` instead of (or in addition to) `customer.address`”
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnAnroknone0/10No 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.
Numeralnone0/10No evidence Numeral offers scoped or least-privilege API key/credential issuance for agents; the docs mention a general MCP server exposing the whole account (nexus, filings, transactions, etc.) but nothing about restricting agent permissions or issuing limited-scope tokens. Missing for 10: any mention of API key scopes, role-based permissions, or agent-specific credential issuance.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
ai-native userBuild against official SDKs
weight 2 · round to NumeralAnroknone0/10Evidence 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.”
Numeral offers a documented REST API with detailed object/endpoint docs, an MCP server, and Claude skills for AI agent integration, but there's no evidence of official language-specific SDKs (e.g., Python/JS/Ruby client libraries) — only raw API/docs and an OpenAPI probe that 404s. missing for 10: official multi-language SDK packages, published OpenAPI spec confirming SDK generation, independent developer corroboration of SDK usage.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “Claude skills that teach an AI coding agent how to integrate the Numeral tax API correctly.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnAnroknone0/10No 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.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to AnrokAnrok'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”
Numeral's MCP server exposes nexus, filings, and transaction data as callable tools, enabling an external AI agent to answer questions like 'which states have I triggered nexus in' — a form of AI-derived insight from the data. However, this requires a separate AI agent/client to consume the MCP tools rather than a built-in, native in-product insights/suggestions feature. Missing for 10: evidence of insights or suggestions generated natively within Numeral's own UI/dashboard without requiring an external agent, and any proactive suggestion capability (vs. query-response only).
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to NumeralAnrok'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, …”
Numeral's core product is autonomous background compliance automation (nexus monitoring, filing, remittance, mail handling, certificate tracking) rather than a user-configurable automation builder, and the MCP server lets an AI agent query/act on nexus, filings, and transactions autonomously. However there's no explicit evidence of scheduled/triggered 'set it and forget it' automations that a user configures themselves via the MCP or API (e.g., recurring jobs, webhooks, or event-driven triggers) — missing for 10: documented scheduling/trigger mechanism for autonomous runs, user-configurable automation workflows, and independent confirmation the MCP tools can run unattended in production.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “We scan, read, and respond to all your sales tax mail from state and local governments.”
- [claimed-docs] “Automatically validate each uploaded certificate * Expiration tracking, renewals, and compliance monitoring”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to AnrokAnrok'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”
Numeralnone0/10Numeral exposes an MCP server so external AI agents (e.g., Claude) can query its tax data, and offers Claude skills for coding agents integrating its API — but this is exposing Numeral as a tool for outside agents, not a built-in AI assistant living inside Numeral's own product UI that a user delegates tasks to. No evidence of an in-product chat/assistant experience is provided.
- [claimed-docs] “Claude skills that teach an AI coding agent how to integrate the Numeral tax API correctly.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
ai-native userOperate the product with natural-language commands
weight 2 · round to NumeralAnrok'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”
Numeral ships a documented MCP server exposing nexus, filings, transactions, and exemption certificates as tools an AI agent can call, explicitly enabling natural-language queries like 'which states have I triggered nexus in' — this is the core enabler for NL-driven operation. However, this is agent-mediated (via MCP tool calls) rather than a native NL command interface within Numeral's own product UI, and there's no evidence of a built-in chat/command box or independent hands-on validation of the NL experience. Missing for 10: first-party NL interface within the product itself, broader coverage of all actions via NL, independent corroboration of real-world usage.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [probe] “official MCP server documented at https://docs.numeral.com/mcp/overview”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnAnroknone0/10The 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…”
Numeralnone0/10Docs describe API endpoints and objects (products, transactions, certificates) but there is no evidence of an interactive reference with runnable/try-it examples; the openapi probe found no spec at standard locations, suggesting no Swagger/Postman-style interactive console.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to AnrokAnrok'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…”
Numeralnone0/10Probes explicitly show all common OpenAPI/swagger spec paths return 404, and no evidence pack item links to a downloadable machine-readable spec; only human-readable docs and an llms.txt are found.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnAnroknone0/10No 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.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to NumeralAnroknone0/10No 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.
Numeral's docs show clear API versioning via dated version paths (e.g., v2026-03-01) in multiple endpoints, indicating a versioning scheme, but no evidence describes a documented deprecation policy, sunset timeline, or migration guidance for older versions. Missing for 10: explicit deprecation policy documentation, version sunset/migration guides, changelog of breaking changes.
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can now pass `customer.ip` instead of (or in addition to) `customer.address`”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to AnrokAnrok'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.”
Numeralnone0/10Evidence only shows single-item API operations (create one product, one transaction, one certificate_request) with no documented batch/bulk endpoints for processing many items in one call. Bulk operations across many items is a plausible axis for a tax compliance API but no evidence supports it.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round drawnAnroknone0/10Anrok's evidence covers tax calculation APIs, certificate/registration tracking, and an AI Q&A assistant (AI Atlas), but nothing describes a user-defined rules engine that automatically triggers actions on events (e.g., 'if nexus threshold crossed, auto-register' as a configurable rule). 'Early alerts' and 'automatic registration completion' are pre-built product features, not user-definable trigger/action rules.
- [claimed-docs] “Ask it anything about your sales tax and get an answer with the reasoning shown, grounded in your own transactions, registrations, filings, …”
- [claimed-docs] “Run tax through Anrok's APIs, or hand it to your agents. One engine powers all five jobs”
- [claimed-docs] “Early alerts before you owe anywhere”
Numeralnone0/10Evidence shows built-in system behaviors (nexus threshold triggering, certificate expiration tracking, automatic validation) but no capability for an AI-native user to author custom rules that trigger arbitrary actions on events — no rules engine, webhook/trigger configuration, or conditional automation framework is documented.
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnAnroknone0/10Anrok is a tax compliance/API platform; no evidence describes any scheduling of recurring jobs or workflows (cron-like automation, scheduled syncs, recurring filings automation via API). Filings, registrations, and calculations are described as on-demand API calls or automatic processes, not user-schedulable recurring jobs.
Numeralnone0/10Numeral's docs describe automated recurring compliance processes (auto-filing, remittance, certificate renewal tracking) as built-in product behavior, but there's no evidence that an AI-native user can programmatically schedule or configure recurring jobs/workflows via the API or MCP server — the MCP tools expose read/trigger actions (nexus status, certificate requests) rather than a scheduling primitive. missing for 10: any API/MCP capability to create, list, or manage recurring/scheduled jobs or workflows initiated by the user or agent.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “Automatically validate each uploaded certificate * Expiration tracking, renewals, and compliance monitoring”
Exemption certificates — stories about exemption certificates in this arenaExemption certificates
Stories about exemption certificates in this arena
Certificate management
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 NumeralAnrok 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”
Numeral's docs describe a full certificate_request object lifecycle (trigger, read state, cancel) and pricing page confirms automatic validation of uploaded certificates plus expiration tracking, renewals, and compliance monitoring, covering collection, validation, and storage/expiry well. However, there is no explicit evidence that certificates are automatically applied at tax calculation time to exempt a transaction. Missing for 10: direct documentation of certificate application/exemption logic during the calculation API call, and independent/hands-on confirmation of the end-to-end flow.
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [claimed-docs] “Automatically validate each uploaded certificate * Expiration tracking, renewals, and compliance monitoring”
Exempt customers
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 NumeralDocs 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.”
Numeral's docs confirm an `exemption-certificates` object and `certificate_request` workflow (trigger/read/cancel) plus certificate validation and expiration tracking, showing exemption handling exists at the API level. However, there's no evidence of explicitly marking a customer or transaction exempt with a specific exemption reason field, nor documentation showing that reason flows through tax calculation, reporting, and the filed return itself. Missing for 10: explicit API fields/endpoint for setting exemption reason on customer/transaction, documentation of reason propagation into calculation logic, and confirmation it appears in reporting/filed returns.
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [claimed-docs] “Automatically validate each uploaded certificate * Expiration tracking, renewals, and compliance monitoring”
Filing remittance — stories about filing remittance in this arenaFiling remittance
Stories about filing remittance in this arena
Autofile
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 NumeralEvidence 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.”
Numeral's marketing claims automatic registration, filing, and remittance across jurisdictions 'on time, every time' and handles related mail from tax authorities, showing strong first-party support for the filing/remittance workflow. However, the evidence pack contains no mention of a specific late-filing penalty guarantee or indemnification, which is a core part of the story. Missing for 10: explicit vendor guarantee/indemnification language covering penalties for late filings, independent verification of on-time filing performance.
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “We scan, read, and respond to all your sales tax mail from state and local governments.”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
Filing visibility
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 NumeralEvidence 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.”
Numeral's docs confirm it manages filings and remittance end-to-end ("Register, file, and remit... on time, every time", MCP tools surfacing filings and nexus status) but there is no evidence of a calendar-style upcoming-returns view, no mention of remitted amounts display, and no mention of downloadable confirmations for submitted returns. missing for 10: calendar view of upcoming filings, remitted-amount reporting per filing, downloadable filing confirmations.
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
Global vat — stories about global vat in this arenaGlobal vat
Stories about global vat in this arena
Invoice compliance
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 AnrokAnrok 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.”
Numeralnone0/10Numeral's docs show tax calculation, transaction/calculation objects, VAT ID validation and nexus/filing management, but there is no evidence of the product generating or feeding compliant invoice documents themselves — no mention of VAT registration numbers on invoices, required invoice line-item fields, or locale-specific invoice formatting rules flowing to an invoicing system.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “Validate customer VAT IDs live”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
Vat coverage
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 AnrokEvidence 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”
Numeral markets itself as covering 'US and global jurisdictions' and offers live VAT ID validation, suggesting some non-US tax support, but there is no evidence of specific OSS/IOSS registration, UK/Canada/Australia threshold tracking, or global filing workflows described in the docs. Missing for 10: explicit OSS/IOSS scheme support, per-country (UK, Canada, Australia) registration threshold tracking, and documented global filing/remittance processes beyond the generic 'global jurisdictions' claim.
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “Validate customer VAT IDs live”
Vat validation
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 NumeralAnroknone0/10Evidence 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.”
Numeral's pricing page claims 'Validate customer VAT IDs live' (numeral-docs-16), suggesting some real-time VAT ID validation capability, but there is no documentation of reverse charge mechanics, official registry (e.g., VIES) integration, or B2B cross-border transaction logic anywhere in the evidence pack — the product's core narrative is US sales tax nexus/filing, not EU VAT compliance. Missing for 10: reverse charge application logic, explicit official-registry validation (VIES or equivalent), B2B cross-border transaction handling, and any independent corroboration of the VAT ID validation claim.
- [claimed-docs] “Validate customer VAT IDs live”
Nexus monitoring — stories about nexus monitoring in this arenaNexus monitoring
Stories about nexus monitoring in this arena
Exposure analysis
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 NumeralAnroknone0/10Evidence 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”
Numeral offers a nexus study and MCP tools that report current nexus position per jurisdiction (thresholds, sales/transaction counts), which partially supports exposure monitoring, but there is no evidence of importing historical transactions to back-calculate liability, or of penalty/interest estimation per jurisdiction. missing for 10: historical transaction import for backdated analysis, estimated liability calculation, penalty and interest estimation per jurisdiction.
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “You can connect your sales channels and receive a free nexus study with no contract or upfront commitment required.”
Threshold tracking
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 drawnAnrok'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.”
Numeral explicitly tracks nexus position per jurisdiction with live economic thresholds and current sales/transaction counts (numeral-docs-10), offers a free nexus study (numeral-docs-14), and surfaces nexus status via MCP queries (numeral-docs-9). However, there is no explicit evidence of proactive threshold-crossing alerts/notifications sent before a limit is hit — the docs describe on-demand querying of current status rather than an automated pre-crossing warning system. Missing for 10: documented proactive alert/notification mechanism triggered before threshold breach, evidence of alert delivery channels (email/dashboard push), and any independent confirmation of alert timing accuracy.
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “You can connect your sales channels and receive a free nexus study with no contract or upfront commitment required.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnAnrok'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…”
Numeral's docs show broad API coverage of core dashboard functions—products, transactions, calculations, exemption certificates, nexus, filings, registrations—and the MCP server exposes these same objects as agent-callable tools, suggesting strong parity between UI and API/agent access. However, there is no explicit statement that 100% of UI functionality is API-accessible, and a probe for a canonical OpenAPI spec returned 404s, leaving completeness unverified. Missing for 10: an explicit UI-to-API feature parity statement, a confirmed complete OpenAPI/API reference, and independent verification that all dashboard actions (e.g., billing, certificate uploads) are API-reachable.
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.numeral.com/openapi.json, https://docs.numeral.com/swagger.json, https://docs.numeral.c…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnAnroknone0/10There 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.”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userControl data retention and deletion
weight 2 · round drawnAnroknone0/10The evidence pack covers Anrok's tax calculation, filing, and certificate APIs but contains no mention of data retention policies, data deletion controls, or privacy/data lifecycle management features for AI-native users. No documentation addresses how users can control or delete stored data.
Product taxability — stories about product taxability in this arenaProduct taxability
Stories about product taxability in this arena
Marketplace rules
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 drawnAnroknone0/10No 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.
Numeralnone0/10The evidence pack details Numeral's nexus tracking, tax calculation, transactions, and filings features, but nowhere mentions marketplace facilitator sales (e.g., Amazon, app stores) or the specific handling needed to track such sales for nexus purposes without double-remitting tax already collected by the facilitator. This is a real and applicable capability for sales tax compliance software, but no evidence addresses it.
Saas rules
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 AnrokAnrok'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”
Numeralnone0/10Evidence shows only generic tax calculation via address+product lookup (numeral-docs-1) and certificate/nexus tracking, but nothing about SaaS-specific state-by-state taxability nuances, digital-goods rules, bundled-offering treatment, or visible research/rationale behind determinations.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “Create a product with a POST to `/tax/products`”
Tax codes
developerMap my catalog to the vendor's tax categories — SaaS, digital goods, services, physical products — so each line item is taxed by what it is, in every jurisdiction it sells
weight 2 · round to AnrokAnrok'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.”
Numeral's docs confirm a product-taxability model (creating `product` objects via POST /tax/products and computing tax based on address + product set), implying category-based tax logic, but the evidence never surfaces the actual taxonomy (SaaS, digital goods, services, physical goods) or a way for developers to map their catalog into it. missing for 10: explicit tax category list/taxonomy, documented mapping workflow from SKU to category, jurisdiction-specific category rules, and independent verification of correctness.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “Create a product with a POST to `/tax/products`”
Tax agent access — stories about tax agent access in this arenaTax agent access
Stories about tax agent access in this arena
Agent operations
ai-native userAn agent can read my tax posture — nexus status, registrations, accrued liability, upcoming filings — and act on it through the API or an MCP surface with scoped credentials
weight 3 · round to NumeralAnrok'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…”
Numeral documents a dedicated MCP server exposing nexus status, filings, registrations, transactions, and exemption certificates as agent-callable tools, plus a full REST API for programmatic access to tax posture and actions (calculations, transactions, certificates). This directly matches the story of an agent reading and acting on tax posture via API/MCP. missing for 10: no explicit documentation of scoped/least-privilege credential support for the MCP endpoint or API keys, and no independent/hands-on corroboration of the MCP server's real-world reliability.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “`certificate_request` — an outstanding ask for an exemption certificate from one of your customers. Trigger one, read its state, cancel it.”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [probe] “official MCP server documented at https://docs.numeral.com/mcp/overview”
Builtin ai
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 AnrokAnrok'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”
Numeralnone0/10Numeral ships an MCP server that lets external AI agents query raw account data (nexus status, filings, transactions) — e.g. 'which states have I triggered nexus' — but this is infrastructure for connecting third-party/generic AI agents, not a first-party built-in tax-Q&A assistant that answers 'is this taxable' or 'why did this invoice tax this way' from its own rule base with citations. No evidence of a native chatbot or rule-cited answer engine exists in the pack.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Claude skills that teach an AI coding agent how to integrate the Numeral tax API correctly.”
Tax calculation — stories about tax calculation in this arenaTax calculation
Stories about tax calculation in this arena
Accuracy guarantee
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 drawnAnroknone0/10No 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'.
Calculation api
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 AnrokAnrok'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”
Docs confirm an API-based flow where you submit an address and products and get back an accurate tax amount, with a create-calculation step before transactions, supporting real-time per-address tax logic (numeral-docs-1, numeral-docs-3, numeral-docs-4). However, there's no explicit claim of rooftop-level (vs ZIP) precision or checkout-speed/latency guarantees, and no independent benchmarking. missing for 10: explicit rooftop-level accuracy claims, latency/performance benchmarks for checkout use, independent verification of real-time speed.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can now pass `customer.ip` instead of (or in addition to) `customer.address`”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.numeral.com/llms.txt # Numeral API - [Introduction](https://docs.numeral.com/introduction.md): Num…”
Integrations
developerThere are maintained integrations for my revenue stack — billing systems, payment processors, and commerce platforms feed transactions in without me building the plumbing
weight 2 · round to NumeralAnrok 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”
Numeral claims 'native integrations for the platforms your business already runs on' and supports connecting sales channels for nexus studies, indicating maintained connections to commerce/billing platforms feed data in without custom plumbing. However, evidence lacks specifics on which billing systems, payment processors, or commerce platforms are actually supported, how they're maintained, or independent confirmation of integration depth/reliability. Missing for 10: named list of specific integrations (Stripe, Shopify, etc.), documentation of integration setup/maintenance process, and independent/hands-on verification that these integrations work reliably.
- [claimed-docs] “Numeral provides native integrations for the platforms your business already runs on.”
- [claimed-docs] “You can connect your sales channels and receive a free nexus study with no contract or upfront commitment required.”
Rate maintenance
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 NumeralAnroknone0/10The 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.
Numeral's core pitch is that it handles tax calculation and returns accurate rates automatically via API (numeral-docs-1), and it manages filings/registrations across jurisdictions (numeral-docs-11), implying rate/rule maintenance is vendor-managed rather than requiring customer redeployment. However, there is no explicit documentation describing how rate/rule changes are tracked, versioned, or communicated to customers, nor any changelog or notice mechanism for jurisdiction rule updates. missing for 10: explicit documentation of automatic rate/rule update process, a changelog or notification system for jurisdiction changes, and confirmation that no client-side redeploy/config change is ever needed when rules change.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
Tax registrations — stories about tax registrations in this arenaTax registrations
Stories about tax registrations in this arena
Registration filing
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 NumeralAnrok'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”
Numeral explicitly claims to 'Register, file, and remit across US and global jurisdictions' on the customer's behalf, and its MCP/API surface exposes 'registrations' as an object with status data (nexus position, filing review status), supporting in-product tracking. However, there is no evidence of transparent per-registration pricing — the pricing docs describe billing tied to filings generally, not itemized registration costs. Missing for 10: explicit per-registration price disclosure, and independent/hands-on confirmation that registrations are actually filed (not just claimed).
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Standard accounts run month-to-month with no required contract; you are only billed as filings occur.”
Remediation
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 drawnAnroknone0/10Evidence 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.
Tax reporting — stories about tax reporting in this arenaTax reporting
Stories about tax reporting in this arena
Adjustments
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 AnrokAnrok'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”
Numeralnone0/10The evidence pack covers tax calculation, transactions, exemption certificates, nexus tracking, and filing/remittance, but nowhere mentions refunds, credit notes, or negative-amount adjustments flowing through liability and reporting. This is a fair axis for a tax compliance product, but no documentation addresses it.
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
Audit trail
ops userEvery calculation is reconstructable — the rate, rules, address resolution, and product category that produced each transaction's tax, retained and exportable for an audit
weight 2 · round to AnrokAnrok'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, …”
Numeral's API models a `calculation` object tied to each `transaction`, uses address/IP for resolution, and ties products to tax categories, suggesting the underlying data needed for reconstruction exists (numeral-docs-1,2,3,4). However, there is no evidence of an audit-export feature, a persisted rate/rule breakdown, or a UI/API for retrieving historical calculation detail for audit purposes. missing for 10: explicit audit-trail/export functionality, documentation of retained rate and rule detail per transaction, and any mention of long-term storage/retrieval of calculation inputs for compliance review.
- [claimed-docs] “You'll give us an address and a set of products, and we'll return the accurate tax amount you should charge.”
- [claimed-docs] “Create a product with a POST to `/tax/products`”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can now pass `customer.ip` instead of (or in addition to) `customer.address`”
Channel imports
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 AnrokAnrok'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.”
Numeral documents native integrations for existing sales/business platforms and an API for creating transactions/calculations, suggesting multi-channel ingestion, but the evidence never specifies which connectors exist (e.g., specific processors/storefronts) or confirms historical backfill/import of past transactions rather than just live transaction creation. Missing for 10: named connector list, explicit backfill/historical-import capability, and confirmation multiple channels roll into a unified filing dataset.
- [claimed-docs] “Numeral provides native integrations for the platforms your business already runs on.”
- [claimed-docs] “After you make a sale, you'll want to create a `transaction`. First, though, you'll have to have made a `calculation`”
- [claimed-docs] “You can connect your sales channels and receive a free nexus study with no contract or upfront commitment required.”
Liability reports
finance leadSee accrued liability by jurisdiction at any moment — collected versus owed, filing-ready detail, and exports my accountant and GL can consume
weight 2 · round to AnrokAnrok'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”
Numeral tracks nexus position and thresholds per jurisdiction and manages filings/registrations, and its API/MCP exposes transactions, sales, and calculations that could underpin liability tracking, but there is no explicit documentation of a 'collected vs owed' liability view or accountant/GL-ready exports. missing for 10: explicit accrued liability by jurisdiction report, collected-vs-owed breakdown, documented GL/accountant export formats (e.g., CSV/QBO sync).
- [claimed-docs] “The account's current nexus position per jurisdiction: whether nexus has been triggered (economic and/or physical), the economic thresholds …”
- [claimed-docs] “Register, file, and remit across US and global jurisdictions, on time, every time.”
- [claimed-docs] “start answering questions like "which states have I triggered nexus in, and are any filings waiting on my review?"”
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableAnrokn/aAnrok is a tax compliance SaaS product, not an AI agent client; the ability to plug MCP servers into it as tools is a client-role capability that doesn't apply to this product category. No evidence suggests Anrok itself functions as an MCP client.
Numeraln/aNumeral is a tax-compliance SaaS/API product that exposes its own data as an MCP server for external AI agents to call (docs-7, docs-9, probe-3) — it is not itself an agent or agent-runtime that would consume other MCP servers' tools. The 'plug MCP servers into this product' framing is a category error for a backend compliance platform; no evidence pack item describes Numeral acting as an MCP client.
- [claimed-docs] “The Numeral MCP server is a single HTTPS endpoint that exposes your Numeral account — nexus, filings, registrations, transactions, sales, pr…”
- [probe] “official MCP server documented at https://docs.numeral.com/mcp/overview”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableAnrokn/aAnrok is a sales tax calculation/compliance product, not an automation-building platform; there is no concept of user-defined automations to version, review, or roll back. This story applies to workflow/agent-builder tools, not a tax engine API.
ai-native userRead the product's source under an open license
weight 2 · not comparableAnrokn/aAnrok is a proprietary SaaS tax platform, not open-source software; source code availability under an open license is not a relevant axis for this product category.
ai-native userSelf-host the core product
weight 3 · not comparableAnrokn/aAnrok is a SaaS tax compliance platform, not open-source infrastructure software; self-hosting is a category error for this kind of hosted API service.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableAnroknone0/10No evidence in the pack addresses data residency, regional storage options, or data location controls for Anrok's platform; all evidence concerns tax calculation, filings, and API endpoints unrelated to data residency.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableAnroknone0/10No evidence in the pack addresses AI training data usage or opt-out policies for Anrok's AI features (e.g., AI Atlas); this is a plausible axis for a product with AI-driven features, but nothing documents a data-training opt-out.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableAnrokn/aAnrok is a tax compliance SaaS platform, not an AI agent/tool whose telemetry or usage-tracking opt-out would be a meaningful buyer axis; the evidence pack contains no relevant material either way.