EU AI Act
EU AI Act - General-Purpose AI Models

EU AI Act EUAI-Art.54: Authorised representatives of providers of general-purpose AI models

A provider of a general-purpose AI model established in a third country must, before placing the model on the Union market, appoint by written mandate an authorised representative established in the Union, and must enable it to perform the mandated tasks. The mandate must empower the representative to verify that the Annex XI technical documentation has been drawn up and that the Art.53 and, where applicable, Art.55 obligations have been fulfilled; to keep a copy of that documentation and the provider's contact details at the disposal of the AI Office and the national competent authorities for ten years after the model was placed on the market; to provide information and documentation on reasoned request; and to cooperate with the AI Office and competent authorities on any action they take in relation to the model, including where it is integrated into AI systems placed on the Union market. The representative must terminate the mandate and immediately inform the AI Office if it considers the provider is acting contrary to its obligations. The duty does not apply to models released under a free and open source licence meeting the stated conditions unless they present systemic risk.

Other controls in EU AI Act - General-Purpose AI Models

You are reading one control. How much of EU AI Act have you already done?

EU AI Act EUAI-Art.54 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of EU AI Act your existing evidence covers. Hold ISO/IEC 42001:2023 and 17 of 43 EU AI Act controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the ISO/IEC 42001:2023 pair alone.

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.