# Time Series Completeness — Numeric Interval Filter + Two-Measure Correlation

> Time Series Completeness — Numeric Interval Filter + 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-10-15).

Filters time series completeness records by a numeric interval and computes correlation between observed_points and expected_points across up to 200 rows, producing two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-16-131?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/time-series-completeness-numeric-interval-filter-two-measure-e66c198d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aCyZLKkJfVmnMGZZYY8Q2

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 time-series-completeness-numeric-interval-filter-two-measure-e66c198d -d '<json body>'
```

Example prompt: I have daily completeness records for two dataset groups from October 1–4, 2026, each with observed_points and expected_points values — can you filter to rows where observed_points falls between 10 and 30, then run a two-measure correlation report between observed_points and expected_points across all 200 rows?

## When to prefer this

Choose this endpoint when you have pre-collected time series completeness records (observed vs expected point counts) and need both a numeric range filter and a correlation analysis between the two measures in a single $0.01 call, without requiring live data lookup, prediction, or external data enrichment. Ideal for offline data quality audits, pipeline monitoring reviews, and batch completeness assessments on up to 200 rows.

## Known failure modes

- Fewer than 1 or more than 200 rows supplied — request rejected
- Date values not in YYYY-MM-DD format — validation error
- observed_points or expected_points outside allowed numeric range — schema error
- minimum greater than maximum — logically invalid interval filter
- Insufficient variance in data to compute meaningful correlation — degenerate result
- Missing required fields (row_id, date, observed_points, expected_points) on any row — rejection

## How this service works

Time series completeness — Numeric interval filter + Two-measure correlation: Numeric interval filter + Two-measure correlation for supplied time series completeness records (observed_points, expected_points). 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 independent analytical reports: (1) rows from the supplied dataset filtered to the specified numeric interval on the chosen field, and (2) a correlation analysis between observed_points and expected_points across those records, all computed locally with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/time-series-completeness-numeric-interval-filter-two-measure-e66c198d/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)