# MyRadar Layer Point Value Extractor

> MyRadar Layer Point Value Extractor 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).

Extracts numeric values from a named weather/radar layer at one or more lat/lon coordinates for a specific valid time.

## Facts

- Endpoint: GET https://agents.myradar.dev/v1/layers/point/{layer}/{valid_time}?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-layer-point-value-extractor-51d40c12
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mTZ04ySUN8j7QRQ86KgQY

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-layer-point-value-extractor-51d40c12
```

Example prompt: What is the 15-minute MRMS precipitation rate at [[41.5,-105.1],[36.1,-96.1]] for valid time 20240615.1430? Give me the values as JSON.

## When to prefer this

Use this endpoint when you need numeric layer values at specific geographic point locations rather than rendered images, tiles, or full-coverage NetCDF files. It is ideal for programmatic analysis of weather or radar data at a set of known coordinates, route-based weather checks, or feeding layer values into downstream models. Prefer this over the render/download endpoint when you need machine-readable numbers rather than visual output, and over the forecast endpoint when you need raw layer/radar data rather than interpreted forecast fields.

## Known failure modes

- Invalid layer name returns an error — use the List Layers endpoint first to get valid names
- Malformed valid_time format (must be YYYYmmdd.HHMM) causes a 400 error
- Invalid latlons JSON format causes a parse error
- Requested valid_time outside available data window returns empty or null values
- Points outside the layer's geographic coverage area may return null or no-data values
- Malformed lat/lon coordinates (out of range) may cause errors or unexpected results

## How this service works

Extracts the value of the layer at each point in latlons, a JSON array of [lat, lon] pairs, for valid_time (YYYYmmdd.HHMM). Set as_csv=true for CSV.

## Output

Returns a JSON array of numeric values (one per input lat/lon pair) representing the layer's value at each point for the specified valid time. If as_csv=true, returns CSV-formatted text instead.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "layer",
  "valid_time",
  "latlons"
 ],
 "properties": {
  "layer": {
   "type": "string",
   "title": "Layer"
  },
  "as_csv": {
   "type": "boolean",
   "title": "As Csv",
   "default": false
  },
  "latlons": {
   "type": "string",
   "title": "Latlons",
   "examples": [
    "[[41.5,-105.1]]"
   ],
   "description": "JSON array of [lat, lon] pairs."
  },
  "valid_time": {
   "type": "string",
   "title": "Valid Time"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-myradar-dev-myradar-layer-point-value-extractor-51d40c12/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)