EU AI Act 2026: What Applies to AI Agents Now

As of October 15, 2026, the EU AI Act is in force, with some obligations not yet applicable. It entered into force on August 1, 2024, and applies in phases. Prohibited practices, AI literacy, general-purpose AI model rules, and Article 50 transparency rules already apply. The Digital Omnibus moved the high-risk rules to December 2, 2027 for Annex III use cases and August 2, 2028 for AI in regulated products.

For AI agents, that means two things. Disclosure duties apply today. Hiring, credit, and insurance agents get about 13 more months before the heavy rules start.

This is not legal advice. It is my reading of the primary texts, as of today.

What changed in 2026: the Digital Omnibus is law

Regulation (EU) 2026/1744, the Digital Omnibus on AI, was signed on July 8, 2026, published in the Official Journal on July 24, and entered into force on July 27. The Commission dates the political agreement to May 7, 2026.

Recital 40 gives the reason: standards and guidance arrived late, and national authorities were not ready. So the high-risk rules in Chapter III, Sections 1 to 3, now apply from December 2, 2027 (Annex III) and August 2, 2028 (Annex I).

Other changes for agents:

AI literacy was softened. Article 4 now requires measures “to support the development of AI literacy” of staff, without a duty to guarantee any specific level.
Two new prohibitions. AI that generates non-consensual intimate images or child sexual abuse material is banned from December 2, 2026.
Legacy high-risk systems. Amended Article 111(2) covers high-risk systems already in service before the Chapter III date only if their design later changes significantly. Public-authority systems must comply by August 2, 2030.
Centralized supervision. Under amended Article 75, the AI Office supervises AI systems built on a general-purpose model when the same company or group provides both. Exceptions cover Annex I products, critical infrastructure, justice, and some law-enforcement, border, and financial-institution systems. Deployers outside the provider’s group stay with national authorities.

Failure mode: reading “delayed” as “done for now.” Article 50 was not delayed. It has applied since August 2, 2026.

EU AI Act timeline: which obligations apply now and which apply later

This table reflects the AI Act as amended by the Omnibus.

Obligation	Who	Applies from	Source
Prohibited practices 1 to 8 (Art. 5)	Providers and deployers	Feb 2, 2025	Art. 113(a)
AI literacy measures (Art. 4)	Providers and deployers	Feb 2, 2025; amended text from Jul 27, 2026	Art. 4 as replaced by the Omnibus
General-purpose AI model duties (Art. 53, 55)	Model providers	Aug 2, 2025; models placed earlier by Aug 2, 2027	Art. 113(b), Art. 111(3)
Commission fines on model providers (Art. 101)	Model providers	Aug 2, 2026	Art. 113(b)
Tell people they are dealing with AI (Art. 50(1))	Providers of interactive systems, including agents	Aug 2, 2026	Art. 50, Art. 113
Label deepfakes and public-interest text; notify for emotion recognition (Art. 50(3), (4))	Deployers	Aug 2, 2026	Art. 50
Machine-readable marking of synthetic output (Art. 50(2))	Providers of generative systems	Aug 2, 2026; Dec 2, 2026 for systems on the market before Aug 2, 2026	Art. 111(4), added by the Omnibus
New bans on non-consensual intimate content and CSAM generation	Providers and deployers	Dec 2, 2026	Art. 113(a) as amended
High-risk requirements and duties, Annex III (Chapter III, Sections 1 to 3)	Providers and deployers	Dec 2, 2027	Art. 113(c)(i) as amended
High-risk requirements, Annex I products	Product providers	Aug 2, 2028	Art. 113(c)(ii) as amended

Under Article 99, breaking a prohibition can cost up to EUR 35 million or 7% of worldwide annual turnover, whichever is higher. Most other operator duties, including Article 50 and the deployer duties in Article 26, carry up to EUR 15 million or 3%.

From today, December 2, 2026 is 48 days away. December 2, 2027 is 413 days away, or 59 weeks.

Provider or deployer: which one are you when you build an agent?

A provider develops an AI system, or has one developed, and puts it on the market or into service “under its own name or trademark.” A deployer is anyone “using an AI system under its authority” outside personal use.

Here is the trap. Build a support agent on a vendor’s model and run it under your brand, and you are probably the provider of that agent. The model vendor is the provider of the general-purpose model. The Commission’s Article 50 guidelines (July 20, 2026) say so directly: a company that builds a chatbot in-house “for its own use and under its name” is a provider.

Article 25(1) adds three ways a deployer becomes the provider of a high-risk system:

You put your name or trademark on it, unless a contract allocates the duties otherwise.
You make a substantial modification to a system that is already high-risk.
You change the intended purpose of a system, including a general-purpose one, so it becomes high-risk. Ask a general assistant to rank job applicants, and you may now be a high-risk provider.

Fine-tuning has a separate test for models. The Commission’s GPAI guidelines use an indicative test: a downstream modifier becomes a new model provider when the compute used for the modification exceeds one third of the original model’s training compute. In my read, prompting, retrieval, and light fine-tuning sit far below that.

Decision rule: if the agent carries your brand, or you wrote its instructions for a purpose the vendor did not market, assume provider duties until counsel says otherwise.

Is your AI agent high-risk? How classification works

Article 6 gives a three-step test for agents outside regulated products.

Step 1: Is the use case in Annex III? If not, the agent is not high-risk under Article 6(2). For most companies the relevant entries are point 4 (hiring, promotion, termination, task allocation, and monitoring of workers) and point 5 (creditworthiness of individuals, and life and health insurance pricing). Fraud detection is carved out of the credit entry.

Step 2: Does the Article 6(3) exemption apply? An Annex III system is not high-risk if it does not materially influence the decision and does one of four things: a narrow procedural task, improving a finished human activity, spotting deviations from past decisions without replacing human review, or a preparatory task. A provider using the exemption must document its assessment before launch and, under Article 49(2), register itself and the system in the EU database.

Step 3: Does it profile people? An Annex III system that profiles natural persons is always high-risk, even if step 2 seemed to apply.

The Commission’s draft classification guidelines (May 19, 2026, still marked draft) draw the line clearly. An output counts as preparatory only if it is “a general input or factor.” If the system produces “a specific recommendation or evaluation of the case,” it plays a decisive role. For hiring, the draft says suitability scores, compatibility assessments, and shortlists are in scope. Converting file formats or sorting degrees into standard categories can be preparatory.

Failure mode: assuming a human reviewer takes you out of scope. Under the draft, a scored shortlist that a recruiter approves is still evaluative. A score alone does not make an agent high-risk; a B2B lead-scoring agent is not in Annex III. But inside an Annex III use case, check the output schema. A score, a rank, or an approve/decline field will usually fail the preparatory test.

Role-and-risk decision table for common agent use cases

This is my reading, not an official classification. Marking deadlines move to Dec 2, 2026 for generative agents live before Aug 2, 2026. Confirm high-risk rows with counsel.

Agent use case	Likely risk class	Your likely role	What applies now	Added from Dec 2, 2027
Customer service agent on a vendor model, under your brand	Transparency only	Provider and deployer	Art. 50(1) disclosure; Art. 50(2) marking of generated text; Art. 4	Nothing, unless it starts making credit or insurance decisions
Outreach agent that sends emails to prospects	Transparency only	Provider and deployer	Art. 50(1) disclosure, including on whose behalf it acts; Art. 50(2) marking	Nothing new
HR screening agent that scores, ranks, or shortlists applicants	High-risk, Annex III 4(a)	Deployer if bought for screening; provider if built or repurposed	Art. 4 literacy; Art. 50(1) if it talks to candidates	Deployer: Art. 26. Provider: Art. 9 to 17, conformity assessment, registration
HR agent that only converts CVs and schedules interviews	Likely not high-risk under Art. 6(3)	Provider documents the assessment and registers under Art. 49(2)	Art. 4; Art. 50(1) for candidate chat	Keep the assessment and registration current
Credit agent that recommends approve or decline for consumers	High-risk, Annex III 5(b)	Usually deployer; provider if built in-house	Art. 4; Art. 50(1) if customer-facing	Art. 26 duties plus an Art. 27 impact assessment
Credit agent that gathers documents for an underwriter, with no score	Possibly not high-risk (preparatory)	Provider documents and registers under Art. 49(2)	Art. 4	High-risk if it profiles applicants
Life or health insurance pricing agent	High-risk, Annex III 5(c)	Deployer or provider	Art. 4	Art. 26 and Art. 27 impact assessment
Internal coding or accounts payable agent	Minimal risk	Provider and deployer	Art. 4; Art. 50(1) where it interacts with people, unless obvious	Nothing new

The Article 50 guidelines name “coding agents” as in scope when they interact directly with people. And agents must disclose “both their artificial nature and the person on whose behalf they are acting.”

What deployers and providers must each do

From December 2, 2027, a deployer of a high-risk agent must, under Article 26:

Assign oversight to people with “the necessary competence, training and authority.” A rubber-stamp reviewer does not meet this. See where to put human approval gates.
Monitor and suspend. If the agent presents a risk, inform the provider and the regulator, and stop using it.
Keep logs for at least six months, to the extent they are under your control. The audit trail guide covers the fields.
Tell workers’ representatives and the affected workers before using a high-risk agent at work, and tell people when a high-risk system helps make decisions about them.

Separately, Article 27 requires a fundamental rights impact assessment from public bodies, private entities providing public services, and deployers of credit or life and health insurance agents. Where your GDPR data protection impact assessment already meets one of its requirements, the Omnibus lets you cross-reference it. Fundamental-rights risks the DPIA does not cover still need their own assessment.

Financial institutions meet the monitoring and log duties through their financial-services rules.

Providers carry the build duties in Articles 9 to 17, from risk management to a quality management system, plus conformity assessment, registration, and post-market monitoring.

Buyer rule: Article 25(4) requires a high-risk provider and each third party supplying an AI system, model, tools, services, components, or processes to agree in writing on the information and technical access the provider needs. Suppliers publishing tools or components under a free and open-source license are exempt, but general-purpose AI models are not. Article 25(2) is separate: when someone else becomes the provider under 25(1), the original provider must hand over documentation, known limitations and failure modes, and testing access, unless it had excluded high-risk use. The Omnibus made both fineable. Outside those cases, documentation and testing access are contract requests, not legal entitlements. My vendor question list has the rest.

Standards and guidance available as of October 2026

Follow a harmonized standard cited in the Official Journal and you are presumed to meet the matching requirement. Without one, you must prove compliance yourself.

On October 14, 2026, CEN-CENELEC JTC 21 announced that Implementing Decision (EU) 2026/2274 cites EN 18286:2026 in the Official Journal. EN 18286 covers the quality management system that Article 17 requires of high-risk providers, and maps to ISO 9001 and ISO/IEC 42001. Standards for the other nine areas in the Commission’s standardisation request, such as risk management, logging, and human oversight, are still in progress. JTC 21 says the amended request runs until February 28, 2027.

Commission guidance now in place:

Guidelines on prohibited practices and the AI system definition (February 2025). Both are non-binding.
The GPAI Code of Practice (July 10, 2025). It is voluntary. As of October 7, 2026, it lists 22 signatories, including Anthropic, OpenAI, Google, Microsoft, Amazon, and Mistral AI. xAI signed only the safety and security chapter.

Decision rule: if you will be a high-risk provider, build your quality system on EN 18286 now, extending ISO/IEC 42001 if you already run it.

Worked example: triaging a hypothetical agent portfolio

Say a 600-person EU lender runs six agents. This is hypothetical, and the classifications are my reading of the texts.

A branded customer service agent built in-house and live since 2025: disclosure plus marking by December 2, 2026.
An outreach email agent it built in-house, live since May 2026: transparency, plus marking by December 2, 2026.
A CV screening agent that ranks applicants: high-risk under 4(a).
A consumer credit pre-screen agent that recommends approve or decline: high-risk under 5(b), with an impact assessment.
An accounts payable agent: minimal risk.
An internal coding agent: minimal risk.

That gives 2 high-risk agents and 2 agents with a marking deadline in 48 days. Agents 1 and 2 owe Article 50(1) disclosure today. Agents 3, 4, and 6 owe it wherever they talk to people directly.

Now the legacy question. Article 111(2) protects high-risk systems already in service before December 2, 2027 unless their design later changes significantly. In my judgment, an agent whose model, prompts, and tools change monthly is unlikely to keep that status. I would plan both high-risk agents as fully in scope.

Work order: Article 50 fixes now, marking before December 2, then the 52 weeks from December 2, 2026 to the high-risk date. The governance operating model shows how to route each tier, and the shadow agent inventory finds the agents nobody listed.

Bottom Line

The EU AI Act did not pause. Article 50 transparency applies now, and agents must say they are AI and whom they act for.

The Omnibus gave high-risk agents until December 2, 2027. Use that time to classify each agent, settle provider versus deployer, and fix vendor contracts.

Start with Annex III. Inside it, scores and recommendations usually mean high-risk.

FAQ

Did the EU delay the AI Act?

Only the high-risk rules, plus a four-month marking grace period for systems already on the market. The new dates are fixed in the text, not tied to a Commission decision on standards as the November 2025 proposal suggested.

Does the EU AI Act apply to US companies?

Yes, in many cases. Article 2(1)(c) covers providers and deployers outside the EU “where the output produced by the AI system is used in the Union.” Article 50 duties apply whether the system is free or paid.

Do I need to disclose AI if a human reviews the agent’s messages?

Usually yes. The Article 50 guidelines require disclosure for AI-generated parts of blended content, unless those outputs “have been properly reviewed and sent by humans as the main interlocutors.” An agent sending on its own does not qualify.

Is AI literacy still mandatory after the Omnibus?

Yes, in a softer form. The Commission must now publish practical compliance examples on its single information platform. My AI acceptable use policy for agents includes a training clause you can adapt.

What fines apply to smaller companies?

For SMEs, including start-ups, Article 99(6) caps each fine at the lower of the fixed amount and the turnover percentage, not the higher. The Omnibus extends that rule to small mid-cap companies for all fines except those for prohibited practices. The Article 50 Q&A puts transparency fines at up to EUR 15 million or 3% of worldwide turnover.

Three Ways to Work With TMA

Need an agent built? We deploy production AI agents in your infrastructure. Working pilot. Real data. Measurable ROI. → Schedule Demo

Want to co-build a product? We’re not a dev agency. We’re co-builders. Shared cost. Shared upside. → Partner with Us

Want to join the Guild? Ship pilots, earn bounties, share profit. Community + equity + path to exit. → Become an AI Architect

EU AI Act 2026: What Applies to AI Agents Now and Later