# Record Routing Analytics: Adjacent Row Changes + Secondary-Measure Weighted Mean

> Record Routing Analytics: Adjacent Row Changes + Secondary-Measure Weighted Mean 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-to-row changes and a secondary-measure weighted mean for up to 200 record routing rows (accepted_records, rejected_records) in two bundled analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-159?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-secondary-measure-990af3f8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NN49vtf5yN970vzh1dSDw

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-secondary-measure-990af3f8 -d '<json body>'
```

Example prompt: Can you run the adjacent row changes and weighted mean reports on my record routing data? I have 4 rows: row-1 on 2026-10-01 group-a with 10 accepted and 1 rejected, row-2 on 2026-10-02 group-b with 20 accepted and 2 rejected, row-3 on 2026-10-03 group-a with 15 accepted and 3 rejected, row-4 on 2026-10-04 group-b with 30 accepted and 4 rejected — use accepted_records as the primary field.

## When to prefer this

Choose this endpoint when you have tabular record routing data (accepted/rejected counts) and need two specific statistical outputs — adjacent row deltas and a weighted mean — computed offline from your own supplied data without any external data fetch, prediction, or live lookup. Ideal for ETL pipeline quality monitoring, batch reporting, and data acceptance trend analysis on datasets up to 200 rows.

## Known failure modes

- More than 200 rows supplied — request will be rejected or truncated
- Missing required fields (row_id, date, accepted_records, rejected_records) — validation error
- Invalid date format (must be YYYY-MM-DD) — schema validation failure
- Null values for both measures — weighted mean may be undefined or return error
- Field enum value not matching accepted_records or rejected_records — invalid input error

## How this service works

Record routing — Adjacent row changes + Secondary-measure weighted mean: Adjacent row changes + Secondary-measure weighted mean 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

Two analytical reports: (1) adjacent row changes showing the difference in the chosen measure between each consecutive row, and (2) a secondary-measure weighted mean summarizing the dataset. Results are computed locally from 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-analytics-adjacent-row-changes-secondary-measure-990af3f8/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)