# Release Note Coverage — Duplicate Key Report + Numeric Distribution

> Release Note Coverage — Duplicate Key Report + Numeric Distribution 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-23).

Analyzes up to 200 release note coverage records to produce two local analytical reports: a duplicate key report and a numeric distribution summary for documented_changes or released_changes.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-writing-15-055?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/release-note-coverage-duplicate-key-report-numeric-distribution-064ebe05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6bRVVK6i5LJxIUVRHFDGU

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-duplicate-key-report-numeric-distribution-064ebe05 -d '<json body>'
```

Example prompt: Can you run a duplicate key check and numeric distribution report on my release note coverage data? Here are up to 200 rows with row_id, document_group, date, released_changes, and documented_changes — analyze the documented_changes field for the distribution.

## When to prefer this

Choose this endpoint when you need to quickly audit a batch of release note coverage records (up to 200 rows) for duplicate keys and understand the numeric distribution of change counts, without requiring external data lookups or real-time computation. It is ideal for pre-publish QA, sprint review automation, or data hygiene checks on release documentation datasets.

## Known failure modes

- Empty rows array returns an error (minItems: 1)
- More than 200 rows submitted exceeds the maxItems limit
- Invalid date format (not YYYY-MM-DD) causes schema validation failure
- Missing required fields (row_id, document_group, date, documented_changes, released_changes) on any row causes rejection
- Invalid field enum value (not 'documented_changes' or 'released_changes') causes an error
- Numeric values outside allowed range (-1e12 to 1e12) are rejected

## How this service works

Release note coverage — Duplicate key report + Numeric distribution: Duplicate key report + Numeric distribution 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 independent analytical reports: (1) a duplicate key report identifying rows sharing the same key values across up to 200 input records, and (2) a numeric distribution summary for the selected field (documented_changes or released_changes), including frequency and spread statistics. No external lookups or predictions are made.

## 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-duplicate-key-report-numeric-distribution-064ebe05/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)