Monitoring subscriptions

A subject is only monitored while your tenant holds an active subscription with a valid legal basis attached. Monitoring is never automatic or on-by-default — it’s an explicit relationship you start, and it has to be backed by a reason you’re allowed to keep watching that subject. See Compliance notes for what counts as a legal basis.

What monitoring actually does

Once a subject has an active subscription, Gungner:

• Watches for upstream changes — company register notifications, person register updates, sanctions and PEP list changes.
• Runs scheduled full refreshes at a cadence appropriate to the subject’s risk — more frequent for higher-risk subjects.
• Emits the change events described in Events and webhooks whenever something changes.

Gungner’s job stops at detecting and delivering changes with their evidence. What a change means for risk — re-rating, opening a review, escalating — is your system’s decision, not Gungner’s. Gungner surfaces facts; you make risk decisions.

Subscription states

State	What it means
active	Currently monitored. Change events flow normally.
suspended	Events pause (for example, non-payment or a lapsed permit). The underlying data is retained, not deleted, so monitoring can resume without re-onboarding the subject.
ended	The relationship is over.

Creating a subscription

Creating and managing subscriptions requires the monitoring:subscribe scope — see Authentication and delegation for how scopes are granted.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"subject_id": "SUBJECT_ID", "kind": "company", "legal_basis": "aml_cdd"}' \
  https://api.gungner.ai/v1/subscriptions

kind is "person" or "company" — whichever the subject is; a company subscription on a person subject (or the reverse) is rejected. legal_basis is one of aml_cdd, contract, legal_obligation, consent, or legitimate_interest — see Compliance notes for what each means in practice.

See the MCP tools reference for the equivalent tool if you’re working through an MCP client instead of REST directly.