# Damaged Stock Numeric Row Ordering + Two-Measure Correlation

> Damaged Stock Numeric Row Ordering + 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-30).

Sorts damaged stock records by row number and computes Pearson/rank correlation between handled_units and damaged_units across up to 200 supplied rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-18-120?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/damaged-stock-numeric-row-ordering-two-measure-correlation-559adfe1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OScaEnffVdCDqWtT2pzpn

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-numeric-row-ordering-two-measure-correlation-559adfe1 -d '<json body>'
```

Example prompt: I have 4 rows of damaged stock data — row-1 group-a 2026-10-01 handled=10 damaged=1, row-2 group-b 2026-10-02 handled=20 damaged=2, row-3 group-a 2026-10-03 handled=15 damaged=3, row-4 group-b 2026-10-04 handled=30 damaged=4 — can you sort those records numerically by row and compute the correlation between handled_units and damaged_units?

## When to prefer this

Choose this endpoint when you have up to 200 rows of damaged stock records with handled_units and damaged_units fields and need both a numeric row sort and a two-measure correlation between those fields in a single call. It is a low-cost ($0.01 USDC), self-contained local computation with no external dependencies, ideal for offline batch analysis of retail or warehouse damage data where no real-time lookup or predictive modeling is needed.

## Known failure modes

- More than 200 rows submitted — request exceeds row limit
- Missing required fields (row_id, date, handled_units, damaged_units) — validation error
- Date field not matching YYYY-MM-DD pattern — schema rejection
- Null values in both numeric fields for a row — may affect correlation computation
- Single-row input — correlation between two measures is undefined with n=1

## How this service works

Damaged stock — Numeric row ordering + Two-measure correlation: Numeric row ordering + 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

Returns two independent analytical reports from shared local engines: (1) the input rows sorted in numeric row order, and (2) a two-measure correlation analysis between handled_units and damaged_units, including a correlation coefficient or equivalent statistic. No external lookups or predictions are performed.

## 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-numeric-row-ordering-two-measure-correlation-559adfe1/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)