# Registry Snapshots — String Normalisation + Two-Measure Correlation

> Registry Snapshots — String Normalisation + Two-Measure Correlation 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).

Performs string normalisation and two-measure correlation analysis on registry snapshot data (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-033?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-two-measure-correlation-aa70f655
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NVXoCD083XfhKR6ebqJiW

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-two-measure-correlation-aa70f655 -d '<json body>'
```

Example prompt: Can you run string normalisation and two-measure correlation on my registry snapshot — I have up to 50 rows with company_group, date, registered_entities, and changed_entities fields — and give me both analytical reports?

## When to prefer this

Choose this endpoint when you need both string normalisation and two-measure (registered vs changed entities) correlation computed together on registry snapshot data in a single low-cost call. It is ideal for batch offline analysis of up to 200 rows of company registry records where no live lookups, external predictions, or real-time data enrichment are needed. At $0.01 USDC for two reports, it suits cost-sensitive pipelines processing structured registry snapshots.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, date, registered_entities, changed_entities) cause row rejection
- Invalid date format (non-YYYY-MM-DD) fails pattern validation
- Numeric values outside the allowed range (-1e12 to 1e12) are rejected
- Empty row array is rejected (minItems: 1)
- Insufficient numeric variation may result in undefined or trivial correlation output

## How this service works

Registry snapshots — String normalisation + Two-measure correlation: String normalisation + Two-measure correlation 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

Two independent analytical reports: (1) a string normalisation report covering the text fields in the supplied registry snapshot rows, and (2) a two-measure correlation report quantifying the statistical relationship between registered_entities and changed_entities across the submitted rows. No live lookups, predictions, or external actions are performed.

## 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-string-normalisation-two-measure-correlation-aa70f655/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)