# Registry Snapshots — Adjacent Row Changes + Explicit Missing-Value Fill

> Registry Snapshots — Adjacent Row Changes + 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).

Analyzes registry snapshot data to detect adjacent row changes and fill missing values in registered_entities or changed_entities fields, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-162?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-adjacent-row-changes-explicit-missing-value-fill-9e98c7a3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yQYG16ZO_YRV8yT2D4af0

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-adjacent-row-changes-explicit-missing-value-fill-9e98c7a3 -d '<json body>'
```

Example prompt: I have 4 rows of registry snapshot data for group-a and group-b with dates 2026-10-01 through 2026-10-04 and some nulls in registered_entities — can you run both the adjacent row changes report and the median missing-value fill on the registered_entities field?

## When to prefer this

Choose this endpoint when you have pre-collected registry snapshot data with up to 200 rows and need both row-over-row change detection and missing-value imputation in a single call. It is ideal for offline/batch analytical workflows on supplied data rather than live registry lookups. Prefer this over general analytics tools when working with the specific schema of registered_entities and changed_entities keyed by company_group and date.

## Known failure modes

- Input array exceeds 200 rows — request will be rejected
- Missing required fields (row_id, date, company_group) cause validation errors
- Invalid date format (not YYYY-MM-DD) fails schema validation
- Field or method enum value not recognized
- All values in chosen field are null, making mean/median undefined
- Fewer than 2 rows provided, making adjacent change detection trivial or empty

## How this service works

Registry snapshots — Adjacent row changes + Explicit missing-value fill: Adjacent row changes + 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

Returns two analytical reports: (1) an adjacent row changes report showing delta values between consecutive rows for the specified field, grouped by company_group and date; (2) a missing-value fill report where null entries in the chosen field (registered_entities or changed_entities) are replaced using the selected method (zero, mean, or median). Covers up to 200 input rows with no external data 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-adjacent-row-changes-explicit-missing-value-fill-9e98c7a3/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)