# Geospatial Tile Processing — Numeric Row Ordering + Secondary-Measure Weighted Mean

> Geospatial Tile Processing — Numeric Row Ordering + Secondary-Measure Weighted Mean 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-23).

Ranks geospatial tile processing records by numeric row order and computes a secondary-measure weighted mean across up to 200 supplied rows, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-21-121?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/geospatial-tile-processing-numeric-row-ordering-secondary-measure-52b62a27
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vpB-3Qoi_ZzUTu5_BQB5M

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-secondary-measure-52b62a27 -d '<json body>'
```

Example prompt: I have a batch of geospatial tile processing records — up to 50 rows with fields like row_id, station_group, date, tile_count, and processing_seconds — can you rank them numerically by row order and compute a weighted mean on tile_count, returning both reports?

## When to prefer this

Choose this endpoint when you have structured geospatial tile processing tabular data (up to 200 rows) and need both a numeric row ranking and a weighted mean on a numeric measure in a single low-cost call. It is a pure local analytical computation with no external lookups, making it deterministic and fast. Prefer it over general-purpose analytics tools when the data fits the tile_count/processing_seconds schema and you want two bundled reports for $0.01 USDC.

## Known failure modes

- More than 200 rows submitted — request rejected with validation error
- Missing required fields (row_id, station_group, date, tile_count, processing_seconds) — row-level validation failure
- Invalid date format (not YYYY-MM-DD) — pattern validation error
- Numeric values outside allowed range (±1,000,000,000,000) — schema validation error
- Empty rows array — minItems violation
- Invalid field selector (not 'tile_count' or 'processing_seconds') — enum validation error

## How this service works

Geospatial tile processing — Numeric row ordering + Secondary-measure weighted mean: Numeric row ordering + Secondary-measure weighted mean 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: (1) the input rows sorted by numeric row order, and (2) a secondary-measure weighted mean computed over the chosen field (tile_count or processing_seconds), covering up to 200 input 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-secondary-measure-52b62a27/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)