# Replenishment Timing Analyzer — Numeric Row Ordering + Base-100 Series

> Replenishment Timing Analyzer — Numeric Row Ordering + Base-100 Series 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-31).

Applies numeric row ordering and base-100 index series to user-supplied replenishment timing records (lead_days, received_units) for up to 200 rows, producing 2 independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-12-117?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/replenishment-timing-analyzer-numeric-row-ordering-base-100-series-79ddd973
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mAL1WDhfhW6xIBRjPm-Po

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-numeric-row-ordering-base-100-series-79ddd973 -d '<json body>'
```

Example prompt: Can you run the two replenishment timing reports — numeric row ordering and base-100 series — on my lead_days data for these store groups? I have about 40 rows, and I want the base index starting at row 0.

## When to prefer this

Choose this endpoint when you have up to 200 rows of replenishment timing data (lead_days, received_units) and need both a numeric row ordering and a base-100 index series computed locally without any external data lookup, prediction, or live market data. Ideal for retail supply chain analysts who want lightweight, low-cost ($0.01 USDC for both reports) deterministic analytics on their own datasets.

## Known failure modes

- More than 200 rows submitted — exceeds maxItems limit
- Missing required fields (row_id, store_group, date, lead_days, or received_units) on any row
- Invalid date format (must match YYYY-MM-DD pattern)
- base_index value out of range (must be 0–199 and within actual row count)
- Numeric field values outside allowed range (±1,000,000,000,000)
- Invalid field enum value (must be 'lead_days' or 'received_units')

## How this service works

Replenishment timing — Numeric row ordering + Base-100 series: Numeric row ordering + Base-100 series 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

Returns two independent analytical reports for the supplied replenishment timing data: (1) a numeric row ordering report ranking rows by the selected field (lead_days or received_units), and (2) a base-100 index series anchored to the specified base_index row. All computations are performed locally on the submitted data — no external lookups or predictions are made.

## 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"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/replenishment-timing-analyzer-numeric-row-ordering-base-100-series-79ddd973/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)