# Editorial Turnaround String Normalisation & Numeric Row Ordering

> Editorial Turnaround String Normalisation & 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).

Normalises string fields and orders rows numerically for editorial turnaround records containing draft_hours and review_hours data, producing two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-news-15-025?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/editorial-turnaround-string-normalisation-numeric-row-ordering-453f5dba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KjV27y_s_8HaD8PyojJTh

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 editorial-turnaround-string-normalisation-numeric-row-ordering-453f5dba -d '<json body>'
```

Example prompt: I have 4 editorial turnaround records for October 2026 — row-1 (group-a, draft 10h, review 1h), row-2 (group-b, draft 20h, review 2h), row-3 (group-a, draft 15h, review 3h), row-4 (group-b, draft 30h, review 4h) — can you normalise the string fields and sort them by draft_hours, giving me two reports?

## When to prefer this

Choose this endpoint when you have up to 200 editorial turnaround records (with draft_hours and review_hours) that need both string field normalisation and numeric row ordering in a single call, and you want two independent reports without any live data lookup, prediction, or external action. It is particularly suited for pre-reporting data cleaning of editorial workflow datasets where channel group label consistency and time-ranked ordering are both required.

## Known failure modes

- More than 200 rows submitted — request rejected due to maxItems constraint
- Missing required fields (row_id, channel_group, date, draft_hours, review_hours) — validation error
- Invalid date format not matching YYYY-MM-DD pattern — schema validation failure
- Invalid field enum value other than draft_hours or review_hours — rejected
- Empty rows array — minItems violation
- Numeric values outside the allowed range — schema rejection

## How this service works

Editorial turnaround — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied editorial turnaround records (draft_hours, review_hours). 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: one with string-normalised editorial turnaround records (cleaned channel_group and string fields) and one with rows ordered numerically by the selected field (draft_hours or review_hours), covering up to 200 input rows processed entirely with local analytical engines.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/editorial-turnaround-string-normalisation-numeric-row-ordering-453f5dba/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)