# Record Routing Analytics: Duplicate Key Report + Numeric Distribution

> Record Routing Analytics: Duplicate Key Report + Numeric Distribution 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-24).

Analyzes up to 200 record routing rows to produce a duplicate key report and a numeric distribution report for accepted_records or rejected_records fields.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-055?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/record-routing-analytics-duplicate-key-report-numeric-distribution-faf9248a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4S5lSkdA_usYraAVjNNiJ

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-numeric-distribution-faf9248a -d '<json body>'
```

Example prompt: Can you run a duplicate key report and numeric distribution on my record routing data — here are 5 rows with row_id, dataset_group, date, accepted_records, and rejected_records — and analyze the accepted_records field?

## When to prefer this

Choose this endpoint when you need both a duplicate key report and a numeric distribution on record routing data in a single call for up to 200 rows. It is ideal for data quality checks on ETL or ingestion pipelines where you want to identify repeated identifiers and understand value spread without external lookups or predictions. Prefer it over general analytics tools when working specifically with accepted_records/rejected_records routing metrics and when cost efficiency ($0.01 for two reports) matters.

## Known failure modes

- More than 200 rows submitted — only up to 200 rows are supported
- Missing required fields (row_id, dataset_group, date, accepted_records, rejected_records) cause validation errors
- Invalid date format (must be YYYY-MM-DD) triggers schema rejection
- Numeric values outside the allowed range (-1,000,000,000,000 to 1,000,000,000,000) are rejected
- Empty rows array (minItems: 1) causes request failure
- Invalid field enum value (must be accepted_records or rejected_records) causes error
- Payment not attached or insufficient USDC balance causes x402 rejection

## How this service works

Record routing — Duplicate key report + Numeric distribution: Duplicate key report + Numeric distribution 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 for the supplied routing data: (1) a duplicate key report identifying repeated row_id or key values within the dataset, and (2) a numeric distribution report showing the frequency or spread of values in the selected field (accepted_records or rejected_records). Results cover up to 200 rows and are computed locally without 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-duplicate-key-report-numeric-distribution-faf9248a/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)