# Registry Snapshots — Adjacent Row Changes + Equal-Width Histogram

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

Analyzes registry snapshot data by computing adjacent row changes and equal-width histogram distributions for registered_entities or changed_entities fields, returning two independent analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-156?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/registry-snapshots-adjacent-row-changes-equal-width-histogram-a2a9ac3a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FEQgJPCugG8g94GqmRV-x

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-equal-width-histogram-a2a9ac3a -d '<json body>'
```

Example prompt: I have registry snapshot data for two company groups across 4 dates with registered_entities and changed_entities counts — can you run adjacent row changes and a 5-bin equal-width histogram on the registered_entities field for those rows?

## When to prefer this

Choose this endpoint when you have registry snapshot tabular data with registered_entities or changed_entities fields and need both a sequential delta analysis and a frequency distribution in one call, without requiring live data lookup, prediction, or external integrations. It is especially useful for compact datasets (up to 200 rows) where two lightweight analytical perspectives on a single numeric field are needed at minimal cost.

## Known failure modes

- Missing required fields (row_id, date, company_group, registered_entities, changed_entities) cause validation errors
- More than 200 rows submitted exceeds the row limit
- Invalid date format (not YYYY-MM-DD) fails schema validation
- Bins value outside range 1–30 is rejected
- All null values in the target field may produce empty or degenerate histogram
- Payment of 0.01 USDC not included causes request rejection

## How this service works

Registry snapshots — Adjacent row changes + Equal-width histogram: Adjacent row changes + Equal-width histogram 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) an adjacent row changes report showing row-over-row deltas for the selected field across up to 200 input rows, and (2) an equal-width histogram report breaking the field's values into the specified number of bins with frequency counts, both computed locally without external lookups.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "bins": {
   "type": "integer",
   "default": 5,
   "maximum": 30,
   "minimum": 1
  },
  "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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-adjacent-row-changes-equal-width-histogram-a2a9ac3a/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)