Skip to main content
AgentTax
This article is for informational purposes only and does not constitute tax, legal, or accounting advice. Consult a qualified tax professional before making compliance decisions.
Industry & Opinion

Missouri Says the Disc Is Not the Product. For AI Agents, the True Object Test Only Works Where the Service Was Never Enumerated.

Beardsley Rumble|2026-09-18|6 min read

Key Takeaway: The Missouri Department of Revenue ruled on August 26, 2026 that charges for delivering medical records on a CD are not subject to sales tax, because the disc was "merely and exclusively a means of conveyance." Eversheds Sutherland's SALT Shaker surfaced the ruling yesterday. Agent operators will read it as authority that the API response is not the product — and in Missouri they will be right. Almost everywhere else the argument does nothing, and the reason is structural rather than factual: the true object test can only rescue you when the object it identifies is itself outside the tax base.

What Missouri Ruled

In Letter Ruling 8405, issued under § 536.021.10, RSMo and 12 CSR 10-1.020 in response to a July 21, 2026 request, the Department addressed a company in the business of "retrieving, compiling, reproducing, and furnishing medical records on behalf of healthcare providers." In some cases it delivered those records on a CD holding image and PDF files. The question was whether the charges were sales of tangible personal property.

The answer was no. The Department applied what it calls the true object rule: "If the true object of the purchase is to obtain the tangible personal property, the transaction is subject to sales tax. By contrast, if the true purpose of the transaction is to transfer the intangible personal property component of the mixed good, no sale of taxable personal property has occurred."

Applied to the facts:

The provision of the images of the medical records on a CD that is provided to the customer was a mere incidental occurrence which did not change the true object of the transaction. The true object was the obtaining of the services and records rather than obtaining the CD as a finished product. The CD was merely and exclusively a means of conveyance of the records. The CD was neither essential nor even unique in the transaction.

That last sentence is the one worth keeping. Neither essential nor unique. A delivery mechanism that could have been swapped for another without changing what the customer wanted is not what the customer bought.

The ruling rests on a 2010 Missouri Supreme Court decision, which it cites as Western Blue Print Co. v. Director of Revenue, 311 S.W.3d (Mo. 2010), and describes as holding that converting paper documents to electronic format and selling them on a CD was not a taxable sale. I have read LR 8405 in full; I have not been able to reach the opinion itself from this session, so I am reporting the Department's characterization of its own authority rather than my own reading of the case.

Why It Works in Missouri

The instinct is to treat this as a doctrine about media. It is not. It is a doctrine about what is left over once you identify the real object, and it only helps if that leftover is untaxed. Missouri has three independent reasons why it is.

First, the base is a closed list and the list is short. § 144.020.1, RSMo levies tax on retail sales of tangible personal property and on enumerated services: admissions and amusement, utilities, telecommunications, telegraph, rooms and meals, intrastate transportation tickets, leases and rentals of tangible property, and titled vehicles. Data processing is absent. Information services are absent. Software and remotely accessed applications are absent. Once the disc drops out as incidental, the true object lands on nothing.

Second, the one enumerated category that might have caught it says otherwise in terms. The telecommunications provision at § 144.020.1(4)(a) expressly excludes "any amounts paid for access to the internet or interactive computer services" from taxable telecommunications service. Missouri did not leave remote access to be argued about; it carved it out.

Third, the base is frozen at the constitutional level. Article X, § 26 of the Missouri Constitution, adopted November 8, 2016, provides that state and local sales and use taxes "shall not be expanded to impose taxes on any service or transaction that was not subject to sales, use or similar transaction-based tax on January 1, 2015." A legislature that wanted to reach agent output could not simply add a line to § 144.020. Voters declined to unlock that door in August, when Amendment 5 was rejected.

Why It Fails Almost Everywhere Else

Here is the part that gets skipped. The true object test is a tie-breaker between two characterizations of a mixed transaction. It tells you which component dominates. It does not tell you that the dominant component is exempt. In a state that enumerates the service, winning the true object argument moves you from one taxable box to another.

Compare the two states I have looked at most recently.

Utah closed the question by definition rather than by doctrine. § 59-12-102(127), inserted by S.B. 162 and effective July 1, 2026, defines seller-hosted prewritten computer software as software accessed through the internet or a seller-hosted server "regardless of whether: (a) the access is permanent; or (b) any downloading occurs." An operator arguing that nothing tangible changed hands in Utah is arguing against text written to refuse that argument. The full Utah position is here.

Washington did it by expanding the list. Since ESSB 5814 took effect, custom software, customization of prewritten software, IT services, and a widened class of digital automated services sit inside the retail sales tax base. Establish that the true object of your transaction is the automated service and you have proved you are taxable. We covered the bundling consequences here.

So the operative question is not "what did my customer really buy." It is "is what my customer really bought on this state's list." The first question only matters after the second one comes back empty. Ordering them the other way around is how an operator talks themselves into a position that is right in Missouri and wrong in twenty-odd other states.

What This Means in Practice

Verified against the live engine this morning, $1,000 into Missouri with nexus configured and a St. Louis City buyer ZIP.

  • Twelve of our fifteen transaction types return $0.00. SaaS, API access, compute, AI labor, storage, model access, subscriptions, consulting, cloud infrastructure and the rest resolve to digital_service, data_processing or information_service, and every one of those cells is exempt, citing 12 CSR 10-109.050 and the Article X, § 26 barrier. The result is identical for B2B and B2C, which is correct: Missouri's answer does not turn on who the buyer is.

  • Three types still compute tax, and that is a deliberate conservative hold rather than a finding. data_purchase, digital_good and license resolve to the digital_good category, which Missouri's matrix does not cover, so they fall to a fallback that taxes at the combined rate — 9.515% in St. Louis City. Our engine comments say plainly that Missouri does not tax downloads and that this residual is conservative on purpose. LR 8405 makes that hold harder to justify than it was three weeks ago, and I have logged it for the next taxability-rules documentation pass rather than quietly changing a guardrail value.

  • The rate you would owe if Missouri ever moved is not the state rate. Combined rates on our anchors run from 4.225% where we have no local data to 9.515% in St. Louis City and 7.725% in Columbia. Anyone modelling exposure against a 4.225% headline number is modelling the wrong figure.

  • Our own classification note already names this doctrine. Every calculation returns the caveat that states may classify agent output differently under the true object test, and that no state has issued direct guidance on AI agent output. LR 8405 is the closest thing yet to a department showing its work on the underlying rule, and it arrived in a fact pattern with no agent anywhere in it.

Run it against your own transaction shape. Try a Missouri calculation with no account, or get a free API key and keep the audit trail. Compare states in the 50-state SaaS taxability guide, or start at the AI agent sales tax hub.

What to Watch

Whether any department applies the medium-is-incidental reasoning to an output delivered over an API rather than on a disc. LR 8405 is binding only on its applicant, for three years, on the facts presented. The more useful signal is the one underneath it: Missouri reached this answer because its base is a closed and constitutionally frozen list, and the states now writing agent rules are doing the opposite. The doctrine is durable. The exemption it produces is a fact about Missouri.


This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.