# Vulnerability Queues: String Normalisation + Numeric Row Ordering

> Vulnerability Queues: 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-23).

Normalises string fields and sorts rows numerically for vulnerability queue records (open_findings, remediated_findings), producing 2 analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-security-03-025?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/vulnerability-queues-string-normalisation-numeric-row-ordering-ca1d3b77
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wVtWb8mE6vLckYbGbVVgG

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 vulnerability-queues-string-normalisation-numeric-row-ordering-ca1d3b77 -d '<json body>'
```

Example prompt: Can you normalize the string fields and sort rows numerically for my vulnerability queue data? I have up to 50 rows with open_findings and remediated_findings across control groups, and I need both reports — one for string normalisation and one for numeric row ordering on the open_findings field.

## When to prefer this

Choose this endpoint when you have vulnerability queue records (open_findings / remediated_findings) that need both string-field standardisation and numeric sorting in a single low-cost call. It is ideal for preprocessing security data exports before dashboarding or reporting, when you do not need live threat intelligence, predictions, or external lookups — just clean, ordered data from what you already have.

## Known failure modes

- Exceeding 200 rows results in rejection — trim input to 200 rows maximum
- Missing required fields (row_id, date, open_findings, remediated_findings) cause validation errors
- Invalid date format (not YYYY-MM-DD) triggers schema validation failure
- Null values in the selected numeric field may affect ordering output
- Payment not provided or incorrect amount results in 402 error

## How this service works

Vulnerability queues — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied vulnerability queues records (open_findings, remediated_findings). 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 derived from the supplied rows: a string normalisation report (standardising text fields like row_id and control_group) and a numeric row ordering report (ranking rows by the selected numeric field, either open_findings or remediated_findings). No external lookups or live data — all analysis is performed locally on the submitted data.

## Request schema (JSON Schema)

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

## More

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