# Damaged Stock String Normalisation + Two-Measure Correlation

> Damaged Stock String Normalisation + Two-Measure Correlation 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-23).

Normalises store/group strings and computes two-measure correlation across up to 200 damaged stock records (handled_units vs damaged_units), returning two analytical reports per call.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-18-033?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/damaged-stock-string-normalisation-two-measure-correlation-d7e916e9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IE5I4jTAJSTSPocitgFlK

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-two-measure-correlation-d7e916e9 -d '<json body>'
```

Example prompt: I have up to 200 rows of damaged stock records with handled_units and damaged_units per store group and date — can you normalise the store group strings and run a two-measure correlation between handled and damaged units, giving me both reports?

## When to prefer this

Choose this endpoint when you need to both clean up inconsistent store group string labels AND compute a statistical correlation between two numeric measures (handled vs damaged units) in a single low-cost call ($0.01 USDC for 2 reports). It is ideal for offline/batch retail damage audits on datasets up to 200 rows where no live lookup, prediction, or external data enrichment is needed.

## Known failure modes

- Submitting more than 200 rows returns a validation error
- Missing required fields (row_id, handled_units, damaged_units, date, store_group) causes row rejection
- Null or non-numeric values for handled_units or damaged_units may reduce correlation reliability
- Dates not matching YYYY-MM-DD pattern will fail schema validation
- Insufficient row variance may produce a degenerate or undefined correlation result

## How this service works

Damaged stock — String normalisation + Two-measure correlation: String normalisation + Two-measure correlation 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

Two independent analytical reports per call: (1) a string normalisation output standardising store_group labels across the submitted rows, and (2) a two-measure correlation report quantifying the statistical relationship between handled_units and damaged_units across up to 200 rows. No external lookups, predictions, or live data are included.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/damaged-stock-string-normalisation-two-measure-correlation-d7e916e9/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)