# Replenishment Timing Analyzer — Exact Row Deduplication + Secondary-Measure Weighted Mean

> Replenishment Timing Analyzer — Exact Row Deduplication + Secondary-Measure Weighted Mean 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-29).

Deduplicates replenishment timing records exactly by row and computes a weighted mean for a secondary measure (lead_days or received_units) across up to 200 rows, producing two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-12-051?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/replenishment-timing-analyzer-exact-row-deduplication-secondary-78069ee0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ua-3uSKkNcWmJHaVm5CXr

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-analyzer-exact-row-deduplication-secondary-78069ee0 -d '<json body>'
```

Example prompt: I have up to 200 replenishment timing rows with store group, date, lead_days, and received_units — can you deduplicate them exactly and compute the weighted mean for lead_days across all rows, giving me two analytical reports?

## When to prefer this

Choose this endpoint when you have up to 200 replenishment timing records with lead_days and received_units and need both exact row deduplication and a weighted mean computation in a single low-cost call ($0.01 USDC). Ideal for retail or supply chain analytics pipelines that need offline, deterministic data cleaning and aggregation without external lookups or predictions. Prefer over general-purpose analytics tools when working specifically with store-group-level replenishment timing data and needing two bundled reports in one operation.

## Known failure modes

- More than 200 rows submitted — exceeds maximum row limit
- Missing required fields (row_id, store_group, date, lead_days, or received_units) — validation error
- Invalid date format (must match YYYY-MM-DD pattern) — schema validation failure
- Invalid field enum value (must be 'lead_days' or 'received_units') — rejected input
- All rows are duplicates leaving no unique records — may return empty deduplication result
- Numeric values outside allowed range (-1e12 to 1e12) — schema rejection

## How this service works

Replenishment timing — Exact row deduplication + Secondary-measure weighted mean: Exact row deduplication + Secondary-measure weighted mean 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 analytical reports for the supplied replenishment timing data: one covering exact row deduplication results (identifying and removing duplicate rows), and one providing the secondary-measure weighted mean (for either lead_days or received_units as specified). No external lookups or predictions are made; all analysis is performed locally on the submitted data.

## 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-analyzer-exact-row-deduplication-secondary-78069ee0/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)