# Alert Triage String Normalisation & Numeric Row Ordering

> Alert Triage String Normalisation & Numeric Row Ordering 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-25).

Normalises string fields and orders rows numerically for alert triage records (alert_count, confirmed_events) across up to 200 rows, returning 2 analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-security-18-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alert-triage-string-normalisation-numeric-row-ordering-6d39aa1c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tGx3z3AuZnqZ7JolJimYD

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 alert-triage-string-normalisation-numeric-row-ordering-6d39aa1c -d '<json body>'
```

Example prompt: Can you normalise the string fields and sort these alert triage rows numerically by alert_count? I have 4 rows with dates from 2026-10-01 to 2026-10-04, control groups group-a and group-b, and alert counts of 10, 20, 15, and 30.

## When to prefer this

Choose this endpoint when you have alert triage tabular data (up to 200 rows) that needs both string normalisation and numeric row ordering in a single call, and you want two structured analytical reports at low cost ($0.01 USDC). It operates fully offline on supplied data with no external dependencies, making it suitable for sensitive security operations data that should not leave your pipeline beyond this processing step.

## Known failure modes

- Rows array exceeds 200 items — request rejected
- Missing required fields (row_id, date, alert_count, confirmed_events) — validation error
- Date field does not match YYYY-MM-DD pattern — schema validation failure
- Numeric values outside allowed range (±1,000,000,000,000) — rejection
- Empty rows array (minItems: 1 not met) — error response
- Invalid field enum value (not alert_count or confirmed_events) — rejected

## How this service works

Alert triage — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied alert triage records (alert_count, confirmed_events). 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

Two independent analytical reports per call: one covering string normalisation of fields like control_group, and one covering numeric row ordering based on the selected field (alert_count or confirmed_events). Results are derived entirely from the supplied data using local analytical engines with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/alert-triage-string-normalisation-numeric-row-ordering-6d39aa1c/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)