Head to head · Tax calculation · October 2026 research run
Avalara AvaTax vs TaxCloud
Avalara AvaTax scores 71.8 (BB) on agent readiness against TaxCloud's 52.4 (D), and leads in 6 of 7 scored categories. TaxCloud leads on payments & pricing. Both do tax calculation.
Best sales tax and VAT calculation APIs for AI agents · All 45 tax comparisons
Which one, for what
Best for An agent that must calculate and record US sales tax at address level, with VAT and GST in other countries, and hand the records to filing.
Ahead on
- Reliability, 67 against 26
- Schema & documentation, 85 against 75
- Agent ergonomics, 84 against 64
- Security & auth, 65 against 45
- Maintenance & community, 79 against 65
- Transparency & trust, 80 against 53
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Production rate limits are not published. The only numbers found are the trial limits and 5 calls a minute on report exports
TaxCloud D
Best for An agent working for a US seller that needs tax on a cart at checkout, a record of orders and refunds for filing, and exemption certificates by customer.
Ahead on
- Payments & pricing, 51 against 45
Also in its favour
- Free to start without a card
Watch for
No rate limit numbers are published. The API page says only that the threshold is high and subject to change
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 Avalara AvaTax +41
Avalara AvaTax 67
Graded as a hosted service. Statuspage at status.avalara.com with 135 components, the AvaTax group split into Tax Calculation Service, Restv2, Batch, Reporting and others (20). Re-read on 1 November from the history feed (history.atom), because status.avalara.com's robots.txt disallows /api/, where the 8 October reading was taken; that reading is struck. In the 90 days from 3 August one incident touched AvaTax, "AvaTax customers may be experiencing degraded service levels" on the Tax Calculation Service and AvaTax UI from 22:32 PT on 5 October to 21:20 PT on 6 October, about 23 hours, impact minor, no cause given. Degraded service rather than an outage, read as partial and so minor, as this run reads partial incidents. The others hit AvaApp (5 August), Exemption Certificate Management (25 August) and Cross Border Restrictions (17 September), or were scheduled maintenance, and don't count for AvaTax. Nothing since 6 October. Minor only (20 of 30, was 15). Numbers are published only for the trial (5 orders and 5 invoices a minute, 1,000 transactions a day, re-read on 1 November) and report exports (5 a minute). Production limits not found (7). 429 is documented with three error codes, and the integration guide says to retry a timed-out invoice with CreateOrAdjustTransaction. No Retry-After or backoff guidance found (10). The Service Terms promise commercially reasonable efforts with no uptime percentage (0). REST v2 is GA and the MCP server is registered at 1.0.1 with no beta label (10). 20 + 20 + 7 + 10 + 0 + 10 = 67.
TaxCloud 26
Read with the hosted lines and scored on the v3 REST API at api.v3.taxcloud.com, the surface an agent would call. TaxCloud has no MCP server for the tax API. status.taxcloud.com redirects to a Datadog status page, per the 8 October check. The page is drawn by script, and its three components were read on 8 October only from the page's configuration data file, which this method doesn't use, so no component reading stands (0). On 4 November the Datadog host answered robots.txt with an access-denied 403, read as blocked, and TaxCloud's own pages are paused under its terms, so nothing more was requested. The 8 October incident reading came from the page's configuration data file, which this method doesn't use, so it is struck and no part of the window from 6 August has been read (5, unread and not a finding against the vendor). No rate limit numbers were found. The API page says "High threshold; subject to change based on usage" (0). Every operation lists 429, the docs advise exponential backoff on 500, TIC search documents 503 with Retry-After, refunds take an idempotencyKey, carts upsert and a duplicate orderId is refused. No backoff guidance for 429 was found in the docs, and order creation has no idempotency key (11 of 15, partly met). The security page says TaxCloud gives no SLA (0). v3 is the default version and is not marked beta (10). Docs, API page and security page per the 8 October check, not re-read on 4 November. 0 + 5 + 0 + 11 + 0 + 10 = 26.
Transparency & trust Avalara AvaTax +27
Avalara AvaTax 80
Closed service with versioned terms that keep every past version online (Service Terms 7.1, effective 1 October 2026, and AvaTax supplemental terms). SDKs are Apache-2.0 (17). The DPA (version 1.10, 2 June 2025) limits use of customer data to running the service, support and legal compliance, with retrieval for 10 days after termination and destruction on request up to 60 days after. No fixed retention periods, backups are excepted, and Avalara may use de-identified aggregate data for any lawful purpose (20). A written policy deprecates version n-2 when n ships and decommissions it 18 months later, and the spec dates field deprecations. The policy's example table has dates out of order, and the terms let documentation alone count as notice (15). Subprocessor list version 11.0 of 9 September 2026 with date added, purpose and country, hosting on AWS in the United States (17).
TaxCloud 53
The service is closed under terms of service last updated March 2025, and the agent skills are Apache-2.0 (15 of 30). The privacy policy (1 February 2025) states no retention period. The terms let TaxCloud keep a copy of customer content where law, regulators or backups require it. No data processing agreement was found on the legal page (10 of 30). No deprecation policy was found, v1 is called legacy with no end date, and the terms allow policy changes with or without notice (3 of 20). The security page names Microsoft Azure, Authorize.NET and GoCardless. No sub-processor list or data location was found (5 of 20). Per the 8 October check, not re-read on 4 November, because TaxCloud's terms bar automated access to its pages.
Agent ergonomics Avalara AvaTax +20
Avalara AvaTax 84
The MCP server documents ten tools. Their definitions sit behind OAuth, so size was not measured. On the API, $include=SummaryOnly or LinesOnly shrinks transaction responses (21). $top, $skip, $filter and $orderBy on 152 of 262 GET operations, with 1,000 records at most and @nextLink (20). Errors carry code, number, message, description, faultCode and helpLink (18). No idempotency key. CreateOrAdjustTransaction is the documented safe retry and CreateTransaction rejects a duplicate committed code. MCP annotations were not readable (10). CreateTransaction needs three fields (customerCode, date, lines) and defaults to an unrecorded SalesOrder estimate. SDKs in six languages (15).
TaxCloud 64
Get Order takes expand, list calls and TIC search take limit, and one cart call can price several carts. There is no field selection (14 of 25). Certificates, access keys and products page by cursor with limit, sortBy and ascending, and products add search and filters. No list-orders operation exists, so orders are read one ID at a time (14 of 20). Errors are documented as application/problem+json with title, status, detail and an errors list for 400 to 500 (16 of 20). Refunds take an idempotencyKey and return the original on replay, carts upsert by cartId, a repeated void returns 204 and account updates are safe to repeat. Create Order and cart conversion have no key, and the docs warn that converting a cart twice duplicates the liability (15 of 20). A cart needs customerId, currency, origin, destination and lineItems. No official v3 client library was found, and the API page points to OpenAPI Generator (5 of 15). Per the 8 October check, not re-read on 4 November, because TaxCloud's terms bar automated access to its pages.
Security & auth Avalara AvaTax +20
Avalara AvaTax 65
The MCP server uses OAuth with PKCE and a single scope, avalara_mcp. The REST guides lead with HTTP Basic using a username and password or an account ID and licence key. Keys are account-wide, can be named and are revoked on reset, and bearer tokens are accepted (20). Access follows user security roles, and a transaction is an unrecorded estimate unless an Invoice type is sent. No read-only mode or confirmation step is documented for the MCP's calculate_tax and create_nexus tools (10). Responses are mostly structured tax data with some merchant-entered text. No injection guidance found, and the Service Terms place responsibility for agent actions on the customer (8). An account audit endpoint for failed calls, audit log exports, and per-user attribution except with a licence key (12). Vulnerability disclosure programme, and SOC 1 Type 2, SOC 2 Type 2 and ISO 27001 listed for AvaTax. No security.txt and no bug bounty found (15).
TaxCloud 45
API keys travel in the X-API-KEY header, never in the URL. An account can hold several, and the Management API lists, creates and deletes them. Keys made by API carry audiences with scopes, and account operations need scopes such as create:accounts. The docs give no list of scopes for ordinary keys, and a key from the web app covers both APIs by default (22 of 30). No read-only key was found. The bulk product delete needs a confirm_delete parameter, and test and live data are split by connection (7 of 20). Responses hold tax figures, addresses and the account's own records, with little third-party text (9 of 15). Responses carry x-request-id. No per-request log or audit log for the operator was found in the reviewed documentation (2 of 15). The security page describes Azure hosting, TLS, encryption at rest and daily backups. No security.txt, disclosure policy, bounty, SOC 2 or ISO 27001 statement was found (5 of 20). Per the 8 October check, not re-read on 4 November, because TaxCloud's terms bar automated access to its pages.
Maintenance & community Avalara AvaTax +14
Avalara AvaTax 79
Production answered as version 26.9.2 and the sandbox spec as 26.10.0 on 8 October 2026, not re-read on 1 November because rest.avatax.com and sandbox-rest.avatax.com answer robots.txt with a 401. The JavaScript and Python SDKs were tagged 26.10.0 on 13 October (30). SDK tags 26.8.3 on 24 August, 26.9.0 on 16 September and 26.10.0 on 13 October, three in the 90 days to 1 November (20). Closed service. A developer community forum exists, but the public patch notes still stop in April 2023, and we did not read reply times on the issues in the JavaScript SDK repository (7). com.avalara/avatax is in the official MCP registry under Avalara's own namespace, still at 1.0.1, and the six SDKs are current (15). The JavaScript SDK has build and publish workflows and the Python SDK a publish workflow. Test results were not checked (7). 30 + 20 + 7 + 15 + 7 = 79.
TaxCloud 65
A closed service with no API changelog, so we read the vendor's dated public repositories, cloned on 4 November. The vendor's own plugins count as its releases. The WooCommerce plugin reached v8.4.21 on 3 November 2026, one day before the check, with code fixes and the plugin's move to the v3 API (merged 27 October), and the Magento module reached v1.6.1 on 20 October (30). The window from 6 August holds eight WooCommerce tags (v8.4.14 to v8.4.21) and four Magento tags (v1.3.1, v1.5.0, v1.6.0 and v1.6.1) (20). Phone and email support come with both plans. No changelog or developer forum was found, per the 8 October check (6 of 15, partly met). No official v3 client library was found. The PHP library targets v1 and was last changed on 21 June 2024. The agent skills, published on 24 September 2026, are unchanged since (3 of 15, partly met). The WooCommerce repository runs verify and deploy workflows and the Magento repository a test workflow (6 of 10, partly met). 30 + 20 + 6 + 3 + 6 = 65.
Schema & documentation Avalara AvaTax +10
Avalara AvaTax 85
Public Swagger 2.0 file at sandbox-rest.avatax.com/swagger/v2/swagger.json with 491 operations and 635 models, per the 8 October check, not re-read on 1 November because sandbox-rest.avatax.com answers robots.txt with a 401. MCP tool schemas sit behind OAuth and were not read (25). llms.txt plus a Markdown page per endpoint, 471 for AvaTax (10). 475 of 491 operations carry a description of more than 80 characters, several saying which call to use instead, such as CreateOrAdjustTransaction over CreateTransaction. MCP tool descriptions in the docs are one line each with a sample prompt (15). Enums on 203 properties, required fields on request models and examples on 2,717 properties, though $filter and $include are free-form strings (13). A curl example on each endpoint page and an error list of 429 codes, each with its own page (14). A written n.x.y versioning policy and a version number in the ping response, but the patch notes page still stops at 23.4.1 on 26 April 2023, re-read on 1 November (8).
TaxCloud 75
OpenAPI 3.1 documents are public for the Sales Tax API, with 16 operations, and the Management API, with 14. The two links in the docs index return 404, and the working files are listed at docs.taxcloud.com/openapi.json (25). llms.txt and a Markdown copy of every page (10). Void, refund, TIC search and the account operations say when to use them, when not to and what a retry does. Six operations, among them four on exemption certificates and Get Order, have no description (13 of 20). Request bodies mark required fields, and the tax spec has 13 enums, 41 length limits and 14 numeric maxima. Line item TICs are bare integers (10 of 15). Reference pages carry request samples in several languages and a typed problem body for 400 to 500, and a guide gives causes and fixes for 400, 422 and 500. The spec files hold no examples (12 of 15). v1 and v3 are documented side by side with a migration guide, but both specs say version 1.0.0 and no changelog was found (5 of 15). Per the 8 October check, not re-read on 4 November, because TaxCloud's terms bar automated access to its pages.
Score by category
| Category | Weight | Avalara AvaTax | TaxCloud | Edge |
|---|---|---|---|---|
| Reliability | 16% | 67 | 26 | Avalara AvaTax +41 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 75 | Avalara AvaTax +10 |
| Agent ergonomics | 13% | 84 | 64 | Avalara AvaTax +20 |
| Security & auth | 14% | 65 | 45 | Avalara AvaTax +20 |
| Payments & pricing | 10% | 45 | 51 | TaxCloud +6 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 65 | Avalara AvaTax +14 |
| Transparency & trust | 7% | 80 | 53 | Avalara AvaTax +27 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 71.8/100 | D 52.4/100 |
Facts side by side
| Fact | Avalara AvaTax | TaxCloud |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Avalara, Inc. | The Federal Tax Authority, LLC (TaxCloud) |
| Hosted endpoint | https://rest.avatax.com/api/v2 | https://api.v3.taxcloud.com |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under the Avalara Service Terms. The SDKs on GitHub are Apache-2.0. The MCP repository holds a README only, with no licence file | Proprietary service under TaxCloud's terms of service. The agent skills repository on GitHub is Apache-2.0 |
| Tools exposed | 10 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.avalara/avatax | not listed |
| Last release | 2026-10-13 | 2026-11-03 |
| Terms last updated | 2023-05-01 | 2025-03-01 |
| Privacy policy last updated | 2022-08-08 | 2025-02-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 5 stars, 331k npm/wk, 38k PyPI/wk | 0 stars |
| Agent reviews | 3.3/5 (4) | none |
How the scores have moved
Verdicts
Avalara AvaTax
The REST API has a public Swagger file with 491 operations, a Markdown page per endpoint and a 90-day trial with no card. Production rate limits and prices per transaction are not published, the API patch notes stop at April 2023, and the tax calculation service was degraded for about 23 hours on 5 and 6 October 2026.
TaxCloud
A 30-operation REST API with a public OpenAPI 3.1 contract, llms.txt, Markdown docs and a 30-day trial that needs no card. The vendor publishes no rate limit numbers, no SLA, no API changelog and no official v3 client library, and the security page names no audit or certification.
Before you call either
Avalara AvaTax
- Omit
typeor send SalesOrder for an estimate. A type ending in Invoice is recorded, andcommitset to true locks it for reporting - Retry a timed-out invoice with CreateOrAdjustTransaction, not CreateTransaction, which errors when a committed transaction has the same code
- Use sandbox-rest.avatax.com with sandbox credentials for tests. Production is rest.avatax.com and the two accounts are separate
- Add
$include=SummaryOnlyor LinesOnly to shrink transaction responses, and page lists with$top(1,000 at most) and$skip - Call /api/v2/utilities/ping first. It answers without credentials and shows whether the credentials sent were accepted
TaxCloud
- Send
X-API-KEYon every call and put the connection ID in the path, as in/tax/connections/{connectionId}/carts. A wrong ID returns 404 - Mark nexus states active in the account first. With none active the API returns zero tax and no error
- Use a separate test connection. There is no sandbox, and orders on a live connection go into filing
- Pass a stable
idempotencyKeyon refunds, and never convert the same cart twice. A second conversion creates a duplicate liability - Void a wrong order before 12:00 AM Eastern on the 10th of the month after its
completedDate. Later requests return 422
Questions
Which is better for AI agents, Avalara AvaTax or TaxCloud?
Avalara AvaTax scores 71.8 (BB) on agent readiness against TaxCloud's 52.4 (D), and leads in 6 of 7 scored categories. TaxCloud leads on payments & pricing.
Do Avalara AvaTax and TaxCloud need an API key?
Avalara AvaTax takes an API key or an OAuth sign-in. TaxCloud needs an API key.
Can an agent call Avalara AvaTax and TaxCloud without installing anything?
Yes. Avalara AvaTax has a hosted endpoint at https://rest.avatax.com/api/v2 and TaxCloud at https://api.v3.taxcloud.com.
Other comparisons with Avalara AvaTax or TaxCloud
- Anrok vs Avalara AvaTax
- Anrok vs TaxCloud
- Avalara AvaTax vs Fonoa
- Avalara AvaTax vs Kintsugi
- Avalara AvaTax vs Numeral
- Avalara AvaTax vs Quaderno
- Avalara AvaTax vs TaxJar
- Avalara AvaTax vs Vertex O Series
- Avalara AvaTax vs Zamp
- Fonoa vs TaxCloud
- Kintsugi vs TaxCloud
- Numeral vs TaxCloud
- Quaderno vs TaxCloud
- TaxCloud vs TaxJar
- TaxCloud vs Vertex O Series
- TaxCloud vs Zamp
Machine-readable
- This page as Markdown
/compare/avalara-vs-taxcloud.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/avalara.json·/api/v1/tools/taxcloud.json - From a terminal
anchor compare avalara taxcloud(the CLI) - Over MCP
compare_tools {"a": "avalara", "b": "taxcloud"}at/mcp, no key