> 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/mifid-ii/level-2/rts.md).

# Regulatory technical standards (RTS)

Regulatory technical standards (RTS) — MiFID II (25 instruments).

Regulatory technical standards (RTS) under MiFID II, ordered by official identifier.

* [2017/566 — RTS — Ratio of unexecuted orders to transactions in order to prevent disorderly trading conditions \[in force\]](/mifid-ii/level-2/rts/2017-566-the-ratio-of-unexecuted-orders-to-transactions-in-order-to.md)
* [2017/568 — RTS — Admission of financial instruments to trading on regulated markets \[in force\]](/mifid-ii/level-2/rts/2017-568-the-admission-of-financial-instruments-to-trading-on.md)
* [2017/569 — RTS — Suspension and removal of financial instruments from trading \[in force\]](/mifid-ii/level-2/rts/2017-569-the-suspension-and-removal-of-financial-instruments-from.md)
* [2017/570 — RTS — Determination of a material market in terms of liquidity \[in force\]](/mifid-ii/level-2/rts/2017-570-the-determination-of-a-material-market-in-terms-of.md)
* [2017/571 — RTS — Authorisation, organisational requirements and the publication of transactions for data reporting services providers \[in force\]](/mifid-ii/level-2/rts/2017-571-the-authorisation-organisational-requirements-and-the.md)
* [2017/573 — RTS — Requirements to ensure fair and non-discriminatory co-location services and fee structures \[in force\]](/mifid-ii/level-2/rts/2017-573-requirements-to-ensure-fair-and-non-discriminatory.md)
* [2017/574 — RTS — Level of accuracy of business clocks \[in force\]](/mifid-ii/level-2/rts/2017-574-the-level-of-accuracy-of-business-clocks.md)
* [2017/575 — RTS — Data to be published by execution venues on the quality of execution of transactions \[in force\]](/mifid-ii/level-2/rts/2017-575-regulatory-technical-standards-concerning-the-data-to-be.md)
* [2017/576 — RTS — Annual publication by investment firms of information on the identity of execution venues \[in force\]](/mifid-ii/level-2/rts/2017-576-the-annual-publication-by-investment-firms-of-information.md)
* [2017/578 — RTS — Requirements on market making agreements and schemes \[in force\]](/mifid-ii/level-2/rts/2017-578-the-requirements-on-market-making-agreements-and-schemes.md)
* [2017/584 — RTS — Organisational requirements of trading venues \[in force\]](/mifid-ii/level-2/rts/2017-584-organisational-requirements-of-trading-venues.md)
* [2017/586 — RTS — Exchange of information between competent authorities when cooperating in supervisory activities \[in force\]](/mifid-ii/level-2/rts/2017-586-the-exchange-of-information-between-competent-authorities.md)
* [2017/588 — RTS — Tick size regime for shares, depositary receipts and exchange-traded funds \[in force\]](/mifid-ii/level-2/rts/2017-588-the-tick-size-regime-for-shares-depositary-receipts-and.md)
* [2017/589 — RTS — Organisational requirements of investment firms engaged in algorithmic trading \[in force\]](/mifid-ii/level-2/rts/2017-589-the-organisational-requirements-of-investment-firms-engaged.md)
* [2017/591 — RTS — Application of position limits to commodity derivatives \[in force\]](/mifid-ii/level-2/rts/2017-591-the-application-of-position-limits-to-commodity-derivatives.md)
* [2017/592 — RTS — When an activity is ancillary to the main business \[in force\]](/mifid-ii/level-2/rts/2017-592-the-criteria-to-establish-when-an-activity-is-considered-to.md)
* [2017/1018 — RTS — Information to be notified by investment firms, market operators and credit institutions \[in force\]](/mifid-ii/level-2/rts/2017-1018-information-to-be-notified-by-investment-firms-market.md)
* [2017/1943 — RTS — Information and requirements for the authorisation of investment firms \[in force\]](/mifid-ii/level-2/rts/2017-1943-information-and-requirements-for-the-authorisation-of.md)
* [2017/1946 — RTS — Information to be included by proposed acquirers \[in force\]](/mifid-ii/level-2/rts/2017-1946-an-exhaustive-list-of-information-to-be-included-by.md)
* [2018/63 — RTS — Authorisation, organisational requirements and the publication of transactions for data reporting services providers \[in force\]](/mifid-ii/level-2/rts/2018-63-amending-the-authorisation-organisational-requirements.md)
* [2022/1299 — RTS — Content of position management controls by trading venues \[in force\]](/mifid-ii/level-2/rts/2022-1299-commission-delegated-regulation-eu-2022-1299-of-24-march.md)
* [2022/1302 — RTS — Application of position limits to commodity derivatives \[in force\]](/mifid-ii/level-2/rts/2022-1302-commission-delegated-regulation-eu-2022-1302-of-20-april.md)
* [2022/2402 — RTS — Correcting certain language versions of 2017/1018 \[in force\]](/mifid-ii/level-2/rts/2022-2402-commission-delegated-regulation-eu-2022-2402-of-16-august.md)
* [2023/960 — RTS — Amending 2017/588 as regards the annual application date of the calculations \[in force\]](/mifid-ii/level-2/rts/2023-960-commission-delegated-regulation-eu-2023-960-of-1-february.md)
* [2026/136 — RTS — Correcting the Swedish language version of 2022/1302 \[in force\]](/mifid-ii/level-2/rts/2026-136-commission-delegated-regulation-eu-2026-136-of-8-october.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/mifid-ii/level-2/rts.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.