The line that matters
EU VAT has a category for electronically supplied services: essentially automated, with minimal human intervention. An agent customers activate themselves and that runs on its own sits squarely inside — taxed where the consumer lives, bundled in the OSS return. Once your human work per client is substantial — scoping, configuring, supervising — it shifts to ordinary services with their own place-of-supply rules. Occasional human review of edge cases fails to flip an automated service back.
Per customer type
Self-service to EU consumers: local VAT per country via OSS. EU business clients: invoice VAT-free, reverse charged — in both categories. Outside the EU: generally outside EU VAT, with the patchwork routine beyond. Selling the same agent both self-service and bespoke? Split it in your invoicing — one vague bundle inherits the most awkward rules of both.
The contract layer agents demand
An agent that sends mail, books meetings or moves data can cause damage far beyond any dashboard. The clauses that carry the weight: a liability cap (say, twelve months of fees), exclusion of consequential loss, an explicit nature-of-AI clause with a customer duty to review consequential actions, and — specific to agents — the customer defines and controls the agent’s permissions. Behind the paper: insurance sized to the cap, and a BV (besloten vennootschap, the Dutch private limited company) where the remainder stops.
Margin: tokens are your raw material
Agent costs move with usage. Administer model spend per client or per agent so your pricing tracks reality and a future buyer sees true unit economics — the habit described in the bookkeeping guide. Usage-based pricing (per task, per credit) changes nothing for VAT: the nature of the service and the customer type set the rules rather than the meter.