# Record Routing Analytics — Adjacent Row Changes + Base-100 Series

> Record Routing Analytics — Adjacent Row Changes + 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).

Computes adjacent row changes and a Base-100 indexed series for accepted_records and rejected_records fields in record routing data, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-155?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-analytics-adjacent-row-changes-base-100-series-13c4b74d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YUrlny-6gXVgI6Z6kSC7n

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-analytics-adjacent-row-changes-base-100-series-13c4b74d -d '<json body>'
```

Example prompt: Can you analyze my record routing data — I have 4 rows with dates from 2026-10-01 to 2026-10-04, groups group-a and group-b, and accepted_records values of 10, 20, 15, 30 with rejected_records of 1, 2, 3, 4 — give me the adjacent row changes and base-100 series for accepted_records starting from row 0?

## When to prefer this

Choose this endpoint when you have tabular record routing data with accepted/rejected record counts and need both a row-over-row delta analysis and a base-indexed series in a single low-cost call. It is ideal for lightweight pipeline monitoring, data quality audits, and trend tracking without requiring external data sources or ML predictions. Best suited for batch sizes up to 200 rows where offline, deterministic computation suffices.

## Known failure modes

- Fewer than 1 or more than 200 rows supplied — validation error
- Invalid date format (non-YYYY-MM-DD) — schema validation rejection
- base_index out of range (must be 0–199 and within actual row count)
- Missing required fields (row_id, date, accepted_records, rejected_records) — schema error
- Null values in numeric fields may affect change calculations
- Payment not completed — x402 payment required before response

## How this service works

Record routing — Adjacent row changes + Base-100 series: Adjacent row changes + 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 analytical reports for the supplied rows: (1) adjacent row changes showing period-over-period differences for the selected field (accepted_records or rejected_records), and (2) a Base-100 indexed series anchored at the specified base_index row, enabling relative comparison across all rows. No external lookups or predictions are performed; all computation is local.

## 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"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-analytics-adjacent-row-changes-base-100-series-13c4b74d/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)