# Correction Logs — String Normalisation + Two-Measure Correlation

> Correction Logs — String Normalisation + 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-11-02).

Normalises string fields and computes a two-measure correlation between correction_count and published_items for up to 200 correction log rows, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-news-04-033?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-string-normalisation-two-measure-correlation-90316d93
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Cbr3E7zQKx3s6lJVwtZJf

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-string-normalisation-two-measure-correlation-90316d93 -d '<json body>'
```

Example prompt: Can you run string normalisation and a two-measure correlation on these correction logs — I have 4 rows with channel groups 'group-a' and 'group-b', dates from 2026-10-01 to 2026-10-04, correction counts of 10, 20, 15, 30 and published items of 1, 2, 3, 4?

## When to prefer this

Choose this endpoint when you have correction log data with both string fields (like channel_group) that need normalisation and two numeric measures (correction_count and published_items) you want correlated, and you want both analyses in a single $0.01 call for up to 200 rows without needing live lookup or prediction.

## Known failure modes

- Missing required fields (row_id, date, channel_group, correction_count, published_items) cause validation errors
- Submitting more than 200 rows exceeds the row limit and will be rejected
- Invalid date format (not YYYY-MM-DD) triggers schema validation failure
- Null values for both numeric measures may prevent correlation computation
- Payment of 0.01 USDC not provided results in 402 Payment Required response

## How this service works

Correction logs — String normalisation + Two-measure correlation: String normalisation + Two-measure correlation 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

Two structured analytical reports: (1) a string normalisation report covering the channel_group and other string fields across up to 200 rows, and (2) a two-measure correlation report quantifying the statistical relationship between correction_count and published_items across the supplied rows.

## 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/correction-logs-string-normalisation-two-measure-correlation-90316d93/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)