# Damaged Stock String Normalisation and Numeric Row Ordering

> Damaged Stock 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-10-31).

Normalises store/date strings and orders rows numerically for up to 200 damaged stock records (handled_units, damaged_units), producing 2 local analytical reports per call.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-18-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/damaged-stock-string-normalisation-and-numeric-row-ordering-dfb77d7d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xGluR_xIg88vftftL-HJw

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 damaged-stock-string-normalisation-and-numeric-row-ordering-dfb77d7d -d '<json body>'
```

Example prompt: I have 4 damaged stock records across two store groups — row-1 group-a 2026-10-01 handled_units=10 damaged_units=1, row-2 group-b 2026-10-02 handled_units=20 damaged_units=2, row-3 group-a 2026-10-03 handled_units=15 damaged_units=3, row-4 group-b 2026-10-04 handled_units=30 damaged_units=4 — can you run string normalisation and numeric row ordering on these and give me both the handled_units and damaged_units reports?

## When to prefer this

Choose this endpoint when you need lightweight, local string normalisation and numeric ordering on damaged stock data (up to 200 rows) without any external API calls, predictions, or professional assessments. It is ideal for retail inventory data cleaning pipelines where you want two standardised analytical reports per batch at minimal cost ($0.01 USDC). Prefer alternatives if you need live inventory lookups, damage predictions, or datasets larger than 200 rows.

## Known failure modes

- More than 200 rows submitted — request exceeds maxItems limit
- Missing required fields (row_id, store_group, date, handled_units, or damaged_units) — validation error
- Invalid date format not matching YYYY-MM-DD pattern — schema rejection
- Numeric values outside the allowed range (-1,000,000,000,000 to 1,000,000,000,000) — validation error
- Invalid field enum value (must be 'handled_units' or 'damaged_units') — schema rejection
- Payment not completed — x402 payment required before processing

## How this service works

Damaged stock — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied damaged stock records (handled_units, damaged_units). 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 analytical reports on the supplied damaged stock rows: one covering the selected numeric field (handled_units or damaged_units) with numeric row ordering applied, and one companion report — both derived entirely from the submitted data using local analytical engines, with no external lookups or predictions.

## Request schema (JSON Schema)

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

## More

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