# Ownership Record Completeness — Duplicate Key Report + Adjacent Row Changes

> Ownership Record Completeness — Duplicate Key Report + 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-20).

Analyzes up to 200 ownership record completeness rows to produce two independent reports: a duplicate key report and an adjacent row changes report, using local analytical engines.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-21-062?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ownership-record-completeness-duplicate-key-report-adjacent-row-changes-11155d67
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ay0vcGe70Gmb8hLhVWeI8

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-duplicate-key-report-adjacent-row-changes-11155d67 -d '<json body>'
```

Example prompt: Can you run a duplicate key report and adjacent row changes analysis on my ownership record completeness data? I have rows with row_id, company_group, date, documented_links, and required_links fields — up to 200 rows — and I want to check the documented_links field for duplicates and sequential changes.

## When to prefer this

Choose this endpoint when you need both a duplicate key audit and an adjacent row change analysis on ownership record completeness data in a single API call. It is purpose-built for the documented_links / required_links ownership completeness schema and processes up to 200 rows locally without any external data access. Prefer it over general-purpose data quality tools when working specifically with company-group ownership tracking records and you need both report types at once for a fixed low cost.

## Known failure modes

- Fewer than 1 row supplied — validation error
- More than 200 rows supplied — request rejected
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Missing required fields (row_id, company_group, date, documented_links, required_links) — error response
- Invalid field enum value — schema rejection
- Payment not provided or insufficient — 402 response

## How this service works

Ownership record completeness — Duplicate key report + Adjacent row changes: Duplicate key report + 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

Returns two independent analytical reports: (1) a duplicate key report identifying rows with repeated key combinations across the supplied ownership records, and (2) an adjacent row changes report showing where consecutive rows differ on the selected field (documented_links or required_links). Both reports are generated from the supplied data using local engines 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-duplicate-key-report-adjacent-row-changes-11155d67/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)