# Pipeline Durations Analytics — Numeric Row Ordering + Adjacent Row Changes

> Pipeline Durations Analytics — Numeric Row Ordering + Adjacent Row Changes 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-15).

Analyzes pipeline duration records to produce numeric row ordering and adjacent row change reports for run_seconds or processed_rows fields.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-05-116?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pipeline-durations-analytics-numeric-row-ordering-adjacent-row-changes-ccee1cef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m2sY-Dtxt7FRm396VwiLV

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-numeric-row-ordering-adjacent-row-changes-ccee1cef -d '<json body>'
```

Example prompt: Analyze my pipeline run data and give me two reports — one that ranks each run numerically by run_seconds, and one showing the change in run_seconds between adjacent rows. Here are my records: row-1 on 2026-10-01 for group-a with 120 seconds and 5000 rows, row-2 on 2026-10-02 for group-b with 95 seconds and 4800 rows, row-3 on 2026-10-03 for group-a with 200 seconds and 6200 rows.

## When to prefer this

Choose this endpoint when you need both numeric ranking and sequential delta analysis on pipeline duration data (run_seconds or processed_rows) in a single low-cost call. It is ideal for ETL monitoring, performance auditing, and detecting anomalies in batch pipeline runs without needing a database or external analytics platform. Best when you have up to 200 records ready to submit and want two complementary views — ordered ranking plus row-over-row changes — delivered together.

## Known failure modes

- Missing required fields (row_id, date, run_seconds, processed_rows) causes validation failure
- More than 200 rows submitted exceeds the limit and will be rejected
- Invalid date format (not YYYY-MM-DD) causes schema validation error
- Null values in the selected field may produce null deltas in the adjacent row changes report
- Invalid field enum value (anything other than run_seconds or processed_rows) causes rejection

## How this service works

Pipeline durations — Numeric row ordering + Adjacent row changes: Numeric row ordering + Adjacent row changes 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 numeric row ordering report ranking each pipeline record by the selected field (run_seconds or processed_rows), and (2) an adjacent row changes report showing the delta between consecutive rows for the selected field. Both reports are computed locally against the supplied data 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-numeric-row-ordering-adjacent-row-changes-ccee1cef/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)