# Record Routing — String Normalisation + Explicit Missing-Value Fill

> Record Routing — String Normalisation + Explicit Missing-Value Fill 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).

Normalises string fields and fills missing values (accepted_records, rejected_records) in record routing datasets of up to 200 rows, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-037?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-explicit-missing-value-fill-fc5324e2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1x928vKRrvxfGtDgaZ5Ph

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-explicit-missing-value-fill-fc5324e2 -d '<json body>'
```

Example prompt: Clean up my record routing dataset — I have up to 50 rows with accepted_records and rejected_records fields, some of which are null. Fill the missing accepted_records values using median imputation and normalise the string fields. Here's the data: [{"row_id":"r1","dataset_group":"group-a","date":"2026-10-01","accepted_records":null,"rejected_records":2}].

## When to prefer this

Choose this endpoint when you need lightweight, offline string normalisation and missing-value imputation for record routing datasets (accepted/rejected record counts) without any external data lookups, predictions, or live API calls. Ideal for ETL preprocessing, data quality checks, and pipeline hygiene steps on batches up to 200 rows at minimal cost ($0.01 USDC for two reports).

## Known failure modes

- More than 200 rows submitted — request rejected
- Missing required fields (row_id, date, dataset_group) — validation error
- Invalid date format (must be YYYY-MM-DD) — schema validation failure
- Unsupported imputation method outside enum (zero, mean, median) — rejected
- Field selector outside allowed enum (accepted_records, rejected_records) — error
- Numeric values outside allowed range (±1,000,000,000,000) — validation error

## How this service works

Record routing — String normalisation + Explicit missing-value fill: String normalisation + Explicit missing-value fill 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 independent analytical reports covering string normalisation results and missing-value fill results for the accepted_records and rejected_records fields respectively, applied to up to 200 submitted rows. No external lookups or predictions are made — all processing is local.

## 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"
  },
  "method": {
   "enum": [
    "zero",
    "mean",
    "median"
   ],
   "type": "string",
   "default": "median"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-string-normalisation-explicit-missing-value-fill-fc5324e2/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)