# Process Handoffs — Numeric Row Ordering + Two-Measure Correlation

> Process Handoffs — Numeric Row Ordering + 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-25).

Performs numeric row ordering and two-measure correlation analysis on process handoff records (handoff_count and wait_minutes) for up to 200 rows, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-operations-18-120?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/process-handoffs-numeric-row-ordering-two-measure-correlation-4636a8f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ol3auN1sHJTGaeHNXnhzc

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 process-handoffs-numeric-row-ordering-two-measure-correlation-4636a8f7 -d '<json body>'
```

Example prompt: Can you run a numeric row ordering and two-measure correlation analysis on these process handoff records — I have up to 50 rows with handoff_count and wait_minutes per team group by date, and I want both reports back for the handoff_count field.

## When to prefer this

Choose this endpoint when you need both numeric row ranking and correlation analysis for process handoff data (handoff_count vs wait_minutes) in a single low-cost call. It is ideal for small-to-medium datasets (up to 200 rows) where you want offline, reproducible statistical summaries without any live data lookups or external predictions. Prefer it over generic analytics tools when your data already fits the handoff schema and you need two bundled reports in one payment.

## Known failure modes

- More than 200 rows submitted — exceeds the maxItems limit and will be rejected
- Missing required fields (row_id, date, team_group, handoff_count, or wait_minutes) cause validation errors
- Invalid date format (must match YYYY-MM-DD pattern)
- Null values in numeric fields may affect correlation computation
- field enum value not matching 'handoff_count' or 'wait_minutes' causes rejection

## How this service works

Process handoffs — Numeric row ordering + Two-measure correlation: Numeric row ordering + Two-measure correlation for supplied process handoffs records (handoff_count, wait_minutes). 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) a numeric row ordering of the supplied handoff records, and (2) a two-measure correlation analysis between handoff_count and wait_minutes — all computed locally on the supplied data with no external lookups or predictions.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/process-handoffs-numeric-row-ordering-two-measure-correlation-4636a8f7/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)