# Ownership Record Completeness — String Normalisation + Adjacent Row Changes

> Ownership Record Completeness — String Normalisation + Adjacent Row Changes 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-16).

Analyses ownership record completeness data by applying string normalisation and detecting adjacent row changes across up to 200 rows, producing two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-21-029?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ownership-record-completeness-string-normalisation-adjacent-row-changes-e567e2c1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_otGl-kxnw2CXdzjkw87bz

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 ownership-record-completeness-string-normalisation-adjacent-row-changes-e567e2c1 -d '<json body>'
```

Example prompt: Can you run string normalisation and adjacent row change detection on these ownership completeness records for group-a and group-b across October 2026 — I have 4 rows with documented_links and required_links values and want both reports?

## When to prefer this

Choose this endpoint when you need both string normalisation and adjacent row change detection on ownership completeness records in a single paid call. Ideal for data quality pipelines processing corporate ownership documentation where you want to identify string inconsistencies and row-to-row value shifts in documented vs required link counts. Best suited for batch sizes up to 200 rows where no live lookup or external data enrichment is needed.

## Known failure modes

- More than 200 rows submitted — request rejected, reduce batch size
- Missing required fields (row_id, company_group, date, documented_links, required_links) — validation error
- Invalid date format (must match YYYY-MM-DD pattern) — schema validation failure
- Numeric values outside allowed range (-1,000,000,000,000 to 1,000,000,000,000) — rejection
- Invalid field enum value (must be 'documented_links' or 'required_links') — error
- Payment failure or insufficient USDC balance — transaction not processed

## How this service works

Ownership record completeness — String normalisation + Adjacent row changes: String normalisation + Adjacent row changes for supplied ownership record completeness records (documented_links, required_links). 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 identifying and correcting string inconsistencies in the supplied ownership records, and (2) an adjacent row changes report highlighting value differences between consecutive rows in the specified field (documented_links or required_links). Both reports are computed locally against 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",
     "documented_links",
     "required_links"
    ],
    "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
     },
     "required_links": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "documented_links": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "company_group": "group-a",
     "required_links": 1,
     "documented_links": 10
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "company_group": "group-b",
     "required_links": 2,
     "documented_links": 20
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "company_group": "group-a",
     "required_links": 3,
     "documented_links": 15
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "company_group": "group-b",
     "required_links": 4,
     "documented_links": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "documented_links",
    "required_links"
   ],
   "type": "string",
   "default": "documented_links"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ownership-record-completeness-string-normalisation-adjacent-row-changes-e567e2c1/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)