# Geospatial Tile Processing — Record Quality Audit + String Normalisation + Trailing Mean Series

> Geospatial Tile Processing — Record Quality Audit + String Normalisation + Trailing Mean Series is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-02).

Runs three local analytical reports on geospatial tile processing records: a record quality audit, string normalisation, and a trailing mean time series — no external lookups or live data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-21-199?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/geospatial-tile-processing-record-quality-audit-string-normalisation-1da42cda
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_l3CJCLa_laAYUlLKnrcEa

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 geospatial-tile-processing-record-quality-audit-string-normalisation-1da42cda -d '<json body>'
```

Example prompt: Can you audit the quality of my geospatial tile processing records, normalise the station_group strings, and compute a trailing mean for tile_count with a window of 3 — here are my rows: row-1, 2026-10-01, group-a, 10 tiles, 1.2 seconds; row-2, 2026-10-02, group-b, 20 tiles, 2.4 seconds; row-3, 2026-10-03, group-A, 15 tiles, 3.1 seconds?

## When to prefer this

Choose this endpoint when you have up to 200 geospatial tile processing records and need all three reports — quality audit, string normalisation, and trailing mean series — bundled into a single $0.01 call. Prefer this over separate analytics tools when your data is already structured with row_id, station_group, date, tile_count, and processing_seconds fields and you want purely local, deterministic computation with no external API calls or live data dependencies.

## Known failure modes

- Fewer than 1 or more than 200 rows submitted — rejected with validation error
- Invalid date format (not YYYY-MM-DD) — row-level validation failure
- Window size larger than the number of submitted rows — trailing mean series may be empty or return NaN values
- Null values in tile_count or processing_seconds — quality audit flags them but mean series may skip those rows
- row_id or station_group exceeding 80 characters — truncation or rejection
- Numeric values outside ±1,000,000,000,000 range — schema validation error

## How this service works

Geospatial tile processing — Record quality audit + String normalisation + Trailing mean series: Record quality audit + String normalisation + Trailing mean series for supplied geospatial tile processing records (tile_count, processing_seconds). Up to 200 rows; 3 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 3 supplied-data reports for up to 200 rows.

## Output

Returns three independent analytical reports: (1) a record quality audit flagging null values, out-of-range numbers, and format issues; (2) a string normalisation report showing cleaned station_group values; and (3) a trailing mean series for the selected numeric field (tile_count or processing_seconds) computed over the specified window size — all derived from the supplied rows with no external data sources.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "station_group",
     "date",
     "tile_count",
     "processing_seconds"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "tile_count": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "station_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "processing_seconds": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "tile_count": 10,
     "station_group": "group-a",
     "processing_seconds": 1
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "tile_count": 20,
     "station_group": "group-b",
     "processing_seconds": 2
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "tile_count": 15,
     "station_group": "group-a",
     "processing_seconds": 3
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "tile_count": 30,
     "station_group": "group-b",
     "processing_seconds": 4
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "tile_count",
    "processing_seconds"
   ],
   "type": "string",
   "default": "tile_count"
  },
  "window": {
   "type": "integer",
   "default": 2,
   "maximum": 200,
   "minimum": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/geospatial-tile-processing-record-quality-audit-string-normalisation-1da42cda/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)