# Record Routing String Normalisation and Duplicate Key Report

> Record Routing String Normalisation and Duplicate Key Report 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).

Runs string normalisation and duplicate key detection on up to 200 record routing rows (accepted_records, rejected_records), returning two analytical reports per call.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-021?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-string-normalisation-and-duplicate-key-report-73469099
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tgh9kTKxP6lAAl_yxxYV6

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-string-normalisation-and-duplicate-key-report-73469099 -d '<json body>'
```

Example prompt: Can you run a string normalisation and duplicate key check on these record routing rows — I've got four entries with row IDs row-1 through row-4, dataset groups group-a and group-b, dates from 2026-10-01 to 2026-10-04, accepted_records of 10, 20, 15, 30 and rejected_records of 1, 2, 3, 4? I want both the normalisation report and the duplicate key report.

## When to prefer this

Choose this endpoint when you need offline, local analytical processing of record routing data specifically — string normalisation combined with duplicate key detection — without needing any live lookup, external enrichment, prediction, or professional assessment. It is cost-effective at $0.01 for two reports covering up to 200 rows, making it suitable for lightweight data QA steps in automated pipelines.

## Known failure modes

- More than 200 rows submitted — request rejected, max is 200
- Missing required fields (row_id, date, accepted_records, rejected_records) — validation error
- Date field not matching YYYY-MM-DD pattern — schema validation failure
- row_id empty or exceeds 80 characters — validation error
- No rows provided (empty array) — minimum 1 row required

## How this service works

Record routing — String normalisation + Duplicate key report: String normalisation + Duplicate key report 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 string normalisation report detailing standardised/normalised string values across the submitted rows, and (2) a duplicate key report flagging any duplicate row_ids or dataset_group keys found within the supplied accepted_records and rejected_records data. Up to 200 rows are covered in a single call.

## 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-string-normalisation-and-duplicate-key-report-73469099/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)