# Record Routing — String Normalisation + Exact Row Deduplication

> Record Routing — String Normalisation + Exact Row Deduplication 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-15).

Normalises strings and deduplicates exact rows in record routing datasets (accepted_records, rejected_records) across up to 200 rows, producing 2 analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-020?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/record-routing-string-normalisation-exact-row-deduplication-0e6d256f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fNbiWzpo2d56ENSCGPKQY

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-exact-row-deduplication-0e6d256f -d '<json body>'
```

Example prompt: Can you normalise the strings and deduplicate exact rows in my record routing data? I have 4 rows across two groups — group-a and group-b — with dates from 2026-10-01 to 2026-10-04, accepted record counts of 10, 20, 15, and 30, and rejected counts of 1, 2, 3, and 4. I need both the normalisation and deduplication reports.

## When to prefer this

Choose this endpoint when you need lightweight, local string normalisation and exact row deduplication specifically on record routing data (accepted_records, rejected_records fields) in batches up to 200 rows. It is ideal for pre-ETL data cleaning, audit workflows, or quick QA passes where no external lookup, ML prediction, or live data enrichment is required. It covers both analytical tasks in a single low-cost call.

## Known failure modes

- More than 200 rows submitted — request exceeds maxItems limit and will be rejected
- Missing required fields (row_id, date, dataset_group, accepted_records, rejected_records) cause validation errors
- Date strings not matching YYYY-MM-DD pattern are rejected
- Numeric values outside ±1,000,000,000,000 range fail schema validation
- Empty rows array (minItems: 1 not met) returns an error

## How this service works

Record routing — String normalisation + Exact row deduplication: String normalisation + Exact row deduplication 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 per call: (1) a string normalisation report showing standardised string fields across the submitted rows, and (2) an exact row deduplication report identifying and removing fully duplicate rows from the accepted_records and rejected_records dataset. Both reports are computed locally with 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-string-normalisation-exact-row-deduplication-0e6d256f/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)