Head to head · Tax calculation · October 2026 research run
TaxJar vs Vertex O Series
TaxJar scores 57.8 (C) on agent readiness against Vertex O Series's 51.1 (D), and leads in 5 of 7 scored categories. Vertex O Series 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
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 60
- Agent ergonomics, 61 against 51
- Payments & pricing, 45 against 0
- Maintenance & community, 44 against 32
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
Best for An agent working inside a company that already has an O Series licence, for quotes, invoice tax, tax area lookups and tax configuration across sales tax, use tax and VAT.
Ahead on
- Schema & documentation, 74 against 48
- Security & auth, 57 against 43
Watch for
No public price, free tier or self-serve signup. The security guide sends new users to the Vertex sales team for an account
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.
Payments & pricing TaxJar +45
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.
Vertex O Series 0
Read with the hosted rubric. No x402, MPP or L402 in the developer docs or the specs (0). No public price. www.vertexinc.com/pricing returns 404 and the product page asks visitors to book a demo (0). No free tier or trial was found (0). The security guide says to work with the Vertex sales team to establish an account, and an administrator then creates the API credential in the web interface (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
Schema & documentation Vertex O Series +26
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.
Vertex O Series 74
OpenAPI 3.0 specs for four O Series APIs download without a login from the API reference. Calculation and Tax GIS is still 2.9.0 on 4 November, with 14 operations, 168 schemas and 200, 400, 401, 403 and 500 responses, Tax Configuration v2.1.0 with 29 operations (25). developer.vertexinc.com/llms.txt still returns 404 on 4 November and the llms.txt on www.vertexinc.com is a list of marketing pages, but each guide is served as Markdown at its URL plus .md (5 of 10). The sale operation explains Quotation, Invoice and Distribute Tax and which are stored, and the calculation spec carries 872 descriptions. None says when not to call an operation (14 of 20). 36 enums and string length limits, though transactionType is the only required field among 54 on a sale request (10 of 15). Guides carry sample requests and responses. The calculation spec has 2 examples, and errors are four generic statuses with no catalogue of error codes (8 of 15). The path carries v2 and specs carry versions. Release notes are grouped by service release (SR19 to SR24) without dates (12 of 15).
Reliability TaxJar +24
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.
Vertex O Series 60
Read with the hosted rubric. The graded surface is the O Series Cloud REST v2 API. Statuspage at status.vertexinc.com with 26 components, Vertex Indirect Tax O Series Cloud among them with Calc and Portal under it, read on 4 November from the server-rendered history pages (20). From 6 August to 4 November the history lists 11 incidents besides maintenance, and none names O Series Cloud. The nearest is a 29 September performance degradation for some customers in the cloud returns and configurations areas (18:13 to 21:00 UTC). The only one Vertex marked major, VAT Compliance on 28 August, lasted 27 minutes, and the rest hit Certificate Centre, Smart Categorization, ECW, the eComm Business ID Validator or the BigCommerce connector. Minor only for the product (20). The token endpoint is limited to 10 requests per 8 hours and the Certificate Centre API to 1,000 requests a minute. No limit for the calculation API was found (7 of 15, a partial kept). Certificate Centre documents 429 and the O Series guide says to retry a 500 later. No Retry-After, backoff guidance or idempotency key was found (3 of 15, a partial kept). The trust centre lists a Service Level Exhibit behind an access request that nobody could read, which gives 0 in this run (0). REST v2 is generally available (10). 20 + 20 + 7 + 3 + 0 + 10 = 60.
Security & auth Vertex O Series +14
TaxJar 43
One API token per use, generated in the web app and sent in the Authorization header, never in the URL. It has no scopes and covers every endpoint. The docs mention generating a new token, but we found no statement on how many tokens an account can hold or how one is revoked, so we scored between a single all-powerful key and plain revocable keys (15 of 30). No read-only token and no confirmation step on deleting transactions or customers. The sandbox takes a separate token, and user roles exist for web app logins on Professional (4 of 20). Responses carry tax figures, jurisdiction names and the account's own stored customer and order data, with little third-party text (9 of 15). Plans & Billing shows transaction counts, and no per-request API log was found in the reviewed documentation (3 of 15). SOC 2 Type 2 per the security page, with yearly re-audits announced in March 2021, annual penetration testing and AES-256 at rest. On 4 November www.taxjar.com/.well-known/security.txt still answered 404 and the security page names no disclosure route. Stripe's own security.txt leads to its HackerOne programme (per the 8 October check), but no page read says taxjar.com is in scope (12 of 20). 15 + 4 + 9 + 3 + 12 = 43.
Vertex O Series 57
OAuth 2.0 client credentials. A Cloud credential maps to one API and one partition, the secret is shown once, and access tokens last 3,599 seconds. Token requests with credentials in the URL are rejected. The configuration spec names view and edit scopes, but the Cloud token returns scope profile, which the docs call informational, so we scored between plain revocable keys and scoped ones (22 of 30). On-Premise and On-Demand let an admin build a role with a subset of the API User role and set credential expiry in days. No read-only Cloud credential or confirmation for deletes was found (10 of 20). Responses are structured tax results and configuration records (10 of 15). No audit log of API calls was found. A request can ask for support-level log entries in its own response (2 of 15). The trust centre lists 2025 SOC 1 Type II and SOC 2 Type II reports from Forvis Mazars, annual third-party penetration testing, and on 26 October 2026 announced ISO/IEC 27001:2022 certification. It posts security announcements (a 21 October note on PHP2Shell found no affected technology). security.txt still returns 404, and no bug bounty or disclosure policy was found. The 13 is kept as a partial (13 of 20).
Maintenance & community TaxJar +12
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.
Vertex O Series 32
Vendor dated sources read on 4 November. The O Series release notes carry no dates. Their page was last modified on 25 September 2026 and its newest section is SR24, which moves the calculation spec to 2.9.0, and the calculation spec file itself was last modified on 10 September. Both dates put the newest O Series API change between 31 and 90 days back (20). No three dated O Series entries fall in the 90 days from 6 August (0). The e-Invoicing API's dated notes (21 and 28 August, 1, 4, 10 and 16 September, 9 and 30 October 2026) belong to a separate Vertex product with its own API, docs section and status component, so they aren't counted here, as wasabi-hot-cloud-storage's Cloud NAS notice wasn't counted for its S3 API. Certificate Centre is also a separate API, and its September 2026 release is dated by month only. Closed service with public release notes and support through Vertex Community, which needs a login we don't have (9 of 15). No official SDK or MCP server was found. The only public repository under github.com/vertexinc is a Magento connector last pushed in April 2021, per the 8 October check (0). Specs are synced to the docs site from a source repository per the page metadata, with no public CI to read (3 of 10). 20 + 0 + 9 + 0 + 3 = 32.
Agent ergonomics TaxJar +10
TaxJar 61
Responses are small JSON objects and list calls return IDs only, but there is no field selection and summary_rates returns every region at once (12 of 25). Order and refund lists filter by transaction_date, a date range and provider. No pagination or page size is documented, and the customer list takes no parameters (8 of 20). Errors are JSON with error, detail and status in the reference's examples, and five codes have documented causes and fixes (15 of 20). Calculations have no side effects beyond metering. Orders, refunds and customers use caller-chosen IDs, so a repeated create returns 422 and can be turned into a PUT. No idempotency header exists (13 of 20). A calculation needs to_country, to_zip, to_state and shipping, with nexus read from the account, and official clients cover seven languages, though the Ruby gem dates from August 2022 and the Java and Go repositories were last changed in March 2022 and October 2023 (13 of 15). 12 + 8 + 15 + 13 + 13 = 61.
Vertex O Series 51
Calculation responses can't be trimmed by field. Three indicator flags switch optional blocks on, and configuration lists default to 20 items (12 of 25). Configuration lists take OData $skip, $top (maximum 500) and $filter, and Certificate Centre documents filtering and sorting. Calculation calls return one transaction (16 of 20). Errors carry code, message and target, but the guide lists only 400, 401, 403 and 500 with general advice (10 of 20). No idempotency key. An agent can check whether a transaction exists, then delete, reverse or roll it back, and the docs warn of duplicate transactions outside a 90-day window on Cloud (6 of 20). One required field on a calculation request. No official SDK was found, and the guides show cURL and C# samples (7 of 15).
Score by category
| Category | Weight | TaxJar | Vertex O Series | Edge |
|---|---|---|---|---|
| Reliability | 16% | 84 | 60 | TaxJar +24 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 48 | 74 | Vertex O Series +26 |
| Agent ergonomics | 13% | 61 | 51 | TaxJar +10 |
| Security & auth | 14% | 43 | 57 | Vertex O Series +14 |
| Payments & pricing | 10% | 45 | 0 | TaxJar +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 44 | 32 | TaxJar +12 |
| Transparency & trust | 7% | 72 | 69 | TaxJar +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 57.8/100 | D 51.1/100 |
Facts side by side
| Fact | TaxJar | Vertex O Series |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | TaxJar (Stripe) | Vertex, Inc. |
| Hosted endpoint | https://api.taxjar.com/v2 | https://calcconnect.vertexsmb.com/vertex-ws/v2 |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under TaxJar's terms of service and API licence agreement. The official API clients on GitHub are MIT | Proprietary service under a customer agreement with Vertex, Inc. that isn't published |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-09-02 | 2026-09-25 |
| Terms last updated | 2026-05-14 | no date given |
| Privacy policy last updated | 2022-01-07 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 57 stars, 95k npm/wk, 50k PyPI/wk | none |
How the scores have moved
Verdicts
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.
Vertex O Series
Public OpenAPI 3.0 specs cover calculation, transaction management, tax area lookup and tax configuration, and guides are served as Markdown. Access needs a sales contract. No price, free tier, sandbox signup, calculation rate limit, idempotency key or official SDK was found in the reviewed documentation.
Before you call either
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
Vertex O Series
- Cache the access token for its 3,599-second life. The standard token endpoint allows 10 requests per 8 hours, and tokenguard.vertexcloud.com returns a cached token
- Send no
Authorization: Bearerheader to /oauth/token, and put the client id and secret in the body or a Basic header. Credentials in the URL are rejected - Set
saleMessageTypeto QUOTATION for an estimate. INVOICE is stored for reporting and remittance - Call GET /v2/transaction-exists/{transactionid} before retrying a failed INVOICE. No idempotency key is documented
- Delete, reverse or roll back a Cloud transaction within 90 days of calculation. Later requests can cause calculation errors or duplicates
Questions
Which is better for AI agents, TaxJar or Vertex O Series?
TaxJar scores 57.8 (C) on agent readiness against Vertex O Series's 51.1 (D), and leads in 5 of 7 scored categories. Vertex O Series leads on schema & documentation and security & auth.
Do TaxJar and Vertex O Series need an API key?
TaxJar needs an API key. Vertex O Series uses an OAuth sign-in.
Can an agent call TaxJar and Vertex O Series without installing anything?
Yes. TaxJar has a hosted endpoint at https://api.taxjar.com/v2 and Vertex O Series at https://calcconnect.vertexsmb.com/vertex-ws/v2.
Other comparisons with TaxJar or Vertex O Series
- Anrok vs TaxJar
- Anrok vs Vertex O Series
- Avalara AvaTax vs TaxJar
- Avalara AvaTax vs Vertex O Series
- Fonoa vs TaxJar
- Fonoa vs Vertex O Series
- Kintsugi vs TaxJar
- Kintsugi vs Vertex O Series
- Numeral vs TaxJar
- Numeral vs Vertex O Series
- Quaderno vs TaxJar
- Quaderno vs Vertex O Series
- TaxCloud vs TaxJar
- TaxCloud vs Vertex O Series
- TaxJar vs Zamp
- Vertex O Series vs Zamp
Machine-readable
- This page as Markdown
/compare/taxjar-vs-vertex-tax.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/taxjar.json·/api/v1/tools/vertex-tax.json - From a terminal
anchor compare taxjar vertex-tax(the CLI) - Over MCP
compare_tools {"a": "taxjar", "b": "vertex-tax"}at/mcp, no key