Check whether your country, your regulations and your sector are covered today. Each answer names its source and clears a licence audit before we serve it — and every figure here is read live from that data, not written as marketing copy.
figures read from coverage.json · file generated 2026-07-25
Ask by country, by framework, or by sector — the same three scopes your AI agent uses against the gateway. Only what is live and licence-audited appears; grey means not covered.
The EU-level regulation, guidance and supervisory content every member state inherits (17 corpora) — the live facets are listed here. That's the “+ EU” you see on member-state answers.
Read from coverage.json (generated 2026-07-25). A scope appears only when its corpus is live and its source-licensing audit is GREEN; EU-level coverage applies in member states via the EU corpus, independent of national tiles.
Your AI client connects once, over OAuth. The gateway routes each call to the servers in scope; the answers come from the sources, not from a model.
National law and EU regulation, segmented to article level. 332,420 laws serving across 46 audited jurisdictions — 5.7M provisions in the live tier.
The supervisory layer above the statute. Calls are routed by country and sector to the regulators your business actually answers to.
Vulnerability intelligence, threat modeling, sanctions, OWASP, and the security frameworks your controls map to.
Already in our corpus, currently in licensing audit, content validation, or structural recovery.
What we cover for each sector — regulations and standards a live, source-licensed corpus serves today. Standards are surfaced as requirement mapping, not reproduced text. Premium adds case law and agency guidance.
AppSec, infrastructure security, and product-security obligations.
EU AI Act role classification, obligations, and conformity readiness.
DPIA, privacy-by-design, transfers, and data-subject rights — grounded in GDPR.
Procurement lawfulness, public-body AI duties, and administration compliance.
DORA, MiCA, PSD2 and the prudential stack — at article level, with the technical standards.
Vehicle cybersecurity engineering, TARA, and type-approval evidence.
Drone operations, product security, threat modelling, and counter-UAS.
Autonomous-machinery safety and the AI duties that ride on top.
Medical-device regulation, clinical data, and special-category privacy.
OT security, robot-cell safety, and live ICS advisory enrichment.
Robot and cobot safety, machinery conformity, and the security of the robot stack.
Railway cybersecurity and signalling safety, from CLC/TS 50701 zones to the safety case.
Grid and generation compliance, anchored on NIS2 essential-entity duties.
Sustainability reporting and the EU green-finance taxonomy, at article level.
National regulatory-authority decisions and NIS2 operator obligations.
Aviation-information-security regulation and national security-protection law.
Listed only where a live MCP serves the corpus and its source licensing is GREEN. Per the No Silent Fallbacks policy, planned coverage is in the "in development" list, not above.
This page maps what you query directly through the gateway — corpora that cleared source-licensing review and come back clause by clause, with a citation. Some of what our work rests on can’t be served that way. It still shapes the answer; it reaches you as advice and synthesis, not a feed you pull.
The corpora on this page. Licensed to reproduce, addressable to the clause, returned in the same citation envelope as every other Ansvar source. You query them; you cite them.
Sources we can reference but not republish — licensed standards we map to controls rather than reproduce, confidential engagement material, method that was never a document. We hold these off the gateway and put them to work in our consultancy and delivery, as synthesis, attributed to where it came from.
We never dress synthesis up as a source you could have pulled yourself, and we never serve licensed text we can’t defend. When a point rests on advice rather than a citeable provision, it says so.
What we can’t expose as data, we still bring to the work.
Every framework, jurisdiction, and sector above has cleared source-licensing review. We add new corpora when a real customer workflow needs them and the licensing audit closes — we'd rather say "not yet" than serve content we can't defend.
Tell us the source, the workflow it would unlock, and any license terms you already know about. We come back with an honest read on whether we can host it and roughly how long the licensing review would take.
One MCP connection to gateway.ansvar.eu — Claude, Claude Code, Cursor, VS Code Copilot, or Open WebUI. Free tier: 100 searches a day with a B2B sign-up.