# Replenishment Timing String Normalisation + Date by Category Pivot

> Replenishment Timing String Normalisation + Date by Category Pivot 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).

Runs two local analytical reports on replenishment timing records: string normalisation and a date-by-category pivot, for up to 200 rows of lead_days or received_units data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-12-035?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/replenishment-timing-string-normalisation-date-by-category-pivot-bd93d3a3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2XNdqgJxY6NhBpbviFDnl

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 replenishment-timing-string-normalisation-date-by-category-pivot-bd93d3a3 -d '<json body>'
```

Example prompt: Can you normalise the store group strings and pivot lead_days by date and category for these replenishment records — I have about 50 rows with store_group, date, lead_days, and received_units fields?

## When to prefer this

Choose this endpoint when you need two quick, self-contained analytical reports — string normalisation plus a date-by-category pivot — on replenishment timing data without any live lookups or external predictions. Best suited for small-to-medium datasets (up to 200 rows) of retail replenishment records with store group, date, lead_days, and received_units fields, where the analysis runs entirely on supplied data.

## Known failure modes

- Input exceeds 200 rows — request rejected
- Invalid date format (must be YYYY-MM-DD) — validation error
- Missing required fields (row_id, store_group, date, lead_days, received_units) — schema error
- field enum value not recognised — validation error
- Numeric values outside allowed range — schema rejection
- Empty rows array — minimum items not met

## How this service works

Replenishment timing — String normalisation + Date by category pivot: String normalisation + Date by category pivot for supplied replenishment timing records (lead_days, received_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 local analytical reports: (1) a string normalisation report cleaning and standardising the store_group field values, and (2) a date-by-category pivot table aggregating the selected numeric field (lead_days or received_units) broken down by date and store_group category — both derived from the supplied rows with no external data lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/replenishment-timing-string-normalisation-date-by-category-pivot-bd93d3a3/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)