# Replenishment Timing Record Quality Audit and Numeric Row Ordering

> Replenishment Timing Record Quality Audit and 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).

Runs two local analytical reports on replenishment timing records — a data quality audit and a numeric row ordering — for up to 200 rows of lead_days/received_units data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-12-007?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-record-quality-audit-and-numeric-row-ordering-559ce108
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uF6oXjl28FlUubaOs3xBH

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-record-quality-audit-and-numeric-row-ordering-559ce108 -d '<json body>'
```

Example prompt: Can you run a record quality audit and numeric row ordering on my replenishment timing data? I have 4 rows with store groups group-a and group-b, dates from 2026-10-01 to 2026-10-04, lead_days values of 10, 20, 15, and 30, received_units of 1, 2, 3, and 4 — please use lead_days as the field to order by.

## When to prefer this

Choose this endpoint when you need lightweight, offline data quality auditing and numeric ordering for replenishment timing records (lead_days, received_units) without any external lookups or predictions. Ideal for validating datasets before forecasting pipelines, identifying data hygiene issues in retail inventory data, or generating ranked views of replenishment records at low cost ($0.01 per call for up to 200 rows and 2 reports).

## Known failure modes

- Exceeding 200 rows results in rejection
- Missing required fields (row_id, store_group, date, lead_days, received_units) causes validation error
- Invalid date format (non-YYYY-MM-DD) triggers schema error
- Numeric values outside allowed range cause validation failure
- Empty rows array returns an error
- Invalid field enum value (not lead_days or received_units) causes rejection

## How this service works

Replenishment timing — Record quality audit + Numeric row ordering: Record quality audit + 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

Two independent analytical reports: (1) a record quality audit flagging data issues such as nulls, out-of-range values, or malformed entries in the replenishment timing records; and (2) a numerically ordered ranking of rows by the selected field (lead_days or received_units). 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-record-quality-audit-and-numeric-row-ordering-559ce108/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)