# Registry Snapshots: String Normalisation + Numeric Row Ordering

> Registry Snapshots: String Normalisation + Numeric Row Ordering 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-15).

Normalises company-group strings and orders rows numerically for registry snapshot records (registered_entities, changed_entities) across up to 200 rows with two independent reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-04-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/registry-snapshots-string-normalisation-numeric-row-ordering-2a3f7ced
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HjMr4mNzaiHOpbyBw6Bo9

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-numeric-row-ordering-2a3f7ced -d '<json body>'
```

Example prompt: Can you normalize the company group names and sort my registry snapshot rows numerically by registered_entities? Here are 4 rows: row-1 for group-a on 2026-10-01 with 10 registered and 1 changed, row-2 for group-b on 2026-10-02 with 20 registered and 2 changed, row-3 for group-a on 2026-10-03 with 15 registered and 3 changed, row-4 for group-b on 2026-10-04 with 30 registered and 4 changed.

## When to prefer this

Choose this endpoint when you have registry snapshot data with company group strings needing standardisation and numeric entity counts that need ranked ordering — and you want both reports in a single $0.01 call without any live data lookups or external integrations. Best suited for batch preparation of up to 200 registry rows prior to dashboarding or compliance reporting.

## Known failure modes

- Missing required fields (row_id, date, company_group) return validation errors
- Date strings not matching YYYY-MM-DD pattern are rejected
- Numeric values outside ±1,000,000,000,000 are rejected
- Arrays exceeding 200 items are rejected
- Empty arrays (minItems:1 violated) cause a validation error

## How this service works

Registry snapshots — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering 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 covering: (1) string normalisation of the company_group field across the supplied rows, and (2) numeric ordering of rows by the selected field (registered_entities or changed_entities). Results are produced entirely from the supplied data with no external lookups, covering up to 200 rows.

## 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-string-normalisation-numeric-row-ordering-2a3f7ced/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)