# Registry Snapshots — Record Quality Audit + String Normalisation

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

Audits data quality and normalises strings in registry snapshot records (registered_entities, changed_entities) for up to 200 rows, returning two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-001?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-547c2723
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pqr4gZabYV2GuNItciFb5

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-547c2723 -d '<json body>'
```

Example prompt: Can you audit the data quality and normalise the company group strings in these registry snapshot rows — I have 4 rows with fields like row_id, company_group, date, registered_entities, and changed_entities, and I want both a quality audit report and a string normalisation report back?

## When to prefer this

Choose this endpoint when you need both a data quality audit and string normalisation in a single call for registry snapshot data with up to 200 rows. It is ideal for pre-ingestion validation of company registry data, cleaning inconsistent company group strings, and detecting quality issues in entity count fields — all without requiring live lookups or external data enrichment. Prefer this over generic data cleaning tools when working specifically with registered_entities and changed_entities registry snapshot structures.

## Known failure modes

- More than 200 rows submitted — exceeds the maxItems limit, request rejected
- Missing required fields (row_id, date, registered_entities, changed_entities) on any row — validation error
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Numeric values outside allowed range (±1,000,000,000,000) — schema validation failure
- Empty rows array — minItems constraint violated

## How this service works

Registry snapshots — Record quality audit + String normalisation: Record quality audit + String normalisation 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 supplied rows: (1) a record quality audit highlighting data quality issues, anomalies, or inconsistencies in the registry snapshot fields, and (2) a string normalisation report showing standardised versions of string fields such as company_group. Both reports are computed locally 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-record-quality-audit-string-normalisation-547c2723/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)
