Use Signal Awareness to keep checking known companies for new, dated activity. A monitor stores the company scope, cadence, research instructions, and delivery settings.

Bulk monitor creation supports up to 500 monitors per request.

The full API, SDK, and MCP lifecycle also supports a UTC five-field cron schedule for hourly intervals, daily runs, day intervals, weekly runs, and monthly days 1–28. Signal acquisition always uses the fixed Company Signal Enrichment evidence policy: the caller cannot choose a provider, model, signal type, research prompt, or lookback for a monitor.

From the UI, API, or MCP you can list monitors, change their scope or settings, run one immediately, pause/update it, or delete it. The MCP also supports monitor export, output settings, webhook testing, and sending a saved export.

Each qualifying signal keeps its company identity, event date, source URL, and monitor provenance. Open My Data → All signals to review evidence across runs and use the date filters to distinguish new activity from older saved findings.

Test a webhook before relying on scheduled delivery. Treat a successful HTTP delivery as transport confirmation—not proof that a downstream CRM or workflow completed its own processing. Preserve the Signaliz run or export receipt for recovery.

If you only need one immediate check for one domain, use Company Signal Enrichment.