AI Act Actor Hub.
Obligations, split by who owes them.
Every obligation in the AI Act is addressed to a specific actor. A provider does not carry a deployer's duties. An importer does not carry a notified body's. So pick your role and read only what it owes, instead of parsing all 113 articles. Each page comes from RuleMesh's rule graph of CELEX 32024R1689: every obligation paragraph, Annex block, and GDPR cross-reference.
Choose an actor
11 of 11 liveDevelops an AI system or GPAI model and places it on the market under its own name or trademark.
134 obligation paragraphs →
Uses an AI system under its authority in a professional context.
27 obligation paragraphs →
Places a high-risk AI system from a third country on the EU market.
8 obligation paragraphs →
Makes a high-risk AI system available on the EU market without altering it.
7 obligation paragraphs →
EU-based entity mandated by a third-country provider.
7 obligation paragraphs →
Puts a high-risk AI system into service or uses it in its own name.
1 obligation paragraphs →
Conformity assessment body designated by a national notifying authority.
39 obligation paragraphs →
National authority responsible for market surveillance of AI systems.
26 obligation paragraphs →
Authority designated by each Member State to supervise application of the AI Act.
22 obligation paragraphs →
National authority responsible for setting up and carrying out notification of conformity assessment bodies.
16 obligation paragraphs →
EU body within the Commission overseeing general-purpose AI model governance.
18 obligation paragraphs →
The MCP delivers GDPR and the EU AI Act today.
This hub is a reference. What RuleMesh delivers is the structured IT requirements behind a regulation: the specific, testable things engineers and AI agents implement, pulled through an MCP your coding agent already speaks. GDPR and the EU AI Act are both live today, and they ride on the same engineering work. Point your agent at either one and you have a head start on the other.