Quick tips

A 3-minute read for new subscribers. Once your agent is connected through Setup, the snippet below tells it to query the Ansvar gateway instead of answering from training data — and the rest of the page covers what to ask, how to verify the agent is grounded, and where to send feedback when a source is missing.

1. Paste this into your agent's system prompt

Drop the block below into your system prompt, custom instructions, or agent-instructions field. One snippet works across Claude (web + Desktop), Claude Code, VS Code Copilot, and Cursor — no per-agent variant is needed. When you're ready for the full version — query craft, retries, and output discipline — Instruct your agent carries it.

For any question about EU/EEA law, regulatory compliance, or
cybersecurity controls (GDPR, NIS2, AI Act, DORA, ISO 27001,
sector-specific regulation, national implementations), call the
Ansvar Gateway tools before answering — never from memory.

Always scope search: jurisdictions=["SE"] (your market; add "EU"
for EU regulation) or frameworks=["GDPR"]. Never pass the whole
question as the query — reduce it to 1-3 legal key terms in the
language of the law you are searching (Swedish terms for Swedish
law); try alternative terms as separate searches.

Quote article numbers, paragraph numbers, and authority names
verbatim from the tool output. For questions that touch both an
EU framework and a Member State (e.g. "Swedish law on…", "how
does Germany implement…"), issue at least one Gateway call per
regime — one for the EU instrument, one for each national
jurisdiction — before composing the answer.

If a search returns nothing, retry before concluding there is
nothing: a synonym or the law's own term for the concept first,
still in the law's language, then one search per concept.
Whenever a response reports withheld relaxed matches
(meta.broadening_available is true, or meta.message says so),
tell the user and offer a re-run with allow_broadening=true;
re-run only if they accept, and label any relaxed matches as
such. Never set allow_broadening on your own. Relaxed matches
are frequently off-topic, so present them as unverified leads
for a human to check, never as the answer.

If those retries also return no result:
state which queries you ran, that they returned zero results,
and that you will not substitute training-data recall. Do not
name supervisory authorities, statute numbers, or timelines
unless they appear in a tool result.

2. Which question goes to which tool

Tier links go to pricing.

The tier ladder behind the table:

• Free — €0, sign in with Microsoft, Google or email. Search scoped to one jurisdiction or one framework per question, 100 search calls / day, 3 concurrent requests. No fan-out. One workflow run a month on a system you describe — threat model, gap analysis (incl. NIS2, DORA, CRA, EU AI Act) or DPIA — reported as a watermarked render or JSON.
• Solo — 750 search calls / day, 4 concurrent requests. Multi-source fan-out across the full fleet — every jurisdiction in one question. Shows when case law exists; reading it is Premium. Two workflow runs a month from the same seven types as Free, watermarked render or JSON.
• Premium — 5,000 search calls / day / seat, 5 concurrent requests. The legal evidence layer: case law, preparatory works, and agency guidance inside search — plus 5 workflow runs a month on a system you describe (STRIDE, LINDDUN, TARA), reported as structured JSON; rendered exports start at Team.
• Team — adds workflows on your own documents (gap analysis, DPIA, tender review, and more — run list_workflow_types for the live list), 16 concurrent requests. Self-serve at €490/seat/month — see pricing.
• Company — adds the tamper-evident audit ledger (the ledger is Company-only), 64 concurrent requests. Not self-serve.

Tools above your tier are absent from tools/list and return JSON-RPC -32601 if called anyway; quota and cap overruns return JSON-RPC -32000 with data.cause = "cap_exceeded". start_workflow itself is visible on every tier — a refusal there names the reason (a workflow type outside your plan, or the monthly allowance spent); it is a tier fence on types and runs, not an outage.

Using Ansvar, check the available financial-regulation sources for Ireland and the EU. List the served scope and any gaps before researching a payment institution's question. Keep national and EU sources separate.

Using Ansvar, retrieve DORA Article 30 and relevant served technical standards for an ICT contract review. Cite each source and distinguish retrieved text from your interpretation. Leave unsupported conclusions unresolved.

Using Ansvar, research MiCA CASP authorisation for a firm in France. Find the EU provisions and available French sources, cite them, and identify questions the served material cannot answer.

Using Ansvar, find ECB and EIOPA guidance available for ICT risk in banks and insurers. Keep the authority, publication type and source link with each finding. Report missing sources or access restrictions before drawing conclusions.

Using Ansvar, check whether gap_analysis_dora and document upload are available to my account. If available, run a DORA gap analysis using the policies and ICT contracts I choose to upload. Cite the supporting document paragraphs and regulatory sources, and leave missing evidence unresolved. If access or sources are unavailable, report that and stop.

3. How to tell the agent did (or didn't) ground its answer

Grounded looks like: article numbers (GDPR Art. 32(1)(b)), authority names (Datatilsynet, EDPB), a source_url to a .gov, .europa.eu, or recognised publisher domain, and a named MCP in the response (via danish-law).

Not grounded looks like: hedge words (generally, typically, in most cases), no article numbers, no source URLs, no MCP name.

One-line check. Paste this if you're unsure:

Which Ansvar MCP did you query, and which article number is this from? If you didn't query the Gateway, say so explicitly.

4. Report a missing source

Spot a law, regulator, or dataset Ansvar should cover and doesn't? Tell us — we triage source requests weekly.

• Email: team@ansvar.eu (suggested subject: Missing source)
• See what's already covered: /coverage — the "In active development" stripe lists what's being built next, and "Suggest a source" takes requests for anything missing.