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.
domain: api.weather.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use /alerts/active?point=LAT,LON (documented at weather.gov/documentation/services-web-alerts) for the specific job-site coordinates
Confirm the response maps the point to its enclosing NWS forecast zone or county per the NWS Geolocation Guide, rather than a precise radius around the coordinate
Check both 'onset' and 'effective' timestamps in the returned alert, not just issuance time, before treating a warning as currently in force
Cross-reference the alert's 'severity'/'certainty' CAP fields when deciding dispatch urgency
Re-query periodically rather than caching a single point-in-time result, since alerts can be upgraded/downgraded or cancelled
Known gotchas
A point query returns zone-level (winter alerts are typically zone/county-based, not storm-based polygons) alerts, not hyper-local truth — a large forecast zone can span conditions that don't match one specific site
An alert's issuance time is not the same as its effective/onset time — winter storm warnings are sometimes issued for a future onset window
This point-query pattern is for real-time alerting only; it is not a substitute for the SNOTEL/NOHRSC snowpack datasets already used for seasonal planning
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?