# Know where the seller must register and file, and what has been filed

> Know where the seller must register and file, and what has been filed: 2 companies fully do it, 3 with a limit, 5 carry the tag. Every listing in Tax calculation & compliance with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/tax.filing-status/
- Markdown: https://www.anchorterminal.com/niches/tax.filing-status/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/tax.filing-status/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/tax.filing-status/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 3 | 5 | 16 | 6 |

## What counts as done

Per jurisdiction: sales and transaction counts against the threshold, registration status, and each return with period, status and amount, read through the API or MCP, with the jurisdictions the service does not file for named.

How agents ask for it: where do we have nexus; are we close to the threshold in Texas; was the March return filed; what tax do we owe this quarter

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Kintsugi (Kintsugi AI, Inc.)**: GET /v1/nexus, /v1/registrations and /v1/filings (filterable by state, status and period, paged) cover exposure, registration status and returns with dates, status and amount; registration jurisdictions, including OSS countries, are listed.
- **Numeral (Numeral Two, Inc.)**: The MCP server reads nexus per jurisdiction (status, threshold rule, sales against it), registration status with account numbers and dates, and past and upcoming filings with status, period, due date and tax, penalty and interest.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Anrok (Anrok, Inc.)**: filings/list (premium, on request) lists filings by jurisdiction and period with their transactions; no nexus-threshold endpoint is in the API. acc-02 and acc-04 file EU OSS and international returns outside Anrok.
- **Avalara AvaTax (Avalara, Inc.)**: GET econexusthresholds gives each state's window, thresholds, totals and whether met; the Returns MCP lists filing calendars, filings, liability reports and supported countries. Returns is a separate product on a JWT, and acc-08 filed VAT returns in two dozen countries outside it.
- **Zamp (Zamp Inc.)**: GET registrations gives state, tax id, start and end dates and filing frequencies; GET filings gives period, due date, estimated tax due and amount paid, filterable by completion. No per-state sales against economic nexus thresholds is exposed.

- not this job: Fonoa (Fonoa Technologies Limited): The products are Lookup, Tax and E-invoicing; no registration, nexus-threshold or return-filing endpoints are in the index.
- not this job: Quaderno (Recrea Systems, SL): The API lists the seller's tax registrations (tax_ids) and jurisdictions, but no threshold exposure or filed returns; filing is a done-for-you service booked by call, and acc-05 found the tools stop at collecting data.
- not this job: TaxCloud (The Federal Tax Authority, LLC (d/b/a TaxCloud)): The v3 API has no nexus, registration or filing endpoints; filing happens in the TaxCloud account.
- not this job: TaxJar (TPS Unlimited, Inc. (d/b/a TaxJar, a wholly owned subsidiary of Stripe, Inc.)): GET /v2/nexus/regions lists the account's nexus states; no thresholds, registrations or filed returns are in the API.
- not this job: Vertex O Series (Vertex, Inc.): The calculation and GIS API has no nexus, registration or return endpoints.

## What stops agents finishing

- registration and filing are a done-for-you service booked by call, not an API
- international filing not covered, so returns are filed by hand (acc-02, acc-04)

## Around it

Before: tax.commit-transaction. After: messaging.notify, accounting.journal-entry.

## Where this comes from

Weight 16 of 100 in Tax calculation & compliance: 6 of 29 accounts (acc-02, acc-04, acc-05, acc-07, acc-08, acc-28); the HN thread's main question was who files, not who calculates

As data: https://www.anchorterminal.com/api/v1/use-cases/tax.filing-status.json, or the MCP tool get_use_case with id tax.filing-status. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
