# Numeral > Numeral is a hosted sales tax and VAT compliance service from Numeral Two, Inc. Its REST API calculates tax, records transactions and refunds, and manages exempt customers, and Numeral registers and files. A remote MCP server reads the account. - Canonical: https://www.anchorterminal.com/tools/numeral - Markdown: https://www.anchorterminal.com/tools/numeral.md (~7,700 tokens) - Slim: https://www.anchorterminal.com/tools/numeral.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/numeral.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade D · 49.3/100 · rank #611 of 722 · #10 in Tax calculation & compliance · not agent-ready · confidence medium** ## Assessment Docs are written for agents, with a public OpenAPI spec for 32 operations, Markdown pages, llms.txt and a remote MCP server whose 14 tools are read-only by default. No status page, numeric rate limit or SLA was found, the API ignores idempotency keys, and API access is sold on a custom plan after a demo. ## Facts | Field | Value | | --- | --- | | Vendor | Numeral Two, Inc. (https://www.numeral.com) | | Kind | HTTP API | | Category | Tax calculation & compliance (https://www.anchorterminal.com/categories/tax) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://api.numeralhq.com` | | Auth | API key · The API and the MCP server take a secret API key as a Bearer token, `sk_test_` for the sandbox or `sk_prod_` for live data. Keys are created and revoked in the dashboard at dashboard.numeralhq.com under Developers. No scopes, expiry or OAuth flow were found, and publishable keys are rejected by the MCP server. Dashboard access starts with the get-started form or a demo, and the product page says to book a demo before generating test keys. MCP write tools are enabled per account on request. | | Pricing | Paid ($75 / tx) · Professional is $75 per filing and $150 per state registration, month to month. The tax engine and API are listed under Enterprise at a custom price. Monitoring (nexus study and alerts) is free. Test keys record transactions with no charges or remittance, but no self-serve signup was found and whether a free account can create keys isn't stated (https://www.numeral.com/pricing, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI spec or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under Numeral's terms of service. The Go, Python and Node SDKs are Apache-2.0 | | Tools exposed | 14 | | Packages | go: `github.com/NumeralHQ/numeral-tax-go`; pypi: `numeral-tax`; npm: `numeral-tax` | | Source | https://github.com/NumeralHQ/numeral-tax-go | | Docs | https://docs.numeral.com | | llms.txt | https://docs.numeral.com/llms.txt | | Last release | 2026-09-15 | | GitHub stars | 0 (as of 2026-10-08) | | npm downloads / week | 9 | | PyPI downloads / week | 19 | | API | 32 operations under https://api.numeralhq.com/tax in version 2026-03-01. OpenAPI 3.0.1 at https://docs.numeral.com/api-reference/v2026-03-01/openapi.json. Amounts are integers in minor units | | Versions | 2024-09-01, 2025-05-12, 2026-01-01 and 2026-03-01, chosen with the `X-API-Version` header. Merchant, platform and certificate endpoints need 2026-01-01 or later | | Calculation | `POST /tax/calculations` returns tax per line item and jurisdiction with an `expires_at`. `POST /tax/transactions` commits a `calculation_id` under a `reference_order_id` for filing. The best practices guide gives 24 hours as the calculation lifetime | | MCP server | Remote, stateless Streamable HTTP at https://mcp.numeralhq.com/mcp, POST only. 14 documented read-only tools. Four write tools gated per account. Health check at `GET /ping` | | Credentials | Secret API key as a Bearer token for both surfaces, `sk_test_` or `sk_prod_`. No scopes or OAuth. Revocation takes effect immediately per the MCP docs | | Rate limits | Not published. 429 on the API and 429 with JSON-RPC code -32005 on MCP, metered separately and per account. The docs advise exponential backoff | | Errors | From 2026-01-01, flat JSON with `code`, `type` and `message`, such as `ZIP_STATE_MISMATCH`. MCP tool errors return `error_code` and `error_message` with `isError` set | | Paging | Cursor paging with `has_more`. `limit` defaults to 10 with a maximum of 100 on merchants and certificates, and to 25 with a maximum of 100 on MCP list tools | | Sandbox | Test keys keep merchant, transaction and product data apart from production, and nothing is filed. Certificate endpoints are live only | | Pricing | Monitoring free. Professional $75 per filing and $150 per registration. Enterprise, which lists the tax engine and API, is custom | | SDKs | Go `github.com/NumeralHQ/numeral-tax-go` v0.1.0 (27 August 2026), Python `numeral-tax` 0.1.0a1 (18 December 2025), Node `numeral-tax` 0.1.0-alpha.2 (18 August 2026), generated by Stainless, Apache-2.0 | | Agent docs | llms.txt, Markdown pages, and Claude skills installed with `npx skills add https://docs.numeralhq.com`, which reference an optional `numeral-api-docs` MCP server for the documentation | | Coverage | Numeral says all US jurisdictions and 90+ countries (https://www.numeral.com/product/api) | | Status | No status page found | | Capabilities | tax.calculate, tax.transactions, tax.exemptions, tax.filing | | Tags | hosted, paid, closed-source, api-key, mcp, openapi, llms-txt, sandbox, sales-led, go, python, typescript | | JSON | https://www.anchorterminal.com/api/v1/tools/numeral.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 25 | 5.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 87 | 14.1 | | Agent ergonomics | 13% | 16.2 | 71 | 11.5 | | Security & auth | 14% | 17.5 | 47 | 8.2 | | Payments & pricing | 10% | 12.5 | 10 | 1.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 60 | 5.2 | | Transparency & trust (editorial 36, provenance 53) | 7% | 8.8 | 45 | 3.9 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **49.3 → D** | ### Why each score - Reliability 25: Graded on the REST API with the hosted lines, with the MCP server noted where it differs. No status page was found on numeral.com, the docs or the help centre, and `status.numeral.com` and `status.numeralhq.com` did not answer (0). With no page there is no readable incident history (5). The docs name 429 responses for the API and the MCP server but give no number. The product page says rate limits can be removed on request, and the MCP docs describe a sliding window per account (0). The best practices guide advises exponential backoff on 429 and one retry on 500 or 503. No Retry-After header is documented, and there are no idempotency keys, though the docs give a duplicate-recovery pattern on `reference_order_id` (10). No uptime SLA found. The filing guarantee covers late returns, not availability (0). The API has four dated versions and no beta label, and the MCP docs carry none (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 87: OpenAPI 3.0.1 at `docs.numeral.com/api-reference/v2026-03-01/openapi.json` with 32 operations and 74 schemas. An older unversioned spec with 15 operations is the one llms.txt links (25). `docs.numeral.com/llms.txt` indexes every page and each page is served as Markdown (10). Endpoint pages state purpose, the MCP overview says when to use MCP and when REST, and the AI help page publishes skills that list integration mistakes. We couldn't read the live MCP tool definitions without a key (16). 57 enums and 35 required lists, with 6 numeric bounds and 2 length limits (11). 235 examples in the spec and an error reference listing each `type`. The 2026-03-01 spec declares no 429 response (13). Versions are dates sent in `X-API-Version`, and the changelog covers each version with migration notes. Additions made after 1 March 2026 carry no date (12). - Agent ergonomics 71: List endpoints take `cursor`, and merchants and certificates take `limit` up to 100. No field selection. The MCP server documents 14 tools, list tools return summaries, and `get_sales_summary` aggregates in one call (16). Cursor paging throughout. Certificates filter by status, customer, jurisdiction and dates, while product and customer lists take only a cursor (16). Errors are flat JSON with `code`, `type` and `message` and a documented list of types. MCP tool errors return a stable `error_code` with a corrective message (19). No idempotency keys, and the docs say an `Idempotency-Key` header is silently ignored. Commits are made safe by handling `REFERENCE_ORDER_ID_ALREADY_EXISTS`, and cancelling a certificate request is idempotent. MCP annotations unread (11). A calculation needs an address or IP, line items, `origin_address` and `automatic_tax`. SDKs exist for Go, Python and Node, all below 1.0 and two marked alpha (9). - Security & auth 47: Secret API keys as Bearer tokens, `sk_test_` or `sk_prod_`, created and revoked in the dashboard, with revocation immediate per the MCP docs. No scopes, expiry or OAuth found (20). Test keys reach sandbox data only. The MCP server is read-only by default and its four write tools stay unregistered until Numeral enables them for an account. The REST API has no read-only key and no confirmation step (10). Responses carry merchant, customer and product names written by others, with no injection guidance found. The docs do state that no tool accepts an account identifier (3). The dashboard's Logs tab shows each request and response (8). A trust centre at security.numeral.com runs on Oneleet and is drawn by script, so we couldn't read it. No security.txt, bug bounty or disclosure policy found. The DPA lists security measures (6). - Payments & pricing 10: No x402, MPP or L402 (0). The pricing page gives $75 per filing and $150 per registration on Professional. The tax engine and API sit under Enterprise at a custom price, so the surface an agent calls has no public price (5). The Monitoring plan is free and test keys cost nothing, but the get-started page is a qualification form that ends in a demo booking, and whether a free account can create API keys isn't stated (5). Keys are created by a person in the dashboard (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 60: Closed service. The 2026-03-01 spec was last modified on 15 September 2026 and the docs were rebuilt on 8 October 2026 per their Last-Modified headers (30). The changelog has no dated entry since 1 March 2026. Dated activity in the last 90 days is the spec change, the Go SDK v0.1.0 on 27 August and the npm package on 18 August 2026 (10). A public changelog by version, a help centre and support by email. No public issue tracker in use (7). Go, Python and Node SDKs generated by Stainless, none at 1.0, and the Python package dates from 18 December 2025. Numeral's MCP server isn't in the official registry, where the only entry for the name is a third party's (8). The Go SDK has CI and a changelog (5). - Transparency & trust 45: Closed service under terms last updated 10 June 2025 that name Numeral Two, Inc. and California law. The SDKs are Apache-2.0 (15). The terms let Numeral use customer content to improve the services and other Numeral offerings and say it has no obligation to store it. The DPA of 2 January 2024 limits use to the customer's purposes and promises deletion or return at the end of service. The privacy policy of 11 May 2026 excludes platform data. No retention period or statement on AI training was found (12). No deprecation policy found. Four API versions stay documented with no end dates (4). The DPA says the subprocessor list is available by email and promises 30 days' notice of changes. Hosting location for platform data isn't stated (5). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/numeral.md (JSON https://www.anchorterminal.com/fixes/numeral.json) ### What we couldn't check - unchecked: the trust centre at security.numeral.com, a Oneleet page drawn by script. Certifications, penetration tests and any disclosure policy listed there were not read. Numeral's llms.txt says it holds SOC 2 information - unchecked: the live MCP tool definitions, input schemas and annotations, which need an API key. The count of 14 comes from the tool reference page - unchecked: the dashboard, including whether a free Monitoring account can create test API keys without a demo - Whether a status page exists. None is linked from the site, docs or help centre, and two guessed hostnames did not answer - The numeric rate limits for the API and the MCP server. Neither is published - The product page names Java, Python and Ruby SDKs. We found Go, Python and Node packages and no Java or Ruby one - The price of API access. The pricing page lists the tax engine and API under Enterprise as Custom - The privacy policy excludes platform data, so `provenance.privacy` points at the DPA, the published document that governs personal data in the product - lastRelease is the Last-Modified date of the 2026-03-01 OpenAPI spec, since the changelog carries no dated entry after 1 March 2026 ### Sources - docs index, llms.txt: (seen 2026-10-08) - docs introduction: (seen 2026-10-08) - quickstart: (seen 2026-10-08) - API keys: (seen 2026-10-08) - API reference introduction, version 2026-03-01: (seen 2026-10-08) - OpenAPI spec, version 2026-03-01: (seen 2026-10-08) - OpenAPI spec linked from llms.txt: (seen 2026-10-08) - API changelog: (seen 2026-10-08) - error codes: (seen 2026-10-08) - create calculations endpoint: (seen 2026-10-08) - best practices, error handling: (seen 2026-10-08) - AI help, skills and idempotency guidance: (seen 2026-10-08) - MCP overview: (seen 2026-10-08) - MCP quickstart: (seen 2026-10-08) - MCP tool reference: (seen 2026-10-08) - MCP authentication and limits: (seen 2026-10-08) - MCP health check: (seen 2026-10-08) - pricing: (seen 2026-10-08) - tax engine and API product page: (seen 2026-10-08) - get-started form: (seen 2026-10-08) - terms of service: (seen 2026-10-08) - data processing agreement: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - guarantee: (seen 2026-10-08) - trust centre, script-drawn and unread: (seen 2026-10-08) - marketing llms.txt: (seen 2026-10-08) - security.txt, 404: (seen 2026-10-08) - GitHub organisation repositories: (seen 2026-10-08) - Go SDK: (seen 2026-10-08) - Python package: (seen 2026-10-08) - npm package: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - domain registration, numeral.com: (seen 2026-10-08) - domain registration, numeralhq.com: (seen 2026-10-08) ## Who's behind it (provenance 53/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Numeral Two, Inc. | 20/20 | | Domain age | numeral.com, registered 1997-10-02 (29 years) | 15/15 | | Endpoint on the vendor's domain | api.numeralhq.com is not on numeral.com | 0/15 | | Terms of service | read, states 5 of the 7 things a reader expects | 8.3/10 | | Privacy policy | not found | 0/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms of service (last updated 10 June 2025) name Numeral Two, Inc. d/b/a Numeral, 527 Howard St, San Francisco, and are governed by California law. The API answers at api.numeralhq.com and the MCP server at mcp.numeralhq.com, a second domain. Numeral's docs name both hosts, and the dashboard is at dashboard.numeralhq.com. The privacy policy at numeral.com/legal/privacy-policy (effective 11 May 2026) covers the websites and says it does not apply to data processed through the platform and APIs. The privacy link here is the Data Processing Agreement (last updated 2 January 2024), which governs that data. www.numeral.com/.well-known/security.txt returns 404, as do the same paths on www.numeralhq.com and api.numeralhq.com. No status page was found on the site, the docs or the help centre. The trust centre at security.numeral.com is a Oneleet page drawn by script, which we couldn't read. RDAP gives registration dates of 1997-10-02 for numeral.com and 2022-07-14 for numeralhq.com. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.numeral.com/legal/terms-of-service), read 2026-10-08, gives no date, states 5 of the 7 things a reader expects. - To know. Says access can be ended without notice or for any reason. "Numeral may, with or without notice, terminate or suspend this Agreement (including the Services), at any time and for any reason, including if you have materially breached any provision of this Agreement, or if Numeral is required to do so by law" - To know. Requires arbitration or waives class actions. "It contains procedures for MANDATORY BINDING ARBITRATION AND A CLASS ACTION WAIVER." - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. The law of the State of CALIFORNIA. - Says how changes to the terms are announced. Gives thirty days of notice before a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Numeral may use customer content to improve its services and for development of its other products, during and after the agreement. "Numeral will be free (during and after the term of this Agreement) to (i) use Your Content to improve and enhance the Services and for other development, diagnostic and corrective purposes in connection with the Services and other Numeral offerings" - Also in the text (2026-10-08). Numeral may use the customer's name, logo and trademarks in marketing unless the customer emails to decline. "Numeral may identify you and use your name, logo, and trademarks on the Site and in marketing materials to identify you as a user of the Services." - Also in the text (2026-10-08). Numeral may permanently delete all customer content when the account is terminated. "All of Your Content on the Services (if any) may be permanently deleted by Numeral upon any termination of your Numeral account in its sole discretion." **Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0. ## Live (updated 2026-10-09 02:43 UTC) - Right now: up, HTTP 200, 561 ms, checked 2026-10-09 02:43 UTC (get on `https://api.numeralhq.com`) - Uptime 24h 100.0% (79 probes) · 30 days 100.0% (79 probes) · p50 596 ms · p95 672 ms - Always current: https://www.anchorterminal.com/api/v1/live/numeral.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Filed return, Professional | $75 | per transaction | Per return filed. API access is listed under Enterprise at a custom price | | State registration, Professional | $150 | per transaction | One-time fee per state | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.0.1 spec for version 2026-03-01 with 32 operations, 74 schemas and 57 enums, plus llms.txt and a Markdown copy of every docs page - Remote MCP server at `https://mcp.numeralhq.com/mcp` documents 14 read-only tools. Four write tools are off by default and absent from `tools/list` until enabled - Date-versioned API selected with the `X-API-Version` header, with a changelog and migration notes for each of four versions - Errors are flat JSON with `code`, `type` and `message`, and the docs list every `type`. MCP tool errors carry a stable `error_code` - `sk_test_` keys read and write sandbox data only, and the docs say revoking a key takes effect immediately ## Weaknesses - No status page, uptime SLA or numeric rate limit was found. The product page says rate limits can be removed on request - The API ignores an `Idempotency-Key` header. A retried commit is safe only if the client handles `REFERENCE_ORDER_ID_ALREADY_EXISTS` - Secret keys carry no scopes, and the MCP server has no OAuth flow. One key reads all of the account's tax data - API access is listed under the Enterprise plan at a custom price, and the product page says to book a demo first - SDKs are early. Go is v0.1.0, `numeral-tax` on PyPI is 0.1.0a1 from December 2025 and on npm is 0.1.0-alpha.2 ## Before you call it (notes for agents) 1. Send `X-API-Version: 2026-03-01` on every call to `https://api.numeralhq.com`. Merchant, platform and certificate endpoints reject requests without it 2. Commit with a stable `reference_order_id`. On `REFERENCE_ORDER_ID_ALREADY_EXISTS` look up the existing transaction, because `Idempotency-Key` is ignored 3. Commit before the calculation's `expires_at`. If it has expired, calculate again and commit the new `calculation_id` with the original `reference_order_id` 4. Send `amount` as the line total in minor units to `/tax/calculations` and as the per-unit price to `/tax/platform/calculations` 5. Start with an `sk_test_` key. Certificate endpoints and MCP certificate tools are live only and answer `TESTMODE_NOT_SUPPORTED` or `live_mode_required` ## Connect Install: ```bash go get -u 'github.com/NumeralHQ/numeral-tax-go@v0.1.0' ``` First request: ```bash curl --request POST \ --url https://api.numeralhq.com/tax/calculations \ --header 'Authorization: Bearer ' \ --header 'Content-Type: application/json' \ --header 'X-API-Version: 2026-03-01' \ --data '{ ... }' ``` Claude Code: ```bash claude mcp add --transport http numeral https://mcp.numeralhq.com/mcp \ --header "Authorization: Bearer sk_test_..." ``` MCP client configuration: ```json { "mcpServers": { "numeral": { "headers": { "Authorization": "Bearer sk_test_..." }, "type": "http", "url": "https://mcp.numeralhq.com/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/numeral. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Avalara AvaTax | B | 68.8 | 172 | tax.calculate, tax.transactions, tax.exemptions, tax.filing | no | https://www.anchorterminal.com/tools/avalara.md | | Anrok | C | 61.6 | 361 | tax.calculate, tax.transactions, tax.exemptions, tax.filing | no | https://www.anchorterminal.com/tools/anrok.md | | Kintsugi | C | 60.7 | 392 | tax.calculate, tax.transactions, tax.filing, tax.exemptions | no | https://www.anchorterminal.com/tools/kintsugi.md | | Zamp | D | 49.5 | 609 | tax.calculate, tax.transactions, tax.filing, tax.exemptions | no | https://www.anchorterminal.com/tools/zamp.md | | TaxJar | C | 57.6 | 470 | tax.calculate, tax.transactions, tax.exemptions | no | https://www.anchorterminal.com/tools/taxjar.md | | TaxCloud | C | 57.4 | 475 | tax.calculate, tax.transactions, tax.exemptions | no | https://www.anchorterminal.com/tools/taxcloud.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The 2026-03-01 spec has 32 operations under `/tax` for calculations, transactions, refunds, products, customers, merchants, platform calculations and exemption certificates (source: ) - The MCP server at https://mcp.numeralhq.com/mcp is stateless Streamable HTTP with 14 documented read-only tools for merchants, nexus, registrations, filings, transactions, sales, products and certificates (source: ) - Four MCP write tools (`approve_filing`, `reject_filing`, `set_product_tax_category`, `submit_exemption_certificate`) are gated per account and don't appear in `tools/list` until enabled (source: ) - The docs say Numeral does not support an `Idempotency-Key` header and silently ignores one. Safe retries rest on `reference_order_id` and the `REFERENCE_ORDER_ID_ALREADY_EXISTS` error (source: ) - Version 2026-03-01 added tax calculation from a customer's IP address with four resolution modes (strict, zero, approximate, best_effort) (source: ) - The terms let Numeral use customer content to improve the services and other Numeral offerings, and disclose it in aggregate or de-identified form (source: ) - The only server named numeral in the official MCP registry is `io.usefulapi/numeral`, published by a third party and not by Numeral (source: ) ## Compare - [Anrok vs Numeral](https://www.anchorterminal.com/compare/anrok-vs-numeral.md): C 61.6 vs D 49.3 - [Avalara AvaTax vs Numeral](https://www.anchorterminal.com/compare/avalara-vs-numeral.md): B 68.8 vs D 49.3 - [Fonoa vs Numeral](https://www.anchorterminal.com/compare/fonoa-vs-numeral.md): D 51.7 vs D 49.3 - [Kintsugi vs Numeral](https://www.anchorterminal.com/compare/kintsugi-vs-numeral.md): C 60.7 vs D 49.3 - [Numeral vs Quaderno](https://www.anchorterminal.com/compare/numeral-vs-quaderno.md): D 49.3 vs C 59.5 - [Numeral vs TaxCloud](https://www.anchorterminal.com/compare/numeral-vs-taxcloud.md): D 49.3 vs C 57.4 - [Numeral vs TaxJar](https://www.anchorterminal.com/compare/numeral-vs-taxjar.md): D 49.3 vs C 57.6 - [Numeral vs Vertex O Series](https://www.anchorterminal.com/compare/numeral-vs-vertex-tax.md): D 49.3 vs C 54.7 - [Numeral vs Zamp](https://www.anchorterminal.com/compare/numeral-vs-zamp.md): D 49.3 vs D 49.5 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on numeral.com or one of its subdomains, or the README of github.com/NumeralHQ/numeral-tax-go. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "numeral", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Numeral on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Numeral on Anchor Terminal](https://www.anchorterminal.com/badges/numeral.svg)](https://www.anchorterminal.com/tools/numeral) ``` Plain link: ```html Numeral on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Numeral is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/numeral-dark.png - Light: https://www.anchorterminal.com/assets/share/numeral-light.png