# Building Footprint Observations — Numeric Row Ordering + Adjacent Row Changes

> Building Footprint Observations — 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-11-02).

Performs numeric row ordering and adjacent row change analysis on up to 200 building footprint observation records (footprint_m2 or height_m fields).

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-16-116?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/building-footprint-observations-numeric-row-ordering-adjacent-row-e2d319d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fYVEG5w-0yp7ZgOUrQ8Xf

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 building-footprint-observations-numeric-row-ordering-adjacent-row-e2d319d9 -d '<json body>'
```

Example prompt: I have 50 building footprint observations with footprint_m2 and height_m values — can you run a numeric row ordering report and adjacent row change analysis on them so I can see how footprint_m2 values rank and shift row by row?

## When to prefer this

Choose this endpoint when you need to quickly apply two complementary analytical passes — numeric ordering and sequential delta computation — to a batch of building footprint or height observations without any external data lookup or live prediction. It is ideal for offline analysis of structured building datasets of up to 200 rows where both ranking and row-to-row change detection are needed simultaneously in a single low-cost call.

## Known failure modes

- Missing required row fields (row_id, date, station_group, footprint_m2, height_m) causes validation error
- More than 200 rows submitted exceeds the maximum and will be rejected
- Invalid date format (not YYYY-MM-DD) triggers a pattern mismatch error
- Numeric field values outside the allowed range cause schema rejection
- Empty rows array returns an error due to minItems:1 constraint

## How this service works

Building footprint observations — Numeric row ordering + Adjacent row changes: Numeric row ordering + Adjacent row changes for supplied building footprint observations records (footprint_m2, height_m). 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) a numeric row ordering report ranking the supplied rows by the selected field (footprint_m2 or height_m), and (2) an adjacent row changes report showing the delta between each consecutive row for the selected field, covering up to 200 input records.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/building-footprint-observations-numeric-row-ordering-adjacent-row-e2d319d9/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)