# Record Routing Analytics — Two-Measure Correlation + Secondary-Measure Weighted Mean

> Record Routing Analytics — Two-Measure Correlation + 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-11-02).

Computes two statistical reports (Pearson correlation between accepted and rejected records, plus a weighted mean of a selected measure) over up to 200 rows of record routing data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-181?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/record-routing-analytics-two-measure-correlation-secondary-measure-cfbf9fe7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_B5aHYWSD-ucYSQJXHCjyG

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

Example prompt: I have 4 rows of record routing data — row-1 on 2026-10-01 in group-a with 10 accepted and 1 rejected, row-2 on 2026-10-02 in group-b with 20 accepted and 2 rejected, row-3 on 2026-10-03 in group-a with 15 accepted and 3 rejected, row-4 on 2026-10-04 in group-b with 30 accepted and 4 rejected — can you run the two-measure correlation between accepted and rejected records plus the weighted mean for accepted_records across all rows?

## When to prefer this

Choose this endpoint when you need fast, offline statistical analysis of record routing data specifically — particularly when you want both a correlation between two measures and a weighted mean in a single API call for up to 200 rows. It is ideal for data quality teams tracking acceptance/rejection patterns without needing external data enrichment, live predictions, or professional assessments. Prefer alternatives if you need more than two reports, more than 200 rows, live lookups, or domain types other than record routing (e.g. building occupancy has its own sibling endpoint).

## Known failure modes

- Rows array empty or missing — validation error
- More than 200 rows submitted — rejected with max-items error
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Null values in both measures for a row — may affect correlation calculation
- Field enum value not one of accepted_records or rejected_records — schema rejection
- All values identical (zero variance) — correlation undefined or NaN result

## How this service works

Record routing — Two-measure correlation + Secondary-measure weighted mean: Two-measure correlation + 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

Returns two analytical reports computed locally on the supplied data: (1) a Pearson-style correlation between the accepted_records and rejected_records columns across all rows, and (2) a weighted mean of the chosen field (accepted_records or rejected_records). No external lookups or predictions are made; all computation is on the provided dataset of up to 200 rows.

## 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-two-measure-correlation-secondary-measure-cfbf9fe7/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)