# Geospatial Tile Processing — Numeric Row Ordering + Adjacent Row Changes

> Geospatial Tile Processing — Numeric Row Ordering + 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-25).

Computes numeric row ordering and adjacent row changes for geospatial tile processing records (tile_count, processing_seconds) across up to 200 rows, returning 2 analytical reports.

## Facts

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

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-numeric-row-ordering-adjacent-row-changes-689c3337 -d '<json body>'
```

Example prompt: I have a dataset of geospatial tile processing records with tile counts and processing seconds across multiple station groups — can you sort them by tile_count and also show me the adjacent row-to-row changes for each record?

## When to prefer this

Use this endpoint when you have up to 200 geospatial tile processing records and need both a numeric sort/ranking and sequential adjacent-row delta analysis on either tile_count or processing_seconds in a single low-cost call. It is ideal for offline/batch analytical pipelines where no live external lookup, prediction, or real-time data is needed.

## Known failure modes

- More than 200 rows submitted — request exceeds maximum row limit
- Missing required fields (row_id, date, tile_count, processing_seconds) — validation error
- Invalid date format (not YYYY-MM-DD) — pattern mismatch error
- Numeric values outside allowed range (±1,000,000,000,000) — schema validation failure
- Invalid field enum value (must be tile_count or processing_seconds) — rejected input

## How this service works

Geospatial tile processing — Numeric row ordering + Adjacent row changes: Numeric row ordering + 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 2 analytical reports: (1) the input rows sorted in numeric order by the selected field (tile_count or processing_seconds), and (2) adjacent row change values showing the difference between each consecutive row for the chosen field. Covers up to 200 rows per call.

## 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-numeric-row-ordering-adjacent-row-changes-689c3337/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)