# Registry Snapshots — Numeric Interval Filter + Two-Measure Correlation

> Registry Snapshots — Numeric Interval Filter + 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).

Filters registry snapshot rows by a numeric interval on a chosen field and computes a Pearson/rank correlation between registered_entities and changed_entities, returning two analytical reports for up to 200 supplied rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-131?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-numeric-interval-filter-two-measure-correlation-3b3f328c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0IspzzpbtJfEU2Htnumo1

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-numeric-interval-filter-two-measure-correlation-3b3f328c -d '<json body>'
```

Example prompt: I have registry snapshot data for two company groups across October 2026 — can you filter the rows where registered_entities is between 5 and 50, then run a two-measure correlation between registered_entities and changed_entities and give me two analytical reports?

## When to prefer this

Choose this endpoint when you have up to 200 registry snapshot rows with registered_entities and changed_entities fields and need both a numeric interval filter and a two-measure correlation in a single $0.01 call. Prefer it over general-purpose analytics tools when you want fast, local, no-external-lookup computation on structured registry data with a predictable schema. Use it instead of building custom SQL or Python scripts when the dataset fits within 200 rows and the two-report output format (interval filter + correlation) matches your analysis goals.

## Known failure modes

- Fewer than 1 row supplied — request rejected
- More than 200 rows supplied — exceeds maxItems limit
- minimum greater than maximum — invalid interval produces empty filter result
- Non-numeric or null values in both measure fields — correlation cannot be computed
- Date strings not matching YYYY-MM-DD pattern — schema validation error
- Payment of 0.01 USDC not completed — 402 response, no reports returned

## How this service works

Registry snapshots — Numeric interval filter + Two-measure correlation: Numeric interval filter + 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

Returns two independent analytical reports: (1) the subset of input rows whose selected field value falls within the specified [minimum, maximum] numeric interval, and (2) a correlation analysis (e.g. Pearson or rank correlation) between registered_entities and changed_entities across those filtered rows. All computation 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"
  },
  "maximum": {
   "type": "number",
   "default": 100,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  },
  "minimum": {
   "type": "number",
   "default": 0,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/registry-snapshots-numeric-interval-filter-two-measure-correlation-3b3f328c/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)