# Hail and Wind History at a Point

> Hail and Wind History at a Point is a paid API for AI agents from agents.myradar.dev, paid per call via MPP, price unknown, status unknown (last checked 2026-10-12).

Returns multi-year historical records of hail sizes and high wind events at a given latitude/longitude coordinate.

## Facts

- Endpoint: GET https://agents.myradar.dev/v1/severe/history?utm_source=zero.xyz
- Price: price unknown
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Provider: agents.myradar.dev
- Website: https://agents.myradar.dev
- Canonical page: https://www.zero.xyz/c/agents-myradar-dev-hail-and-wind-history-at-a-point-149826e0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CiL6ookKJnAgGp4H00iXZ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agents-myradar-dev-hail-and-wind-history-at-a-point-149826e0
```

Example prompt: Can you pull up the hail and high wind history for the location at 41.5,-105.1? I want to see all the recorded severe weather events there over the past several years.

## When to prefer this

Use this endpoint when you need multi-year historical records of hail and high wind severe weather events at a specific geographic point. It is ideal for insurance underwriting, property risk assessment, storm damage validation, or site engineering studies. Prefer this over forecast endpoints when the need is retrospective analysis rather than future prediction, and over bounding-box warning endpoints when you need a precise point-level historical record rather than current active alerts.

## Known failure modes

- Missing or malformed latlon parameter returns a 400 error
- Coordinates outside supported coverage area may return empty hail and wind arrays
- Coordinates over open ocean or unsupported regions may return no data
- Network or upstream MyRadar API outage returns a 5xx error
- Improperly formatted latlon (with spaces or invalid values) causes a parsing error

## How this service works

Returns the hail sizes and high wind events recorded at latlon (a comma separated lat,lon) over the last several years.

## Output

Returns a JSON object with the requested location string, an array of hail events (each with a timestamp and estimated hail size in inches), and an array of wind events (each with a timestamp, sustained wind speed in mph, and peak wind gust in mph), covering several years of recorded history.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "latlon"
 ],
 "properties": {
  "latlon": {
   "type": "string",
   "title": "Latlon",
   "examples": [
    "41.5,-105.1"
   ],
   "description": "'lat,lon'."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-myradar-dev-hail-and-wind-history-at-a-point-149826e0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.myradar.dev](https://www.zero.xyz/host/agents.myradar.dev/llms.txt)