# Facilities Usage — String Normalisation + Numeric Row Ordering

> Facilities Usage — 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-10-29).

Normalises team/group strings and sorts rows numerically for up to 200 facilities usage records containing occupied_seats and available_seats fields, producing 2 analytical reports per call.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-operations-12-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/facilities-usage-string-normalisation-numeric-row-ordering-16072cba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UzLpF9BwGyuiGV7IL4qFP

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 facilities-usage-string-normalisation-numeric-row-ordering-16072cba -d '<json body>'
```

Example prompt: Can you run string normalisation and numeric row ordering on my facilities usage records — I have about 50 rows with occupied_seats and available_seats fields, and I want both reports sorted by occupied_seats?

## When to prefer this

Choose this endpoint when you need lightweight, local string normalisation of team/group labels combined with numeric ordering of seat occupancy rows — ideal for cleaning and sorting facilities usage datasets up to 200 rows without requiring live data lookups, ML predictions, or external integrations. Best suited for operations teams doing routine data hygiene and ordering on occupancy records before downstream reporting.

## Known failure modes

- More than 200 rows submitted — request rejected, batch must be split
- Missing required fields (row_id, date, occupied_seats, available_seats) — validation error
- Date field does not match YYYY-MM-DD pattern — schema validation failure
- Numeric seat values outside allowed range (±1,000,000,000,000) — rejected
- Empty rows array — minimum 1 row required
- Invalid field enum value (not occupied_seats or available_seats) — error returned

## How this service works

Facilities usage — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied facilities usage records (occupied_seats, available_seats). 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 2 independent analytical reports covering the supplied facilities usage rows: one applying string normalisation to team/group labels and one providing numeric row ordering based on the selected field (occupied_seats or available_seats). Reports cover up to 200 input rows and are generated locally without external lookups or predictions.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/facilities-usage-string-normalisation-numeric-row-ordering-16072cba/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)