# Record Routing Analytics — Secondary-Measure Weighted Mean + Explicit Missing-Value Fill

> Record Routing Analytics — Secondary-Measure Weighted Mean + 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-15).

Computes a secondary-measure weighted mean and fills missing values explicitly for up to 200 record routing rows (accepted_records, rejected_records), returning 2 analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-187?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-analytics-secondary-measure-weighted-mean-explicit-99df13bb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8M9chWnGmp9NmYXKtppq5

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-secondary-measure-weighted-mean-explicit-99df13bb -d '<json body>'
```

Example prompt: I have 4 rows of daily record routing data — 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 null accepted and 3 rejected on 2026-10-03, and group-b had 30 accepted and 4 rejected on 2026-10-04 — can you compute the weighted mean of accepted_records (weighted by rejected_records) and fill any missing accepted_records values using the median?

## When to prefer this

Choose this endpoint when you have tabular record routing data (accepted/rejected counts) with potential nulls and need both a weighted mean statistic and explicit missing-value imputation in a single $0.01 call. It is ideal for pre-processing routing metrics before downstream aggregation or reporting, supporting up to 200 rows. Prefer it over general statistics APIs when your data specifically tracks accepted_records and rejected_records by date and dataset group, and you need both analytics together.

## Known failure modes

- Rows array exceeds 200 items — request rejected
- Missing required fields (row_id, date, dataset_group) in any row — validation error
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Unknown fill method or field value outside allowed enums — error response
- All values for the target field are null — weighted mean may be undefined or return an error

## How this service works

Record routing — Secondary-measure weighted mean + Explicit missing-value fill: Secondary-measure weighted mean + 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

Returns 2 analytical reports: (1) a weighted mean of the specified field (accepted_records or rejected_records) using the other measure as the weight, and (2) the same dataset with missing values in the target field explicitly filled using the chosen method (zero, mean, or median). No external lookups or predictions are made; all computation 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-analytics-secondary-measure-weighted-mean-explicit-99df13bb/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)