# Capacity Planning String Normalisation and Numeric Row Ordering

> Capacity Planning String Normalisation and 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 team/group strings and sorts capacity planning rows numerically by available_hours or assigned_hours, returning two analytical reports for up to 200 records.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-operations-04-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/capacity-planning-string-normalisation-and-numeric-row-ordering-f01acf6c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TN3lGFvEwAbSczdyD3hNd

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 capacity-planning-string-normalisation-and-numeric-row-ordering-f01acf6c -d '<json body>'
```

Example prompt: Can you run string normalisation and numeric row ordering on my capacity planning records? I have 4 rows — row-1 for group-a on 2026-10-01 with 10 available hours and 1 assigned, row-2 for group-b on 2026-10-02 with 20 available and 2 assigned, row-3 for group-a on 2026-10-03 with 15 available and 3 assigned, row-4 for group-b on 2026-10-04 with 30 available and 4 assigned — and I want both reports sorted by available_hours.

## When to prefer this

Choose this endpoint when you need lightweight, local string normalisation of team/group labels combined with numeric row ordering for capacity planning records — specifically when you want two independent analytical reports in a single call for up to 200 rows, without needing live data lookups, ML predictions, or external integrations. Ideal for pre-processing capacity data before reporting pipelines.

## Known failure modes

- More than 200 rows submitted — request will be rejected or truncated
- Missing required fields (row_id, team_group, date, available_hours, assigned_hours) cause validation errors
- Invalid date format (must match YYYY-MM-DD pattern) triggers schema rejection
- Invalid field enum value (must be 'available_hours' or 'assigned_hours') causes error
- Numeric values outside the allowed range (-1e12 to 1e12) may be rejected
- Empty rows array (minItems:1 not met) returns error

## How this service works

Capacity planning — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied capacity planning records (available_hours, assigned_hours). 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 covering: (1) string-normalised team_group values across all supplied rows, and (2) rows numerically ordered by the selected field (available_hours or assigned_hours). Both reports are computed locally from supplied data with no external lookups or predictions, covering up to 200 input rows.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "team_group",
     "date",
     "available_hours",
     "assigned_hours"
    ],
    "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
     },
     "assigned_hours": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "available_hours": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "team_group": "group-a",
     "assigned_hours": 1,
     "available_hours": 10
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "team_group": "group-b",
     "assigned_hours": 2,
     "available_hours": 20
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "team_group": "group-a",
     "assigned_hours": 3,
     "available_hours": 15
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "team_group": "group-b",
     "assigned_hours": 4,
     "available_hours": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "available_hours",
    "assigned_hours"
   ],
   "type": "string",
   "default": "available_hours"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/capacity-planning-string-normalisation-and-numeric-row-ordering-f01acf6c/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)