# Correction Logs Quality Audit and Numeric Row Ordering

> Correction Logs Quality Audit and 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-10-30).

Performs a record quality audit and numeric row ordering on supplied correction log data (correction_count, published_items) for up to 200 rows, returning 2 independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-news-04-007?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/correction-logs-quality-audit-and-numeric-row-ordering-75da2f7e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TwO_GEMORFLoXKNHewQLN

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-quality-audit-and-numeric-row-ordering-75da2f7e -d '<json body>'
```

Example prompt: Can you run a quality audit and numeric row ordering on these correction logs — I have 4 rows with fields like correction_count and published_items across channel groups, and I want both reports for the correction_count field?

## When to prefer this

Choose this endpoint when you have tabular correction log data with correction_count and published_items fields and need both a data quality audit and a numeric ranking of rows in a single call. Ideal for editorial teams auditing news correction records or analysts validating correction log datasets before downstream reporting. Not suitable for live data lookups, predictive analytics, or datasets larger than 200 rows.

## Known failure modes

- Input array exceeds 200 rows — request rejected
- Missing required fields (row_id, date, channel_group) on any row — validation error
- Invalid date format (must match YYYY-MM-DD pattern) — schema validation failure
- Numeric values outside allowed range (-1e12 to 1e12) — rejected
- Empty rows array — minimum 1 item required
- Invalid field enum value (must be correction_count or published_items) — error

## How this service works

Correction logs — Record quality audit + Numeric row ordering: Record quality audit + 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 two independent analytical reports: (1) a record quality audit flagging completeness and data issues across the supplied rows, and (2) a numeric row ordering ranking rows by the chosen field (correction_count or published_items). Up to 200 rows processed per call; no external lookups or live data involved.

## 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-quality-audit-and-numeric-row-ordering-75da2f7e/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)