# Request Latency — Record Quality Audit + String Normalisation + Numeric Row Ordering

> Request Latency — Record Quality Audit + 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-11-02).

Audits record quality, normalises string fields, and orders rows numerically for up to 200 request latency records (latency_ms, request_count) in three bundled reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-software-03-196?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/request-latency-record-quality-audit-string-normalisation-numeric-row-c5add4a7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WKDCreJeSi9seF1KmCS0Q

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 request-latency-record-quality-audit-string-normalisation-numeric-row-c5add4a7 -d '<json body>'
```

Example prompt: Can you run a record quality audit, string normalisation, and numeric row ordering on my request latency dataset? I have rows with fields like row_id, component, date, latency_ms, and request_count — up to 50 rows — and I want the analysis focused on latency_ms.

## When to prefer this

Choose this endpoint when you need three bundled data-quality operations (audit, string normalisation, row ordering) on request latency tabular data in a single low-cost call. It is ideal for pre-processing raw latency logs before dashboarding, reporting, or storage. It does not perform live monitoring, prediction, or external lookups, so prefer it for offline batch cleaning of up to 200 rows rather than real-time alerting.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, component, date, latency_ms, request_count) causes rejection
- Invalid date format (not YYYY-MM-DD) fails schema validation
- Selecting a field value other than 'latency_ms' or 'request_count' is rejected by enum constraint
- Empty rows array is rejected (minItems: 1)
- Payment failure via x402 protocol blocks the request

## How this service works

Request latency — Record quality audit + String normalisation + Numeric row ordering: Record quality audit + String normalisation + Numeric row ordering for supplied request latency records (latency_ms, request_count). Up to 200 rows; 3 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 3 supplied-data reports for up to 200 rows.

## Output

Three independent analytical reports per call: (1) a record quality audit flagging issues in the supplied rows, (2) a string normalisation report on text fields like component names, and (3) a numeric row ordering report ranking rows by the selected numeric field (latency_ms or request_count). All analysis is performed locally on the supplied data with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/request-latency-record-quality-audit-string-normalisation-numeric-row-c5add4a7/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)