> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/mica.wtf/ai-act/chapter-v-general-purpose-ai-models-art.-51-56/55.md).

# Art. 55 — Obligations of providers of general-purpose AI models with systemic risk

1. In addition to the obligations listed in [Articles 53](/mica.wtf/ai-act/chapter-v-general-purpose-ai-models-art.-51-56/53.md) and [54](/mica.wtf/ai-act/chapter-v-general-purpose-ai-models-art.-51-56/54.md), providers of general-purpose AI models with [systemic risk](https://headlesslaw.com/definitions/ai-act/systemic-risk/) shall:
   1. perform model evaluation in accordance with standardised protocols and tools reflecting the state of the art, including conducting and documenting adversarial testing of the model with a view to identifying and mitigating systemic risks;
   2. assess and mitigate possible systemic risks at Union level, including their sources, that may stem from the development, the [placing on the market](https://headlesslaw.com/definitions/ai-act/placing-on-the-market/), or the use of general-purpose AI models with systemic risk;
   3. keep track of, document, and report, without undue delay, to the [AI Office](https://headlesslaw.com/definitions/ai-act/ai-office/) and, as appropriate, to national competent authorities, relevant information about serious incidents and possible corrective measures to address them;
   4. ensure an adequate level of cybersecurity protection for the [general-purpose AI model](https://headlesslaw.com/definitions/ai-act/general-purpose-ai-model/) with systemic risk and the physical infrastructure of the model.
2. Providers of general-purpose AI models with systemic risk may rely on codes of practice within the meaning of [Article 56](/mica.wtf/ai-act/chapter-v-general-purpose-ai-models-art.-51-56/56.md) to demonstrate compliance with the obligations set out in paragraph 1 of this Article, until a [harmonised standard](https://headlesslaw.com/definitions/ai-act/harmonised-standard/) is published. Compliance with European harmonised standards grants providers the presumption of conformity to the extent that those standards cover those obligations. Providers of general-purpose AI models with systemic risks who do not adhere to an approved code of practice or do not comply with a European harmonised standard shall demonstrate alternative adequate means of compliance for assessment by the Commission.
3. Any information or documentation obtained pursuant to this Article, including trade secrets, shall be treated in accordance with the confidentiality obligations set out in [Article 78](/mica.wtf/ai-act/chapter-ix-post-market-monitoring-information-sharing-and-market-surveillance-art.-72-94/78.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.mica.wtf/mica.wtf/ai-act/chapter-v-general-purpose-ai-models-art.-51-56/55.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.