# Watches, Warnings, and Advisories at a Point

> Watches, Warnings, and Advisories 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 all active NWS watch, warning, and advisory polygons that contain a given latitude/longitude point.

## Facts

- Endpoint: GET https://agents.myradar.dev/v1/severe/wwa/{lat}/{lon}?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-watches-warnings-and-advisories-at-a-point-b14054ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UDK8wnVU0ILzfAIr4XK-0

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-watches-warnings-and-advisories-at-a-point-b14054ab
```

Example prompt: Are there any active weather watches, warnings, or advisories right now at latitude 35.4676 and longitude -97.5164? Give me the type, start time, and end time for each one.

## When to prefer this

Use this endpoint when you need to check all categories of NWS alerts (watches, warnings, AND advisories) for a specific geographic point. Prefer it over the 'Severe warnings at a point' endpoint when you need the broader advisory/watch tier in addition to warnings, and over the bounding-box variant when you have a precise coordinate rather than a region.

## Known failure modes

- Invalid or out-of-range latitude/longitude values result in an error response
- No active alerts at the point returns an empty results array with count 0
- Network or upstream MyRadar API downtime may cause 5xx errors
- Missing required lat or lon path parameters returns a 422 validation error

## How this service works

Returns the watch, warning, and advisory polygons that contain the point, as count, total, limit, offset, and results.

## Output

A paginated JSON object containing count, total, limit, offset, and a results array. Each result entry includes the phenomenon type (phenom), VTEC identifier string, geometry as lat/lon pairs defining the alert polygon, and timestamps for when the alert was issued, begins, ends, and expires.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "lat",
  "lon"
 ],
 "properties": {
  "lat": {
   "type": "number",
   "title": "Lat"
  },
  "lon": {
   "type": "number",
   "title": "Lon"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-myradar-dev-watches-warnings-and-advisories-at-a-point-b14054ab/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)