# Registry Snapshots — Record Quality Audit + String Normalisation + Adjacent Row Changes

> Registry Snapshots — Record Quality Audit + String Normalisation + 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).

Runs three independent analytical reports (record quality audit, string normalisation, and adjacent row change detection) on up to 200 registry snapshot rows containing registered_entities and changed_entities counts.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-200?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-record-quality-audit-string-normalisation-adjacent-36e84e49
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_l2O5843otbkMCXCbABkHd

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-record-quality-audit-string-normalisation-adjacent-36e84e49 -d '<json body>'
```

Example prompt: Can you run the full quality audit, string normalisation, and adjacent-row change detection on this batch of company registry snapshots — I have 4 rows covering groups 'group-a' and 'group-b' from 2026-10-01 to 2026-10-04 with their registered_entities and changed_entities counts, and I want to check the registered_entities field?

## When to prefer this

Choose this endpoint when you need three combined analytical passes — quality audit, string normalisation, and adjacent row change detection — on registry snapshot data in a single cost-efficient call ($0.01 USDC for all three reports). It is ideal for batch offline analysis of up to 200 rows of company registration data where no live lookup, prediction, or external action is needed.

## Known failure modes

- Submitting more than 200 rows returns a validation error
- Missing required fields (row_id, date, company_group, registered_entities, changed_entities) cause row-level rejection
- Invalid date format (non-YYYY-MM-DD) triggers schema validation failure
- Numeric values outside the allowed range (-1e12 to 1e12) are rejected
- Invalid field enum value (anything other than 'registered_entities' or 'changed_entities') causes a bad request error
- Payment failure or insufficient USDC balance blocks the call

## How this service works

Registry snapshots — Record quality audit + String normalisation + Adjacent row changes: Record quality audit + String normalisation + Adjacent row changes for supplied registry snapshots records (registered_entities, changed_entities). Up to 200 rows; 3 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 3 supplied-data reports for up to 200 rows.

## Output

Returns three independent analytical reports for the submitted rows: (1) a record quality audit flagging completeness and consistency issues, (2) a string normalisation report identifying and correcting inconsistencies in company_group strings, and (3) an adjacent row changes report highlighting row-to-row differences in the selected numeric field (registered_entities or changed_entities). All analysis is performed locally on 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-record-quality-audit-string-normalisation-adjacent-36e84e49/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)