# Request Latency IQR Outlier Flags and Two-Measure Correlation

> Request Latency IQR Outlier Flags and Two-Measure Correlation 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-24).

Analyzes supplied request latency records to flag IQR outliers and compute correlation between latency_ms and request_count, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-software-03-176?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/request-latency-iqr-outlier-flags-and-two-measure-correlation-a1ebd086
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bm79UwgStzp2wgtIlRLCu

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-iqr-outlier-flags-and-two-measure-correlation-a1ebd086 -d '<json body>'
```

Example prompt: Can you run IQR outlier flagging and a two-measure correlation between latency_ms and request_count on my request latency dataset — here are my rows with row_id, component, date, latency_ms, and request_count for up to 200 records?

## When to prefer this

Choose this endpoint when you have up to 200 rows of request latency records and need both IQR-based outlier detection and a statistical correlation between latency and request count in a single low-cost call. It is ideal for lightweight, offline statistical analysis of performance data without requiring a full analytics platform or live monitoring system. Prefer it over general-purpose analytics when cost efficiency ($0.01 for two reports) and simplicity matter.

## Known failure modes

- Input array exceeds 200 rows — request will be rejected or truncated
- Missing required fields (row_id, date, latency_ms, request_count) cause validation errors
- Null or non-numeric latency_ms or request_count values may reduce correlation accuracy or be excluded
- Date strings not matching YYYY-MM-DD pattern will fail schema validation
- Too few rows for meaningful IQR or correlation computation may produce degenerate results

## How this service works

Request latency — IQR outlier flags + Two-measure correlation: IQR outlier flags + Two-measure correlation for supplied request latency records (latency_ms, request_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) per-row IQR outlier flags indicating which latency_ms values fall outside the interquartile range, and (2) a two-measure correlation result between latency_ms and request_count across the supplied dataset. No external data is fetched; analysis is performed entirely on the supplied rows.

## 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-iqr-outlier-flags-and-two-measure-correlation-a1ebd086/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)