# Camera Coverage Numeric Interval Filter and Keyed Dataset Comparison

> Camera Coverage Numeric Interval Filter and Keyed Dataset Comparison 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-22).

Applies numeric interval filtering and keyed dataset comparison to camera coverage records (shot_count, coverage_seconds) across up to 200 rows, returning 2 independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-creative-12-134?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/camera-coverage-numeric-interval-filter-and-keyed-dataset-comparison-4ba4f325
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RRFSPZTcJQ98Pm_rte75I

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-numeric-interval-filter-and-keyed-dataset-comparison-4ba4f325 -d '<json body>'
```

Example prompt: I have two sets of camera coverage records (up to 200 rows each) with shot_count and coverage_seconds — can you run a numeric interval filter on shot_count and compare the two datasets keyed by row_id, for rows like row-1 through row-4 across asset groups group-a and group-b dated 2026-10-01 to 2026-10-04?

## When to prefer this

Choose this endpoint when you have camera coverage tabular data (shot_count, coverage_seconds) and need both numeric interval filtering and a side-by-side keyed comparison of two datasets in a single low-cost call ($0.01 USDC for both reports). It is ideal for offline batch analysis of up to 200 rows without requiring live data lookups or external integrations.

## Known failure modes

- Empty rows array or exceeding 200 rows limit returns validation error
- Invalid date format (not YYYY-MM-DD) causes schema rejection
- Missing required fields (row_id, asset_group, date, shot_count, coverage_seconds) causes row rejection
- Null values in numeric fields may affect interval filter results
- Mismatched row_ids between primary and secondary datasets may produce incomplete comparison results

## How this service works

Camera coverage — Numeric interval filter + Keyed dataset comparison: Numeric interval filter + Keyed dataset comparison 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 2 independent analytical reports: one covering numeric interval filter results on the selected field (shot_count or coverage_seconds) across the primary dataset, and one covering a keyed comparison between the primary and secondary datasets, both computed locally without external 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"
  },
  "other": {
   "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
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/camera-coverage-numeric-interval-filter-and-keyed-dataset-comparison-4ba4f325/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)