# Record Routing IQR Outlier Flags + Secondary-Measure Weighted Mean Analytics

> Record Routing IQR Outlier Flags + Secondary-Measure Weighted Mean 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-23).

Computes IQR-based outlier flags and secondary-measure weighted mean statistics on accepted_records and rejected_records data for record routing datasets, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-177?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/record-routing-iqr-outlier-flags-secondary-measure-weighted-mean-71d6dd71
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BV1Eyb0wK-M0pVG9Z2YOD

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-iqr-outlier-flags-secondary-measure-weighted-mean-71d6dd71 -d '<json body>'
```

Example prompt: Can you run IQR outlier detection and a secondary-measure weighted mean on my record routing data — I have rows with accepted_records and rejected_records across groups like 'group-a' and 'group-b' from October 2026, and I want to analyze the accepted_records field?

## When to prefer this

Choose this endpoint when you have up to 200 rows of record routing data (with accepted_records and rejected_records fields) and need both IQR-based outlier flagging and a secondary-measure weighted mean in a single low-cost call. It is ideal for offline/batch statistical quality checks on data pipeline routing logs where no live lookup, prediction, or external action is needed. Prefer this over general-purpose analytics APIs when you want a pre-packaged dual-report (two analyses for one $0.01 USDC call) specifically tailored to record routing acceptance and rejection metrics.

## Known failure modes

- Fewer than 1 row submitted — rejected by minItems constraint
- More than 200 rows submitted — rejected by maxItems constraint
- Missing required fields (row_id, date, dataset_group, accepted_records, rejected_records) — validation error
- Invalid date format not matching YYYY-MM-DD pattern — schema rejection
- Non-numeric values in accepted_records or rejected_records where numbers are expected — type error
- Payment failure or insufficient USDC balance — request not processed

## How this service works

Record routing — IQR outlier flags + Secondary-measure weighted mean: IQR outlier flags + 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 two analytical reports: (1) IQR outlier flags for each row indicating whether the selected measure (accepted_records or rejected_records) is a statistical outlier based on interquartile range, and (2) a secondary-measure weighted mean summarizing the selected field across the supplied rows. No external lookups or predictions are included.

## 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-iqr-outlier-flags-secondary-measure-weighted-mean-71d6dd71/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)