# Find the tax rate and jurisdictions for an address

> Find the tax rate and jurisdictions for an address: 0 companies fully do it, 10 with a limit, 18 carry the tag. Every listing in Tax calculation & compliance with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/tax.rate-lookup/
- Markdown: https://www.anchorterminal.com/niches/tax.rate-lookup/index.md (~1,100 tokens)
- Slim: https://www.anchorterminal.com/niches/tax.rate-lookup/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/tax.rate-lookup/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

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 10 | 18 | 10 | 3 |

## What counts as done

The combined rate and each jurisdiction (state, county, city, district) for a validated street address, not only the ZIP, with the address correction returned when the input was changed, from one call.

How agents ask for it: what is the sales tax rate at this address; which jurisdictions apply here; is this address in city limits for tax; what VAT rate applies in Spain for ebooks

## 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.)**: address/resolve normalises an address and returns its taxable jurisdictions, but the endpoint is premium and enabled on request, and street-level resolution outside the US is a further premium feature.
- **Avalara AvaTax (Avalara, Inc.)**: GET taxrates/byaddress returns rates for a street address and ListJurisdictionsByAddress the jurisdictions, but the docs call byaddress approximate and US-only, and the address correction is a separate resolve call. acc-01 measured AvaTax 99.6% correct.
- **Fonoa (Fonoa Technologies Limited)**: A calculation by country and tax category code gives the VAT or GST rate and name, which answers the ebook-in-Spain case; street-address resolution to US jurisdictions with an address correction is not documented.
- **Kintsugi (Kintsugi AI, Inc.)**: POST /v1/address_validation/search validates the street address and fills in the county, then an estimate gives the rate and components; two calls, not one, and the estimate needs a product.
- **Numeral (Numeral Two, Inc.)**: A calculation returns each jurisdiction's rate and authority with the address used and its resolution precision, but needs a product line; there is no rate-only lookup endpoint.
- **Quaderno (Recrea Systems, SL)**: The calculate call takes to_street, to_city and postal code and returns the combined rate with region, county and city, but not each jurisdiction's own rate or an address correction.
- **TaxCloud (The Federal Tax Authority, LLC (d/b/a TaxCloud))**: POST verify-address corrects the address and a cart then gives the combined rate; two calls, and no state, county or city split is returned.
- **TaxJar (TPS Unlimited, Inc. (d/b/a TaxJar, a wholly owned subsidiary of Stripe, Inc.))**: GET /v2/rates/:zip takes street and city for rooftop accuracy and returns state, county, city and combined district rates; address validation is a separate Professional call. acc-18 shows ZIP-and-city inputs giving the wrong rate.
- **Vertex O Series (Vertex, Inc.)**: POST /address-lookup verifies and cleanses an address and returns its tax areas and jurisdictions; rates need a separate quotation call.
- **Zamp (Zamp Inc.)**: POST /addresses validates US addresses, and a calculation returns each jurisdiction's tax; two calls, US only for validation, and the calculation needs a line item.

## What stops agents finishing

- rate by ZIP only (acc-01, acc-18)
- street-level international addresses only on a premium plan

## Around it

Before: contacts.customer-address. After: tax.checkout-quote.

## Where this comes from

Weight 10 of 100 in Tax calculation & compliance: 3 of 29 accounts (acc-01, acc-18, acc-22); all three about ZIP-level rates being wrong or fields missing

As data: https://www.anchorterminal.com/api/v1/use-cases/tax.rate-lookup.json, or the MCP tool get_use_case with id tax.rate-lookup. 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
