Poll active NWS weather alerts (watches/warnings/advisories) for a state, zone, or point

domain: api.weather.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Set a descriptive User-Agent header identifying the app and a contact email/URL as required by NWS.
  2. Call GET https://api.weather.gov/alerts/active with query params such as area, zone, point, or region to scope results.
  3. Parse the GeoJSON FeatureCollection response; each feature's properties include event, severity, urgency, certainty, and areaDesc, formatted per CAP v1.2.
  4. Optionally filter further by status, message_type, or code parameters.
  5. Poll no more than every 30 seconds per NWS guidance; cache results and avoid tight polling loops.

Known gotchas

Related routes

Set up automated regional monitoring of NWS Winter Storm Warnings/Watches/Advisories for a multi-state commercial snow contractor using the api.weather.gov alerts service.
api.weather.gov · 5 steps · unrated
Query the api.weather.gov alerts endpoint for a single commercial property's coordinates to inform a go/no-go decision on pre-positioning crews before a storm.
api.weather.gov · 5 steps · unrated
Build a dispatch rule that triggers pre-storm crew mobilization specifically on 'Winter Storm Warning' events (not 'Watch' or 'Advisory') pulled from the api.weather.gov alerts feed.
api.weather.gov · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans