# Registry Snapshots — Trailing Mean Series + Base-100 Series

> Registry Snapshots — Trailing Mean Series + Base-100 Series 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 trailing moving-average time series and a base-100 indexed series for registry snapshot data (registered_entities, changed_entities) supplied by the caller.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-147?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-base-100-series-fdc528c8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J3Vl-Ish8p7yiGZUtHRfq

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-base-100-series-fdc528c8 -d '<json body>'
```

Example prompt: I have 150 rows of registry snapshots with company_group, date, registered_entities, and changed_entities columns — can you run a trailing mean series with a window of 5 and a base-100 series starting at index 0 for the registered_entities field?

## When to prefer this

Choose this endpoint when you have pre-collected registry snapshot data (up to 200 rows) and need both a trailing moving-average series and a base-100 normalized index in a single paid call. It is ideal for offline/batch analytical reporting on company entity registration data where no live data lookup or prediction is needed. Prefer it over single-report endpoints when you want both time-series smoothing and relative indexing computed together cost-efficiently.

## Known failure modes

- More than 200 rows supplied — request rejected or truncated
- Invalid date format (non-YYYY-MM-DD) causes schema validation failure
- Window size larger than available rows per group yields insufficient data for trailing mean
- base_index out of range for a given group produces undefined or null base reference
- Missing required fields (row_id, date, registered_entities, changed_entities) cause validation errors
- Payment of 0.01 USDC not received — request rejected with 402 status

## How this service works

Registry snapshots — Trailing mean series + Base-100 series: Trailing mean series + Base-100 series 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 independent analytical reports: (1) a trailing mean series showing the rolling average of the selected field (registered_entities or changed_entities) over the specified window, and (2) a base-100 indexed series normalizing values relative to the row at the specified base_index — both computed per-group from the supplied rows, covering up to 200 input records.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-trailing-mean-series-base-100-series-fdc528c8/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)