AI workers for NWS Storm Reports

What is an AI worker for NWS Storm Reports?

An AI worker for storm reports reads the Local Storm Reports issued by the US National Weather Service - the record of severe weather somebody actually saw and reported, with the hail size in inches, the county it fell in, and the hour it happened. This is the evidence layer rather than the prediction layer: where a forecast says what a model expects, a storm report says what an observer confirmed, which is the difference between a lead worth chasing and a guess. There is no account to connect and no key to paste, because the record is public and the platform reaches it on your behalf.

What these workers do

Find the neighbourhoods worth visiting

After a storm, the reports inside a service area with their hail sizes, so a crew is sent where damage was actually confirmed rather than where the radar looked bad.

Know overnight what happened

A morning brief of anything filed in the areas that matter, with the biggest first, so the day starts from what happened instead of from somebody else's phone call.

Check a claim or a callout against the record

Whether severe weather was actually reported near an address on a given day, and what size, so a conversation starts from the public record rather than from memory.

Watch for damage near assets or sites

Sites, branches, fleet yards or job sites checked against the reports around them, so damage is investigated because it was reported rather than because somebody noticed.

Give another worker the ground truth

Confirmed severe weather becomes context for a job somewhere else: a customer message, a dispatch plan or a report that needs to say what really happened.

How an AI worker runs in NWS Storm Reports

A report is an observation, not a forecast

The size is the whole point

Areas are counties, not radiuses, when it matters

A storm day is not a calendar day

Coverage is the United States, and it says so

Reports are worth citing, so they arrive citable

NWS Storm Reports questions, answered.

Is this a forecast or a record of what happened?

A record. These are Local Storm Reports: severe weather that an observer on the ground reported and a national weather service published, with the hail size, the county and the hour. It is the opposite of a forecast, and the distinction matters more here than almost anywhere else, because the two can be confused into an answer that sounds equally confident either way. If the question is what is coming, the forecast surface answers it. If the question is what happened, this one does.

Do we need an account or an API key?

No, and there is nothing to set up. The reports are public and the platform reaches them on your behalf, so a kit that uses this installs ready to run: no consent screen, no admin to chase, no credential to store, and no connection that can expire or leave with somebody. It is the same posture as the weather surface.

What areas does it cover?

The United States and its territories, because that is where the National Weather Service reports. Anywhere else there is simply no record, and a worker asking about such a place is told so rather than handed an empty result - which would otherwise read as a confident nothing happened. Inside the coverage, an empty result genuinely means no report was filed for that window.

How precise is a report, and can we trust the size?

Each report is a point with a time, a county and a nearest-place description, filed by the public, a trained spotter, law enforcement or a weather office. Sizes come marked as measured or estimated, and both are kept as they were filed rather than blended, so a worker can prefer measured reports or say which kind it relied on. What this is not is a continuous damage map: it records where somebody reported, so an area with no report is an area nobody reported from, which is not quite the same as an area nothing happened in.

How far back does the record go?

Years, which is enough to check a past date against what was actually reported rather than against anybody's recollection. A single request covers up to about a month, deliberately: the source stops adding rows past a fixed ceiling without saying that it has, so a wider window would come back looking complete when it was not. Rather than hand over a quietly partial record, a request that wide is refused with the narrower one named.

What AI workers can do in NWS Storm Reports

The tools a worker can be granted in NWS Storm Reports once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.

Find Storm Reports

Find verified severe-weather reports for an area and date window - hail with its measured size, damaging wind, tornadoes and more. These are Local Storm Reports issued by the US National Weather Service: human observations of what ACTUALLY happened, not a model's forecast, so each one is evidence you can act on and cite. Give an area as `states`/`counties` (exact, and how a service area is usually written) or as a `latitude`/`longitude`/`radiusMiles` point. Hail sizes are in inches, where 1.00 is the severe-criteria threshold and roughly where roof shingles start taking damage. IMPORTANT: a report day runs 12:00 UTC to 12:00 UTC, so asking for one date covers that afternoon and evening across the US - which is when severe weather actually happens. Coverage is the United States and its territories only.

Summarize Storm Reports

Count verified severe-weather reports for an area and date window, broken down by type and by county, with the peak magnitude in each. The cheap way to ask 'did anything happen in my area' before pulling individual reports - same area and window arguments as storm_reports_search, but it returns totals instead of rows. Use it first on a wide area, then call storm_reports_search on whatever it turns up. Hail peaks are in inches (1.00 is the severe-criteria threshold), wind in mph. Coverage is the United States and its territories only.