# Geospatial Tile Processing — String Normalisation + Adjacent Row Changes

> Geospatial Tile Processing — String Normalisation + Adjacent Row Changes is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Normalises string fields and computes adjacent row changes for geospatial tile processing records (tile_count, processing_seconds) across up to 200 rows, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-21-029?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/geospatial-tile-processing-string-normalisation-adjacent-row-changes-c2d5fc78
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OZ8o3W_egdm9hbaFCJwv3

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-string-normalisation-adjacent-row-changes-c2d5fc78 -d '<json body>'
```

Example prompt: I have up to 200 rows of geospatial tile processing records with tile_count and processing_seconds per station group — can you normalise the string fields and compute the adjacent row changes for tile_count, and give me both reports?

## When to prefer this

Choose this endpoint when you need lightweight, local string normalisation combined with adjacent row change computation on geospatial tile processing records, especially when your dataset fits within 200 rows and you want two bundled reports for a single flat fee of $0.01 USDC. It is not suitable for live geospatial lookups, prediction, or datasets requiring external enrichment.

## Known failure modes

- More than 200 rows submitted — request rejected or truncated
- Missing required fields (row_id, date, station_group, tile_count, or processing_seconds) — validation error
- Invalid date format (must be YYYY-MM-DD) — schema rejection
- Numeric values outside allowed range (±1,000,000,000,000) — validation error
- Empty rows array — minimum 1 item required

## How this service works

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

## Output

Returns two analytical reports: one covering normalised string fields (e.g. cleaned station_group values) and one covering adjacent row changes for the selected numeric field (tile_count or processing_seconds), computed locally across up to 200 supplied rows with no external lookups.

## 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/geospatial-tile-processing-string-normalisation-adjacent-row-changes-c2d5fc78/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)