# Severe Warnings at a Point

> Severe Warnings 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 severe weather warning polygons (not watches/advisories) that contain a given latitude/longitude point, with pagination metadata.

## Facts

- Endpoint: GET https://agents.myradar.dev/v1/severe/warnings/{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-severe-warnings-at-a-point-a3475bd3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NBrawvkeRCQCgf2H3saN5

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-severe-warnings-at-a-point-a3475bd3
```

Example prompt: Are there any active severe weather warnings at coordinates 35.46 latitude, -97.51 longitude right now? Show me the warning type and how long each one is in effect.

## When to prefer this

Use this endpoint when you need only severe weather *warnings* (not the full set of watches, warnings, and advisories) at a specific geographic point. Prefer this over the watches/warnings/advisories endpoint when you want a narrower, warning-only result set. Prefer this over the bounding-box variant when querying for a single precise location rather than a geographic region.

## Known failure modes

- Invalid latitude or longitude values (out of range) may return an error or empty results
- Point located outside of US coverage area may return zero results
- No active warnings at the given coordinates returns count=0 and empty results array
- Network timeout if the underlying MyRadar API is temporarily unavailable
- Missing required lat or lon path parameters will return a 422 or 404 error

## How this service works

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

## Output

Returns a JSON object with count (number of warnings found), total (total matching results for pagination), limit (max results returned), offset (current pagination offset), and a results array. Each result contains: begins and ends timestamps for the warning period, issued and expires timestamps, phenom (the warning type/phenomenon label), vtec (unique VTEC identifier string), and geom (array of lat/lon coordinate pairs defining the warning polygon boundary).

## 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-severe-warnings-at-a-point-a3475bd3/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)