# Detection Rules Analytics — Numeric Row Ordering + Secondary-Measure Weighted Mean

> Detection Rules Analytics — Numeric Row Ordering + 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-10-26).

Performs numeric row ordering and secondary-measure weighted mean analysis on detection rules data (rule_count, alert_count), returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-security-17-121?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/detection-rules-analytics-numeric-row-ordering-secondary-measure-a8d841c1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YAumUZ3aOBS6wV5ckkKJ-

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 detection-rules-analytics-numeric-row-ordering-secondary-measure-a8d841c1 -d '<json body>'
```

Example prompt: Can you rank my detection rules records by rule_count and also compute the alert_count weighted mean? I have 4 rows: row-1 on 2026-10-01 with rule_count=10 and alert_count=1 in group-a, row-2 on 2026-10-02 with rule_count=20 and alert_count=2 in group-b, row-3 on 2026-10-03 with rule_count=15 and alert_count=3 in group-a, and row-4 on 2026-10-04 with rule_count=30 and alert_count=4 in group-b.

## When to prefer this

Choose this endpoint when you need to statistically analyze a batch of detection rules records (up to 200 rows) and require both a ranked numeric ordering and a weighted mean of a secondary measure in a single call. Ideal for security analysts who want two complementary statistical views of rule_count and alert_count data without building custom analytics. Not suitable for real-time threat detection, live rule lookups, or datasets larger than 200 rows.

## Known failure modes

- Fewer than 1 row submitted — minItems validation error
- More than 200 rows submitted — maxItems exceeded error
- Missing required fields (row_id, control_group, date, rule_count, alert_count) — schema validation failure
- Invalid date format (not YYYY-MM-DD) — pattern validation error
- row_id or control_group exceeds 80 characters — maxLength error
- Numeric values outside allowed range (±1,000,000,000,000) — range validation error
- Invalid field enum value (not rule_count or alert_count) — enum validation error

## How this service works

Detection rules — Numeric row ordering + Secondary-measure weighted mean: Numeric row ordering + Secondary-measure weighted mean for supplied detection rules records (rule_count, alert_count). 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) numeric row ordering of the submitted detection rules records sorted by the selected field (rule_count or alert_count), and (2) a secondary-measure weighted mean calculation across the dataset. Both reports are computed locally from supplied data with no external lookups.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "control_group",
     "date",
     "rule_count",
     "alert_count"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "rule_count": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "alert_count": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "control_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "rule_count": 10,
     "alert_count": 1,
     "control_group": "group-a"
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "rule_count": 20,
     "alert_count": 2,
     "control_group": "group-b"
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "rule_count": 15,
     "alert_count": 3,
     "control_group": "group-a"
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "rule_count": 30,
     "alert_count": 4,
     "control_group": "group-b"
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "rule_count",
    "alert_count"
   ],
   "type": "string",
   "default": "rule_count"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/detection-rules-analytics-numeric-row-ordering-secondary-measure-a8d841c1/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)