> 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-ix-post-market-monitoring-information-sharing-and-market-surveillance-art.-72-94/80.md).

# Art. 80 — Procedure for dealing with AI systems classified by the provider as non-high-risk in appli

1. Where a [market surveillance authority](https://headlesslaw.com/definitions/ai-act/market-surveillance-authority/) has sufficient reason to consider that an [AI system](https://headlesslaw.com/definitions/ai-act/ai-system/) classified by the [provider](https://headlesslaw.com/definitions/ai-act/provider/) as non-high-risk pursuant to [Article 6(3)](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/6.md) is indeed high-risk, the market surveillance authority shall carry out an evaluation of the AI system concerned in respect of its classification as a high-risk AI system based on the conditions set out in [Article 6(3)](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/6.md) and the Commission guidelines.
2. Where, in the course of that evaluation, the market surveillance authority finds that the AI system concerned is high-risk, it shall without undue delay require the relevant provider to take all necessary actions to bring the AI system into compliance with the requirements and obligations laid down in this Regulation, as well as take appropriate corrective action within a period the market surveillance authority may prescribe.
3. Where the market surveillance authority considers that the use of the AI system concerned is not restricted to its national territory, it shall inform the Commission and the other Member States without undue delay of the results of the evaluation and of the actions which it has required the provider to take.
4. The provider shall ensure that all necessary action is taken to bring the AI system into compliance with the requirements and obligations laid down in this Regulation. Where the provider of an AI system concerned does not bring the AI system into compliance with those requirements and obligations within the period referred to in paragraph 2 of this Article, the provider shall be [subject](https://headlesslaw.com/definitions/ai-act/subject/) to fines in accordance with [Article 99](/mica.wtf/ai-act/chapter-xii-penalties-art.-99-101/99.md).
5. The provider shall ensure that all appropriate corrective action is taken in respect of all the AI systems concerned that it has made available on the Union market.
6. Where the provider of the AI system concerned does not take adequate corrective action within the period referred to in paragraph 2 of this Article, [Article 79(5)](/mica.wtf/ai-act/chapter-ix-post-market-monitoring-information-sharing-and-market-surveillance-art.-72-94/79.md) to (9) shall apply.
7. Where, in the course of the evaluation pursuant to paragraph 1 of this Article, the market surveillance authority establishes that the AI system was misclassified by the provider as non-high-risk in order to circumvent the application of requirements in Chapter III, Section 2, the provider shall be subject to fines in accordance with [Article 99](/mica.wtf/ai-act/chapter-xii-penalties-art.-99-101/99.md).
8. In exercising their power to monitor the application of this Article, and in accordance with Article 11 of Regulation (EU) 2019/1020, market surveillance authorities may perform appropriate checks, taking into account in particular information stored in the EU database referred to in [Article 71](/mica.wtf/ai-act/chapter-viii-eu-database-for-high-risk-ai-systems-art.-71/71.md) of this Regulation.


---

# 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-ix-post-market-monitoring-information-sharing-and-market-surveillance-art.-72-94/80.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.
