# Pipeline Durations Analytics: Two-Measure Correlation + Date-by-Category Pivot

> Pipeline Durations Analytics: Two-Measure Correlation + Date-by-Category Pivot 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-14).

Runs two local analytical reports on pipeline duration data: a Pearson/rank correlation between run_seconds and processed_rows, plus a date-by-category pivot table, for up to 200 supplied rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-05-182?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pipeline-durations-analytics-two-measure-correlation-date-by-category-f549b130
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_F68gaDsmcG_K0hY1YDjFR

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 pipeline-durations-analytics-two-measure-correlation-date-by-category-f549b130 -d '<json body>'
```

Example prompt: Can you analyze my pipeline run data and give me both a correlation between run_seconds and processed_rows, and a date-by-group pivot table? Here are my rows: [{"row_id":"r1","dataset_group":"ingest","date":"2024-03-01","run_seconds":120,"processed_rows":5000},{"row_id":"r2","dataset_group":"transform","date":"2024-03-01","run_seconds":240,"processed_rows":9800},{"row_id":"r3","dataset_group":"ingest","date":"2024-03-02","run_seconds":95,"processed_rows":4200}]

## When to prefer this

Choose this endpoint when you have up to 200 pipeline execution records and need both a correlation analysis between run duration and row volume AND a date-grouped pivot table in a single call. It is purpose-built for ETL/pipeline performance analytics and runs entirely on supplied data with no external dependencies, making it fast, deterministic, and privacy-safe. Prefer it over general-purpose analytics tools when you want two specific report types (correlation + pivot) for pipeline metrics without standing up infrastructure.

## Known failure modes

- Fewer than 1 row supplied — request rejected
- More than 200 rows supplied — exceeds maxItems limit
- Missing required fields (row_id, dataset_group, date, run_seconds, processed_rows) on any row
- Date field not matching YYYY-MM-DD pattern — schema validation error
- All values for a measure are null — correlation cannot be computed
- Invalid field enum value (not run_seconds or processed_rows)
- Payment not included or insufficient — x402 payment required error

## How this service works

Pipeline durations — Two-measure correlation + Date by category pivot: Two-measure correlation + Date by category pivot for supplied pipeline durations records (run_seconds, processed_rows). 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 independent analytical reports: (1) a two-measure correlation report showing the statistical relationship (e.g., Pearson r) between run_seconds and processed_rows across the supplied rows, and (2) a date-by-category pivot table aggregating the selected field (run_seconds or processed_rows) grouped by date and dataset_group. All computation is local with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pipeline-durations-analytics-two-measure-correlation-date-by-category-f549b130/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)