# Zamp > Zamp is a managed sales tax service for US and Canadian sellers. Its REST API calculates tax by address, records transactions for filing and reads registrations and filings, while Zamp's team registers, files and remits. - Canonical: https://www.anchorterminal.com/tools/zamp - Markdown: https://www.anchorterminal.com/tools/zamp.md (~8,050 tokens) - Slim: https://www.anchorterminal.com/tools/zamp.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/zamp.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.5/100 · rank #609 of 722 · #9 in Tax calculation & compliance · not agent-ready · confidence medium** ## Assessment A free 30-day sandbox key needs no card or sales call, and the docs are served as Markdown with llms.txt and a published limit of 1,000 requests a minute. There is no OpenAPI file, SDK, API changelog or published price, production keys come with a sales-led account, and the site footer says SOC 2 compliance is in progress. ## Facts | Field | Value | | --- | --- | | Vendor | Zamp Inc. (https://zamp.com) | | Kind | HTTP API | | Category | Tax calculation & compliance (https://www.anchorterminal.com/categories/tax) | | Transport | HTTP | | Endpoint | `https://api.zamp.com` | | Auth | API key · Every request carries an API key as a Bearer token in the `Authorization` header. A 30-day sandbox key is emailed after a form that asks for a business email, with no card or sales call. A production key is copied from the Integrations page of app.zamp.com or issued by Zamp's account team, and a Zamp account comes through a demo and an Order Form. No scopes, read-only keys or expiry settings were found in the reviewed documentation. The docs tell users to rotate or reset an exposed key without describing how. | | Pricing | Paid (Paid) · No price is published. The pricing page names three plans, Free, U.S. and U.S. + Canada, and the two paid plans read "Contact sales". Free includes a rate-limited 30-day API sandbox with no card. Zamp says API calls are never metered and that usage is counted in committed transactions. The terms count ten calculation calls as one transaction for customers who use calculation only (https://zamp.com/pricing, https://zamp.com/terms-conditions section 6.2, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the developer docs, the pricing page or the terms (checked 2026-10-08). | | Licence | Proprietary service under Zamp's Standard Terms and Conditions, which form part of a signed Order Form. The sandbox has its own Developer trial terms | | Docs | https://developer.zamp.com | | llms.txt | https://developer.zamp.com/llms.txt | | Last release | 2026-08-31 | | API | 11 documented operations under https://api.zamp.com with JSON bodies. No version in the path and no OpenAPI file | | Calculation | `POST /calculations` returns `taxDue` and a `taxes` array with one entry per jurisdiction (state, county, city, district) for each line item and for shipping. Historical rates from 2023. Nothing is saved | | Transactions | `POST`, `GET`, `PUT` and `DELETE` on `/transactions`. Refunds are new transactions linked by `parentId`. Updates and deletes are refused for closed filing periods | | Read-only resources | `GET /filings` (status, due date, confirmation numbers and signed file links that expire after 1 hour), `GET /registrations`, `GET /companies` and `GET /tax-codes` | | Exemptions | Set on the transaction with `entity` (seven values such as `NON_PROFIT`) and `purpose` (such as `RESALE`). No certificate endpoint is documented | | Coverage | Zamp says 12,000+ US jurisdictions plus Canada. The countries guide also lists the United Kingdom, Australia, New Zealand and 27 EU states for VAT. Address validation is US only | | Credentials | API key as a Bearer token. Sandbox key by email, production key from the Integrations page of app.zamp.com. No scopes found | | Rate limits | 1,000 requests a minute per the FAQ. 429 returns the code `TOO_MANY_REQUESTS`. Responses carry `x-zamp-rate-limit-remaining` and `x-zamp-rate-limit-reset`, seen on a live response and not documented | | Errors | 14 named codes from `PARSE_ERROR` to `INTERNAL_SERVER_ERROR`, each with a message. Validation errors add an `issues` array with `code`, `message` and `path` | | Paging | Cursor paging with `limit` 1 to 100, default 10, newest first. `GET /tax-codes` returns every code in one response | | Sandbox | 30-day trial key with all 47 remote-seller state registrations preset. Same base URL as production. Data is deleted after 30 days and nothing is filed | | Pricing | Not published. Free plan with sandbox, U.S. and U.S. + Canada plans through sales | | SDKs | No official SDK found on npm, PyPI or Zamp's GitHub organisation, which holds one Adobe Commerce extension | | Webhooks | None, per the FAQ | | Status | Statuspage at https://zamp.statuspage.io (status.zamp.com redirects there) with four components. No incident has been posted | | Capabilities | tax.calculate, tax.transactions, tax.filing, tax.exemptions, shipping.address-validation | | Tags | hosted, paid, closed-source, api-key, llms-txt, sandbox, free-trial, no-card, sales-led, status-page | | JSON | https://www.anchorterminal.com/api/v1/tools/zamp.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 | 72 | 14.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 44 | 7.2 | | Agent ergonomics | 13% | 16.2 | 64 | 10.4 | | Security & auth | 14% | 17.5 | 40 | 7.0 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 42 | 3.7 | | Transparency & trust (editorial 27, provenance 73) | 7% | 8.8 | 50 | 4.4 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **49.5 → D** | ### Why each score - Reliability 72: Graded on the public REST API at api.zamp.com with the hosted lines. Statuspage at zamp.statuspage.io, reached from status.zamp.com, with four components (Calculations API, Transactions API, Zamp API, Zamp Dashboard) (20). The incident feed is empty and the page record was last changed on 29 June 2024. A clean record earns 30, and we took 10 off because no entry of any kind has been posted in over two years, so a monitored page can't be told from an unused one (20). The FAQ gives a limit of 1,000 requests a minute (15). 429 is documented with the code `TOO_MANY_REQUESTS`, and a live response carried `x-zamp-rate-limit-remaining` and `x-zamp-rate-limit-reset`. No Retry-After, backoff guidance or idempotency keys were found. A repeated `POST /transactions` with the same id returns 409 (7). No SLA found. The Accuracy Guarantee in the terms covers penalties and interest, not availability (0). No beta or preview label on the API (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 44: No machine-readable contract for the API. The one OpenAPI file on the docs host, `api-reference/openapi.json`, is the documentation platform's plant store sample (0). `llms.txt`, `llms-full.txt` and a Markdown copy of every page at the page address plus `.md` (10). Guides say when to calculate and when to post, the refund guide shows invalid and correct requests side by side, and the FAQ states what the API can't do (14). Parameters are listed with types, required flags, length limits and enumerated values for `entity`, `purpose`, `marketplace` and filing frequency. There is no schema, `isResale` appears in examples but not in the property list, and the update call is listed as `PUT /transactions` while its example uses `/transactions/123` (8). cURL, Node.js and Python examples in the quickstart, full response examples, and an error table of 14 codes with two example bodies (12). No version in the path and no API changelog found. `subtotal` is marked deprecated with no date (0). - Agent ergonomics 64: List endpoints take `limit` from 1 to 100, default 10, with no field selection. A calculation returns one entry per jurisdiction for each line item and a second where shipping is taxed, and `GET /tax-codes` returns every code in one response (12). Cursor paging on lists, with filters by transaction date on `/transactions` and by state, due date and completion on `/filings` (17). Errors carry a named code and message, and validation errors add an `issues` array with the path of each field. No recovery advice per code (16). The caller sets the transaction id, a duplicate create returns 409, `PUT` replaces by id and `/calculations` saves nothing, so retries are safe. No idempotency keys (12). Few required fields, a default tax code of `R_TPP` and a default country of US. No official SDK found (7). - Security & auth 40: One Bearer API key per account or integration, emailed for the sandbox and copied from the Integrations page for production. The docs say to rotate or reset an exposed key without describing how, and no scopes or expiry were found (17). No read-only key or approval step found. `DELETE /transactions/:id` deletes permanently, though updates and deletes are refused for closed filing periods, and the API can't start registrations or file returns (5). Responses hold the caller's own transaction data and Zamp's tax codes, with no injection guidance found (8). The API product page says customers can "access detailed logs, transaction histories, and calculation outputs". No description of an audit log of key use was found (5). A trust centre exists at trust.zamp.com but is drawn by script and we couldn't read it. The site footer reads "Compliance in progress for AICPA SOC2". No security.txt, disclosure policy or bug bounty found (5). - Payments & pricing 20: No x402, MPP or L402 (0). No price is published. The pricing page names Free, U.S. and U.S. + Canada plans, and the paid plans read "Contact sales" (0). A free 30-day sandbox key with no card, per the trial page (20). The key is emailed after a web form that asks for a business email, and a production account goes through a demo and an Order Form (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 42: Closed service with no API changelog. The newest dated entry in the docs is the QuickBooks connector's release notes of 31 August 2026, 38 days before the check (20). Three dated entries in the last 90 days, QuickBooks on 30 July and 31 August and WooCommerce plugin 3.4.0 on 4 August 2026. All three are connectors, not the API, so we scored this in part (12). No public changelog for the API. Support by email and telephone (5). No official SDK on npm, PyPI or GitHub, and no entry in the official MCP registry (0). The Adobe Commerce extension on GitHub is at 1.0.13 with a last commit on 22 April 2026 that added a CI check (5). - Transparency & trust 50: Closed service. The Standard Terms and Conditions are public, cover the API in section 2.2 and are governed by Delaware law. They carry no date and name the company only as ZAMP (13). The terms give 30 days to retrieve Customer Data after termination and let Zamp use data derived from Customer Data to improve its services. The privacy policy, last updated 11 February 2025, gives no retention periods and says Zamp does not support calculations outside the US, which disagrees with the countries guide. The Data Processing Agreement the terms refer to isn't linked (10). No deprecation policy found. The terms let Zamp discontinue the service in whole or in part at any time (2). No subprocessor list or data location found on the pages we could read (2). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/zamp.md (JSON https://www.anchorterminal.com/fixes/zamp.json) ### What we couldn't check - unchecked: the trust centre at trust.zamp.com, which is drawn by script. Certifications, subprocessors and data locations listed there were not read - unchecked: the Accuracy Guarantee the terms refer to. No link to it was found on the pages we read - unchecked: the certification spreadsheet and the connector release notes held in Google Docs - Whether SOC 2 is complete. The site footer says compliance is in progress and the developer docs say "SOC 2 controls" - Which countries the API calculates for. The docs home says US and Canada, the countries guide adds the UK, Australia, New Zealand and the EU, and the privacy policy says the US only - The legal entity. The footer says Zamp Inc., the terms say ZAMP, and the Companies API example shows Zamp Technologies, Inc. - How a key is rotated or revoked, and whether an account can hold several keys. The docs say to rotate or reset a key without giving steps - Whether the `x-zamp-rate-limit-reset` header is supported. It was seen on a live 401 response and is not documented - lastRelease is the date of the newest connector release note (QuickBooks, 31 August 2026), since Zamp publishes no API changelog - The lead's coverage claim of 12,000+ US jurisdictions and Canada matches the docs home and is Zamp's own statement ### Sources - developer docs home: (seen 2026-10-08) - docs index for agents: (seen 2026-10-08) - full docs in one file: (seen 2026-10-08) - API reference introduction: (seen 2026-10-08) - calculations reference: (seen 2026-10-08) - transactions reference: (seen 2026-10-08) - addresses, filings, registrations, companies and tax codes reference: (seen 2026-10-08) - sample OpenAPI file on the docs host: (seen 2026-10-08) - authentication: (seen 2026-10-08) - trial key: (seen 2026-10-08) - developer trial terms and conditions: (seen 2026-10-08) - production API access: (seen 2026-10-08) - quickstart: (seen 2026-10-08) - errors: (seen 2026-10-08) - pagination: (seen 2026-10-08) - FAQ, rate limit, webhooks and environments: (seen 2026-10-08) - refunds guide: (seen 2026-10-08) - countries guide: (seen 2026-10-08) - QuickBooks connector release notes: (seen 2026-10-08) - WooCommerce plugin downloads and release notes: (seen 2026-10-08) - unauthenticated API response and headers: (seen 2026-10-08) - pricing: (seen 2026-10-08) - API product page: (seen 2026-10-08) - Standard Terms and Conditions: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - status page summary: (seen 2026-10-08) - status incident history: (seen 2026-10-08) - trust centre, script-drawn and unread: (seen 2026-10-08) - security.txt, 404: (seen 2026-10-08) - GitHub organisation and Adobe Commerce extension: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - domain registration: (seen 2026-10-08) ## Who's behind it (provenance 73/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Zamp Inc. | 20/20 | | Domain age | zamp.com, registered 2001-08-01 (25 years) | 15/15 | | Endpoint on the vendor's domain | api.zamp.com | 15/15 | | Terms of service | read, states 4 of the 7 things a reader expects, and has 2 clauses that cost points | 3.4/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | zamp.statuspage.io | 10/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | The site footer reads "© 2026 Zamp Inc." with an address in Miami, Florida. The terms name the company only as ZAMP, and the Companies API example shows "Zamp Technologies, Inc." trading as Zamp Tax. The Standard Terms and Conditions at zamp.com/terms-conditions form part of the customer's Order Form and are governed by Delaware law. Section 2.2 covers the API. The page carries no date. Sandbox use is governed by the Developer trial terms and conditions at developer.zamp.com/guides/developer-trial-terms-and-conditions, effective 1 October 2025. The privacy policy, last updated 11 February 2025, defines the Service as the website and adds a Global Privacy Statement on data sent through the API. It is the only privacy document found. The terms refer to a Data Processing Agreement. No link to it was found on the pages we read. The API answers at api.zamp.com, on the vendor's domain. Its response headers name Vercel as the server. status.zamp.com redirects to zamp.statuspage.io. The page lists four components and its incident feed is empty. zamp.com, developer.zamp.com and api.zamp.com all return 404 for /.well-known/security.txt. No API changelog was found. The docs carry dated release notes for the QuickBooks, WooCommerce and NetSuite connectors only. RDAP for zamp.com gives a registration date of 2001-08-01, which predates the company's use of the name. ### 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://zamp.com/terms-conditions), read 2026-10-08, gives no date, states 4 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "attempt or provide a means to execute any “bulk download” operations, including without limitation by “crawling” the API or Content;" - To know. Restricts benchmarking or competitive use (costs points). "(F) use the API to create a product or service that is competitive with any Zamp Service." - To know. Says access can be ended without notice or for any reason. "In addition to any other remedies it may have, either party may also terminate this Agreement upon thirty (30) days’ notice (or without notice in the case of nonpayment), if the other party materially breaches any of the terms or conditions of this Agreement." - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. The law of the State of Delaware. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Zamp may use information concerning customer data to improve its services and for development of other Zamp offerings, during and after the term. "Company will be free (during and after the term hereof) to (i) use such information and data to improve and enhance the Services and for other development, diagnostic and corrective purposes in connection with the Services and other Company offerings" - Also in the text (2026-10-08). API customers may not cache, store or modify the sales tax content returned by the API unless Zamp authorises it. "cache or otherwise store any Content and/or modify any Content;" - Also in the text (2026-10-08). Zamp upgrades a customer to a higher tier automatically after three consecutive months above the tier's monthly transactions or when the supported states are exceeded. "if Customer exceeds the monthly transactions for three (3) consecutive months or exceeds the states supported which includes a one (1) state buffer for each tier, Company will automatically upgrade Customer to a tier that aligns with either the monthly transactions achieved over that time period" **Privacy policy** (https://zamp.com/privacy-policy), read 2026-10-08, dated 2025-02-11, states 8 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2025-02-11. - Says how long data is kept. For as long as needed, with no period named. - Also in the text (2026-10-08). Data partners may use cookies to link website visits and logins to a person's email or home address, and marketing may then be sent there. "When you visit or log in to our website, cookies and similar technologies may be used by our online data partners or vendors to associate these activities with other personal information they or others have about you, including by association with your email or home address." - Also in the text (2026-10-08). Zamp may share personal information with business partners to offer products, services or promotions. "With business partners: We may share Your information with Our business partners to offer You certain products, services or promotions." ## Live (updated 2026-10-09 02:46 UTC) - Right now: up, HTTP 418, 278 ms, checked 2026-10-09 02:43 UTC (get on `https://api.zamp.com`) - Uptime 24h 100.0% (79 probes) · 30 days 100.0% (79 probes) · p50 265 ms · p95 1.3 s - Vendor status page: none, All Systems Operational - Always current: https://www.anchorterminal.com/api/v1/live/zamp.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. ## Strengths - Free 30-day sandbox key by email with no card or sales call, preloaded with all 47 remote-seller state registrations - Docs served as Markdown with `llms.txt` and `llms-full.txt`, and cURL, Node.js and Python examples in the quickstart - Published limit of 1,000 requests a minute, and responses carry `x-zamp-rate-limit-remaining` and `x-zamp-rate-limit-reset` headers - Errors return a named code and message, and validation failures add an `issues` array with the path of each bad field - One transaction object is used by `/calculations` and `/transactions`, with a per-jurisdiction breakdown in every response ## Weaknesses - No OpenAPI file for the API. The one file on the docs host is the documentation platform's plant store sample - No price is published. The U.S. and U.S. + Canada plans read "Contact sales", and production keys come with a Zamp account - No API changelog, version in the path, deprecation policy or official SDK found in the reviewed documentation - API keys have no scopes or read-only mode in the reviewed documentation, and `DELETE /transactions/:id` deletes permanently - No security.txt or disclosure policy found, and the site footer says SOC 2 compliance is in progress - No webhooks, and registrations can't be started or approved through the API ## Before you call it (notes for agents) 1. Call `POST /calculations` for a quote and `POST /transactions` only when the sale is final. Put the returned `taxDue` in `taxCollected` when posting 2. Keep transaction and line item ids to 25 characters. A repeated `POST /transactions` with an existing id returns 409 `CONFLICT`, so a retry doesn't create a second record 3. For a refund, post a new transaction with `parentId` set to the sale's id and a negative `quantity`. Never send a negative `amount` on a line item 4. Send `shipToAddress.state` and `country` set to CA for Canadian orders. `POST /addresses` validates US addresses only 5. Page lists with `limit` (1 to 100, default 10) and `cursor` until `nextCursor` is null. `GET /transactions` returns only transactions written with the same key 6. Don't store sensitive or personal data in the sandbox. Trial data is deleted after 30 days and the trial terms forbid live customer data ## Connect First request: ```bash curl -X POST https://api.zamp.com/calculations \ -H "Authorization: Bearer {your-api-key}" \ -H "Content-Type: application/json" \ -d '{"id":"123","name":"INV-123","transactedAt":"2023-07-01T00:00:00.000Z","isResale":false,"discount":2,"subtotal":18,"shippingHandling":5,"total":23,"shipToAddress":{"line1":"120 SW 10TH AVE","line2":null,"state":"KS","city":"TOPEKA","zip":"66612"},"lineItems":[{"id":"LI-123","amount":10,"quantity":2,"discount":0,"shippingHandling":0,"productName":"The Ultimate Sampler","productSku":"SAMPLER-100","productTaxCode":"R_TPP_FOOD-BEVERAGE_HOME-CONSUMPTION"}]}' ``` Through letme (picks today, calling later): https://letme.dev/zamp. 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 | | TaxJar | C | 57.6 | 470 | tax.calculate, tax.transactions, tax.exemptions, shipping.address-validation | no | https://www.anchorterminal.com/tools/taxjar.md | | TaxCloud | C | 57.4 | 475 | tax.calculate, tax.transactions, tax.exemptions, shipping.address-validation | no | https://www.anchorterminal.com/tools/taxcloud.md | | Numeral | D | 49.3 | 611 | tax.calculate, tax.transactions, tax.exemptions, tax.filing | no | https://www.anchorterminal.com/tools/numeral.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 API reference documents 11 operations on 7 resources at https://api.zamp.com, covering `/calculations`, `/transactions`, `/addresses`, `/tax-codes`, `/companies`, `/registrations` and `/filings` (source: ) - The docs are served as Markdown by adding `.md` to a page address, with an index at `llms.txt` and the whole set in `llms-full.txt` (source: ) - The only OpenAPI file on the docs host, `api-reference/openapi.json`, is the documentation platform's sample for a plant store and does not describe Zamp's API (source: ) - The FAQ gives a rate limit of 1,000 requests a minute, says there are no webhooks, and says registrations can't be started or approved through the API (source: ) - The site footer reads "Compliance in progress for AICPA SOC2", while the developer docs say "SOC 2 controls and audit-ready records" (source: ) - The countries guide lists the United States, Canada, the United Kingdom, Australia, New Zealand and 27 EU states, while the privacy policy says Zamp does not support calculations outside the US (source: ) - The docs host answers MCP requests at `/mcp` with two read-only tools that search the documentation. It is the documentation platform's server and does not reach a Zamp account (source: ) - No Zamp server appears in the official MCP registry (source: ) ## Compare - [Anrok vs Zamp](https://www.anchorterminal.com/compare/anrok-vs-zamp.md): C 61.6 vs D 49.5 - [Avalara AvaTax vs Zamp](https://www.anchorterminal.com/compare/avalara-vs-zamp.md): B 68.8 vs D 49.5 - [Fonoa vs Zamp](https://www.anchorterminal.com/compare/fonoa-vs-zamp.md): D 51.7 vs D 49.5 - [Kintsugi vs Zamp](https://www.anchorterminal.com/compare/kintsugi-vs-zamp.md): C 60.7 vs D 49.5 - [Numeral vs Zamp](https://www.anchorterminal.com/compare/numeral-vs-zamp.md): D 49.3 vs D 49.5 - [Quaderno vs Zamp](https://www.anchorterminal.com/compare/quaderno-vs-zamp.md): C 59.5 vs D 49.5 - [TaxCloud vs Zamp](https://www.anchorterminal.com/compare/taxcloud-vs-zamp.md): C 57.4 vs D 49.5 - [TaxJar vs Zamp](https://www.anchorterminal.com/compare/taxjar-vs-zamp.md): C 57.6 vs D 49.5 - [Vertex O Series vs Zamp](https://www.anchorterminal.com/compare/vertex-tax-vs-zamp.md): C 54.7 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 zamp.com or one of its subdomains. 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": "zamp", "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 Zamp on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Zamp on Anchor Terminal](https://www.anchorterminal.com/badges/zamp.svg)](https://www.anchorterminal.com/tools/zamp) ``` Plain link: ```html Zamp on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Zamp 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/zamp-dark.png - Light: https://www.anchorterminal.com/assets/share/zamp-light.png