# Replenishment Timing — Duplicate Key Report + Numeric Interval Filter

> Replenishment Timing — Duplicate Key Report + Numeric Interval Filter 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).

Analyzes up to 200 replenishment timing records to produce a duplicate key report and a numeric interval filter on lead_days or received_units fields.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-12-059?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-duplicate-key-report-numeric-interval-filter-b0e72808
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xFt-SNuoSZ-bZUm86EIqL

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-duplicate-key-report-numeric-interval-filter-b0e72808 -d '<json body>'
```

Example prompt: Check my replenishment timing data for duplicate row IDs and also filter records where lead_days is between 5 and 30 — here are my rows: row-1 (group-a, 2026-10-01, lead_days=10, received_units=1), row-2 (group-b, 2026-10-02, lead_days=20, received_units=2), row-3 (group-a, 2026-10-03, lead_days=15, received_units=3).

## When to prefer this

Choose this endpoint when you need simultaneous duplicate-key detection and numeric range filtering on replenishment timing records (lead_days or received_units) in a single $0.01 call. It is ideal for data quality checks before ETL pipeline uploads, inventory audits, or validating supply chain datasets up to 200 rows. It does not perform live lookups, predictions, or external integrations — prefer it for local, offline-style analytical reporting on data you already have.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, store_group, date, lead_days, received_units) causes rejection
- Date strings not matching YYYY-MM-DD pattern fail schema validation
- Numeric values outside ±1,000,000,000,000 bounds are rejected
- Empty rows array is not accepted (minItems: 1)
- minimum greater than maximum may return empty interval filter results

## How this service works

Replenishment timing — Duplicate key report + Numeric interval filter: Duplicate key report + Numeric interval filter 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: (1) a duplicate key report identifying which row_ids appear more than once in the supplied dataset, and (2) a numeric interval filter report listing which records have the specified numeric field (lead_days or received_units) falling within the supplied minimum and maximum bounds. Both reports are computed locally against the submitted rows with no external data lookup.

## 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"
  },
  "maximum": {
   "type": "number",
   "default": 100,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  },
  "minimum": {
   "type": "number",
   "default": 0,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/replenishment-timing-duplicate-key-report-numeric-interval-filter-b0e72808/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)