Kentucky HB 757: Data Brokering Tax and a New Nexus Rule That Every AI Agent Operator Should Read

Kentucky enacted House Bill 757 on April 14, 2026. It is an omnibus revenue bill, and most of the coverage has focused on fantasy contest excise taxes and premium cigar rates. For AI agent operators, two provisions buried in the same bill matter more than the headline items: a new sales tax on "data brokering services" effective August 1, 2026, and the elimination of Kentucky's 200-transaction economic nexus threshold as of the same date.

Neither provision is framed as an AI law. Both of them affect AI agent operators directly.

What HB 757 Actually Does

HB 757 amends KRS 139.010 to define "data brokering services" as a newly enumerated category and amends KRS 139.200 to impose Kentucky's 6 percent sales and use tax on those services. The Senate Committee Substitute narrowed the definition before passage by removing language that would have captured "the use of data by a third party," limiting the statute to the brokering act itself rather than downstream use.

The bill also rewrites Kentucky's economic nexus test. Under current law, a remote seller establishes nexus by either exceeding \$100,000 in Kentucky sales or completing 200 or more separate transactions into the state. HB 757 removes the 200-transaction prong. Starting August 1, 2026, only the \$100,000 sales threshold applies.

Both changes take effect August 1, 2026. Kentucky joins Illinois, which made a similar nexus change effective January 1, 2026, in a small but growing group of states that have concluded the transaction-count threshold captures too many small sellers.

Why the Data Brokering Tax Matters for AI Agents

Most AI agent transactions in Kentucky were already taxable. Kentucky pulled SaaS and remotely accessed software into its tax base effective January 1, 2023, under HB 8, and the state's definition of "prewritten computer software access services" at KRS 139.200(2)(k) is broad enough to capture most agent-as-a-service offerings. An AI agent that processes compute jobs, generates research reports, or drafts content through a hosted platform has been taxable in Kentucky for three years.

What HB 757 does is open a second path to taxation for a specific category of agent. Many AI agents are, in effect, data brokers. They aggregate data from multiple sources, clean it, enrich it, and sell or license the enriched output to another agent or to a human buyer. That workflow does not always require a software-access subscription; the deliverable is sometimes a one-time data file, an API call, or a pass-through lookup.

Before HB 757, if the agent delivered data without giving the buyer access to the underlying platform, there was a reasonable argument that the transaction was a nontaxable information service rather than taxable prewritten software access. The new data brokering statute closes that argument for Kentucky customers. The tax follows the sale of the data itself.

The narrowed definition matters. Because the Senate Committee Substitute removed downstream use from the scope, a Kentucky retailer who licenses third-party data and uses it internally is not brokering within the meaning of the statute. The tax applies when the data itself is the product being sold.

What the Nexus Change Means

The transaction-count threshold has always been the more punitive prong for low-ticket, high-volume sellers. An AI agent that processes thousands of small API calls into Kentucky at \$0.01 per call can easily clear 200 transactions while generating less than \$20 in revenue. Under the current rule, that seller has full Kentucky collection obligations. Under HB 757, that seller does not, unless or until Kentucky sales reach \$100,000 in a calendar year.

This is a meaningful simplification for AI agents with large-volume, low-value workloads. x402 agent transactions, per-call metered APIs, and agent-to-agent microtransactions all benefit. If an operator was registered in Kentucky solely because of the 200-transaction prong, HB 757 creates grounds to deregister after August 1, assuming sales are below \$100,000.

The flip side is that an operator who was relying on the 200-transaction prong to trigger nexus for other sellers in a marketplace scenario may need to reassess. Marketplace facilitator rules still apply, but the threshold that triggers the facilitator's own obligations has moved.

Practical Impact for AI Agent Operators

If you operate an AI agent that sells to Kentucky buyers, three actions are worth taking before August 1.

First, review whether your output fits the "data brokering" definition. If you sell aggregated, enriched, or standalone data, assume Kentucky's 6 percent sales tax will apply to that transaction beginning August 1, 2026, even if you have historically treated it as a nontaxable information service.

Second, reassess your Kentucky nexus position. If you registered solely because of the transaction count, calculate your Kentucky sales for the past twelve months. If they are under \$100,000 and likely to stay there, you have a path to deregister after August 1.

Third, update your collection logic. The data brokering provision is a new tax category. If your tax engine is configured to treat Kentucky SaaS as the only taxable digital event, you may undercollect on standalone data sales starting August 1.

AgentTax users should note that the engine's Kentucky treatment (6 percent on digital services) already captures the SaaS-delivered case. The data brokering expansion will flow through our next engine update once the Kentucky Department of Revenue publishes implementation guidance clarifying the scope of the narrowed definition.

What to Watch Next

Kentucky has historically issued DOR guidance and administrative regulations in the quarter following a tax expansion. Expect a revenue circular, a Taxpayer Advisory, or an amendment to 103 KAR 28 addressing the data brokering scope before August. The key interpretive question is whether "data brokering" requires a third-party seller-to-buyer relationship in the traditional sense, or whether it captures any sale of data as a standalone product. The narrower reading leaves most AI agent sellers alone; the broader reading sweeps in a large share of agent-to-agent data commerce.

The nexus change is less ambiguous and less likely to move. Illinois made the same change without meaningful controversy, and Kentucky's removal of the transaction prong is the cleaner of the two provisions.

Kentucky is not an AI-focused jurisdiction, and HB 757 is not an AI-focused bill. But for operators selling data products or operating high-volume low-value agent workflows into the state, it is the most consequential tax law change of the quarter.

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

AgentTax calculates sales tax, use tax, and economic nexus exposure for AI agent transactions across all 51 US jurisdictions. Check Kentucky and 50 other jurisdictions or read our 50-state SaaS taxability guide for the full picture.