# Replenishment Timing Numeric Interval Filter + Date by Category Pivot

> Replenishment Timing Numeric Interval Filter + Date by Category Pivot 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 a numeric interval filter and a date-by-category pivot analysis to supplied replenishment timing records (lead_days, received_units) for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-12-133?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-numeric-interval-filter-date-by-category-pivot-0b265a92
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zpTKnZiR9NIQgIS4U6UdN

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-numeric-interval-filter-date-by-category-pivot-0b265a92 -d '<json body>'
```

Example prompt: I have 150 replenishment timing records with lead_days and received_units — can you filter them to only show rows where lead_days is between 5 and 30, and also give me a date-by-category pivot grouped by store_group?

## When to prefer this

Choose this endpoint when you have up to 200 replenishment timing records and need both a numeric range filter (on lead_days or received_units) and a date-by-category pivot in a single low-cost call. Ideal for retail or supply chain workflows that need quick offline analytical summaries without external API dependencies or live data lookups. Best when you already have the data locally and need structured analytical outputs cheaply ($0.01 USDC for both reports).

## Known failure modes

- Input array exceeds 200 rows — request rejected
- Invalid date format (must be YYYY-MM-DD) causes row rejection
- Minimum greater than maximum produces empty filter result
- Missing required fields (row_id, store_group, date, lead_days, received_units) causes validation error
- Numeric values outside ±1,000,000,000,000 bounds rejected
- Empty rows array returns error

## How this service works

Replenishment timing — Numeric interval filter + Date by category pivot: Numeric interval filter + Date by category pivot 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 numeric interval filter result showing replenishment rows where the selected field (lead_days or received_units) falls within the specified minimum-maximum range, and (2) a date-by-category pivot table aggregating the replenishment data by store_group and date. Both reports are computed from the supplied rows with no external data 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"
  },
  "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-numeric-interval-filter-date-by-category-pivot-0b265a92/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)
