National Weather Service — Alerts API
What we use it for
Show original issued alert records, geographic areas and expiry times.
What it cannot prove
An alert is not proof of damage to a building. APIs may fail or be delayed.
Review original sourceWe are building a consumer resource from official public weather and preparedness sources, with an existing EmpireOS storm intelligence engine behind the research. Here's exactly what each data source can—and cannot—establish.
Public sources and their limitations are displayed side by side. A linked data source does not make National Storm Hub an official warning service.
Show original issued alert records, geographic areas and expiry times.
An alert is not proof of damage to a building. APIs may fail or be delayed.
Review original sourceShort-range forecast periods for an approximate US ZIP centroid.
Grid forecasts are regional estimates, not measured conditions at a home. Missing forecasts cannot be guessed.
Review original sourceWhere available, evaluate whether a ZIP-centroid point intersects SPC categorical forecast polygons.
Categorical outlook area does not imply property loss. SPC mapping covers CONUS; other areas require separate sources.
Review original sourceFuture Storm Memory timelines and searchable retrospective events.
Records are delayed and incomplete; not real-time confirmation of damage.
Review original sourceSource-linked Florida and hurricane guides; later separately validated GIS layers.
The cone describes forecast track uncertainty of the centre; impacts may occur outside it.
Review original sourceHousehold emergency planning, flood safety, disaster recovery checklists.
Guidance does not replace local emergency instructions.
Review original sourcePotential later researched community-context layer.
Relative long-run community risk is not the probability of tomorrow's storm or a specific property claim.
Review original sourceGive the visitor official risk context first. Avoid unsupported damage calculators, false 'hail hit your roof' banners and personal-data pressure.
Reuse EmpireOS event classifications and governance. Combine NWS point forecast and SPC categories in a read-only tool; do not portray event alerts as proprietary AI forecasts.
Build event replay only from archived datasets and named observations. NCEI often publishes data months after a storm, so use dated as-of coverage.
Provide reliable user identity, granular purpose consent, export and erasure before cloud storage. Current local browser preview does not protect sensitive documents.
State guides must include independent useful content, jurisdiction-specific preparedness, local sources and demonstrable update cycles—not dozens of duplicated doorway pages.
Pro subscriptions and explicitly authorised enquiries need validated buyers, fulfilment, unit economics, regulatory review and payment evidence.