Vermont Taxes Seller-Hosted Software 'However Accessed' — What That Means for AI Agents

Vermont is one of the cleanest states in the country for answering a question AI agent operators keep hoping to answer differently: is remote access to my software a taxable sale? Since July 1, 2024, Vermont's answer has been yes, by statute, with language broad enough that the usual counterarguments do not survive contact with it. We have not profiled Vermont before. Given how often the state's framing settles a debate that is still live elsewhere, it is worth a close read.

The Statute Vermont Actually Wrote

Vermont taxes tangible personal property at a 6 percent state rate, with a 1 percent local option tax in a number of municipalities, for a combined rate up to 7 percent. The relevant move happened in 2024. Act 183 (H.887), enacted over Governor Scott's veto, repealed Vermont's prior exemption for remotely accessed software — the carve-out that had lived in the 2015 session law since the state first grappled with cloud computing.

The operative language is what matters for the agent economy. Vermont's definition of tangible personal property now includes prewritten computer software "regardless of the method in which the prewritten computer software is paid for, delivered, or accessed." That is the whole game in one clause. Delivered on media, downloaded, or accessed remotely over the internet — Vermont treats all three the same. The sales and use tax provisions sit in 32 V.S.A. Chapter 233, and the taxable-property definition flows from the definitions in 32 V.S.A. § 9701.

Custom software written to a specific purchaser's specifications remains outside the base when delivered electronically. That distinction — prewritten versus custom — is the line that still does real work in Vermont. Almost nothing an AI agent operator sells at scale falls on the custom side of it.

Why "However Accessed" Is the Clause That Binds

Most state software-taxability fights turn on a single argument that operators make in slightly different dialects: we are not transferring software to the customer; we are providing a service the customer accesses. In states whose statutes were written around "delivered electronically" or "load and leave," that argument has room to breathe, because remote access is arguably neither delivery nor a load-and-leave installation.

Vermont closed that room. The phrase "regardless of the method in which the prewritten computer software is paid for, delivered, or accessed" is a direct answer to the access-is-a-service theory. It does not matter that nothing lands on the customer's machine. It does not matter that the agent runs entirely on the seller's infrastructure and the customer never touches the binary. If what the customer is paying for is prewritten software functionality, Vermont taxes the transaction.

For AI agent products, that maps almost perfectly onto the dominant architecture. A hosted agent — an API-accessible research assistant, a compute service, a retrieval-augmented pipeline, an agentic workflow a customer calls over the wire — is prewritten software the customer pays to access without any transfer. That is exactly the fact pattern Vermont's clause was written to capture.

Where the Agent Angle Gets Specific

The harder questions in Vermont are not about whether hosted software is taxable. They are about characterization at the margins.

An agent product that is genuinely a data-processing or information service — where the customer pays for a result, not for access to the software that produced it — can present a closer call. Vermont, like most states, will look at the true object of the transaction. But operators should be realistic about how that analysis usually comes out. When the customer is paying a recurring subscription for standing access to a software capability, the "true object" is the software, and the information-service framing tends to lose. The service wrapper has to be more than a billing label.

Bundling is the other live issue. If an agent subscription combines taxable hosted-software access with a genuinely non-taxable component, Vermont's treatment turns on whether the components are separately stated and separately valued. A single undifferentiated subscription fee for a bundle that includes taxable software is exposed to tax on the whole. This is not a Vermont peculiarity — it is the general rule in most states — but Vermont's broad software definition means the taxable component is more likely to be present than operators assume.

Economic Nexus: The Threshold Has Not Moved

Vermont's remote-seller economic nexus threshold is unchanged: $100,000 in sales into Vermont or 200 or more separate transactions in the preceding 12-month period, measured on a rolling basis, with the "or" doing real work. Marketplace sales count toward the threshold. Once you cross either line, the collection obligation begins.

The recharacterization risk is the same one we flagged for Utah. An agent operator that treated its Vermont access fees as non-taxable services may also have been leaving that revenue out of its nexus math. Because Vermont's software definition is broad and its threshold counts all sales, an operator sitting at $80,000 of Vermont API revenue it thought was untaxed service revenue may in fact be closer to the line than it modeled — and the 200-transaction count usually binds first for high-volume, low-ticket agent products. Two hundred Vermont calls is a low bar for anything with real usage.

What Operators With Vermont Exposure Should Do

Three concrete steps, in order.

First, pull your Vermont-billed or Vermont-shipped transaction history for the trailing twelve months and check it against both nexus thresholds. If you are over either and unregistered, register. Vermont measures the lookback window, not just the period after you notice.

Second, audit how your billing system classifies hosted-agent access to Vermont customers. If that line item maps to a non-taxable "service" SKU, that mapping is the exposure. Hosted prewritten software access to a Vermont buyer belongs in a taxable category at the 6 percent state rate plus any local option tax.

Third, write down the characterization decision for anything you treat as a non-taxable service or a separately stated non-taxable bundle component. Vermont's broad statute means the default answer for hosted software is "taxable," and a departure from the default is exactly what an auditor will ask you to justify. The defensible version of that justification is one you documented before the question was asked.

The Pattern Vermont Fits Into

Vermont is another data point in a convergence we have tracked across states all year. Washington's ESSB 5814, Utah's statutory cleanup on seller-hosted software, New York's reaffirmation in Matter of Beeline.com that web-based access to prewritten software is taxable regardless of a service wrapper, and Kentucky's administrative position that an AI component does not change software's prewritten character — all point the same direction. The language legislatures wrote for an earlier era of software distribution did not naturally reach remote access, and states are closing that gap, each in its own idiom. Vermont's idiom just happens to be unusually blunt: "regardless of the method in which the prewritten computer software is paid for, delivered, or accessed."

For agent operators, the takeaway is operational, not doctrinal. In a growing majority of states, hosted software access to a customer is taxable in some configuration, and the compliance question is no longer "is this taxable" but "does my system compute the right answer for this state, at this rate, at the moment of sale, without anyone having to think about it." That is a routing problem. Our AI agent sales tax state-by-state overview tracks the rule that applies to API-style access in every jurisdiction, Vermont included.

See how AgentTax routes per-state software taxability so the Vermont answer — and the other forty-something — is computed for you.

This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.