# Record Routing: Numeric Interval Filter + Adjacent Row Changes

> Record Routing: Numeric Interval Filter + Adjacent Row Changes 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).

Analyzes record routing data (accepted/rejected records) by applying a numeric interval filter and detecting adjacent row changes, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-127?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-adjacent-row-changes-7232988c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fnxvyZ5jyYw6N6kRgb0_O

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-adjacent-row-changes-7232988c -d '<json body>'
```

Example prompt: I have a routing dataset with accepted and rejected record counts — can you filter it to rows where accepted_records falls between 5 and 100, and also flag any adjacent rows where the value changed? Here's the data: row-1 2026-10-01 group-a accepted=10 rejected=1, row-2 2026-10-02 group-b accepted=20 rejected=2, row-3 2026-10-03 group-a accepted=150 rejected=3.

## When to prefer this

Choose this endpoint when you have structured record routing data with accepted/rejected record counts and need two specific analyses in one call: a numeric range filter and adjacent-row change detection. It is ideal for ETL pipeline audits, data quality checks, and routing anomaly detection where you already have the data in hand and want fast, local computation without any external API calls or live data lookups. It covers up to 200 rows per call for $0.01 USDC.

## Known failure modes

- Fewer than 1 row supplied — request rejected
- More than 200 rows supplied — request rejected
- Invalid date format (not YYYY-MM-DD) — validation error
- Field value not in enum ['accepted_records','rejected_records'] — validation error
- minimum greater than maximum — may return empty interval filter result
- null values in accepted_records or rejected_records — affected rows may be excluded from computations

## How this service works

Record routing — Numeric interval filter + Adjacent row changes: Numeric interval filter + Adjacent row changes 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 reports: (1) rows where the selected field (accepted_records or rejected_records) falls within the specified minimum–maximum interval, and (2) a row-by-row adjacency change report showing where consecutive rows differ in value. Both reports are derived solely from the supplied data using local analytical engines — no external lookups or predictions.

## 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-numeric-interval-filter-adjacent-row-changes-7232988c/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)