The EU AI Act timeline for autonomous agents
When each EU AI Act obligation actually bites — and what teams shipping autonomous AI agents must have ready for the Article 50 transparency deadline on 2 August 2026.
Definition
The EU AI Act is the European Union's risk-based AI regulation. Its obligations phase in over several years; for autonomous agents the nearest hard deadline is the Article 50 transparency duties, enforceable from 2 August 2026, which govern how AI involvement must be disclosed.
Most teams building autonomous agents know the EU AI Act exists. Far fewer know when each part applies to them. The Act does not switch on all at once — it phases in by risk tier over several years, and for agents the relevant clock is closer than the headline “2027” most people remember.
The Act regulates behavior, not the label “agent”
The AI Act never defines an “agent” as a regulated category. It regulates by risk and by role. That is good news: you do not need a lawyer to tell you whether your system is “an agent.” You map what your agent does onto the Act’s obligations.
- Does it interact with people or generate content? Article 50 transparency applies.
- Does it operate in a high-risk domain (Annex III) such as hiring, credit or critical infrastructure? High-risk obligations apply.
- Is it built on a general-purpose model? GPAI obligations flow down from the provider.
The phased timeline
Prohibited practices + AI literacy
Article 5 bans take effect; Article 4 requires staff to have adequate AI literacy.
GPAI obligations begin
Duties for general-purpose AI model providers start to apply.
Article 50 transparency enforceable
Disclosure of AI interaction, labeling of AI-generated content, deepfake marking. The nearest hard deadline for most agent teams.
High-risk (Annex III) duties
Conformity, risk management and oversight obligations for high-risk use cases.
Remaining high-risk (Annex I)
Obligations tied to regulated products phase in.
What does Article 50 actually require of an agent?
For the August 2026 deadline, three duties matter to a typical agent:
- Disclose the AI. If a user interacts with your agent, they must be able to tell it is an AI system, unless it is obvious from context.
- Label AI-generated content. Output that is generated or meaningfully manipulated by AI must be marked as such, in a machine-readable way where feasible.
- Mark deepfakes. Synthetic image, audio or video content must be disclosed.
None of this is exotic. The engineering work is mostly plumbing: a disclosure in the interface, a content-provenance signal, and a record that the disclosure happened.
The honest version of the penalty story
It is tempting to sell compliance with the scary number. Resist it. The 35 million euro / 7% of turnover tier is reserved for prohibited practices under Article 5 — manipulative or exploitative systems — not for missing a transparency label. Article 50 breaches sit in a lower tier. Communicating this accurately is itself a trust signal: you describe a real, dated obligation without manufacturing fear.
The fine tiers, so the 7% figure lands on the right breach:
| Breach tier | What it covers | Maximum fine |
|---|---|---|
| Prohibited practices (Art. 5) | Manipulative, exploitative or banned systems | €35M or 7% of global turnover |
| Other obligations (incl. Art. 50, high-risk) | Transparency, high-risk and provider duties | €15M or 3% of turnover |
| Incorrect information to authorities | Misleading or incomplete information to regulators | €7.5M or 1% of turnover |
What to do before August 2026
- Inventory every agent that talks to people or produces content.
- Add clear AI disclosure to those interfaces.
- Capture signed, tamper-evident audit logs of agent decisions — a log that can be altered is worthless before an EU court.
- Document who is accountable for each agent’s actions.
For the controls that make oversight real, see human oversight; for the audit-logging foundation, see observability. Definitions of the terms above live in the glossary.
Frequently asked questions
Does the AI Act regulate AI agents specifically?
It does not name agents as a category at all; it regulates by risk and by role, and an agent inherits its obligations from what it actually does. If your agent interacts with people or generates content, the Article 50 transparency duties apply. If it operates in a high-risk domain listed in Annex III — hiring, credit scoring, critical infrastructure and similar — the high-risk obligations apply, with their conformity, risk-management and oversight requirements. If it is built on a general-purpose model, GPAI obligations flow down to you from the model provider. The practical consequence is liberating: you do not need a legal ruling on whether your system counts as an agent, because the law never asks that question. You map your agent's concrete behaviours onto the Act's risk tiers and adopt whichever duties those behaviours trigger. When in doubt, classify by the most consequential thing the agent can do, not by the most flattering description of it.
What exactly changes on 2 August 2026?
The Article 50 transparency obligations become enforceable, which for most agent teams is the nearest hard deadline in the whole Act. Three duties matter in practice. First, disclosure: if a user is interacting with an AI system, they must be able to tell, unless it is already obvious from context. Second, content labeling: output that is generated or meaningfully manipulated by AI has to be marked as such, in a machine-readable way where feasible. Third, deepfake marking: synthetic image, audio or video must be disclosed. For an agent that chats with customers or produces written, visual or audio content, that translates into a clear notice in the interface plus a provenance signal on generated artefacts. The engineering is modest — mostly interface text, a content-provenance marker and a record that the disclosure happened — but the date is fixed, so it belongs on the roadmap now rather than in mid-2026.
Is it true that fines reach 7% of turnover?
The 7% figure is real but routinely misapplied. The highest tier — up to 35 million euro or 7% of global annual turnover, whichever is greater — is reserved for prohibited practices under Article 5, meaning manipulative or exploitative systems that the Act bans outright. Ordinary transparency duties under Article 50 do not sit in that tier; most obligations, including high-risk and transparency, fall under a lower ceiling of up to 15 million euro or 3% of turnover, and supplying incorrect information to authorities is lower still. Quoting the 7% number against a missing disclosure label is therefore inaccurate, and for SMEs the Act generally applies the lower of the fixed amount or the percentage. Describing the penalty honestly — naming the right tier for the right breach — is both more correct and more credible than reaching for the scariest figure, which is exactly the posture a regulator and a customer both reward.
Does the AI Act apply if my company is outside the EU?
Very often, yes, because the Act follows the market rather than the company's address. Its scope is extraterritorial: it reaches providers and deployers established outside the EU when their AI system is placed on the EU market, or when the system's output is used within the EU. So a company headquartered elsewhere that offers an agent to EU users, or whose agent produces results consumed in the EU, generally falls within scope even with no EU office. This mirrors the familiar reach of the GDPR and is deliberate, to prevent regulatory arbitrage. The practical takeaway is not to assume you are exempt because you are not an EU entity; instead, check whether EU users interact with your agent or rely on its output, and if they do, plan for the same Article 50 and, where relevant, high-risk obligations as an EU-based provider would. Geography of incorporation is the wrong test; where the system and its effects land is the right one.