# Record Routing Analytics — Adjacent Row Changes & Two-Measure Correlation

> Record Routing Analytics — Adjacent Row Changes & Two-Measure Correlation 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_records, rejected_records) by computing adjacent row changes and a two-measure correlation report for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-158?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-two-measure-correlation-d270985f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uSMta0i4HdIWgCjxsu3u7

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-two-measure-correlation-d270985f -d '<json body>'
```

Example prompt: Can you run an adjacent row change analysis and two-measure correlation on my record routing data? Here are up to 200 rows with accepted_records and rejected_records fields — I want the report focused on the accepted_records field.

## When to prefer this

Choose this endpoint when you have tabular record routing data (with accepted and rejected record counts) and need both a sequential row-change analysis and a correlation between the two measures in a single low-cost call. It is ideal for lightweight ETL monitoring, pipeline auditing, and data quality reviews where you already have the data and need local statistical computation rather than live lookups or predictions.

## Known failure modes

- More than 200 rows submitted — request rejected or truncated
- Missing required fields (row_id, date, accepted_records, rejected_records) — validation error
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Null values in both measure columns may reduce correlation reliability
- Invalid field enum value (not 'accepted_records' or 'rejected_records') — rejected

## How this service works

Record routing — Adjacent row changes + Two-measure correlation: Adjacent row changes + Two-measure correlation 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) an adjacent row changes report showing how accepted_records or rejected_records shift between consecutive rows, and (2) a two-measure correlation report quantifying the statistical relationship between accepted_records and rejected_records across the supplied dataset. Both reports are computed locally on the supplied data (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-two-measure-correlation-d270985f/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)