Article 50 Guidelines: what AI agents do not have to mark

As of the Article 50 transparency milestone in Legalithm’s enforcement calendar (Article 50): the duties apply from that date. High-risk Annex III and Annex I embedded product dates sit later on the same calendar. This post states only facts the Commission’s Article 50 Guidelines make explicit in the paragraphs named below — nothing else.

The answer first

If you are shipping an AI agent stack into the EU, the most valuable half of the Commission’s Article 50 Guidelines (adopted 20 July 2026, 51 pages) is not a new checklist of labels. It is the negative scope: what does not count as synthetic content under Article 50(2), and which agent communications fall outside the transparency surface altogether.

For a developer audience, that is the half that saves weeks of over-marking. Lead with what you may leave unmarked. Then read the agent disclosure rule in Paragraph 31 for what you still must tell people.

This article does not invent commentary beyond those Guidelines paragraphs. Where a date appears for Article 50, Annex III high-risk, or Annex I embedded products, it is the date Legalithm stores in its enforcement-date source of truth for that milestone — not a guess.

What you do not have to mark (Paragraph 63)

Paragraph 63 is the negative scope, and it is the only official statement of this kind in the Guidelines text we rely on here.

Under Paragraph 63, the following do not qualify as synthetic content under Article 50(2):

1. Actions that do not contain AI-generated or manipulated content — including intermediate processing steps such as reasoning and chain of thought.
2. AI-generated actions not intended to be directly perceived by natural persons — for example a web request or a browser action.

That is the developer-facing line. An agent’s internal plan, scratchpad, tool-selection rationale, or multi-step chain of thought is not, under Paragraph 63, synthetic content that Article 50(2) requires you to mark as artificially generated. A background HTTP call or browser automation step that no natural person is meant to perceive is likewise outside that Article 50(2) synthetic-content qualification.

Do not stretch Paragraph 63 past what it says. It answers the Article 50(2) synthetic-content question for those categories. It does not cancel Article 50(1) disclosure when a natural person is interacting with the agent. Those are different limbs of Article 50.

Backend machine-to-machine calls (Paragraph 30(iv))

Paragraph 30(iv) excludes backend machine-to-machine calls between AI systems.

If your architecture is agent A calling agent B (or model service C) over a private backend path with no natural person in that hop, Paragraph 30(iv) places that backend M2M call outside the interaction surface the Guidelines are carving here. Again: this is an exclusion for that class of call, not a licence to hide an agent from a user who is instructing it or chatting with it.

Agent-to-agent communication (Paragraph 68)

Paragraph 68 excludes agent-to-agent communication.

Multi-agent meshes that only talk to each other are not, under Paragraph 68, brought into the Guidelines’ agent-to-agent exclusion in reverse — the exclusion is the point. The human-facing edge is where Paragraph 31 bites; agent-to-agent traffic is called out as excluded in Paragraph 68.

What agents still must disclose (Paragraph 31)

Paragraph 31 is the affirmative agent rule under Article 50(1).

AI agents are covered by Article 50(1) if capable of interacting with the persons instructing them or with other natural persons. When that condition holds, they must disclose:

• their artificial nature, and
• the person on whose behalf they are acting,

reflecting delegation of authority and accountability for the consequences of their actions.

Paragraph 31 states that this covers complex multi-agent architectures. Coverage is not limited to a single chatbot process.

Where the provider cannot reliably determine in advance whether the agent will interact with a natural person, the agent must be designed at architecture level to disclose itself in every situation where interaction is reasonably likely. That is a design-time duty, not a post-hoc banner you hope someone remembers to toggle.

Agents must also disclose to the persons instructing them at key steps — authorisation, reporting, validation — and at every new interaction.

So the practical split for builders is:

Identifying agents (Footnote 21)

Footnote 21 raises EU Digital Identity Wallets and European Business Wallets as means of identifying AI agents.

That is a pointer to identification infrastructure, not a mandate in the facts we are allowed to state here. If you need a durable way to bind an agent to the person on whose behalf it acts, Footnote 21 is the Guidelines’ own signal that those wallet instruments are in view.

Why Article 50 is the live agent obligation

Article 50 transparency obligations are the agent-facing duty that sits on Legalithm’s enforcement calendar as the live transparency milestone. High-risk obligations for Annex III systems, and later for Annex I embedded products, are separate milestones on that same calendar — later, and not a substitute for Article 50 where Article 50 applies.

The Guidelines adopted on 20 July 2026 are the Commission’s reading of Article 50. They do not replace the regulation. They tell you how the Commission reads agents, synthetic content, and the exclusions above. The amending instrument title and in-force date are stamped on this page from Legalithm’s LEGAL_INSTRUMENTS source of truth — not restated as free-standing literals in this body.

What this means in an agent codebase

Map your stack to the table, not to vibes.

1. Separate perception from processing. If a step is intermediate reasoning or a tool call no person is meant to see, Paragraph 63 says it is not Article 50(2) synthetic content. Do not burn sprint capacity watermarking chain-of-thought logs for Article 50(2) on the strength of Paragraph 63 alone.
2. Keep the human edge honest. If an instructor or other natural person can interact with the agent, Paragraph 31 requires disclosure of artificial nature and of the person on whose behalf the agent acts, including at authorisation, reporting, validation, and every new interaction.
3. Design for “reasonably likely” interaction. If you cannot know in advance whether a natural person will appear on the other side, Paragraph 31 requires architecture-level disclosure wherever interaction is reasonably likely — including in complex multi-agent setups.
4. Do not confuse M2M with user secrecy. Paragraph 30(iv) and Paragraph 68 exclude backend M2M and agent-to-agent communication; they do not erase Paragraph 31 at the human interface.
5. Record the role. Disclosure of the person on whose behalf the agent acts is part of Paragraph 31’s accountability framing. Wire that identity into the same place you render the artificial-nature notice.

In practice, treat Paragraph 63 as a marking filter for Article 50(2) and Paragraph 31 as a disclosure filter for Article 50(1). Teams that collapse both into a single “label everything the agent touches” policy will over-comply on synthetic-content marking while still missing instructor-facing disclosure at authorisation, reporting, validation, and each new interaction. The Guidelines text we are allowed to use here draws that split explicitly; your implementation should too.

Limits of this article

• This post cites Paragraphs 31, 63, 30(iv), 68 and Footnote 21 of the Commission’s Article 50 Guidelines (adopted 20 July 2026), plus Article 50 of Regulation (EU) 2024/1689 as amended. It does not summarise the other ~51 pages.
• Commission guidelines are interpretive guidance, not a free-standing statute. Your obligations still come from the regulation.
• This is not legal advice. Map your concrete architecture with counsel.
• Legalithm’s product surface for this problem is evidence and disclosure tooling, not a runtime gateway that blocks agent traffic.

Tool: classify the edge, then disclose

If you need a concrete next step in the product:

1. Run the EU AI Act applicability checker on the system that faces natural persons.
2. Generate user-facing copy with the AI Act disclosure generator for the Article 50(1) edge Paragraph 31 describes.
3. Keep intermediate reasoning and unperceived tool actions out of your Article 50(2) marking backlog unless some other duty (contract, policy, or a different article) says otherwise — Paragraph 63 is the Guidelines’ negative scope for synthetic content under Article 50(2).

Article 50 is currently the agent obligation in force on the transparency calendar. Build the disclosure at the human edge; do not mark what Paragraph 63 says is not synthetic content under Article 50(2).