EU AI Act Transparency Obligations: Article 13 & Article 50
The EU AI Act splits transparency into two regimes. Article 13 governs the relationship between providers and deployers of high-risk AI. Article 50 governs the relationship between AI systems and the people they interact with — covering chatbots, deepfakes, and AI-generated content.
EU AI Act Transparency Obligations: Article 13 & Article 50
The EU AI Act splits transparency into two regimes. Article 13 governs the relationship between providers and deployers of high-risk AI. Article 50 governs the relationship between AI systems and the people they interact with — covering chatbots, deepfakes, and AI-generated content.
Last updated: July 4, 2026
Article 13: Transparency to Deployers
Providers of high-risk AI must furnish deployers with sufficient information to use the system correctly and exercise meaningful oversight.
- Provider identity and contact details
- Intended purpose, accuracy, robustness, and cybersecurity properties
- Known limitations and known foreseeable misuses
- Performance with respect to specific persons or groups
- Input data requirements and expected output interpretation
- Human oversight measures and how to exercise them
- Maintenance and lifecycle expectations
Article 50: Transparency to Users & the Public
Article 50 applies more broadly than just high-risk systems. Four core duties:
- AI interaction disclosure — natural persons must be informed they are interacting with an AI system (e.g., chatbots), unless obvious from context
- Synthetic content marking — AI-generated audio, image, video, or text must be machine-readable and detectable as artificial
- Deepfake disclosure — content depicting real persons or events must be disclosed as artificially generated, with limited exceptions for clearly artistic, satirical, or fictional works
- Public-interest text — AI-generated text published to inform the public on matters of public interest must be disclosed unless human review and editorial responsibility apply
How Articles 13 and 50 Interact
The two transparency regimes operate at different levels of the value chain:
Article 13 is a B2B obligation between providers and deployers. Article 50 is end-user-facing. A provider of a high-risk chatbot owes Article 13 documentation to its enterprise deployers AND Article 50 disclosure to the natural persons the chatbot speaks with.
Article 50 Exceptions and Implementation Checklist
Article 50 disclosure duties come with narrow exceptions, and Article 13 documentation has concrete build requirements. Work through both:
- Interaction disclosure exception — you can skip the "you are talking to an AI" notice only where it is obvious to a reasonably well-informed person from the context of use; when in doubt, disclose
- Deepfake artistic exception — for evidently artistic, creative, satirical, or fictional work, the disclosure can be limited to a form that does not hamper the display or enjoyment of the work, rather than omitted entirely
- Law-enforcement exception — detection, prevention, investigation, and prosecution of criminal offences may be exempt from certain synthetic-content and interaction duties where authorised by law
- Machine-readable marking — synthetic-content marking must be effective, interoperable, robust, and reliable as far as technically feasible; plan for a durable technique such as watermarks, metadata, or cryptographic provenance signals
- Article 13 instructions for use — package provider identity, intended purpose, accuracy and robustness metrics, known limitations, and human-oversight measures into deployer-facing documentation you can version and update
- Timing — Article 50 transparency duties apply from 2 August 2026; build the disclosure and marking mechanisms into your product now rather than retrofitting them
This checklist is an editorial summary, not legal advice; confirm the exact conditions of each exception against the regulation text and any AI Office guidance before relying on it.
How AIAgentree helps
AIAgentree gives you the disclosure records and deployer-facing evidence that Articles 13 and 50 expect, without changing how your agents run.
- Tamper-evident decision records capture when an AI interaction, synthetic-content, or deepfake disclosure was shown, so you can demonstrate Article 50 compliance to an auditor after the fact
- Human-oversight and approval workflows document the oversight measures Article 13 requires deployers to be able to exercise, with a record of who approved or overrode a decision and why
- Structured exports over REST, MCP, A2A, and OpenTelemetry — using the Python and TypeScript SDKs — let you fold decision evidence into the instructions-for-use and technical documentation you owe deployers, hosted with EU data residency in Germany
Frequently Asked Questions
What is the difference between Article 13 and Article 50 transparency?
Article 13 is a provider-to-deployer duty: providers of high-risk AI must give deployers instructions for use covering purpose, accuracy, limitations, and human-oversight measures. Article 50 is a system-to-person duty: people must be told when they are interacting with AI or seeing AI-generated or manipulated content. A single high-risk chatbot can owe both.
When do the Article 50 transparency obligations apply?
The Article 50 transparency obligations for providers and deployers apply from 2 August 2026 under Regulation (EU) 2024/1689. Building disclosure and synthetic-content marking into a product early is far cheaper than retrofitting it after launch.
Do I always have to label AI-generated content?
Not in every case. Article 50 provides narrow exceptions — for example, where AI interaction is obvious from context, for evidently artistic or satirical works (where a limited-form disclosure suffices), and for certain law-enforcement uses authorised by law. Outside those conditions, synthetic and deepfake content must be marked as artificially generated or manipulated.
Does the deepfake disclosure exception mean I can skip marking artistic content?
No. For evidently artistic, creative, satirical, or fictional work the disclosure may be presented in a way that does not hamper the display or enjoyment of the work, but it must still be disclosed. The exception limits the form of disclosure, it does not remove it.
Continue exploring the EU AI Act guide
EU AI Act Compliance Guide
The complete guide to EU AI Act compliance for AI agents — start here.
Article 12 — Record-Keeping & Logging
What every high-risk AI system must log, and how to capture it.
Article 14 — Human Oversight
Designing effective human-in-the-loop controls for AI decisions.
Annex III — High-Risk AI Systems
Which AI use cases the Act classifies as high-risk.
EU AI Act Compliance Checklist
A step-by-step checklist to reach and document compliance.
Compliance Cost Calculator
Estimate your EU AI Act compliance effort and cost.
Deadlines & Timeline
Key enforcement dates, including the August 2, 2026 deadline.
Fines & Penalties
Penalty tiers up to €35M or 7% of global annual turnover.
Risk Management & Conformity Assessment
Build a risk management system and assess conformity.
GPAI Obligations
Rules for providers of general-purpose AI models.
EU AI Act for US Companies
Extraterritorial scope and what US providers must do.
Omnibus Update
The latest changes to the EU AI Act timeline and rules.
Penalty Calculator
Estimate your maximum fine under the Article 99 tiers.
Article 11 + Annex IV
What technical documentation the EU AI Act requires.
Article 26: Deployer Obligations
What deployers of high-risk AI must do, including log retention.
Article 17: Quality Management
The QMS providers of high-risk AI must document.
Article 10: Data Governance
Data quality, bias mitigation, and governance duties.
Article 4: AI Literacy
The staff AI-literacy duty in force since February 2025.
Deployer vs Provider
Who bears which obligation — and when a deployer becomes a provider.
FRIA (Article 27)
Who must run a Fundamental Rights Impact Assessment, and how.
Who Does It Apply To?
Scope, operators, and the extraterritorial reach of the EU AI Act.
Post-Market Monitoring
Articles 72–73: ongoing monitoring and incident reporting.
ISO 42001 vs EU AI Act
How the voluntary standard and the binding law fit together.
NIST AI RMF vs EU AI Act
A practical crosswalk between the framework and the law.
EU AI Act for Healthcare
High-risk medical AI, MDR/IVDR interplay, and clinician oversight.
EU AI Act for Financial Services
Credit scoring, insurance pricing, and existing financial regulation.
EU AI Act for HR & Employment
Hiring AI as high-risk, plus NYC LL144 and EEOC overlap.