# Parking Utilization – Adjacent Row Changes

> Parking Utilization – 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-18).

Computes adjacent row-to-row changes in occupied or available parking spaces across zones and dates for up to 200 records.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-analytics-parking-utilization-period-change?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/parking-utilization-adjacent-row-changes-a50cd623
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iiU7UMu2Hqc97wrrzn52A

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 parking-utilization-adjacent-row-changes-a50cd623 -d '<json body>'
```

Example prompt: Can you run an adjacent row changes report on this parking utilization dataset — I have up to 50 rows with zone, date, row_id, occupied_spaces, and available_spaces — and I want to analyze changes in occupied_spaces between consecutive rows?

## When to prefer this

Choose this endpoint when you have a flat dataset of parking utilization records (up to 200 rows) and need to quickly compute adjacent row-to-row deltas for occupied or available spaces without requiring forecasting, enrichment, or external data. It is ideal for local descriptive analytics on structured parking data where you control row ordering and want a bounded, low-cost computation.

## Known failure modes

- Fewer than 1 row supplied — returns validation error
- More than 200 rows supplied — exceeds maxItems limit
- Missing required fields (row_id, zone, date, occupied_spaces, available_spaces) — schema validation failure
- Invalid date format not matching YYYY-MM-DD pattern — rejected
- Invalid field enum value other than occupied_spaces or available_spaces — rejected
- Payment of 0.01 USDC not completed — 402 Payment Required response

## How this service works

Parking utilization - Adjacent row changes: Adjacent row changes for Parking utilization. Up to 200 supplied typed records. Local descriptive analytics; no enrichment or forecast. One of 25 new profiles across 20 shared operations in this industry. 0.01 USDC includes one bounded adjacent row changes report.

## Output

A bounded descriptive analytics report listing the adjacent (consecutive row) change values for the selected metric field (occupied_spaces or available_spaces) across the supplied parking utilization records, with no forecasting or external enrichment.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/parking-utilization-adjacent-row-changes-a50cd623/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)