# Registry Snapshots — Adjacent Row Changes + Keyed Dataset Comparison

> Registry Snapshots — Adjacent Row Changes + Keyed Dataset Comparison 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 (registered_entities, changed_entities) with two local analytical reports: adjacent row-to-row changes and keyed dataset comparison, for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-161?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-keyed-dataset-comparison-9ab0c3b6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VUr2ikDqfrZ9dQVD2P7jM

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-keyed-dataset-comparison-9ab0c3b6 -d '<json body>'
```

Example prompt: I have two sets of registry snapshot records for company groups like group-a and group-b — can you run both an adjacent row change report and a keyed dataset comparison on them, focusing on the registered_entities field, for up to 200 rows each?

## When to prefer this

Choose this endpoint when you need both row-to-row delta analysis and a keyed cross-dataset comparison for registry snapshot data in a single API call. It is ideal for compliance auditing, entity churn tracking, or before/after registry diffs for up to 200 rows, all without external data lookups or live queries.

## Known failure modes

- Missing required fields (row_id, company_group, date, registered_entities, changed_entities) causes validation error
- Exceeding 200 rows in either dataset returns an error
- Invalid date format (not YYYY-MM-DD) causes schema validation failure
- Null values in selected field may produce incomplete delta calculations
- Mismatched keys between rows and other datasets may yield empty comparison results

## How this service works

Registry snapshots — Adjacent row changes + Keyed dataset comparison: Adjacent row changes + Keyed dataset comparison 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) an adjacent row change report showing delta values between consecutive rows for the selected field, and (2) a keyed dataset comparison report diffing the supplied rows dataset against the other dataset by matching keys — all computed locally from 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"
  },
  "other": {
   "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
  
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-adjacent-row-changes-keyed-dataset-comparison-9ab0c3b6/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)