# Record Routing Analytics: String Normalisation + Secondary-Measure Weighted Mean

> Record Routing Analytics: String Normalisation + Secondary-Measure Weighted Mean is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-03).

Performs string normalisation and secondary-measure weighted mean calculations on record routing data (accepted_records, rejected_records) for up to 200 rows, returning 2 analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-034?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/record-routing-analytics-string-normalisation-secondary-measure-37a8e1ee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h3RziCdJBVWgyZpPfrQwB

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-analytics-string-normalisation-secondary-measure-37a8e1ee -d '<json body>'
```

Example prompt: I have 4 rows of record routing data across two groups — group-a had 10 accepted and 1 rejected on 2026-10-01, group-b had 20 accepted and 2 rejected on 2026-10-02, group-a had 15 accepted and 3 rejected on 2026-10-03, and group-b had 30 accepted and 4 rejected on 2026-10-04. Can you run string normalisation and weighted mean analytics on the accepted_records field and give me both reports?

## When to prefer this

Choose this endpoint when you need offline, local computation of string normalisation and weighted mean statistics on record routing data (accepted vs rejected counts) for up to 200 rows in a single call, and you want two bundled analytical reports for a fixed low cost. It is not a live lookup or predictive service — ideal for post-hoc batch analytics on routing pipeline outputs.

## Known failure modes

- Rows array exceeds 200 items — request rejected
- Missing required fields (row_id, date, accepted_records, rejected_records) — validation error
- Date field does not match YYYY-MM-DD pattern — schema validation failure
- Numeric values outside allowed range (±1,000,000,000,000) — rejected
- Invalid field enum value (not 'accepted_records' or 'rejected_records') — error

## How this service works

Record routing — String normalisation + Secondary-measure weighted mean: String normalisation + Secondary-measure weighted mean 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 2 analytical reports covering (1) string normalisation of the specified field across the submitted rows and (2) a secondary-measure weighted mean calculation, both computed locally without external lookups. Reports are based solely on the supplied accepted_records and rejected_records data for 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-analytics-string-normalisation-secondary-measure-37a8e1ee/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)