# Replenishment Timing — Grouped Numeric Summary + Numeric Row Ordering

> Replenishment Timing — Grouped Numeric Summary + Numeric Row Ordering 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-24).

Computes grouped numeric summaries and numeric row ordering for replenishment timing records (lead_days, received_units) across store groups, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-12-087?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/replenishment-timing-grouped-numeric-summary-numeric-row-ordering-f889b552
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Y-1EZCS6Yn4D_HoU5cVVg

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-grouped-numeric-summary-numeric-row-ordering-f889b552 -d '<json body>'
```

Example prompt: Can you run a grouped numeric summary and numeric row ordering on my replenishment timing data? I have records with lead_days and received_units across store groups — here are up to 200 rows, and I want to summarize by lead_days.

## When to prefer this

Choose this endpoint when you have replenishment timing records with lead_days and received_units fields and need both a grouped aggregate summary by store_group and a numerically ordered ranking of rows in a single low-cost call ($0.01 USDC). It is ideal for offline/batch analytical workflows on supplied data (up to 200 rows) where no live data lookup or prediction is needed. Prefer alternatives if you need forecasting, external data enrichment, or more than 200 rows processed at once.

## Known failure modes

- Rows array exceeds 200 items — request rejected
- Invalid date format (not YYYY-MM-DD) — validation error
- row_id missing or empty — schema validation failure
- Numeric field values outside allowed range (±1,000,000,000,000) — rejected
- field enum value not 'lead_days' or 'received_units' — invalid input
- Empty rows array — minimum 1 row required

## How this service works

Replenishment timing — Grouped numeric summary + Numeric row ordering: Grouped numeric summary + Numeric row ordering 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 analytical reports: (1) a grouped numeric summary showing aggregate statistics (e.g. count, min, max, mean) of the selected field (lead_days or received_units) broken down by store_group, and (2) a numeric row ordering ranking all submitted rows by the selected field value. Both reports are computed locally from the supplied data with no external 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-grouped-numeric-summary-numeric-row-ordering-f889b552/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)