# Record Routing — Numeric Interval Filter + Base-100 Series

> Record Routing — Numeric Interval Filter + 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-23).

Filters record routing rows (accepted/rejected records) by a numeric interval and computes a base-100 indexed series, returning two analytical reports for up to 200 supplied rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-128?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/record-routing-numeric-interval-filter-base-100-series-c755f406
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-EhTRZlZZ9BPcq2bag6un

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 record-routing-numeric-interval-filter-base-100-series-c755f406 -d '<json body>'
```

Example prompt: Run a numeric interval filter (minimum 0, maximum 500) on accepted_records and compute a base-100 series starting from row index 0 for this record routing dataset: group-a on 2024-01-01 had 120 accepted and 5 rejected, group-b on 2024-01-02 had 340 accepted and 12 rejected, group-a on 2024-01-03 had 210 accepted and 8 rejected.

## When to prefer this

Choose this endpoint when you have up to 200 rows of record routing data with accepted/rejected record counts and need exactly two analytical operations in one call: a numeric range filter to isolate rows within a value band, plus a base-100 normalized index series for trend comparison. It is ideal for lightweight, offline analytical tasks on ETL, data pipeline, or routing audit datasets where no external data enrichment or live lookup is needed. Prefer it over general-purpose analytics tools when you want a cheap ($0.01 USDC), deterministic, two-report bundle on supplied data without any side effects.

## Known failure modes

- More than 200 rows submitted — request rejected or truncated
- base_index value exceeds the number of submitted rows — index out of bounds error
- Rows missing required fields (row_id, date, accepted_records, rejected_records) — validation error
- Date strings not matching YYYY-MM-DD pattern — schema validation failure
- minimum greater than maximum — interval produces no matching rows, empty filter result
- Non-numeric values in accepted_records or rejected_records where number expected — type error

## How this service works

Record routing — Numeric interval filter + Base-100 series: Numeric interval filter + Base-100 series for supplied record routing records (accepted_records, rejected_records). 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 numeric interval filter report listing which rows have the selected field (accepted_records or rejected_records) within the specified [minimum, maximum] range, and (2) a base-100 series report that re-indexes all row values relative to the designated base row, enabling normalized trend comparison — all computed locally on the supplied data with no external lookups.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "dataset_group",
     "date",
     "accepted_records",
     "rejected_records"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "dataset_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "accepted_records": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "rejected_records": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "dataset_group": "group-a",
     "accepted_records": 10,
     "rejected_records": 1
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "dataset_group": "group-b",
     "accepted_records": 20,
     "rejected_records": 2
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "dataset_group": "group-a",
     "accepted_records": 15,
     "rejected_records": 3
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "dataset_group": "group-b",
     "accepted_records": 30,
     "rejected_records": 4
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "accepted_records",
    "rejected_records"
   ],
   "type": "string",
   "default": "accepted_records"
  },
  "maximum": {
   "type": "number",
   "default": 100,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  },
  "minimum": {
   "type": "number",
   "default": 0,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-numeric-interval-filter-base-100-series-c755f406/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)