# Warehouse Movements Two-Measure Correlation

> Warehouse Movements 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-18).

Computes the statistical correlation between received_units and dispatched_units across up to 200 warehouse movement records, returning a bounded correlation deliverable with local numeric processing.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-sector-analytics-warehouse-movements-correlation?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/warehouse-movements-two-measure-correlation-c343d66e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4clcaorC8LEp7rDxpPqpe

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

Example prompt: Can you run a two-measure correlation on these warehouse movement records to see how closely received units and dispatched units track each other? I have 4 rows: location group-a received 10 and dispatched 1 on 2026-10-01, group-b received 20 and dispatched 2 on 2026-10-02, group-a received 15 and dispatched 3 on 2026-10-03, and group-b received 30 and dispatched 4 on 2026-10-04.

## When to prefer this

Choose this endpoint when you need a quick, local statistical correlation between two numeric warehouse movement measures (received vs dispatched units) on a small-to-medium dataset (up to 200 records) without requiring external enrichment, forecasting, or multi-measure analysis. It is purpose-built for logistics and warehouse analytics workflows where data privacy matters and results need to be bounded and auditable. Prefer alternatives if you need forecasting, more than two measures, or datasets exceeding 200 rows.

## Known failure modes

- Fewer than 1 row supplied — minimum items validation error
- More than 200 rows supplied — maxItems constraint violation
- Invalid date format (not YYYY-MM-DD) — pattern validation failure
- Missing required fields (row_id, location, date, received_units, dispatched_units) — schema validation error
- All values for one measure are null — insufficient numeric data for correlation
- Constant variance in one measure — correlation undefined or returns NaN
- Extra properties in row objects — additionalProperties:false rejection

## How this service works

Warehouse movements - Two-measure correlation: Two-measure correlation for Warehouse movements. Up to 200 supplied typed records. Local numeric and data-quality processing; no external enrichment or forecasting. One of 25 profiles or calculations across 20 shared operations in this sector. 0.01 USDC includes one bounded two-measure correlation deliverable.

## Output

Returns a bounded two-measure correlation deliverable quantifying the statistical relationship (correlation coefficient and associated data-quality indicators) between received_units and dispatched_units across the supplied warehouse movement records. Processing is local and numeric with no external enrichment.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/warehouse-movements-two-measure-correlation-c343d66e/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)