Summary No. Under the proposed Cloud and AI Development Act (CADA), an AI agent does not automatically count as frontier AI. The proposal defines the two as separate concepts in Article 2: "frontier AI" turns on capability and generality (Article 2(4)), while "AI agent" turns on autonomy and behaviour (Article 2(5)). An agent is frontier AI only if it also meets the frontier definition — and a frontier model is an agent only if it also meets the agent definition.

Detail

The relationship between AI agents and frontier AI under CADA is set by the definitions in Article 2. The proposal keeps the capability of a system (whether it is frontier) separate from its architecture (whether it is an agent).

The definition of frontier AI

Article 2(4) defines "frontier AI" as:

"AI models or AI systems built upon such models that can perform a wide variety of tasks and that approach, reach or exceed the current state of the art."

This has two cumulative elements:

  1. Generality — the system can perform a wide variety of tasks.
  2. Performance — it approaches, reaches or exceeds the current state of the art.

Both must be present. A narrow system, however advanced, is not frontier AI; nor is a general system that performs below the state of the art.

The definition of AI agent

Article 2(5) defines "AI agent" as:

"an AI system or a coordinated set of AI systems, that can perceive and act upon their environment, with a degree of autonomy, using tools as needed to achieve specific goals and adapt to changing inputs and contexts."

This turns on behaviour — perception, autonomy, tool use, and goal-directed adaptation. It says nothing about performance, scale or state-of-the-art benchmarks. (Both definitions build on "AI system," which CADA defines in Article 2(3) by cross-reference to the AI Act, Regulation (EU) 2024/1689.)

Where the two overlap

The key point for architects is that agency is not a proxy for frontier status.

  1. An agent can be non-frontier. You can build an AI agent on a smaller or specialised model that does not reach the state of the art. An autonomous bot that uses a narrow model to reorder stock is an "AI agent" under Article 2(5), but it is not frontier AI under Article 2(4) if it lacks the generality and state-of-the-art performance.
  2. A frontier model can be non-agentic. A state-of-the-art, general model used in a static chat interface, without autonomous tool use or environmental action, is frontier AI under Article 2(4) but not an "AI agent" under Article 2(5).
  3. The intersection. Build an autonomous agent on a state-of-the-art general model and the result is both an AI agent and frontier AI — because it satisfies both definitions at once.

Why the distinction matters

CADA treats the two categories through different support mechanisms.

  • Frontier AI features in the proposal as a strategic asset. Under Article 8, the Commission may recognise projects as "frontier AI priority projects," and under Article 9 AI computing resources may be allocated to such projects. The focus is on capability and scale.
  • AI agents feature as a deployment paradigm. Under operational objective 6 of the Cloud and AI Leadership Initiatives (Article 3(2)(f), implemented by Article 4(6)), the Initiatives are to support the development of advanced platforms for the development, deployment and orchestration of AI agents at scale. The focus is on orchestration and autonomy.

So labelling a system an "agent" does not, by itself, open the frontier-AI support routes, nor does it exempt a system from being treated as frontier AI if it meets the Article 2(4) threshold.

What this means for you

For CTOs and architects assessing classification and funding eligibility, apply two separate checklists:

  1. Check for agency (Article 2(5)). Does the system perceive its environment, act with a degree of autonomy, and use tools to achieve goals? If so, it is an AI agent — relevant to the agent-platform support under operational objective 6.
  2. Check for frontier status (Article 2(4)). Does the model or system perform a wide variety of tasks and approach, reach or exceed the state of the art? If so, it is frontier AI — relevant to frontier AI priority projects (Article 8) and compute allocation (Article 9).

Practical impact:

  • Building a niche agent on a frontier base model? If the resulting system retains the wide task range and state-of-the-art performance, it would still be frontier AI — Article 2(4) expressly covers "AI systems built upon such models."
  • Using a smaller model? You can build autonomous agents without meeting the frontier threshold — useful for SMEs and specialised players that need autonomy but not a state-of-the-art general model.
  • Documentation. When seeking support under the Cloud and AI Leadership Initiatives, be clear whether you are applying in relation to frontier model development (Articles 8-9) or to agentic-platform development under operational objective 6 (Article 4(6)).

Common misconceptions

  • "Any autonomous AI is frontier AI." Autonomy is a feature of agents (Article 2(5)), not a criterion of frontier AI (Article 2(4)). Frontier AI is defined by generality and performance.

  • "An agent built on a frontier model is 'just an application' and no longer frontier." Article 2(4) expressly includes "AI systems built upon such models." If the system keeps the wide task range and state-of-the-art performance, it remains frontier AI.

  • "Frontier AI only means large language models." The Article 2(4) definition is technology-neutral. It covers any AI model or system meeting the generality and state-of-the-art criteria, not only LLMs.

Official sources

Related

This is general information about a draft EU regulation, not legal advice.