# Registry Snapshots — String Normalisation + Explicit Missing-Value Fill

> Registry Snapshots — String Normalisation + Explicit Missing-Value Fill 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).

Normalises string fields and fills missing numeric values in registry snapshot records (registered_entities, changed_entities) for up to 200 rows using two local analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-037?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-string-normalisation-explicit-missing-value-fill-7ae246c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WTbWcrb6CaXSTbzhdJ_-J

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-string-normalisation-explicit-missing-value-fill-7ae246c9 -d '<json body>'
```

Example prompt: Can you clean up my registry snapshot data — normalise the company_group strings and fill any missing registered_entities values using median imputation? I have about 50 rows with dates, row IDs, and both registered_entities and changed_entities columns.

## When to prefer this

Choose this endpoint when you need lightweight, local string normalisation and missing-value imputation on registry snapshot data (registered_entities, changed_entities) without requiring live data lookups, external enrichment, or complex analytics. Ideal for pre-processing company registry exports of up to 200 rows before downstream reporting or analysis. At $0.01 USDC for two reports, it is cost-effective for small-to-medium batch cleaning tasks.

## Known failure modes

- More than 200 rows submitted — request rejected at maxItems limit
- Missing required fields (row_id, company_group, date, registered_entities, changed_entities) cause validation errors
- Date strings not matching YYYY-MM-DD pattern cause schema rejection
- Numeric values outside allowed range (-1e12 to 1e12) cause validation failure
- Invalid fill method or field enum value causes schema rejection

## How this service works

Registry snapshots — String normalisation + Explicit missing-value fill: String normalisation + Explicit missing-value fill 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 analytical reports: one covering string normalisation applied to the company_group and related string fields, and one covering explicit missing-value fill for the selected numeric field (registered_entities or changed_entities) using the chosen method (zero, mean, or median). Results are derived entirely from the supplied rows 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"
  },
  "method": {
   "enum": [
    "zero",
    "mean",
    "median"
   ],
   "type": "string",
   "default": "median"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-string-normalisation-explicit-missing-value-fill-7ae246c9/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)