# Camera Coverage Trailing Mean & Two-Measure Correlation Analyzer

> Camera Coverage Trailing Mean & Two-Measure Correlation Analyzer 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-17).

Computes a trailing mean time series and a two-measure correlation report for camera coverage data (shot_count and coverage_seconds) supplied by the caller, up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-creative-12-150?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/camera-coverage-trailing-mean-two-measure-correlation-analyzer-9032ce3a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_V_k9GcrcPpma0y1lxz6zB

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-trailing-mean-two-measure-correlation-analyzer-9032ce3a -d '<json body>'
```

Example prompt: I have 4 rows of camera coverage data — for group-a: 2026-10-01 shot_count=10 coverage_seconds=1, 2026-10-03 shot_count=15 coverage_seconds=3; for group-b: 2026-10-02 shot_count=20 coverage_seconds=2, 2026-10-04 shot_count=30 coverage_seconds=4 — can you compute the trailing mean series for shot_count with a window of 2, and also give me the two-measure correlation between shot_count and coverage_seconds?

## When to prefer this

Choose this endpoint when you have camera coverage records (shot counts and coverage seconds) and need two specific statistical outputs — a trailing mean time series and a pairwise correlation — computed purely on your supplied data without any external lookup, prediction, or professional assessment. Ideal for media production analysts, video ops teams, or agent pipelines that already hold the data locally and want lightweight, deterministic statistical summaries at low cost ($0.01 USDC for both reports on up to 200 rows).

## Known failure modes

- More than 200 rows submitted — request rejected or truncated
- Invalid date format (not YYYY-MM-DD) causes row rejection or error
- Missing required fields (row_id, date, shot_count, coverage_seconds) cause validation failure
- Window size outside 2–200 range causes parameter error
- Null values in shot_count or coverage_seconds may affect correlation and mean calculations
- Invalid field enum value (not shot_count or coverage_seconds) causes error

## How this service works

Camera coverage — Trailing mean series + Two-measure correlation: Trailing mean series + Two-measure correlation 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

Returns two analytical reports: (1) a trailing mean time series computed over the specified window for the chosen field (shot_count or coverage_seconds), and (2) a two-measure correlation report between shot_count and coverage_seconds — both derived entirely from the caller-supplied rows, with no external data lookups.

## 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"
  },
  "window": {
   "type": "integer",
   "default": 2,
   "maximum": 200,
   "minimum": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/camera-coverage-trailing-mean-two-measure-correlation-analyzer-9032ce3a/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)