# Registry Snapshots Base-100 Series + Missing Value Fill

> Registry Snapshots Base-100 Series + 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 base-100 indexed time series and fills missing values for registry snapshot data (registered_entities, changed_entities) across company groups.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-169?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-base-100-series-missing-value-fill-4d06affc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mw6_OR-1J_1op0NZUwXKE

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-base-100-series-missing-value-fill-4d06affc -d '<json body>'
```

Example prompt: I have registry snapshot rows for two company groups from October 2026 — can you normalize the registered_entities field to a base-100 series starting at row index 0 and fill any missing values using median imputation? Here are up to 200 rows with row_id, company_group, date, registered_entities, and changed_entities.

## When to prefer this

Choose this endpoint when you need to normalize registry snapshot counts (registered or changed entities) to a comparable base-100 scale and/or impute missing values in one pass, using only your own supplied data — no external data source or live registry lookup is involved. Ideal for preparing company group registry time series for trend comparison, dashboards, or downstream analytics pipelines.

## Known failure modes

- Input array exceeds 200 rows — request rejected
- Missing required fields (row_id, date, company_group) cause row-level errors
- Invalid date format (not YYYY-MM-DD) fails schema validation
- base_index out of range (0–199) or referencing a null-value row causes indexing failure
- All values for selected field are null — imputation and base-100 indexing cannot proceed
- Numeric values outside allowed range (±1,000,000,000,000) rejected by schema

## How this service works

Registry snapshots — Base-100 series + Explicit missing-value fill: Base-100 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: (1) a base-100 indexed time series for the specified field (registered_entities or changed_entities) relative to the chosen base row index, and (2) the same series with explicit missing values filled using the selected method (zero, mean, or median). Results cover up to 200 input rows and are computed entirely from the supplied data with no external lookups.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-base-100-series-missing-value-fill-4d06affc/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)