# Record Routing Analytics — Numeric Row Ordering & Weighted Mean

> Record Routing Analytics — Numeric Row Ordering & 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-10-15).

Computes numeric row ordering and secondary-measure weighted mean for up to 200 rows of record routing data (accepted_records, rejected_records) across two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-121?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-numeric-row-ordering-weighted-mean-b57899f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__CwYAeY4fmaBAWoK44EIF

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-numeric-row-ordering-weighted-mean-b57899f6 -d '<json body>'
```

Example prompt: Can you rank these 4 routing rows by accepted_records and compute a weighted mean — row-1 (group-a, 2026-10-01, accepted=10, rejected=1), row-2 (group-b, 2026-10-02, accepted=20, rejected=2), row-3 (group-a, 2026-10-03, accepted=15, rejected=3), row-4 (group-b, 2026-10-04, accepted=30, rejected=4) — using accepted_records as the primary field?

## When to prefer this

Choose this endpoint when you need lightweight, local numeric row ordering and weighted mean analytics on record routing data (accepted/rejected counts) without any external API calls, predictions, or live lookups. It is ideal for data quality pipelines, ETL auditing, and batch analytics on up to 200 rows at minimal cost ($0.01 USDC for two reports).

## Known failure modes

- More than 200 rows submitted — request rejected at max item limit
- Missing required fields (row_id, date, dataset_group, accepted_records, rejected_records) cause validation error
- Invalid date format (not YYYY-MM-DD) fails pattern validation
- Field value outside numeric range (-1,000,000,000,000 to 1,000,000,000,000) rejected
- Empty rows array (minItems: 1 violated) returns error
- Invalid field enum value (not accepted_records or rejected_records) causes rejection

## How this service works

Record routing — Numeric row ordering + Secondary-measure weighted mean: Numeric row ordering + 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 independent analytical reports: (1) a numeric row ordering of the supplied routing records ranked by the chosen field (accepted_records or rejected_records), and (2) a secondary-measure weighted mean computed across all provided rows. Results are computed locally with no external lookup or prediction.

## 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-numeric-row-ordering-weighted-mean-b57899f6/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)