# Release Note Coverage: Numeric Row Ordering + Two-Measure Correlation

> Release Note Coverage: 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-24).

Ranks rows numerically and computes correlation between documented_changes and released_changes fields for up to 200 release note coverage records, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-writing-15-120?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/release-note-coverage-numeric-row-ordering-two-measure-correlation-0f77b44e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_w7WCU2To0-YoJcSdfEU_H

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 release-note-coverage-numeric-row-ordering-two-measure-correlation-0f77b44e -d '<json body>'
```

Example prompt: I have a set of release note records with documented_changes and released_changes counts per row — can you rank them numerically by documented_changes and also compute the correlation between documented_changes and released_changes for these rows: row-1 (group-a, 2024-01-10, documented=10, released=1), row-2 (group-b, 2024-01-11, documented=20, released=2), row-3 (group-a, 2024-01-12, documented=15, released=3)?

## When to prefer this

Choose this endpoint when you need both a ranked ordering of release note records AND a correlation between two numeric change metrics in a single call against your own supplied data (up to 200 rows). It is ideal when you do not need live data lookup, external enrichment, or predictive modeling — just fast, local computation on structured release coverage records with documented_changes and released_changes fields.

## Known failure modes

- Fewer than 1 row submitted — endpoint requires minItems: 1
- More than 200 rows submitted — maxItems: 200 limit exceeded, request rejected
- Missing required fields (row_id, date, documented_changes, released_changes) on any row — validation error
- Invalid date format (must match YYYY-MM-DD pattern) — schema validation failure
- All values for one measure are null — correlation cannot be computed, partial result or error returned
- Payment of 0.01 USDC not included or rejected — 402 Payment Required response

## How this service works

Release note coverage — Numeric row ordering + Two-measure correlation: Numeric row ordering + Two-measure correlation for supplied release note coverage records (documented_changes, released_changes). 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

Two analytical reports: (1) a numeric row ordering of the supplied records ranked by the selected field (documented_changes or released_changes), and (2) a Pearson or equivalent correlation between documented_changes and released_changes across all supplied rows. No external data is fetched; all computation is performed locally on the submitted dataset.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/release-note-coverage-numeric-row-ordering-two-measure-correlation-0f77b44e/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)