# Geospatial Tile Processing — String Normalisation + Base-100 Series

> Geospatial Tile Processing — String Normalisation + Base-100 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).

Performs string normalisation and Base-100 series indexing on supplied geospatial tile processing records (tile_count and processing_seconds), delivering two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-21-030?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-string-normalisation-base-100-series-8d99c0d8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-ZWb-gR20iFQqctJttoUM

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-base-100-series-8d99c0d8 -d '<json body>'
```

Example prompt: Can you run string normalisation and a Base-100 series analysis on my geospatial tile processing data — I have 4 rows with tile_count as the field, starting base index at 0, covering station groups A and B across early October 2026?

## When to prefer this

Choose this endpoint when you have structured geospatial tile processing records and need both string normalisation and Base-100 time-series indexing computed together in a single low-cost call. It is ideal for small-to-medium datasets (up to 200 rows) where you want two reports from shared local analytical engines without any live data lookup, external API calls, or prediction. It is not suitable for large datasets exceeding 200 rows, real-time streaming tile data, or use cases requiring external geospatial lookups or predictive modelling.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Invalid date format (non-YYYY-MM-DD) causes schema rejection
- Missing required fields (row_id, tile_count, processing_seconds) triggers a 400 error
- base_index out of range (0–199) causes parameter rejection
- Null numeric values may produce incomplete series results
- Non-numeric tile_count or processing_seconds values will fail schema validation

## How this service works

Geospatial tile processing — String normalisation + Base-100 series: String normalisation + Base-100 series 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 structured analytical reports per call: (1) string-normalised values for the chosen field (tile_count or processing_seconds) across all supplied rows, and (2) a Base-100 indexed series anchored at the specified base_index row, enabling relative comparison of geospatial tile processing metrics across up to 200 records.

## 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"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/geospatial-tile-processing-string-normalisation-base-100-series-8d99c0d8/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)