> 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-iii-high-risk-ai-systems-art.-6-49/29.md).

# Art. 29 — Application of a conformity assessment body for notification

1. [Conformity assessment](https://headlesslaw.com/definitions/ai-act/conformity-assessment/) bodies shall submit an application for notification to the [notifying authority](https://headlesslaw.com/definitions/ai-act/notifying-authority/) of the Member State in which they are established.
2. The application for notification shall be accompanied by a description of the conformity assessment activities, the conformity assessment module or modules and the types of AI systems for which the [conformity assessment body](https://headlesslaw.com/definitions/ai-act/conformity-assessment-body/) claims to be competent, as well as by an accreditation certificate, where one exists, issued by a national accreditation body attesting that the conformity assessment body fulfils the requirements laid down in [Article 31](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/31.md).

   Any valid document related to existing designations of the applicant [notified body](https://headlesslaw.com/definitions/ai-act/notified-body/) under any other Union harmonisation legislation shall be added.
3. Where the conformity assessment body concerned cannot provide an accreditation certificate, it shall provide the notifying authority with all the documentary evidence necessary for the verification, recognition and regular monitoring of its compliance with the requirements laid down in [Article 31](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/31.md).
4. For notified bodies which are designated under any other Union harmonisation legislation, all documents and certificates linked to those designations may be used to support their designation procedure under this Regulation, as appropriate. The notified body shall update the documentation referred to in paragraphs 2 and 3 of this Article whenever relevant changes occur, in order to enable the authority responsible for notified bodies to monitor and verify continuous compliance with all the requirements laid down in [Article 31](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/31.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-iii-high-risk-ai-systems-art.-6-49/29.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.