← Marketplace

Commons signalFree

Weather & Severe Alerts

The National Weather Service, wrapped in governance: storm warnings land next to your open promises.

Ask how Weather & Severe Alerts fits what you run.

Answers are based on this listing. For anything it can't answer, our team can.

For anything this page can't answer, talk to us.

About

This Commons feed reads the National Weather Service API: point forecasts, active watches and warnings, and severe-weather alerts for the counties and zones you care about. Each event lands tenant-stamped and source-tagged like every other Fibric signal, so an operator can put a winter-storm warning next to the two hundred orders promised into that region this week.

The upstream is free and public, published by NOAA with no key required. Fibric adds the governance: deduplication, replayable history, and honest provenance on every event, so a forecast in an operator's reasoning is never confused with a fact about your orders.

Highlights

  • Free public feed, no key required
  • Severe alerts by county, zone, or exact site coordinates
  • The classic play: storm inbound + open promises = proactive outreach
Kind
Commons signal
Category
Commons signals
Publisher
Fibric Commons
Upstream
NWS / NOAA (api.weather.gov)
Feed health
Feed live, data flowing (270ms, checked 2026-07-06T23:28Z)
Availability
Early access
Delivery
Managed by Fibric; nothing to install
Data direction
Read-only
Pricing
Free
Sold by
Fibric
Support
Developed and supported by Fibric
Tags
weather, alerts, commons, free

Authentication

None. The NWS API is free and public; Fibric identifies itself with a User-Agent as NOAA requests.

What it reads

  • Active watches, warnings, and advisories by county, zone, or point
  • Point forecasts and hourly forecast periods for your sites
  • Alert lifecycle updates as events are issued, extended, and cancelled

What it can do

This is a sensing source: it reads, it does not write. Operators act through the write-capable connectors alongside it.

How it works

1

Sense

Active watches, warnings, and advisories by county, zone, or point.

2

Reason

Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.

3

Act

Nothing. This is a sensing source; operators act through the write-capable connectors alongside it.

Pricing

Public upstream feed · managed deployment terms

The upstream signal may be publicly accessible, but no public Fibric plan or hosted feed is offered here. Integration, validation, limits, and support are scoped in writing for a managed deployment.

Deployment engineer
Wires and verifies the integration with you during onboarding
Managed validation
Review maturity, authority, supported records, and deployment boundaries before go-live
Execution records
Supported reads, proposals, policy decisions, and reported outcomes kept for review
Support from the builders
Developed, run, and supported directly by Fibric

Requirements

System requirements
  • The locations (sites, zones, or service regions) you want watched

Your deployment engineer verifies each line with you during onboarding.

Support and resources

Supported by the people who built it

This signal feed is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.

Works with

Listings this is designed to pair with. Each listing has its own live or managed early-access state.

Operator by Fibric

Order Risk

BearScope has a live governed order-risk path. This listing expresses that capability as a target operator contract, not as a public pack or generalized runtime claim.

View details

Operator by Fibric

Field Dispatch

A managed early-access pattern for matching supported field signals to a reviewed route and dispatch proposal.

View details

Support & comms connector

Kustomer

Kustomer data is live in BearScope through a governed product path. This listing expresses the target read and supported-note contract; it is not a public installable artifact.

View details

Support & comms connector

Microsoft Teams

Routes approvals and alerts to the channel that owns the call. One confirm in Teams turns a proposed plan into a vetted action.

View details

Control & actuation connector

Twilio

A managed reference connector for calls and texts. Throttling, stable keys, human authority, and delivery reconciliation reduce repeat-send and flood risk.

View details

Bring Weather & Severe Alerts into your early-access deployment

Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.