Regulatory Snapshot docs
Regulatory Snapshot is a horizon-scanning workspace. You configure the jurisdictions and regulatory areas that matter to you, run a scan, and a few minutes later read the result as a dated, cited briefing: a pressure heatmap, an executive narrative, trends, a deadline timeline, and a per-item audit trail. Re-running the same scope tracks what has changed between runs, and Studio turns any scan into shareable artefacts — decks, tearsheets, infographics, audio and video. Everything the app does with scans is also reachable over a JSON API.
These docs cover the two ways in, plus the shared vocabulary:
Common starting points
- Your first scan — the order form walked end-to-end, from empty state to reading the result.
- The app at a glance — the tab bar, the More menu, the ticker, filters, and how the surfaces fit together.
- Reading the Overview — the executive hero, the four editorial panels, the pressure heatmap, and the Change Monitor.
- Make your first API request — create a key, run a scan, poll it, download an export.
- Authentication — how bearer keys work and how to rotate them.
- Scans and snapshots — the lifecycle both the app and the API share.
One model, two doors
The product and the API expose the same objects. A scan is a run; it produces a snapshot — the dated, self-contained result holding items, trends, an executive summary and a source index. Identical-scope re-runs group into a series, which is what change tracking reads. The dashboard tabs are different readings of one loaded snapshot; every Studio artefact and API export derives from one named snapshot. Concepts explains this model in plain terms — ten minutes there makes both doors easier.
Scope
These pages document what you can reach through the product and the public /v1 API — no more. How scans are computed, and the engineering behind the product, is deliberately out of scope. For terminology, the glossary is the fast path; every page cross-links its neighbours.