Review official alerts, published area descriptions, timing changes, and source evidence in one maintained release.
Buyer decisionWhich published alerts and timing changes should our operations team review?
The public contract describes the normalized record and decision boundary. Current alert rows and customer geographies remain private.
| Field group | Included evidence | Decision use |
|---|---|---|
| Alert identity | Official identifier, event type, issuing office, and source URL | Preserve provenance and eliminate duplicate notices |
| Geography | Affected zones and declared area description | Review the published area; exact facility and route matching requires configuration |
| Operational state | Severity, urgency, certainty, onset, effective, and expiry times | Order review and identify timing changes |
| Change state | New, updated, persisted, or ended | Separate new work from already reviewed alerts |
The amount below is Introductory pricing for the stated recurring scope.
Review official alerts and save filters for published area names.
For larger operating footprints and ongoing configuration support.
For systems that need authenticated release checks and watchlist delivery.
The standard subscription provides release files and saved text filters. Exact facility, route, or polygon overlap requires your locations and a separately configured geographic rule; it is not inferred from a text match.
Every matched alert remains traceable to an official record and the approved customer geography.
Retrieve NWS alerts with required source identification and rate-conscious caching.
Preserve alert identity, zones, area description, severity, urgency, certainty, and timestamps.
Evaluate only the facility, route, or operating area agreed with the buyer.
Separate new, updated, persistent, and ended alerts.
Publish populated or valid empty releases only after freshness, evidence, integrity, and delivery checks pass.