One jurisdiction, followed all the way down: the regulation, the Commission layer, and what Berlin, Paris and The Hague do with it. Signed webhooks push changes into your systems, a REST API and an MCP server answer the rest. Every answer carries its primary source.
Free while in beta. No card, no trial timer, no sales call.
The pipeline sweeps ten official sources every 30 minutes. Regulators publish a handful of items a week, so the dates below are their official publication dates; the sweep is what guarantees nothing newer exists that we have not seen. Pulled from the public feed as this page loads, no key involved.
See also: what moved and which act moved it ·
what applies to your role
Same data, three ways:
RSS ·
Atom ·
REST
Regulation (EU) 2026/1744, the Digital Omnibus on AI, amended the AI Act itself. High-risk obligations under Annex III shifted to December 2027, the product-safety route to August 2028, while the labelling of synthetic content moved forward. Anyone who copied the deadline table into a wiki in June has been working from wrong dates ever since.
This is the whole argument for the product in one event. Not a feed you read, a record you query, kept honest against the primary sources. When something moves, the change is logged with the act that caused it, so you can see what it was before.
Read the amending regulation on EUR-Lex
Subscribe to topics like gpai, high-risk,
standards, national-de. Matching updates
arrive as HMAC-signed JSON with exponential-backoff retries. Nothing
to poll, nothing to remember to check.
Query the whole record. Filter by source, severity, topic or article reference. OpenAPI 3 documented, built for backfills, audit trails and dashboards you own.
Drop-in tool for Claude, Cursor or any agent stack. Code scanners find AI usage in your repo. This tells your agent which obligation that usage triggers, and cites the regulation for it.
query_ai_act_updatesget_obligation_for_rolesummarize_changes_sinceA feed only helps on the days something happens. Most of the time the real question is different: given what we ship and the role we play, which obligations are already live and which clock is running?
That question is answerable from the same record, which is why the MCP server exposes it directly. Point an agent at it and let it work through provider versus deployer, Annex III classification, Article 53 duties and the national layer, with a citation to the primary source on every claim.
Where this stands: the sources, the event record and the three MCP
tools are live. The role-by-role obligation model behind
get_obligation_for_role is being built out source by
source, and every entry ships with its citation so you can check it.
We would rather say that plainly than pretend it is finished.
{
"mcpServers": {
"aiactradar": {
"url": "https://mcp.aiactradar.com/mcp/v1",
"headers": {
"Authorization": "Bearer YOUR_BETA_KEY"
}
}
}
}Beta keys are issued by hand, usually within a day of you asking.
The feed and the health endpoint are open. Paste either line and you have seen the product before talking to anyone.
curl https://api.aiactradar.com/feed.xmlcurl https://api.aiactradar.com/v1/health{
"id": "evt_2026_0427_001",
"type": "guidance",
"source": "EU_AI_Office",
"topics": ["gpai", "transparency"],
"severity": "medium",
"title_en": "Updated GPAI Training Data Summary template v2.1",
"title_de": "Aktualisiertes GPAI-Trainingsdaten-Zusammenfassungs-Template v2.1",
"summary_en": "AI Office released revision 2.1 of the public template providers must use to summarise training data under Art. 53(1)(d). Adds fields for synthetic data sources.",
"summary_de": "Das KI-Buero hat Version 2.1 des oeffentlichen Templates veroeffentlicht, mit dem Anbieter Trainingsdaten gemaess Art. 53(1)(d) zusammenfassen muessen. Neue Felder fuer synthetische Datenquellen.",
"url_official": "https://digital-strategy.ec.europa.eu/...",
"ai_act_articles": ["Art. 53(1)(d)"],
"published_at": "2026-04-27T10:00:00Z",
"language_versions": ["en","de","fr","it","es"],
"disclaimer": "Informational content only. Not legal advice."
}There are trackers that cover every AI law on earth at a glance. This is the opposite trade. One regulation, followed to the depth you actually need when you ship into the EU, including the national layer where the work really lands.
Not "Annex III applies" as a single line, but the obligations behind it, article by article, with the trigger that switches each one on and the evidence you are expected to hold. Amendments to the act are tracked as they happen.
AI Office guidance, the GPAI Code of Practice, templates, delegated and implementing acts, harmonised standards as they reach the Official Journal. The material that decides how the text is actually read.
Who supervises you, under which national act, with which sandbox and which penalties. Germany's implementing act took effect on 29 July 2026 and made the Bundesnetzagentur the central authority. That is the layer a global overview leaves out.
Every event carries the official publication it came from, with the time it was fetched and a link to the original. We aggregate and structure, we do not interpret, and we never invent an article reference that is not in the source. If you cannot check it, it does not belong in the record.
Verified and being added next: the AI Act Service Desk feed, the EDPB, the Fundamental Rights Agency, the Court of Justice, and the national regulators of France, Italy and the Netherlands. Two older adapters, EU Have-Your-Say and OECD.AI, are paused for a rebuild and deliberately not counted above. Live per-source status is on the status page.
Roughly five to ten relevant items a week.
EU regulators are not a firehose. If you want volume, this is the wrong product. If you want to stop refreshing EUR-Lex, it is the right one.
Manual onboarding, by a human.
Keys and endpoints are set up by hand during the beta. Slower than self-serve, but you get direct access to the person building it.
Legal advice, or a compliance verdict.
We publish structured facts with citations. What you do with them stays your call, and your counsel's.
We are still proving that a structured AI Act wire is worth building. Until that is settled, the whole thing is free and there is no billing code in your way.
€0/month
Paid plans, eventually
Enrichment and delivery cost real money, so this will not be free forever. It is free until the product has earned a price.
AI Act Radar provides informational content only. It does not constitute legal advice and is not a substitute for qualified legal counsel. Use of this service does not establish any attorney-client or advisory relationship. The content reflects publicly available regulatory and standardisation sources at the time of ingestion and may be incomplete or outdated.
Tell us what you're building and we'll set up your API key and webhook endpoint by hand, usually within a day. Free, no payment details, and you can walk away whenever you like.