# Registry Snapshots — Numeric Row Ordering + Adjacent Row Changes

> Registry Snapshots — Numeric Row Ordering + Adjacent Row Changes 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 supplied registry snapshot data to produce numeric row ordering and adjacent row change reports for registered_entities or changed_entities fields.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-116?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-numeric-row-ordering-adjacent-row-changes-b475ad9c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_50fXwf8AEWe6crZo-7JVW

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-numeric-row-ordering-adjacent-row-changes-b475ad9c -d '<json body>'
```

Example prompt: I have registry snapshot data for two company groups — can you rank those rows numerically by registered_entities and show me the adjacent row-to-row changes? Here are the rows: group-a on 2026-10-01 had 10 registered and 1 changed, group-b on 2026-10-02 had 20 registered and 2 changed, group-a on 2026-10-03 had 15 registered and 3 changed.

## When to prefer this

Choose this endpoint when you have up to 200 rows of registry snapshot data and need both a numeric ordering of rows and a sequential delta (adjacent row change) report in a single call for either registered_entities or changed_entities — particularly useful for compliance, audit, or trend analysis workflows where row-level ranking and period-over-period differences matter. Prefer this over general analytics tools when working specifically with company group registry snapshot data and needing both reports together at low cost.

## Known failure modes

- Missing required fields (row_id, date, company_group, registered_entities, changed_entities) causes validation error
- Submitting more than 200 rows exceeds the maxItems limit
- Invalid date format (not YYYY-MM-DD) fails pattern validation
- Numeric values outside the allowed range (±1,000,000,000,000) are rejected
- Empty rows array is rejected (minItems: 1)
- Invalid field enum value (anything other than 'registered_entities' or 'changed_entities') causes error

## How this service works

Registry snapshots — Numeric row ordering + Adjacent row changes: Numeric row ordering + Adjacent row changes 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 independent analytical reports for the submitted dataset (up to 200 rows): (1) numeric row ordering ranking each row by the selected field (registered_entities or changed_entities), and (2) adjacent row changes showing the delta between each consecutive row for the selected field, using local analytical engines without any live lookup or external data.

## 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"
  }
 }
}
```

## More

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