# Record Routing Analytics — Duplicate Key Report + Two-Measure Correlation

> Record Routing Analytics — Duplicate Key Report + 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 up to 200 record routing rows to produce a duplicate key report and a two-measure correlation between accepted_records and rejected_records.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-066?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-duplicate-key-report-two-measure-correlation-9502cdb6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d_K897p2e-gW7cpIHWNFT

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-duplicate-key-report-two-measure-correlation-9502cdb6 -d '<json body>'
```

Example prompt: Can you run a duplicate key check and a correlation analysis on my record routing data? I have rows with row_id, date, dataset_group, accepted_records, and rejected_records — here are my 50 rows grouped into group-a and group-b across October 2026.

## When to prefer this

Choose this endpoint when you need both a duplicate key integrity check and a two-measure correlation between accepted and rejected record counts in a single low-cost call ($0.01 USDC). It is ideal for lightweight, offline data quality validation of record routing batches up to 200 rows, with no external lookups or live data dependencies. Prefer it over general-purpose analytics tools when you need a quick, deterministic, self-contained report on routing record data quality and measure relationships.

## Known failure modes

- Rows exceeding 200 items will be rejected — keep input within maxItems limit
- Missing required fields (row_id, date, dataset_group, accepted_records, rejected_records) will cause validation errors
- Malformed date strings not matching YYYY-MM-DD pattern will fail schema validation
- Supplying only one row makes correlation statistically meaningless — at least a few rows are needed for meaningful correlation
- null values in accepted_records or rejected_records are allowed but may reduce correlation reliability

## How this service works

Record routing — Duplicate key report + Two-measure correlation: Duplicate key report + 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) a duplicate key report identifying any repeated row_id values across the submitted rows, and (2) a two-measure correlation report quantifying the statistical relationship between accepted_records and rejected_records across all submitted data.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-analytics-duplicate-key-report-two-measure-correlation-9502cdb6/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)