# Building Footprint Observations — String Normalisation + Numeric Row Ordering

> Building Footprint Observations — String Normalisation + Numeric Row Ordering 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).

Normalises strings and orders rows numerically for building footprint observation records (footprint_m2, height_m) across up to 200 rows, returning 2 analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-16-025?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-string-normalisation-numeric-row-f9ad4400
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PASrIHfuI1e8S6AVP57HT

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-string-normalisation-numeric-row-f9ad4400 -d '<json body>'
```

Example prompt: Can you run string normalisation and numeric row ordering on my building footprint observations? I have 4 rows with footprint_m2 and height_m values for two station groups — group-a and group-b — dated from 2026-10-01 to 2026-10-04, and I want the reports ordered by footprint_m2.

## When to prefer this

Choose this endpoint when you have building footprint observation records (with footprint_m2 and height_m fields) that need text/string normalisation and numeric sorting as a data preparation step, and you want both operations delivered as two reports in a single API call for $0.01 USDC. It is purpose-built for this specific combination of operations on building observation data and avoids the overhead of general-purpose ETL pipelines.

## Known failure modes

- More than 200 rows submitted — endpoint rejects input exceeding maxItems limit
- Missing required fields (row_id, date, footprint_m2, height_m, station_group) causes validation error
- Invalid date format (not YYYY-MM-DD) triggers pattern validation failure
- Numeric values outside allowed range (±1,000,000,000,000) rejected
- Invalid field selector (not 'footprint_m2' or 'height_m') causes enum validation error
- Payment not provided or insufficient USDC causes x402 payment-required response

## How this service works

Building footprint observations — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering 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

Two analytical reports covering: (1) string-normalised versions of the submitted building footprint observation records (cleaning station_group and other text fields), and (2) numerically ordered rows based on the selected numeric field (footprint_m2 or height_m). No external lookups or predictions are included — all processing is local and analytical.

## 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-string-normalisation-numeric-row-f9ad4400/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)