# Record Routing – String Normalisation + Category Frequencies

> Record Routing – String Normalisation + Category Frequencies 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).

Computes string normalisation and category frequency reports for accepted_records and rejected_records fields across up to 200 record routing rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-024?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-category-frequencies-e4818424
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KiVXMrWKboxc7r3s9HNNf

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-category-frequencies-e4818424 -d '<json body>'
```

Example prompt: Analyse these 4 record routing rows — 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, and row-4 on 2026-10-04 in group-b with 30 accepted and 4 rejected — give me the string normalisation and category frequency reports.

## When to prefer this

Choose this endpoint when you need lightweight, local string normalisation and category frequency analytics on record routing data (accepted/rejected record counts) without requiring any external data lookup, prediction, or live API calls. It is especially useful for ETL pipeline audits, data quality reviews, and summarising routing distributions across dataset groups at low cost ($0.01 for up to 200 rows with two reports).

## Known failure modes

- More than 200 rows submitted — request will be rejected or truncated
- Missing required fields (row_id, date, accepted_records, rejected_records) cause row-level errors
- Date strings not matching YYYY-MM-DD pattern will fail validation
- Null numeric values may be excluded from frequency calculations
- row_id exceeding 80 characters will be rejected

## How this service works

Record routing — String normalisation + Category frequencies: String normalisation + Category frequencies 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

Two analytical reports per call: (1) a string normalisation report that standardises the string fields (such as dataset_group) across the submitted rows, and (2) a category frequency report showing how often each distinct category value appears in the accepted_records and rejected_records fields. Results are computed locally with no external lookups, covering up to 200 input 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-string-normalisation-category-frequencies-e4818424/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)