# Registry Snapshots — Trailing Mean Series + Explicit Missing-Value Fill

> Registry Snapshots — Trailing Mean Series + Explicit Missing-Value Fill 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).

Computes a rolling trailing mean time series and fills missing values in registry snapshot data (registered_entities, changed_entities) using a chosen fill method.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-154?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/registry-snapshots-trailing-mean-series-explicit-missing-value-fill-c6f7ce08
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7lTjEwplkRsA7NULu4YDO

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 registry-snapshots-trailing-mean-series-explicit-missing-value-fill-c6f7ce08 -d '<json body>'
```

Example prompt: I have registry snapshot data for two company groups over four dates — can you compute a trailing mean series with a window of 3 using median fill for the registered_entities field? Here are my rows: group-a on 2026-10-01 had 10 registered and 1 changed, group-a on 2026-10-03 had 15 registered and 3 changed, group-b on 2026-10-02 had 20 registered and 2 changed, group-b on 2026-10-04 had 30 registered and 4 changed.

## When to prefer this

Choose this endpoint when you have tabular registry snapshot data (registered_entities and/or changed_entities) and need both a rolling trailing mean time series and explicit missing-value imputation in a single call. Ideal for offline/batch analytical pipelines processing up to 200 rows where no live data lookup is required. Prefer over generic stats tools when you want both smoothing and gap-filling delivered together as two coordinated reports for a shared dataset.

## Known failure modes

- Fewer than 1 row supplied — request rejected
- More than 200 rows submitted — exceeds maximum batch size
- Invalid date format (not YYYY-MM-DD) — schema validation error
- Window size outside 2–200 range — validation failure
- Unknown fill method or field enum value — schema rejection
- All values null for a group — trailing mean may be undefined or empty
- Payment not confirmed — endpoint returns 402

## How this service works

Registry snapshots — Trailing mean series + Explicit missing-value fill: Trailing mean series + Explicit missing-value fill for supplied registry snapshots records (registered_entities, changed_entities). 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 covering: (1) a trailing mean time series for the specified field computed over the given rolling window, and (2) an explicit missing-value fill applied to the same field using the chosen method (zero, mean, or median). Results are based purely on the supplied rows (up to 200) with no live lookup or external data.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-trailing-mean-series-explicit-missing-value-fill-c6f7ce08/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)