# MyRadar Point Time Series (POST, JSON Body)

> MyRadar Point Time Series (POST, JSON Body) 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).

Fetches a multi-variable weather and road conditions time series forecast for a list of lat/lon points, submitted as a JSON body to support large point lists.

## Facts

- Endpoint: POST https://agents.myradar.dev/v1/timeseries/point?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-myradar-point-time-series-post-json-body-a62cf4ac
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PkXUj1MeUEnTw5FDr3UX3

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-myradar-point-time-series-post-json-body-a62cf4ac -d '<json body>'
```

Example prompt: Starting at 8:00 AM on May 22, 2024, get the full weather and road conditions time series — including road temperature, ice risk, delay risk, precipitation, and wind — for these two locations: 41.5°N 105.1°W and 36.1°N 96.1°W.

## When to prefer this

Use this POST endpoint instead of the equivalent GET endpoint when your list of lat/lon points is too long to fit in a URL query string. Prefer this over single-point forecast endpoints when you need time series data across many locations in one call. Choose this over the driving-route endpoint when your points are not necessarily along a connected route. This is the right choice when you need road-specific variables (road condition codes, surface temperature, delay risk) in addition to standard atmospheric forecasts.

## Known failure modes

- Invalid latlons format — must be a JSON array of [lat, lon] pairs
- Invalid itime format — must be YYYYmmdd.HHMM
- Request body missing required fields latlons or itime
- Points outside supported geographic coverage area may return null or sparse data
- Authentication or payment failure returns 402 or 401
- Extremely large point lists may hit rate or size limits

## How this service works

The same request as the GET point time series with latlons, itime, and as_csv in a JSON body, for point lists too long for a query string.

## Output

Returns a JSON object where each weather variable (road temperature, road condition, air temperature, surface temperature, precipitation rate, precipitation type, cloud cover, wind speed, wind direction, cross wind, visibility, solar radiation, snow depth, delay risk, and their deltas) is a 2D array indexed by [point_index][time_index], plus a validTimes array of Unix epoch seconds. Optionally returns CSV if as_csv is true.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "title": "PointRequest",
 "required": [
  "latlons",
  "itime"
 ],
 "properties": {
  "itime": {
   "type": "string",
   "title": "Itime",
   "examples": [
    "20250101.0000"
   ]
  },
  "as_csv": {
   "type": "boolean",
   "title": "As Csv",
   "default": false
  },
  "latlons": {
   "type": "string",
   "title": "Latlons",
   "examples": [
    "[[41.5,-105.1],[36.1,-96.1]]"
   ]
  }
 },
 "description": "Body form of the point query, for callers with many locations."
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-myradar-dev-myradar-point-time-series-post-json-body-a62cf4ac/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)