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

# Regulatory technical standards (RTS)

Regulatory technical standards (RTS) — MiFIR (25 instruments).

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

* [2016/2020 — RTS — Criteria for determining whether derivatives should be subject to the trading obligation \[in force\]](/mifir/level-2/rts/2016-2020-criteria-for-determining-whether-derivatives-subject-to-the.md)
* [2016/2021 — RTS — Access in respect of benchmarks \[in force\]](/mifir/level-2/rts/2016-2021-access-in-respect-of-benchmarks.md)
* [2016/2022 — RTS — Information for registration of third-country firms \[in force\]](/mifir/level-2/rts/2016-2022-regulatory-technical-standards-concerning-the-information.md)
* [2017/572 — RTS — Specification of the offering of pre-and post-trade data \[in force\]](/mifir/level-2/rts/2017-572-the-specification-of-the-offering-of-pre-and-post-trade.md)
* [2017/577 — RTS — Volume cap mechanism and the provision of information \[in force\]](/mifir/level-2/rts/2017-577-the-volume-cap-mechanism-and-the-provision-of-information.md)
* [2017/579 — RTS — Direct, substantial and foreseeable effect of derivative contracts within the Union \[in force\]](/mifir/level-2/rts/2017-579-the-direct-substantial-and-foreseeable-effect-of.md)
* [2017/580 — RTS — Maintenance of relevant data relating to orders in financial instruments \[in force\]](/mifir/level-2/rts/2017-580-the-maintenance-of-relevant-data-relating-to-orders-in.md)
* [2017/581 — RTS — Clearing access in respect of trading venues and central counterparties \[in force\]](/mifir/level-2/rts/2017-581-clearing-access-in-respect-of-trading-venues-and-central.md)
* [2017/582 — RTS — Obligation to clear derivatives traded on regulated markets and timing of acceptance for clearing \[in force\]](/mifir/level-2/rts/2017-582-the-obligation-to-clear-derivatives-traded-on-regulated.md)
* [2017/583 — RTS — Transparency requirements for trading venues and investment firms in respect of bonds \[in force\]](/mifir/level-2/rts/2017-583-transparency-requirements-for-trading-venues-and-investment.md)
* [2017/585 — RTS — Data standards and formats for financial instrument reference data and technical measures \[in force\]](/mifir/level-2/rts/2017-585-the-data-standards-and-formats-for-financial-instrument.md)
* [2017/587 — RTS — Transparency requirements for trading venues and investment firms in respect of shares \[in force\]](/mifir/level-2/rts/2017-587-transparency-requirements-for-trading-venues-and-investment.md)
* [2017/590 — RTS — Reporting of transactions to competent authorities \[in force\]](/mifir/level-2/rts/2017-590-the-reporting-of-transactions-to-competent-authorities.md)
* [2017/2154 — RTS — Indirect clearing arrangements \[in force\]](/mifir/level-2/rts/2017-2154-indirect-clearing-arrangements.md)
* [2017/2417 — RTS — Trading obligation for certain derivatives \[in force\]](/mifir/level-2/rts/2017-2417-the-trading-obligation-for-certain-derivatives.md)
* [2021/529 — RTS — Amending 2017/583 as regards adjustment of liquidity thresholds \[in force\]](/mifir/level-2/rts/2021-529-commission-delegated-regulation-eu-2021-529-of-18.md)
* [2022/629 — RTS — Amending 2017/583 as regards adjustment the liquidity thresholds \[in force\]](/mifir/level-2/rts/2022-629-commission-delegated-regulation-eu-2022-629-of-12-january.md)
* [2022/749 — RTS — Amending 2017/2417 as regards the transition to new benchmarks \[in force\]](/mifir/level-2/rts/2022-749-commission-delegated-regulation-eu-2022-749-of-8-february.md)
* [2023/944 — RTS — Amending and correcting 2017/587 as regards transparency requirements for equity instruments \[in force\]](/mifir/level-2/rts/2023-944-amending-and-correcting-the-regulatory-technical-standards.md)
* [2023/945 — RTS — Amending 2017/583 as regards certain transparency requirements applicable to transactions in non-equity instruments \[in force\]](/mifir/level-2/rts/2023-945-amending-the-regulatory-technical-standards-laid-down-in.md)
* [2025/1143 — RTS — Authorisation and organisational requirements for approved publication arrangements and approved reporting mechanisms \[in force\]](/mifir/level-2/rts/2025-1143-commission-delegated-regulation-eu-2025-1143-of-12-june.md)
* [2025/1155 — RTS — Input and output data of consolidated tapes \[in force\]](/mifir/level-2/rts/2025-1155-commission-delegated-regulation-eu-2025-1155-of-12-june.md)
* [2025/1156 — RTS — Obligation to make market data available to the public on a reasonable commercial basis \[in force\]](/mifir/level-2/rts/2025-1156-commission-delegated-regulation-eu-2025-1156-of-12-june.md)
* [2025/1246 — RTS — Transparency requirements for trading venues and investment firms in respect of bonds \[in force\]](/mifir/level-2/rts/2025-1246-commission-delegated-regulation-eu-2025-1246-of-18-june.md)
* [2026/392 — RTS — Amending 2017/577 as regards the volume cap and the provision of information \[in force\]](/mifir/level-2/rts/2026-392-commission-delegated-regulation-eu-2026-392-of-20.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/mifir/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.