Head to head · Tax calculation · October 2026 research run
Fonoa vs Zamp
Zamp scores 52.4 (D) on agent readiness against Fonoa's 41.8 (E), and leads in 4 of 7 scored categories. Fonoa leads on schema & documentation and security & auth. Both do tax calculation.
Best sales tax and VAT calculation APIs for AI agents · All 45 tax comparisons
Which one, for what
Fonoa E
Best for An agent working for a company that already has a Fonoa contract and needs tax ID validation, VAT or GST calculation, or e-invoice reporting across many countries through one API.
Ahead on
- Schema & documentation, 68 against 44
- Security & auth, 47 against 40
Watch for
No self-serve signup. Sandbox, demo and production keys are issued by Fonoa after contact by email or the sales form
Zamp D
Best for An agent working for a US or Canadian seller that wants Zamp's team to register, file and remit, and needs calculation and transaction sync through a small API.
Ahead on
- Reliability, 72 against 27
- Payments & pricing, 30 against 5
- Maintenance & community, 60 against 21
Also in its favour
- Free to start without a card
Watch for
No OpenAPI file for the API was found in the developer docs
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Zamp +45
Fonoa 27
Graded on the public REST API with the hosted lines. status.fonoa.com runs on UptimeRobot. Its monitors and update feed were read on 8 October from the page's /api/ data feeds, which UptimeRobot's robots.txt disallows, so those readings are struck. With no component reading left, the status-page line scores 0, and with no readable history the incident line scores 5. No rate limit numbers found (0), per the 8 October check, not re-read on 4 November because Fonoa's terms bar automated access. E-invoicing and onboarding endpoints document a 429 that says to try again a bit later, with no Retry-After or backoff guidance. Submissions are idempotent by transaction_id and the docs say replays are safe. That is 429 guidance plus safe-retry guidance (12). Lookup and Tax writes carry no idempotency key, so the keys don't cover the listing's core writes (not 15). No SLA found on the public pages (0). Lookup v2, Tax v2 and E-invoicing v1 carry no beta label, while Instant Lookup is still being rolled out by country (10). 0 + 5 + 0 + 12 + 0 + 10 = 27.
Zamp 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 components for Zamp Dashboard, Calculations API and Transactions API under a Zamp API group (20). The history feed is empty and was last updated on 29 June 2024, and the page shows no incident from 21 October to 4 November 2026. 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. No Retry-After, backoff guidance or idempotency keys were found. A repeated POST /transactions with the same id returns 409, partly met (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). 20 + 20 + 15 + 7 + 0 + 10 = 72.
Maintenance & community Zamp +39
Fonoa 21
Closed service with no release tags or changelog, per the 8 October check, not re-read on 4 November because Fonoa's terms bar automated access. The newest reference pages read on 8 October, on document templates, carry an updatedAt of 2 October 2026, but the date doesn't show what changed, so it doesn't set recency. The newest dated API change is a product updates post covering July 2026 releases, dated to its month, 96 to 126 days ago (10). Fewer than three dated changes in the 90 days from 6 August (0). Support through a Zendesk request form and a support email address, with no public changelog or community channel found (6). No official SDK found (0). No packages to assess. The docs site is current (5). 10 + 0 + 6 + 0 + 5 = 21.
Zamp 60
Closed service with no API changelog. Zamp's own connectors carry dated release notes in the docs. The newest are the WooCommerce plugin 3.4.1 and the Adobe Commerce extension 1.0.14, both 15 October 2026, 20 days before the check (30). In the 90 days from 6 August there are QuickBooks on 31 August, Xero on 12 October, WooCommerce 3.4.1 and Adobe Commerce 1.0.14 on 15 October, and a new product tax code set in October 2026 (20). No public changelog for the API. Support by email and telephone (5). No official SDK on npm, PyPI or GitHub (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). 30 + 20 + 5 + 0 + 5 = 60.
Payments & pricing Zamp +25
Fonoa 5
No x402, MPP or L402 (0). No price is published, per the 8 October check. www.fonoa.com/pricing returns 404 and the site asks visitors to get in touch (0). No free tier or card-free trial found. A sandbox with unlimited usage and a demo environment exist, and a key for either comes from Fonoa after contact, scored as partial (3). Keys are issued by Fonoa staff, so an agent cannot get access on its own (0). 0 + 0 + 3 + 0 = 3. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 3 is 5.
Zamp 30
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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Schema & documentation Fonoa +24
Fonoa 68
Per the 8 October check, not re-read on 4 November, each reference page carries an OpenAPI 3.0 definition for its endpoint, readable in the Markdown twin. No single downloadable spec was found (20). docs.fonoa.com/llms.txt indexes every page as Markdown (10). Lookup descriptions state purpose and result states, and e-invoicing guides explain when to adjust, credit or cancel. The calculation endpoint's description covers only its two examples (13). The Lookup definitions carry 29 enums. The e-invoicing definitions carry none, with allowed values in prose and query parameters typed as plain strings (8). Request and response examples on every page read, a page on synchronous and asynchronous errors, and sandbox inputs that trigger each error. The calculation definition lists no 401 or 429 (12). Versions sit in the path, with Lookup v1 beside v2. No changelog was found and docs.fonoa.com/changelog returns 404 (5). 20 + 10 + 13 + 8 + 12 + 5 = 68.
Zamp 44
No machine-readable contract for the API was found in the docs (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, and a new tax code set from October 2026 is announced only on a legacy codes page (0).
Security & auth Fonoa +7
Fonoa 47
Per the 8 October check, not re-read on 4 November, one subscription key in the Ocp-Apim-Subscription-Key header, issued by Fonoa as a primary and secondary pair, with no scopes or expiry found (20). Separate keys for sandbox and production, and countries enabled per tenant. No read-only key or approval step for cancellations and credits found (5). Returns business names, addresses and tax authority messages written by others, with no injection guidance found (3). A history endpoint lists every operation on a transaction, and the security page mentions a dashboard for user access. No log of API key use found (6). ISO/IEC 27001 badge, a vulnerability disclosure programme with an email address, and third-party penetration tests with reports under NDA. No security.txt or bug bounty, and the Vanta trust centre is drawn by script and was not read (13). Webhooks are signed with an OIDC token that includes a body checksum, noted without points. 20 + 5 + 3 + 6 + 13 = 47.
Zamp 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 now reads "SOC 2 Type II compliant", with no report or disclosure route found. No security.txt, disclosure policy or bug bounty found (5).
Score by category
| Category | Weight | Fonoa | Zamp | Edge |
|---|---|---|---|---|
| Reliability | 16% | 27 | 72 | Zamp +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 68 | 44 | Fonoa +24 |
| Agent ergonomics | 13% | 64 | 64 | even |
| Security & auth | 14% | 47 | 40 | Fonoa +7 |
| Payments & pricing | 10% | 5 | 30 | Zamp +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 21 | 60 | Zamp +39 |
| Transparency & trust | 7% | 49 | 51 | Zamp +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 41.8/100 | D 52.4/100 |
Facts side by side
| Fact | Fonoa | Zamp |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Fonoa Technologies Limited | Zamp Inc. |
| Hosted endpoint | https://api.fonoa.com | https://api.zamp.com |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service. The API contract is not published. The public Terms of Service took effect on 14 May 2020, are labelled as last updated 9 May 2025, and name older seller sites | 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-02 | 2026-10-15 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no date given | 2025-02-11 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
How the scores have moved
Verdicts
Fonoa
The API reference is served as Markdown with an OpenAPI definition on each endpoint page, and e-invoicing submissions are idempotent by transaction_id. API keys are issued by Fonoa staff after contact, no price, rate limit or changelog is published, and the only public terms date from May 2020, cover older seller sites and bar automated access.
Zamp
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 SOC 2 claim has no report or disclosure route.
Before you call either
Fonoa
- Send the key in the
Ocp-Apim-Subscription-Keyheader. Use the sandbox key at https://sandbox.fonoa.com and the production key at https://api.fonoa.com - Treat validations and e-invoicing submissions as asynchronous. POST, then poll the GET endpoint or wait for the webhook, and avoid tight polling
- Reuse the same
transaction_idon a retry of/v1/transactions. A transaction already processed is not processed again - Commit a calculation with POST
/tax/v2/calculations/<uuid>/commitonly when the sale is final. The commit adds it to revenue tracking - Ask the Fonoa contact to configure webhooks. There is no API for it, and always fetch
resource_urlas given in the webhook
Zamp
- Call
POST /calculationsfor a quote andPOST /transactionsonly when the sale is final. Put the returnedtaxDueintaxCollectedwhen posting - Keep transaction and line item ids to 25 characters. A repeated
POST /transactionswith an existing id returns 409CONFLICT, so a retry doesn't create a second record - For a refund, post a new transaction with
parentIdset to the sale's id and a negativequantity. Never send a negativeamounton a line item - Send
shipToAddress.stateandcountryset to CA for Canadian orders.POST /addressesvalidates US addresses only - Page lists with
limit(1 to 100, default 10) andcursoruntilnextCursoris null.GET /transactionsreturns only transactions written with the same key - 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
Questions
Which is better for AI agents, Fonoa or Zamp?
Zamp scores 52.4 (D) on agent readiness against Fonoa's 41.8 (E), and leads in 4 of 7 scored categories. Fonoa leads on schema & documentation and security & auth.
Do Fonoa and Zamp need an API key?
Both need an API key.
Can an agent call Fonoa and Zamp without installing anything?
Yes. Fonoa has a hosted endpoint at https://api.fonoa.com and Zamp at https://api.zamp.com.
Other comparisons with Fonoa or Zamp
Machine-readable
- This page as Markdown
/compare/fonoa-vs-zamp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fonoa.json·/api/v1/tools/zamp.json - From a terminal
anchor compare fonoa zamp(the CLI) - Over MCP
compare_tools {"a": "fonoa", "b": "zamp"}at/mcp, no key