# Correction Logs — Numeric Distribution + Numeric Row Ordering

> Correction Logs — Numeric Distribution + Numeric Row Ordering is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-02).

Computes numeric distribution statistics and numeric row ordering for correction log data (correction_count, published_items) on up to 200 supplied rows, returning 2 independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-news-04-073?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/correction-logs-numeric-distribution-numeric-row-ordering-dac7566f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3Ug3S1iW5UjGuVPcoBGmW

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 correction-logs-numeric-distribution-numeric-row-ordering-dac7566f -d '<json body>'
```

Example prompt: Can you run a numeric distribution and row ordering analysis on my correction log data — I have rows with correction_count and published_items by channel_group and date — and give me both reports for the correction_count field?

## When to prefer this

Choose this endpoint when you have tabular correction log data (up to 200 rows) with numeric fields and need both a distribution breakdown and a row-level numeric ranking in a single low-cost call. It is purpose-built for editorial/news correction data with channel_group and date dimensions. Prefer it over generic analytics tools when you want a fast, offline (no external lookup) dual-report output for correction_count or published_items.

## Known failure modes

- Fewer than 1 row supplied — minItems violation returns validation error
- More than 200 rows supplied — maxItems exceeded, request rejected
- Invalid date format (not YYYY-MM-DD) causes schema validation failure
- Missing required fields (row_id, channel_group, date, correction_count, published_items) causes row rejection
- Field enum value not 'correction_count' or 'published_items' causes error
- Null values in the selected numeric field may affect distribution and ordering results
- Payment of 0.01 USDC not included causes x402 payment required response

## How this service works

Correction logs — Numeric distribution + Numeric row ordering: Numeric distribution + Numeric row ordering for supplied correction logs records (correction_count, published_items). 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 2 independent analytical reports: (1) a numeric distribution report showing how values of the selected field (correction_count or published_items) are spread across the supplied rows, and (2) a numeric row ordering report ranking the rows by the selected numeric field — all computed locally on the supplied data with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/correction-logs-numeric-distribution-numeric-row-ordering-dac7566f/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)