# Camera Coverage String Normalisation and Numeric Row Ordering

> Camera Coverage String Normalisation 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-21).

Normalises string fields and orders rows numerically for camera coverage records containing shot_count and coverage_seconds, producing 2 analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-creative-12-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/camera-coverage-string-normalisation-and-numeric-row-ordering-eeba1212
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mClzjCQf7lknX-DR9hxCs

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 camera-coverage-string-normalisation-and-numeric-row-ordering-eeba1212 -d '<json body>'
```

Example prompt: I have a list of camera coverage records with shot counts and coverage seconds across different asset groups — can you normalise the string fields and sort the rows by shot_count so I get two clean analytical reports? I'll send up to 4 rows: row-1 on 2026-10-01 for group-a with 10 shots and 1 second, row-2 on 2026-10-02 for group-b with 20 shots and 2 seconds, row-3 on 2026-10-03 for group-a with 15 shots and 3 seconds, row-4 on 2026-10-04 for group-b with 30 shots and 4 seconds.

## When to prefer this

Choose this endpoint when you have camera coverage tabular data (shot_count, coverage_seconds per asset group and date) and need both string normalisation and numeric ordering in a single low-cost call. It is purpose-built for media production analytics workflows where data cleanliness and ranking are needed together, with no external lookup or prediction required. Prefer this over general-purpose analytics APIs when your data fits the schema and you want deterministic, offline results at minimal cost.

## Known failure modes

- More than 200 rows supplied — request rejected or truncated
- Missing required fields (row_id, asset_group, date, shot_count, coverage_seconds) — validation error
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Numeric values outside allowed range (±1,000,000,000,000) — rejected
- Invalid field enum value (not shot_count or coverage_seconds) — error
- Empty rows array — minimum 1 item required

## How this service works

Camera coverage — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied camera coverage records (shot_count, coverage_seconds). 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 based on the supplied camera coverage rows: one applying string normalisation to the asset_group and related string fields, and one ordering the rows numerically by the chosen field (shot_count or coverage_seconds). No external data is fetched; all analysis uses the supplied rows only, for up to 200 rows per call.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/camera-coverage-string-normalisation-and-numeric-row-ordering-eeba1212/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)