> For the complete documentation index, see [llms.txt](https://www.headlesslaw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.headlesslaw.com/mar/chapters/4.md).

# Chapter 4 — ESMA and competent authorities

Articles 22–29 of Regulation (EU) No 596/2014 (MAR).

* [Article 22 — Competent authorities](/mar/articles/22.md)
* [Article 23 — Powers of competent authorities](/mar/articles/23.md)
* [Article 24 — Cooperation with ESMA](/mar/articles/24.md)
* [Article 25 — Obligation to cooperate](/mar/articles/25.md)
* [Article 25a — Mechanism to exchange order data](/mar/articles/25a.md)
* [Article 25b — Collaboration platforms](/mar/articles/25b.md)
* [Article 26 — Cooperation with third countries](/mar/articles/26.md)
* [Article 27 — Professional secrecy](/mar/articles/27.md)
* [Article 28 — Data protection](/mar/articles/28.md)
* [Article 29 — Disclosure of personal data to third countries](/mar/articles/29.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.headlesslaw.com/mar/chapters/4.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.