Regulatory Snapshot

Multi-jurisdiction regulatory horizon scanning for compliance and finance teams. Configure your jurisdictions and topics, run a scan, and a few minutes later you have a structured snapshot of what is on the horizon — heatmap, executive briefing, timeline, trend analysis, and shareable deliverables.

Why Regulatory Snapshot

Tracking regulatory change across multiple jurisdictions usually means thirty browser tabs, a spreadsheet, and the nagging sense you missed something. Regulatory Snapshot replaces that with a single workspace: one configuration, one scan, one structured briefing — and a built-in record of what has changed since you last looked. The same engine that powers the app is exposed as a JSON API for teams that want to embed it in their own systems.

Pick your path

For compliance and research teams → Configure jurisdictions and topics, run scans, read the dashboard, and produce tearsheets, infographics, audio briefings, slide decks, and PDFs in Studio.

For developers → Programmatic access to the same engine over JSON-over-HTTPS. Bearer auth, idempotency, SSE streaming, RFC 9457 errors, and Python + JavaScript SDKs.

Common starting points

• Run your first scan — the wizard, walked through end-to-end with a concrete example.
• Read the dashboard — heatmap, briefing, trends, timeline, detail panel, sources.
• Make your first API request — create a key, run a scan, fetch the snapshot.
• Authentication — how bearer keys work and how to rotate them.
• What an export looks like — tearsheets, infographics, audio, slides, video, PDFs.
• API changelog — versioned history of the public surface.

Core concepts

Both the product and the API share one underlying model: a scan runs an analysis pass and produces a snapshot — items, trends, an executive summary, and a narrative — and on recurring scans, a record of what changed. The Concepts section explains the model in plain terms; both audiences benefit from a quick read.

• What is a snapshot? — the core data model.
• Scans and snapshots — the lifecycle.
• Changes between scans — how Snapshot tracks what is new vs unchanged.

What’s in scope

These docs cover using the product and building against the API. They do not cover internal engineering — model selection, prompt design, benchmark methodology, the contributor workflow — which lives in the source repository. If you are evaluating Regulatory Snapshot for a team, the product guide is the right place to start; if you are integrating, the API reference is.

If you cannot find an answer here, the glossary is a fast lookup for terminology, and every page closes with related links.