# Building Footprint Observations — Record Quality Audit & String Normalisation

> Building Footprint Observations — Record Quality Audit & String Normalisation 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).

Runs a record quality audit and string normalisation on up to 200 building footprint observation rows (footprint_m2, height_m), returning two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-16-001?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/building-footprint-observations-record-quality-audit-string-9d322a3d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vjrWU6Q8hSFL0PlLtJ6_S

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-record-quality-audit-string-9d322a3d -d '<json body>'
```

Example prompt: Can you audit the quality of my building footprint observation records and normalise the string fields? I have about 50 rows with columns for row_id, station_group, date, footprint_m2, and height_m — I need both the record quality audit and the string normalisation reports.

## When to prefer this

Choose this endpoint when you have up to 200 building footprint observation records (with footprint_m2 and height_m fields) and need both a data quality audit and string normalisation in a single call, without any live lookup, prediction, or external data enrichment. It is ideal for pre-processing pipelines that need to validate and clean building measurement data locally before downstream analysis.

## Known failure modes

- Exceeding 200 rows causes a validation error rejecting the request
- Missing required fields (row_id, station_group, date, footprint_m2, height_m) on any row causes rejection
- Invalid date format (not YYYY-MM-DD) triggers a schema validation failure
- row_id exceeding 80 characters or being empty causes a validation error
- Numeric values outside the allowed range cause schema rejection
- Malformed JSON body returns an error response

## How this service works

Building footprint observations — Record quality audit + String normalisation: Record quality audit + String normalisation 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 independent analytical reports per batch: (1) a record quality audit highlighting issues such as missing values, out-of-range measurements, and malformed dates across the supplied footprint_m2 and height_m fields; and (2) a string normalisation report showing standardised versions of string fields like station_group. Both reports cover up to 200 input rows processed locally without external lookups.

## 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/building-footprint-observations-record-quality-audit-string-9d322a3d/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)