TaxJar vs Numeral
TaxJar
TPS Unlimited, Inc. (a Stripe company)
Numeral wins · 6–20 (20 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 NumeralTaxJarnone0/10Direct probes show no llms.txt (404) and no discoverable OpenAPI spec, and no evidence of agent-oriented documentation exists anywhere in the pack.
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 TaxJarTaxJar exposes a full REST API with API-key auth and official client libraries in seven languages, which supports headless/CI automation for tax calculations, transaction uploads, and nexus tracking. Missing for 10: no published OpenAPI/Swagger spec or llms.txt (both probes 404), no explicit CI/CLI examples or independent hands-on automation reports.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “TaxJar uses API keys to allow access to the API.”
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
- [claimed-docs] “'x-api-version' must be specified in API call request headers.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 NumeralTaxJarnone0/10TaxJar is a SaaS tax API/service, so an official MCP server is a fair question, but evidence only shows a traditional REST API with language SDKs, no MCP server; probes for llms.txt and OpenAPI spec both returned 404s, indicating no AI-native integration surface.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 drawnTaxJarnone0/10No evidence of an official CLI tool; TaxJar offers API clients in several languages but nothing resembling a command-line interface, and probes for openapi/llms.txt failed, suggesting no such tooling exists.
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
ai-native userDrive the product through a documented public API
weight 3 · round to NumeralTaxJar documents a full public REST API with API-key auth, versioned headers, and official client libraries in seven languages, covering rate lookups, transaction upload, and tax code parameters — clearly a documented public API for programmatic/agentic use. missing for 10: no discoverable OpenAPI/Swagger spec or llms.txt (probes returned 404s), and no independent/hands-on corroboration of API usability beyond vendor docs.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “TaxJar uses API keys to allow access to the API.”
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
- [claimed-docs] “'x-api-version' must be specified in API call request headers.”
- [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 drawnTaxJarnone0/10TaxJar's docs only describe a single API key mechanism with no mention of scoped, least-privilege, or per-agent credential issuance; no OAuth scopes, roles, or granular permission tokens are evidenced, and OpenAPI/llms.txt probes returned 404.
- [claimed-docs] “TaxJar uses API keys to allow access to the API.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 TaxJarTaxJar documents official API clients across seven languages (Ruby, Python, PHP, Node, C#/.NET, Java, Go) with API key auth and versioned headers, giving AI-native developers concrete official SDKs to build against. Missing for 10: no public OpenAPI spec or llms.txt (both probes 404), and no independent/hands-on corroboration of SDK quality or completeness.
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
- [claimed-docs] “TaxJar uses API keys to allow access to the API.”
- [claimed-docs] “'x-api-version' must be specified in API call request headers.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 drawnTaxJarnone0/10No evidence of any webhook or event-subscription capability in TaxJar's API docs; only REST API key access, client libraries, and integrations are documented, with no mention of webhooks.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “TaxJar uses API keys to allow access to the API.”
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to NumeralTaxJarnone0/10No evidence of AI-generated insights, recommendations, or in-product analytics powered by AI; the nexus threshold tracker (taxjar-docs-7/8) is rule-based reporting, not AI-generated. Missing for 10: any mention of AI/ML-driven insights, natural-language summaries, or suggestion features within TaxJar.
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
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 NumeralTaxJar's AutoFile feature runs autonomously in the background to file and remit state tax returns without manual intervention, which is a genuine 'set-and-forget' automation. However, this is a single fixed built-in feature rather than a general automation framework letting AI-native users configure their own triggers/workflows, and there is no evidence of webhooks, scheduled jobs, or agent-friendly automation tooling beyond the core API. Missing for 10: general-purpose automation/trigger framework, webhook or event-driven automation support, evidence of AI-agent-configurable workflows beyond AutoFile.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
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 drawnTaxJarnone0/10The 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.)
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 NumeralTaxJarnone0/10No evidence of any natural-language interface, chatbot, or NL command layer; TaxJar exposes only a traditional REST API with SDKs, and probes for llms.txt/OpenAPI discovery artifacts returned 404s. Missing for 10: any NL command support, conversational interface, or agent-friendly API documentation.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “TaxJar uses API keys to allow access to the API.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 drawnTaxJarnone0/10No evidence of an interactive API reference with runnable examples; probes for llms.txt and OpenAPI spec both returned 404, and docs only describe static API reference content and client libraries.
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
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 drawnTaxJarnone0/10Direct probes for llms.txt and common OpenAPI/Swagger spec paths all returned 404, and no documentation references a downloadable machine-readable API spec; only client libraries and reference docs are mentioned.
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
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 drawnTaxJarnone0/10No evidence pack mentions a sandbox, test mode, or non-production environment for the TaxJar API; only production API usage, keys, and integrations are documented.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to NumeralTaxJar's API requires an 'x-api-version' header, indicating some form of API versioning exists, but there is no documented deprecation policy, changelog, or sunset timeline evidenced anywhere in the pack. Probes for OpenAPI spec and llms.txt both failed (404), further limiting machine-readable API contract discovery for AI-native tooling. Missing for 10: documented deprecation/sunset policy, changelog of version changes, OpenAPI/machine-readable spec, and any evidence of long-term version support commitments.
- [claimed-docs] “'x-api-version' must be specified in API call request headers.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 TaxJarThe API docs vaguely mention that you can "upload transactions" via the API, hinting at bulk transaction import, but there is no documented batch/bulk endpoint, CSV import spec, or rate-limit guidance for large-scale calls. Missing for 10: explicit bulk/batch API endpoint documentation, throughput/rate-limit specs for large batches, and any first-party or independent evidence of successful bulk operations at scale.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
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 drawnTaxJarnone0/10TaxJar offers fixed automated behaviors (AutoFile filing, nexus threshold tracking) but there is no evidence of a user-configurable rules/trigger system letting an AI-native user define custom event-based automations; no webhooks, event API, or rule engine documented.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
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 drawnTaxJarnone0/10TaxJar's evidence covers API access, AutoFile, nexus tracking, and integrations, but there is no mention of scheduling recurring jobs/workflows or any workflow-automation/cron-like feature for AI-native users. AutoFile is a fixed filing automation, not a user-schedulable job system. missing for 10: any scheduler/cron API, workflow orchestration, or recurring job configuration capability.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
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 NumeralTaxJarnone0/10No evidence in the pack describes exemption/resale certificate collection, validation, expiry tracking, or automatic application at calculation time — the pack only covers tax rate/category APIs, AutoFile, nexus tracking, and integrations, none of which address certificate management.
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 NumeralTaxJarnone0/10No evidence pack item mentions exemption certificates, exemption reasons, or marking customers/transactions exempt via the API — only generic API reference, product_tax_code, and AutoFile filing features are documented. Missing for 10: any mention of exemption_type/exemption_id parameters, exemption certificate storage/reporting, or exemption data flowing into filed returns.
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 drawnTaxJar's AutoFile is explicitly documented to handle state tax returns and remittances with deadlines guaranteed, backed by a vendor guarantee (taxjar-docs-6), directly matching the core of the story. However, evidence doesn't clarify guarantee scope/terms (e.g., what penalties are covered, caps, exclusions), doesn't confirm coverage in every registered jurisdiction (state-only per wording), and there's no independent/hands-on corroboration of the guarantee being honored in practice. Missing for 10: detailed guarantee terms/limits, evidence of local/city jurisdiction filing beyond state level, and independent customer confirmation of guarantee payouts.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
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 NumeralTaxJarnone0/10Evidence confirms AutoFile handles filing/remittance and nexus tracking, but there is no mention of a filing calendar, per-filing status view, remitted-amount reporting, or downloadable confirmations for submitted returns. missing for 10: filing calendar UI, per-filing status tracking, remittance amount reporting, downloadable filing confirmations.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
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 drawnTaxJarnone0/10TaxJar's evidence pack covers only US sales tax rates, categories, economic nexus tracking, and state tax return AutoFiling — there is no mention of VAT-specific fields, EU/international registration numbers, invoice generation, or locale-specific compliance rules for VAT jurisdictions. The axis is fair for a tax-compliance product, but no evidence shows TaxJar addresses VAT invoicing at all.
- [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”
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 NumeralTaxJarnone0/10All evidence describes US sales tax nexus tracking, AutoFile for state returns, and US-centric integrations; nothing addresses EU OSS/IOSS, UK VAT, Canada GST/HST, Australia GST, foreign VAT registration thresholds, or international filing support.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”
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 NumeralTaxJarnone0/10TaxJar's evidence is entirely focused on US sales tax (economic nexus, AutoFile state returns, US integrations) with no mention of VAT, EU/UK tax ID validation, official registry checks (e.g., VIES), or reverse charge mechanics for B2B cross-border sales. Nothing in the docs or community evidence addresses global VAT compliance.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”
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 NumeralTaxJarnone0/10Evidence shows TaxJar can track economic nexus thresholds and upload/import transactions via API, but nothing describes a backdated exposure analysis with estimated liability, penalties, and interest per jurisdiction. Missing for 10: any mention of historical liability calculation, penalty/interest estimation, or jurisdiction-level backdated exposure reporting.
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
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 drawnTaxJar's economic nexus dashboard tracks sales/transaction counts against state thresholds and 'pinpoints states where you've met economic nexus thresholds' (taxjar-docs-7, taxjar-docs-8), showing real-time progress like '$90k of $100k' and '125 of 200' transactions. However, evidence does not confirm proactive alerting BEFORE crossing a threshold (vs. after), nor coverage of country-level (international) thresholds as the story specifies. missing for 10: explicit pre-crossing alert/notification mechanism, international/country threshold tracking, independent user confirmation of alert timing.
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
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 to NumeralDocs show a real API for tax calculation, categories, and transaction uploads, but no evidence that UI-only features like AutoFile automated filing or the economic nexus threshold dashboard are exposed via API, and probes confirm no public OpenAPI spec or llms.txt exists. missing for 10: API coverage for AutoFile/state filing, API for nexus threshold tracking/dashboard, machine-readable OpenAPI spec for full API discoverability.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 drawnTaxJarnone0/10The evidence pack shows only API access for uploading/retrieving transaction and rate data, with no documented bulk data-export feature, open-format full account export, or data-portability tooling; probes for llms.txt and OpenAPI specs both failed (404s). Missing for 10: any documented full-account data export capability, open format (CSV/JSON) bulk export tool, or data portability/account closure export guarantee.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userControl data retention and deletion
weight 2 · round drawnTaxJarnone0/10No evidence in the pack addresses data retention policies, deletion controls, or privacy/data lifecycle management for TaxJar's API or platform; documentation focuses solely on tax calculation, filing, and integrations.
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 drawnTaxJarnone0/10The evidence pack shows TaxJar tracks economic nexus thresholds and integrates with Amazon FBA, but there is no documentation describing how marketplace-facilitator-collected transactions are flagged, excluded from remittance, or reported separately for nexus purposes — the exact capability the story asks about is unaddressed.
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”
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 drawnTaxJarnone0/10Evidence only shows a generic `product_tax_code` parameter for categorizing line items, with no documentation of specific SaaS-taxability rules by state, digital-goods nuances, bundled-offering logic, or any visible research/citations behind determinations.
- [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
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 TaxJarTaxJar's API supports a `product_tax_code` parameter per line item, which maps catalog items to tax categories (e.g., SaaS, digital goods, services, physical goods) so each is taxed correctly per jurisdiction — this is the core mechanism for the story. However, evidence lacks a published/detailed taxonomy list of category codes, guidance on how many categories exist or how granular they are, and no independent/hands-on confirmation of correct jurisdictional tax application per category. missing for 10: full published category taxonomy/reference list, hands-on validation of correct per-jurisdiction tax outcomes by category, documentation on default categorization behavior when no code is supplied.
- [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
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 NumeralTaxJar has a documented REST API with API-key auth (docs-1,2,4) and a nexus-threshold tracking feature (docs-7,8), but evidence shows no API/agent access to registrations or accrued liability, no scoped/limited credentials beyond a flat API key, and no MCP surface — probes for llms.txt and OpenAPI discovery both failed (taxjar-probe-1, taxjar-probe-2). Missing for 10: API endpoints for registrations/accrued liability/filings, scoped/least-privilege credential model, any MCP server or agent-facing surface, independent confirmation of nexus data via API rather than dashboard-only.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “TaxJar uses API keys to allow access to the API.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 drawnTaxJarnone0/10No evidence of any AI/chatbot feature answering nexus or invoice-taxation questions with citations; evidence pack only covers API endpoints, AutoFile, nexus threshold tracking dashboards, and integrations. Probe results even show missing llms.txt/openapi discoverability artifacts, and there's no mention of an AI assistant anywhere in docs or community items.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.taxjar.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 drawnTaxJarnone0/10The only guarantee-related evidence concerns AutoFile ensuring filing deadlines are met, not calculation accuracy or audit support for erroneous tax calculations. No documentation in the pack describes a calculation-accuracy guarantee, indemnification, or audit-support commitment tied to TaxJar's tax rate/amount outputs.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
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 NumeralDocs confirm a REST API with API keys, multi-language clients, and line-item/product_tax_code support for tax calculation, implying real-time rate lookups suitable for checkout integration, but no evidence explicitly addresses rooftop/address-level accuracy claims or documented latency/performance suitable for checkout timing. Missing for 10: explicit documentation of rooftop-level address accuracy vs ZIP approximation, published latency/performance benchmarks, independent/hands-on corroboration of real-time checkout use, and a working OpenAPI spec (probes returned 404s).
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
- [claimed-docs] “'x-api-version' must be specified in API call request headers.”
- [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 TaxJarTaxJar documents pre-built integrations for major commerce/payment platforms (Amazon FBA, BigCommerce, eBay, Magento 2, NetSuite, PayPal, Shopify, Square, Stripe, WooCommerce) plus official API client libraries in seven languages, directly addressing the plug-and-play revenue-stack integration story. Missing for 10: no independent/hands-on verification that these integrations are actively maintained/up-to-date, no evidence of a public integrations marketplace or update changelog, and no OpenAPI spec available (probe returned 404s) to assess developer experience depth.
- [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”
- [claimed-docs] “We currently provide API clients for the following languages: Ruby Sales Tax API, Python Sales Tax API, PHP Sales Tax API, Node Sales Tax AP…”
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
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 NumeralTaxJar's API model implies rates are served dynamically (docs-1, docs-4 x-api-version header) so calculations don't require client redeploys, and nexus/AutoFile features suggest ongoing compliance handling, but there's no explicit documentation of a rate/rule change log, update cadence, or effective-date notices for jurisdiction changes. Missing for 10: explicit changelog/documentation of when rate/rule updates take effect, confirmation of automatic jurisdiction coverage updates, and independent verification that no client-side action is ever needed.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “'x-api-version' must be specified in API call request headers.”
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
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 NumeralTaxJarnone0/10Evidence only covers TaxJar's AutoFile service for filing state tax returns and remittances, and nexus threshold tracking — nothing about registering for sales tax permits (state/local registration filing) or per-registration pricing/status tracking. Missing for 10: any mention of permit registration service, registration pricing, or registration status tracking.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
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 drawnTaxJarnone0/10Evidence covers nexus tracking, AutoFile remittance, and API/integrations, but nothing addresses voluntary disclosure agreements (VDAs) or back-filing/remediation support for past-due, uncollected jurisdictions. Absence of evidence for this applicable capability means it is not shown to be delivered.
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
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 drawnTaxJarnone0/10No evidence pack item addresses refunds or credit notes, how negative amounts propagate through liability/reporting, or whether they auto-reconcile into the next filing without manual fixes. Evidence only covers general API usage, tax codes, AutoFile filing, and nexus tracking — none of which speaks to refund-specific tax adjustment. missing for 10: any documentation of a refund/credit-note API or workflow, confirmation that negative line items reduce liability correctly, and evidence that refunds are reflected in AutoFile filings without manual journal entries.
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 NumeralTaxJarnone0/10The evidence pack shows TaxJar's API can return rates, categories, and accept product_tax_code parameters, but there is no documentation of a stored, exportable audit record showing the exact rate, rule, address resolution, and category used for each historical transaction's calculation. Nothing addresses retention or export of calculation provenance for audit purposes.
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “the TaxJar API allows you to submit a `product_tax_code` parameter with each `line_item` in an order.”
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 TaxJarTaxJar's API supports uploading transactions and backfilling data programmatically, and its documented integrations list covers major storefronts and processors (Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce), enabling multi-channel data consolidation for filings. This directly supports the developer story of importing transactions from multiple sources into one nexus/filing view. Missing for 10: no independent/hands-on verification of connector sync reliability across all listed platforms, no detail on how conflicting/duplicate transactions from multiple sources are reconciled, and no OpenAPI spec confirming full API backfill capabilities (probe endpoints 404).
- [claimed-docs] “You can use our API to get information on sales tax rates, categories or upload transactions.”
- [claimed-docs] “Amazon FBA, BigCommerce, Ebay, Magento 2, Netsuite, PayPal, Shopify, Square, Stripe, Woocommerce”
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.taxjar.com/openapi.json, https://developers.taxjar.com/swagger.json, https://deve…”
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 NumeralEvidence shows nexus threshold tracking and AutoFile remittance/filing automation, which implies some jurisdiction-level tax handling, but there is no documentation of a liability report showing collected-vs-owed by jurisdiction, no mention of filing-ready detail views, and no export formats designed for accountants or GL consumption. missing for 10: collected-vs-owed liability dashboard, jurisdiction-level accrued liability reporting, GL/accountant-ready export formats, evidence of real-time 'at any moment' visibility.
- [claimed-docs] “Tracking Economic Nexus Sales threshold: $90k of $100k Transaction threshold: 125 of 200”
- [claimed-docs] “This tool will pinpoint states where you've met economic nexus thresholds.”
- [claimed-docs] “AutoFile handles state tax returns and remittances for you, ensuring deadlines are never missed – all backed by our guarantee.”
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 comparableTaxJarn/aTaxJar is a tax-calculation SaaS API/service, not an AI agent host that could consume MCP servers as tool providers; the evidence pack only covers TaxJar's own REST API, integrations, and clients, with no mention of MCP client functionality. This axis (plugging MCP servers into the product) is a category error for this kind of product.
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 comparableTaxJarn/aTaxJar is a sales-tax calculation/filing API and SaaS product, not an automation/workflow builder; there is no concept of 'automations' to version, review, or roll back in its product surface. This axis is a category error for this product type.
ai-native userRead the product's source under an open license
weight 2 · not comparableTaxJarn/aTaxJar is a commercial SaaS tax API product, not an open-source codebase; source availability under an open license is not a fair axis for this product category.
ai-native userSelf-host the core product
weight 3 · not comparableTaxJarn/aTaxJar is a cloud SaaS tax-calculation/API service, not open-source software; self-hosting the core product is a category error for this type of service.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableTaxJarnone0/10No evidence in the pack mentions data residency, regional data storage options, or any control over where TaxJar stores customer data; all documentation covers API usage, integrations, and tax filing features.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableTaxJarn/aTaxJar is a sales tax calculation/compliance API, not an AI model or AI-native product with data-training policies; no evidence relates to AI training data usage, so this axis is a category error for this product type.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableTaxJarn/aTaxJar is a sales-tax compliance/API product, not an AI agent or tool with client-side telemetry settings relevant to AI-native usage; opting out of telemetry/usage tracking is not a fair axis for this product category.