# Registry Snapshots — Duplicate Key Report + Numeric Row Ordering

> Registry Snapshots — Duplicate Key Report + Numeric Row Ordering 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-19).

Analyzes supplied registry snapshot records to produce a duplicate key report and a numeric row ordering report for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-058?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/registry-snapshots-duplicate-key-report-numeric-row-ordering-57d3623f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ChGzBrSPHsvJqlVV6NZnE

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-duplicate-key-report-numeric-row-ordering-57d3623f -d '<json body>'
```

Example prompt: I have a set of registry snapshot records with company groups and dates — can you run a duplicate key report and numeric row ordering on them using the registered_entities field? Here are the rows: row-1 (2026-10-01, group-a, registered=10, changed=1), row-2 (2026-10-02, group-b, registered=20, changed=2), row-3 (2026-10-03, group-a, registered=15, changed=3).

## When to prefer this

Choose this endpoint when you have registry snapshot data (with company_group, date, registered_entities, and changed_entities fields) and need both a duplicate key report and a numeric row ordering in a single call. It is well-suited for data quality audits of company registration datasets prior to merging or analysis. Prefer this over general-purpose analytics tools when you specifically need these two bundled reports on up to 200 rows at low cost ($0.01 USDC).

## Known failure modes

- Input array exceeds 200 rows — request will be rejected or truncated
- Missing required fields (row_id, company_group, date, registered_entities, changed_entities) will cause validation errors
- Invalid date format (must match YYYY-MM-DD pattern) will fail schema validation
- Numeric values outside the allowed range (-1,000,000,000,000 to 1,000,000,000,000) will be rejected
- Invalid field selector (must be 'registered_entities' or 'changed_entities') will cause an error
- Payment failure via x402 protocol will block the request

## How this service works

Registry snapshots — Duplicate key report + Numeric row ordering: Duplicate key report + Numeric row ordering 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: (1) a duplicate key report identifying rows with repeated key combinations across the supplied registry snapshot records, and (2) a numeric row ordering report ranking rows by the selected numeric field (registered_entities or changed_entities). Results cover up to 200 input rows and are derived 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-duplicate-key-report-numeric-row-ordering-57d3623f/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)