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.

Policy

Digital Services Taxes Reach a Record — and Start Billing Downstream to AI Agent Operators

Beardsley Rumble|2026-07-26|7 min read

On July 23, 2026, the Computer and Communications Industry Association reported that digital services taxes in five European markets collected roughly $3.6 billion in 2025 — a record, and about 20 percent above 2024. Three weeks earlier, on July 1, Meta began charging advertisers explicit "location fees" of 2 to 5 percent depending on where the ad is served, at rates tracking the local DST line for line. The totals are not the interesting part. What matters is that a tax nominally imposed on very large platforms has started arriving, itemized, on the invoices of businesses far below the threshold — and that no one has answered which limb of a DST catches an agent business, or who the "user" is when the party across the interface is an autonomous agent.

What the report says, and what it does not

The CCIA's 2026 Status of Key Digital Services Taxes is trade advocacy and should be read as such, but the figures hold up: the UK's 2 percent DST leads at $1.25 billion in 2025 and $4.34 billion since 2021, followed by France at $875 million, Italy at $720 million, Spain at $463 million, and Austria at $155 million.

What the report does not mention is artificial intelligence — not an oversight, but a reflection of the statutes. On the Tax Foundation's European DST tracker, no enacted regime names AI services as a taxable category. Every DST in force runs through some combination of three limbs: online advertising, digital interfaces or intermediation, and the transmission of user data.

The pass-through arrived on July 1

Meta's location fees are the development to put in a cost model. From July 1, 2026, advertising delivered to audiences in Austria carries a 5 percent fee, France 3 percent, Italy 3 percent, Spain 3 percent, Türkiye 5 percent, and the UK 2 percent — the statutory DST rate in each. The fee attaches based on where the ad is served rather than where the advertiser sits, and Meta's budget optimization does not net it out, so invoiced totals can exceed the budget you set. Google, Amazon, and Apple began passing DSTs through in late 2020; Meta absorbed them for roughly six years and has now stopped.

This is the architecture we described in Virginia's data center electricity tax last week, moved to the international layer: a levy on someone else that reaches you as price. One difference favors you — Meta's fee is itemized, jurisdiction-tagged, and rate-matched rather than buried in vendor pricing. It is also not tax, and no sales tax engine will treat it as such. It is a contractual fee measured by a tax.

Which limb catches an agent business

A pure inference API — per token or per call for model output — does not map obviously onto any enacted limb, which is why the question has drawn so little attention in agent tooling. The exposure sits one layer up, in intermediation. The UK's statutory test for an "online marketplace" has two prongs in HMRC's manual: the service enables users to sell things to other users, or to advertise or offer them for sale; and a main purpose of the service is to facilitate those sales. HMRC is explicit that it makes no difference whether the transactions are B2C, B2B, or C2C. Now hold an agent-economy artifact against that test — a paid tool registry that takes a cut, an x402-gated directory of callable agent services, an agent-to-agent hub where one operator's agent contracts with another's. France's DST reaches "digital interface" revenue on similar logic, and the Belgian proposal expressly names digital intermediation including online marketplaces.

I am not going to tell you those venues are in scope; applying these definitions to machine-mediated B2B intermediation has not been tested by any authority I can cite, and this is analysis, not a conclusion. But it is the question domestic marketplace facilitator laws put to agent platforms — does facilitating plus collecting make you the party on the hook — arriving as a gross-receipts tax rather than a collection duty. My comfort on the domestic version sits at more likely than not for platforms that both facilitate the listing and process the payment. The DST analogue deserves the same seriousness and has received far less.

Who is the user?

DST is computed on revenue attributable to users in the taxing jurisdiction, which makes the identity and location of the user the whole ballgame. HMRC's manual is broad on who qualifies: a user is anyone that uses the digital service activity — individuals, legal persons, and other arrangements — excluding the provider and its own group. For marketplaces, revenue is UK-attributable where the transaction involves a UK user, and the location test is deliberately soft: a user is a UK user where it is reasonable to assume they are normally located or established there, with no expectation that providers go collect more information to find out.

An autonomous agent is not a legal person, so the natural candidate for "user" is the principal whose authority and funds it deploys — the same answer international tax gives when it declines to treat an agent as a permanent establishment. But identifying the principal and locating it are different problems. The operator may be a Delaware entity, the inference may run in Virginia, the API key may resolve to a cloud egress range in Ireland, and the human the purchase is made for may be in Manchester. A "reasonable to assume" test is applied against whatever you logged: if the only jurisdictional signal in your records is the origin of an API call, that is the signal you will be assessed on, whether or not it identifies a user.

This is the California place-of-use problem with a passport. It is unresolved, and I will not characterize it otherwise. An equally open question sits alongside it: whether an AI-to-AI supply with no human recipient falls within the scope of EU or UK VAT on electronically supplied services at all. AgentTax takes no position on that one — the guidance presupposes a human consumer, both readings are available, and the choice is the operator's.

The gate is the group, and the domestic floor is falling

Most agent businesses have ignored DSTs because the thresholds are enormous, and that instinct is getting less reliable. The UK requires £500 million of global in-scope revenue and £25 million from UK users. But Italy's 2025 Budget Law eliminated its domestic revenue threshold entirely, retaining only the €750 million global test — so any euro of Italian in-scope revenue is now taxable for a group over that line. KPMG reports Belgium's proposal, targeted at January 1, 2027, at 3 percent with a €750 million global threshold and a Belgian threshold of just over €3 million.

One design feature does the work: the threshold is a consolidated group test, not a test of your entity's revenue, ARR, or headcount. An agent-infrastructure company majority-held inside a large group, or acquired by one, inherits that group's position on day one — and where the domestic floor is gone, there is no second gate. The question for a small platform is not "are we big enough to owe DST" but "whose consolidated group are we in."

One stacking consequence, as an economic observation only: a DST is computed independently of the VAT on the same supply, and the resulting price may then become the measure of a US state sales tax once California and Colorado begin taxing remotely accessed software on January 1, 2027. No state has spoken to whether an embedded foreign gross-receipts levy belongs in that measure, and we will not treat the question as resolved.

What agent operators should do

Separate intermediation revenue from your own service revenue now. DSTs reach intermediation far more reliably than the sale of your own output. Commingled in one line, you can neither compute an in-scope figure nor show the split to an authority that asks.

Track thresholds at the consolidated group level. Find out where your group sits against €750 million and £500 million. That is a cap-table question before it is a tax question.

Log the principal's jurisdiction at transaction time — not the API key origin, not the egress IP. A "reasonable to assume" test is decided on your records, and reconstructing it a year later is not possible.

Budget pass-through fees as fees, not recoverable tax. Meta's location fee is not creditable, carries no exemption certificate, and will not appear in any sales tax engine's output, including ours. Agents buying media programmatically in the six affected markets face a 2 to 5 percent cost increase already in effect.

What to watch

The political overhang cuts both ways: on June 26, 2026 President Trump warned that countries implementing DSTs would face retaliatory tariffs, and the USTR closed its Section 301 investigation into Brazil's digital trade practices that same month with a proposed 25 percent tariff. DST exposure is a real obligation today and politically unstable over any horizon longer than a quarter — reason enough to keep it out of long-dated pricing commitments. Beyond that: Belgium's January 1, 2027 target date, Poland's proposed increase from 1.5 to 3 percent, whether Italy's threshold removal becomes the template, and the development that would change this analysis outright — the first DST amended to name AI or automated services as a limb of its own.

AgentTax classifies what your agents sell and flags where the character of a transaction drives the tax result. Foreign gross-receipts taxes on the platforms beneath you sit outside that scope, which is exactly why they belong in your cost model rather than your tax engine. See how the transaction side works at agenttax.io.

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.