Article 50 of the EU AI Act imposes transparency obligations — telling people when they are interacting with AI and marking AI-generated content — and those obligations take effect on 2 August 2026. As of July 2026, that is roughly three weeks away, and unlike the high-risk requirements, this deadline did not move: the May 2026 Digital Omnibus delayed the Annex III high-risk obligations to December 2027 but left Article 50 (and Article 49 registration) on the original schedule.

If you ship a chatbot, an AI agent, a voice assistant, or anything that generates text, images, audio, or video used in the EU, this article is about work you need to complete this quarter. For the full regulation in engineering terms, see the EU AI Act explained for engineering teams; for exactly what the Omnibus did and did not change, see what changed in the 2026 Digital Omnibus.

Who Article 50 applies to

Article 50 applies to providers and deployers of AI systems that interact with people or generate content — regardless of risk tier. This is the point teams most often miss: transparency obligations are not a high-risk-only concern. A minimal-risk customer support bot that would never appear in Annex III still has to disclose that it is AI.

The obligations split by role:

  • Providers of AI systems intended to interact directly with natural persons must design the system so those persons are informed they are interacting with AI — unless that is obvious to a reasonably well-informed person from the context.
  • Providers of systems that generate synthetic audio, image, video, or text content must ensure outputs are marked in a machine-readable format as artificially generated or manipulated.
  • Deployers of emotion recognition or biometric categorisation systems must inform the people exposed to them.
  • Deployers who generate or manipulate deepfake content — images, audio, or video resembling real persons, places, or events — must disclose that the content is artificial.
  • Deployers who publish AI-generated text to inform the public on matters of public interest must disclose the AI origin, unless the content underwent human review and a person holds editorial responsibility.

The extraterritorial scope follows the rest of the Act: if the system's output is used in the EU, the obligations apply, wherever your company is incorporated.

What "informing the user" means in practice

The interaction-disclosure duty is satisfied by clear, timely notice — at or before the first interaction — not by a line buried in terms of service. For an engineering team, this decomposes into a small set of concrete tasks:

  • Disclosure UX. A visible label or statement in the chat surface, voice prompt, or email footer stating the user is interacting with an AI system. If your agent operates across channels (web chat, Slack, email, phone), each channel needs its own disclosure treatment.
  • The "obvious from context" judgment. The exemption is narrow. A product literally named "AI Assistant" with a robot avatar may qualify; an agent answering a support line or sending human-sounding emails does not. If you plan to rely on the exemption, document the reasoning.
  • Agent-to-human boundaries. Agentic systems complicate the analysis: an agent that drafts messages a human sends is different from an agent that sends them autonomously. Map where AI-originated content actually reaches people without human mediation — that boundary is where disclosure attaches. Maintaining a current inventory of your agents and what each one can send externally is the practical starting point.

What content marking requires from your pipeline

Synthetic-content marking is a generation-pipeline requirement, not a UI requirement: the marking must be machine-readable and applied at output time. That means engineering work in the layer where content is produced:

  • Machine-readable marking. Techniques include metadata standards (such as C2PA-style content credentials), watermarking where the modality supports it, and explicit provenance fields in APIs that serve generated content. The Act requires the solution to be effective, interoperable, robust, and reliable to the extent technically feasible — a standard that rewards using established provenance mechanisms over homegrown flags.
  • Text is included. Teams often assume marking is an image/video problem. Generated text distributed at scale is in scope for provider marking, and public-interest text publication carries a separate deployer disclosure duty.
  • Third-party models don't do this for you by default. If you build on a foundation model API, the marking obligation for your product's outputs is still your problem to engineer. Verify what provenance features your model provider exposes and what you must add on top.
  • Evidence. When a regulator or customer asks whether outputs were marked during a given period, you need logs that show marking was applied — which is an audit-trail design question. Append-only, tamper-evident audit logs covering the generation path are how you make the answer demonstrable rather than asserted.

Don't forget Article 49 lands the same day

Article 49 requires providers (and certain public-authority deployers) of high-risk AI systems to register them in the EU database before placing them on the market — and that obligation also takes effect 2 August 2026, unchanged by the Omnibus. Even though the substantive Annex III high-risk conformity obligations moved to December 2027, the registration machinery starts now.

The practical consequence: you still need the classification exercise today. You cannot know whether Article 49 registration applies to you without having classified each system against Annex III. A structured AI agent compliance checklist covering classification, registration status, and transparency treatment per agent is the fastest way to establish where you stand.

A three-week engineering plan

Three weeks is enough to reach defensible compliance if you scope tightly to what Article 50 actually demands.

Week 1 — inventory and classify the surfaces. List every place an AI system interacts with people or emits generated content that reaches the EU. For each: does the interaction-disclosure duty apply, does content marking apply, do the deepfake or public-interest text provisions apply? Record the reasoning, including any "obvious from context" claims.

Week 2 — ship disclosure and marking. Add the disclosure UX per channel. Wire machine-readable marking into the generation pipeline, preferring established provenance standards. Where full technical marking is not yet feasible for a modality, document the constraint and the mitigation — the feasibility qualifier in the Act is not a blanket excuse, but honest documentation of limits is far more defensible than silence.

Week 3 — instrument and evidence. Log disclosure delivery and marking application as auditable events. Generate a point-in-time report showing which systems are in scope, what treatment each has, and where the gaps are. Fold the result into your broader governance posture — the complete AI governance guide covers how transparency controls sit alongside oversight, audit, and classification obligations.

Common questions

Was Article 50 delayed by the Digital Omnibus? No. As of July 2026, the May 2026 Digital Omnibus delayed only the Annex III high-risk obligations, to December 2027. Article 50 transparency obligations and Article 49 registration obligations take effect on 2 August 2026 as originally scheduled.

Does Article 50 apply to low-risk chatbots? Yes. Transparency obligations attach to systems that interact with people or generate content regardless of risk tier. A minimal-risk support bot must still disclose that it is AI, and its generated content is still subject to marking obligations on the provider side.

We use a third-party LLM API — is content marking the provider's problem or ours? Roles are assessed per system, not per model. If you place an AI system on the market that generates content, the provider-side marking obligation for that system's outputs sits with you, even if the underlying model is someone else's. Check what provenance tooling your model vendor offers, then close the remainder in your own pipeline.

What counts as machine-readable marking for generated text? The Act sets an outcome — outputs detectable as artificially generated, marked in a machine-readable format, effective and robust to the extent technically feasible — rather than a single mandated technique. Metadata-based provenance (content credentials), watermarking where available, and explicit provenance fields in distribution APIs are the mechanisms teams are converging on. Document your choice and its limits.

What are the penalties for non-compliance with transparency obligations? The AI Act's penalty framework provides for administrative fines that scale with company revenue, with transparency-obligation violations sitting below the ceiling reserved for prohibited practices but still material. The more immediate commercial risk in 2026 is procurement: enterprise buyers are already asking for AI Act compliance evidence in vendor assessments.