Structured alerts, not scraped pages.
Every alert in RegAlytics is a typed record with a stable schema: regulator, sector, jurisdiction, alert type, dates, classifications and the linked relationships that make the dataset addressable. No ‘bring your own regex’, no cleanup, no guessing what the source meant. The normalisation is done by the time the feed reaches you.
One record. Fourteen high-signal fields. Full provenance.
The RegAlytics alert record is intentionally narrow. Every field earns its place. We optimise for the queries GRC products actually run: filter by jurisdiction, group by sector, surface the latest guidance in a topic, stitch a regulator’s enforcement history together.
| Field | Type | Notes |
|---|---|---|
| regalytics_alert_id | string | Canonical identifier, stable across retrievals. |
| title | string | Regulator-published headline, de-duplicated across sources. |
| summary | string | Normalised summary, extracted from the source. |
| agencies | string[] | One or more agency names from the 11,480-regulator set. |
| countries | string[] | ISO-aligned country names, 121 covered. |
| sector_type | string[] | From a controlled vocabulary of 25 sectors. |
| alert_type | string[] | Rulemaking, bulletin, enforcement, guidance, and related types. |
| classification | string[] | Higher-level alert classification for portfolio views. |
| tags | string[] | Topical tags, e.g. artificial intelligence, cyber, ESG. |
| original_publication_date | date | When the regulator published the alert. |
| latest_update | date | When we last detected an upstream change. |
| rule_effective_date | date | When the rule takes force, where applicable. |
The full schema is in the developer docs. The table above shows the fields you’ll reach for most often.
Controlled vocabularies that are also queryable
11,480 agencies. One canonical record per regulator. Onboarded hourly.
121 countries. Coverage across every major jurisdiction, with state-level detail.
25 sectors. A controlled vocabulary that maps onto your own taxonomy.
12+ alert types. Rulemaking, enforcement, guidance, bulletins, consultations.
How the feed stays clean
Freshness
GAWAIN is continuous, not nightly. The moment a regulator posts, the alert enters PERCIVAL and lands in the feed within hours.
Backfill
Historical depth from platform launch for every regulator in coverage. Real time-series for your product.
LADI: linked analytics, not isolated rows.
LADI is the component of ARTHR that ties the dataset together. Every alert carries references to the regulators it came from, the regulations it implements, the jurisdictions it affects and the prior alerts it supersedes.
That graph is what lets your product answer real questions. ‘Everything Ncontracts needs to know about AI regulation in the EU, this quarter’ instead of shipping a flat keyword search.
Build on the data model.
Request sandbox access and we’ll give you scoped access to every production endpoint, with the full schema available to query in minutes.