Head to head · Tax calculation · October 2026 research run
Fonoa vs TaxJar
TaxJar scores 57.8 (C) on agent readiness against Fonoa's 41.8 (E), and leads in 4 of 7 scored categories. Fonoa leads on schema & documentation. 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 48
Watch for
No self-serve signup. Sandbox, demo and production keys are issued by Fonoa after contact by email or the sales form
TaxJar C
Best for An agent working for a US seller that needs sales tax on an order at checkout and a record of orders and refunds for state reporting, with exempt customers handled by ID.
Ahead on
- Reliability, 84 against 27
- Payments & pricing, 45 against 5
- Maintenance & community, 44 against 21
- Transparency & trust, 72 against 49
Also in its favour
- Free to start without a card
Watch for
No OpenAPI spec or llms.txt was found. The taxjar/openapi repository on GitHub holds only a README
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 TaxJar +57
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.
TaxJar 84
Read with the hosted lines and scored on the public REST API at api.taxjar.com, the surface an agent would call. TaxJar has no MCP server. status.taxjar.com on Statuspage shows six top-level components on its page (TaxJar Reporting, TaxJar API with Tax Calculations, Tax Rates and Transaction Push, Other API Services and TaxJar Autofile), re-read on 4 November from the page and its Atom feed rather than the status API (20). In the 90 days from 6 August the feed holds only scheduled database maintenance on 30 August, announced on 13 August with a warning of momentary outages of some API endpoints. The last incidents were an integration fault on 26 March 2026 and a degraded API on 28 February 2026, and the page posts incidents, so the record is clean (30). Rate limits with numbers, 10,000 requests a minute on Professional and 25,000 on Premium, re-read on 4 November (15). The docs list 429 and advise caching, calculating only in nexus states and falling back to summarised rates. No Retry-After header or backoff guidance was found. Writes are keyed on a caller-chosen transaction_id, a duplicate create returns 422 and the docs direct a PUT (9 of 15). No uptime SLA was found. The published SLA covers support response times only, and the terms supply the API as is (0). The API is at v2 and generally available (10). 20 + 30 + 15 + 9 + 0 + 10 = 84.
Payments & pricing TaxJar +40
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.
TaxJar 45
Read with the hosted rubric. No x402, MPP or L402 (0). Plan prices are public, Professional from $99 a month at 200 orders, with a stated conversion of ten calculations to one order. Higher tiers sit on a selector, and the Premium plan named in the rate-limit docs has no public price. That is plan pricing (10 of 20). A 30-day trial with Professional plan access and the API needs no card, re-read on the pricing page on 4 November (20). A person has to sign up in a browser and generate the token in the web app (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Maintenance & community TaxJar +23
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.
TaxJar 44
A closed service, so we read releases from the official clients and plugins in their own repositories (clones on 4 November). The newest code release is the WooCommerce plugin 4.2.10 (tag 9 September 2026), which fixed coding-standard errors in the transaction sync and plugin files. The Node client 5.0.0, on npm since 2 September per the 8 October check, only removed the node-fetch dependency in favour of native fetch and raised the Node floor, so it can't set recency (20 of 30). In the 90 days from 6 August that is Node 5.0.0 at half, WooCommerce 4.2.9 (2 September) and 4.2.11 (5 October) at half each as tested-version bumps, and 4.2.10 in full, 2.5 releases. .NET 5.0.0 (NuGet 4 August) and Magento 4.0.2 (3 August) are now outside the window, and the API changelog has no entry since 24 January 2022 (0). Support is by email with a published response time of one business day on Professional, though the API licence agreement promises no API support. Reply times on the client repositories weren't measured (8 of 15). Seven official clients, four released since April 2025. The Ruby gem dates from August 2022, and the Java and Go repositories were last changed in March 2022 and October 2023 (11 of 15). The Node repository runs CodeQL only, with no test workflow in public CI (5 of 10). 20 + 0 + 8 + 11 + 5 = 44.
Transparency & trust TaxJar +23
Fonoa 49
Closed service. The only public terms took effect on 14 May 2020, name older seller sites and are governed by Croatian law. The page, read on 4 November, is now labelled as last updated 9 May 2025. The contract for API customers is not published (8). Per the 8 October check, not re-read on 4 November, the privacy notice says it does not cover data processed on behalf of customers, gives no retention periods and says data is stored primarily in the EEA. The 2020 terms say issued invoices are stored for up to 18 months. No public DPA found (10). No deprecation policy found. Lookup v1 is documented beside v2 with no end date (3). Storage primarily in the EEA is stated. No subprocessor list was found on the pages read, and the trust centre was not readable (6). 8 + 10 + 3 + 6 = 27.
TaxJar 72
The service is closed under terms of service and an API licence agreement last updated 14 May 2026. The clients are MIT (15 of 30). The privacy policy dates from 7 January 2022 and gives no fixed retention period. The data processing agreement of 14 May 2026 promises deletion or return of personal data after termination at the customer's choice, and notice of a data incident without undue delay. The documents agree but name no periods (18 of 30). No deprecation policy was found. Three dated API versions remain accepted, and the terms promise 30 days' notice of changes to terms and prices. International calculation was closed to new customers with no dated notice in the reviewed pages (5 of 20). The sub-processor list, updated 26 June 2026, names seven processors with purpose and country, and the privacy policy says the service is hosted in the United States (17 of 20), per the 8 October check. The terms of 14 May 2026 were re-read on 4 November. 15 + 18 + 5 + 17 = 55.
Schema & documentation Fonoa +20
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.
TaxJar 48
No OpenAPI spec was found. The taxjar/openapi repository on GitHub holds only a README, last changed in May 2020. The Node client ships TypeScript parameter and return types, which we counted as a partial contract (4 of 25). No llms.txt on developers.taxjar.com or www.taxjar.com, both 404 (0). The reference is one page covering 21 operations, with notes on sourcing, nexus and exemptions, and guides on product tax codes, marketplaces and avoiding unnecessary calls. Few entries say when not to use an endpoint (12 of 20). Parameter tables give a type and required, conditional or optional for each field, with allowed values for exemption_type in prose. Constraints such as amount arithmetic are enforced only on newer API versions (9 of 15). Request and response examples for every operation in cURL and seven client languages, an error code table, causes and fixes for 400, 401, 403, 406 and 422, and a sandbox header that mocks errors (13 of 15). Versions are dated and set by the x-api-version header, with a public changelog whose newest entry is 24 January 2022 (10 of 15), re-read on 4 November. 4 + 0 + 12 + 9 + 13 + 10 = 48.
Score by category
| Category | Weight | Fonoa | TaxJar | Edge |
|---|---|---|---|---|
| Reliability | 16% | 27 | 84 | TaxJar +57 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 68 | 48 | Fonoa +20 |
| Agent ergonomics | 13% | 64 | 61 | Fonoa +3 |
| Security & auth | 14% | 47 | 43 | Fonoa +4 |
| Payments & pricing | 10% | 5 | 45 | TaxJar +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 21 | 44 | TaxJar +23 |
| Transparency & trust | 7% | 49 | 72 | TaxJar +23 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 41.8/100 | C 57.8/100 |
Facts side by side
| Fact | Fonoa | TaxJar |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Fonoa Technologies Limited | TaxJar (Stripe) |
| Hosted endpoint | https://api.fonoa.com | https://api.taxjar.com/v2 |
| 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 TaxJar's terms of service and API licence agreement. The official API clients on GitHub are MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-02 | 2026-09-02 |
| Terms last updated | no document linked | 2026-05-14 |
| Privacy policy last updated | no date given | 2022-01-07 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| 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 |
| Popularity | none | 57 stars, 95k npm/wk, 50k PyPI/wk |
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.
TaxJar
A 21-operation REST API with a no-card 30-day trial, caller-chosen transaction IDs that make order pushes safe to repeat, and no status-page incident since March 2026. No OpenAPI spec or llms.txt was found, the API changelog stops at January 2022, recent client releases are mostly dependency or tested-version bumps, and tokens carry no scopes.
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
TaxJar
- Send
x-api-version: 2022-01-24on every call. Accounts opened before 3 February 2022 default to an older version with weaker validation - Pass
nexus_addresses[]or keep nexus states in the account. Without nexus the API returns zero tax and reports no error - Create orders with your own
transaction_id. On 422 the order already exists, so send a PUT to update it - Post JSON with
Content-Type: application/json. Form-encoded arrays such asline_items[]can return 406 - Cache calculations and skip states without nexus. Each calculation or rate lookup counts as a tenth of an order, errors included
Questions
Which is better for AI agents, Fonoa or TaxJar?
TaxJar scores 57.8 (C) on agent readiness against Fonoa's 41.8 (E), and leads in 4 of 7 scored categories. Fonoa leads on schema & documentation.
Do Fonoa and TaxJar need an API key?
Both need an API key.
Can an agent call Fonoa and TaxJar without installing anything?
Yes. Fonoa has a hosted endpoint at https://api.fonoa.com and TaxJar at https://api.taxjar.com/v2.
Other comparisons with Fonoa or TaxJar
Machine-readable
- This page as Markdown
/compare/fonoa-vs-taxjar.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fonoa.json·/api/v1/tools/taxjar.json - From a terminal
anchor compare fonoa taxjar(the CLI) - Over MCP
compare_tools {"a": "fonoa", "b": "taxjar"}at/mcp, no key