The Federal Shield Against State Income Tax Was Written for Order-Takers

Agent operators spend real effort on state sales tax and almost none on state income tax, on the intuition that a company with no offices or employees outside its home state cannot owe income tax anywhere else. That intuition rests, knowingly or not, on one federal statute from 1959. Read it against an agent operator's facts and it fails twice — once for what you sell, and once for what your agent does.

What the Statute Actually Says

Public Law 86-272 is codified at 15 U.S.C. § 381. Its operative sentence, as in effect this month, is this:

No State ... shall have power to impose ... a net income tax on the income derived within such State by any person from interstate commerce if the only business activities within such State by or on behalf of such person during such taxable year are ... (1) the solicitation of orders by such person, or his representative, in such State for sales of tangible personal property, which orders are sent outside the State for approval or rejection, and, if approved, are filled by shipment or delivery from a point outside the State ...

Three limits are packed into that sentence and each is load-bearing. The protection covers only a net income tax, so it says nothing about sales tax or gross receipts taxes. It covers only tangible personal property. And it covers only solicitation of orders approved and filled from outside the state.

The First Failure: You Do Not Sell Goods

The Multistate Tax Commission's Statement of Information on P.L. 86-272 — the model interpretation most state revenue departments work from, last revised August 4, 2021 — opens on exactly this point:

Only the solicitation to sell tangible personal property is afforded immunity under P.L. 86-272; therefore, the leasing, renting, licensing or other disposition of tangible personal property, or transactions involving intangible property ... or any other type of property are not protected activities under P.L. 86-272.

The next paragraph adds that any service not entirely ancillary to soliciting orders for goods is likewise unprotected.

An operator selling inference, API access, agent runs, or a subscription is outside the statute at the first sentence. There is no reading in which a pure services or software business arrives on the protected side, because it never sold tangible personal property. The federal shield is not narrow for you. It is absent.

The opposite over-reading is just as wrong: it does not follow that you owe income tax in forty states. It follows that P.L. 86-272 is not the reason you don't. Whether a state can reach your net income turns on that state's own income-tax nexus rules and the constitutional limits on them — a different and considerably less generous inquiry than the one most operators believe they are running.

The Second Failure: The Agent Is the Disqualifying Activity

The second failure belongs to a different company: one that does sell goods across state lines, has relied on P.L. 86-272 for years, and has just shipped an AI agent onto its storefront. The 2021 revision added a section on activities conducted via the internet. Its general rule is one sentence: "when a business interacts with a customer via the business's website or app, the business engages in a business activity within the customer's state." Static text and photos are carved out. Then come eleven worked examples, four of which describe things an agent does by design.

• Regular post-sale assistance by chat or email, initiated by a customer clicking an icon, defeats immunity — the example is a business that "regularly advises customers on how to use products after they have been delivered." That is a support agent, described before anyone called it one.

• Cookies gathering customer search information used to adjust production schedules and inventory or develop new products defeat immunity. That is telemetry feeding a recommendation model.

• Remotely fixing or upgrading previously purchased products by transmitting code over the internet defeats immunity. That is an agent pushing an update.

• Streaming video or music for a charge defeats immunity, because streaming is not a sale of tangible personal property.

Two examples stay protected, and the contrast is the whole lesson. Cookies are fine if they do nothing but remember a cart, store details the customer already gave, and recall previously viewed items — they must "perform no other function." And the protected baseline is a site that lets customers "search for items, read product descriptions, select items for purchase, choose among delivery options, and pay."

That baseline describes a vending machine. The unprotected example describes a conversation. An agent is a conversation by construction, and every design decision that makes it more useful moves it further across the line.

One caution about weight. The Statement is a recommendation, not law; states have adopted, adapted, or ignored it individually, and where they adopted it, taxpayers have litigated. One state's guidance was voided on administrative-procedure grounds; another state's regulation survived an appeal this year. I could not obtain either decision while writing this, so I name neither — and neither belongs in your file as authority until you or your counsel have read it.

Why This Gets Missed: Two Nexus Questions, One Word

Most operators run one nexus analysis — the post-Wayfair economic thresholds, typically $100,000 in receipts or 200 transactions. That answers a sales tax question and only a sales tax question. Income tax nexus is a separate track with its own state tests, its own factor-presence standards, and its own federal overlay, which is the statute above. Clearing or failing the sales-tax threshold tells you nothing about the income-tax answer; the two questions share a word and little else.

Our position on the sales-tax side is that the effect of agent activity on economic nexus is unresolved: no state has issued guidance addressed to autonomous agent commerce, and whether agent-initiated transactions count toward a threshold at all is an open question rather than one we are simplifying. The income-tax side is thinner still. See the Streamlined Sales Tax Project's registration guidance for where sales-tax registration begins, and our economic nexus explainer for how thresholds are measured.

What Our Engine Does and Does Not Tell You

Reciprocity obliges a scope statement. Take a $1,000 business-to-business compute charge billed to a Massachusetts buyer, no nexus configured. The engine returns $0.00, with an advisory saying in as many words that the zero is a default and not a determination — not a finding that nothing is owed in Massachusetts — and reporting the $62.50 owed once nexus is set. Configure nexus and it computes that $62.50 at 6.25%, with our conservative Massachusetts data-processing position disclosed. The same charge to a New York buyer computes $40.00 at the 4% state rate; to a California buyer, $0.00 today, because California's software expansion does not take effect until January 1, 2027.

Every one of those figures is a transaction tax. None is an income tax number, and nothing in those responses speaks to whether Massachusetts may tax your net income. That is a scope boundary rather than a gap we are about to close. If one sentence survives this post, make it that our zero and your income-tax exposure are unrelated facts.

What Operators Should Do

• Put state income tax on the calendar as its own line item. It is not a corollary of the sales-tax work and it will not fall out of it.

• Stop treating "no employees there" as the answer. Physical presence stopped being the sales-tax boundary in 2018, and income-tax factor-presence standards got there earlier.

• Inventory what your agent does in each customer's state — chat, code delivery, telemetry — and, for telemetry, why. Purpose is what separates the protected cookie example from the unprotected one.

• If you sell goods and recently added an agent, re-run the analysis. The agent may have changed an answer that was correct the day before you shipped it.

• Do not treat the MTC Statement as law, in whichever direction happens to help you.

What to Watch

Watch Congress: bills have been introduced to redefine "solicitation of orders" far more broadly, which would restore protection to goods sellers and still not reach a services business. Watch for the first state adoption of the internet-activities section tested on an autonomous agent rather than a 2021-vintage chat widget — that is the case that will matter here, and I know of none yet. And watch whether the MTC revisits those eleven examples, all of which assume a human clicking an icon.

For where agent activity sits in each state's transaction tax base, see our AI agent sales tax guide; for how the figures above are derived, see our tax methodology.

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.