Product

One platform for regulatory signals: detect, understand, act.

RegSignal watches 96 active official sources across 21 jurisdictions, classifies every publication into one vocabulary, scores it against your products, and pushes the result into the systems your team already uses.

Request access Explore the console

Built for regulatory, quality and compliance teams

Food & beverage
Supplements
Cosmetics
Pharma
Medical devices
Consumer products
Chemicals & packaging

How RegSignal works

Four steps from an official publication to work your team can own.

Surface the signals that matter

A continuously updated feed of official publications: federal registers, agency pages, gazettes, RSS feeds and WTO notifications across 21 jurisdictions, in the original language.

A feed from 96 active official sources, each polled on its own cadence
Keyset pagination and updated_after for incremental sync that never misses an item
Multilingual semantic search over the whole corpus with POST /v1/signals/search, and summaries translated on demand into 15 languages
Your own supplier notices and internal documents ingested as private signals
Per-jurisdiction freshness and verification status on the coverage grid

Turn publications into decisions

Every signal is classified into one controlled vocabulary, summarised, scored against your product profiles and ready to be asked about.

Classification into 7 verticals, 67 product categories and 19 topics, each with a confidence score
Summaries and key points, plus effective dates and comment deadlines
Impact matching against product profiles: heuristic-first scoring, then an AI assessment with rationale and required actions
Ask answers with citations that resolve to the exact source passage, and says so when the evidence is insufficient

Move the work forward

Matches land in an inbox your team can triage, and in the systems you already run, through signed webhooks, SDKs and a REST API.

Impact inbox with owners, due dates, statuses and bulk triage
Signed webhooks for signal.created, signal.updated and impact.matched, with retries, backoff and a delivery log per endpoint
Saved filters for the views your team returns to
Slack and Microsoft Teams notifications, and Jira and ServiceNow tickets raised from impact matches
SDKs for Python and TypeScript, a REST API with 98 paths under /v1, and an MCP server for AI assistants

Built for enterprise teams

Roles, isolation and traceability are enforced by the API on every request, not bolted onto the console.

Organisation roles (owner, admin, analyst, viewer) enforced per endpoint, with a permission matrix in the console
Tenant isolation: internal signals are visible only to the organisation that submitted them, in the feed, search, Ask, impact matching and webhooks alike
Every classification records model, provider and confidence; every answer cites its sources
API keys created and revoked in the console; each key is shown once and acts as analyst
Supabase Auth with magic link, Google and SAML 2.0 single sign-on
Audit log of every change, with actor, action, target and request id

SOC 2 Type I is in progress, not yet audited. We do not list certifications we do not hold.

Value from day one

Coverage, one vocabulary and delivery are there the day you get a key, not after a rollout.

21jurisdictions
96active official sources
7verticals
98API paths
3webhook events
2SDKs

Counts from the source registry, taxonomy and API reference, September 2026.

Built with your team in mind

Twelve modules in one console, each backed by the same API you can call yourself.

Signals feed

The table every analyst starts from: official publications from 21 jurisdictions, newest first, filterable by jurisdiction, vertical, topic, document type and date. Open any row for the summary, classification and source link.

Keyset pagination with updated_after for incremental sync
Facets for jurisdictions, verticals, topics and document types
Multilingual semantic search, with summaries translated on demand into 15 languages
Detail drawer with summary, key points, chips and confidence

See it in the console

Sources and coverage

101 official sources in the registry, 96 of them active, across 21 jurisdictions, each registered with its publisher, adapter, cadence and verification status. The coverage grid shows how fresh each jurisdiction is and which sources feed it.

Federal Register, WTO ePing, JSON APIs, RSS feeds and HTML listings
Per-source cadence, last run, last status and verification flag
Sources sheet per jurisdiction with links to the publisher
GET /v1/jurisdictions/coverage and GET /v1/sources

See it in the console

Internal documents

Supplier notices, lab reports and internal memos become signals with one POST. They are enriched like official publications and never leave your organisation.

POST /v1/signals with title, text and jurisdiction
Synchronous or queued enrichment
Visible only to your organisation in feed, search, Ask, impact matching and webhooks
Remove at any time with DELETE /v1/signals/{id}

See it in the console

Classification

Each publication is classified into one controlled vocabulary: 7 verticals, 67 product categories, 19 topics and 9 document types. Slugs are validated against the taxonomy, never free-form.

Verticals, categories, topics, affected markets and dates
Confidence score on every classification
Model and provider recorded on every result
POST /v1/classify for your own text

See it in the console

Impact matching

Every new signal is scored against your active product profiles. A heuristic pass on markets, verticals, categories and topics runs first; the top candidates get an AI assessment.

Levels high, medium, low and none, with a numeric score
Rationale and required actions on every match
Runs automatically from the worker or on demand per profile
Stateless POST /v1/impact/match for ad-hoc checks

See it in the console

Ask

Ask a question in plain language and get an answer grounded in the corpus, with citations that resolve to a document, URL and chunk. When the evidence is not there, it says so.

Filtered retrieval by jurisdiction, vertical and date
Citations resolve to the source passage
Explicit insufficient-evidence responses instead of guesses
Your internal signals included, for your organisation only

See it in the console

Webhooks

Subscribe an endpoint to signal.created, signal.updated or impact.matched with a filter, and receive signed deliveries with retries and a log you can inspect.

HMAC-SHA256 X-RegSignal-Signature over timestamp and body
Exponential backoff, up to 8 attempts per delivery
Test deliveries and secret rotation from the console
Delivery log per endpoint via GET /v1/webhooks/{id}/deliveries

See it in the console

Enterprise foundation

Governance, traceability and connectivity, without a services engagement.

Governance

Who can see and change what is decided once, enforced by the API everywhere.

Four roles: owner, admin, analyst, viewer, enforced per endpoint
Every triage action stamps status, owner, due date, notes and time on the match
Organisation settings, invitations and API keys managed by admins and owners
Audit log of every change, readable by analysts and exportable as CSV by admins

Traceability

Nothing in RegSignal is an unexplained number. Every output points back to where it came from.

Every signal links to the official source URL
Every answer cites the document, URL and chunk it relied on
Every classification records model, provider and confidence
Every webhook delivery is logged with attempts, status and response time

Connectivity

One REST API, optionally behind a Kong gateway, documented like a product and wrapped in SDKs.

REST under /v1 with an OpenAPI 3 spec
Python and TypeScript SDKs, including the webhook verifier
Signed webhooks, Slack and Teams notifications, Jira and ServiceNow connectors
MCP server exposing signals, Ask and impact as read-only tools

Read the API reference

See it in action

Request access Explore the console

One platform for regulatory signals: detect, understand, act.

How RegSignal works

Surface the signals that matter

Turn publications into decisions

Move the work forward

Built for enterprise teams

Coverage, one vocabulary and delivery are there the day you get a key, not after a rollout.

Built with your team in mind

Signals feed

Sources and coverage

Internal documents

Classification

Impact matching

Impact inbox

Ask

Webhooks

Saved filters

Product profiles

Members and roles

API keys and usage

Enterprise foundation

Governance

Traceability

Connectivity

See it in action