# Record Routing String Normalisation + Base-100 Series Analytics

> Record Routing String Normalisation + Base-100 Series Analytics 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).

Computes string normalisation and base-100 index series for accepted_records and rejected_records fields across up to 200 supplied record routing rows, returning two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-030?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-base-100-series-analytics-e0602200
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A5ggVcNJCF_DJC-i7LTH0

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-base-100-series-analytics-e0602200 -d '<json body>'
```

Example prompt: Can you run string normalisation and a base-100 index series on my record routing data — I have 4 rows across group-a and group-b from 2026-10-01 to 2026-10-04, with accepted_records values of 10, 20, 15, 30 and rejected_records of 1, 2, 3, 4, starting the base index at row 0, and I want the report for the accepted_records field?

## When to prefer this

Choose this endpoint when you need offline, local string normalisation and base-100 index series computation on record routing data (accepted_records and rejected_records) for up to 200 rows, without requiring any live lookup, prediction, or external data enrichment. Ideal for batch analytical reporting on routing quality metrics grouped by dataset_group and date.

## Known failure modes

- More than 200 rows submitted — request exceeds maxItems limit
- Missing required fields (row_id, date, accepted_records, rejected_records) in any row — validation error
- date field does not match YYYY-MM-DD pattern — schema validation failure
- base_index value out of range (0–199) — invalid parameter
- field enum value not one of accepted_records or rejected_records — validation error
- Empty rows array — minItems constraint violated

## How this service works

Record routing — String normalisation + Base-100 series: String normalisation + Base-100 series 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: a string normalisation report and a base-100 index series, computed locally from the supplied record routing rows (accepted_records and rejected_records fields). No external data is fetched; all analysis is derived from the submitted dataset of up to 200 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
  },
  "field": {
   "enum": [
    "accepted_records",
    "rejected_records"
   ],
   "type": "string",
   "default": "accepted_records"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-string-normalisation-base-100-series-analytics-e0602200/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)