# Ownership Record Completeness — Numeric Row Ordering & Adjacent Row Changes

> Ownership Record Completeness — Numeric Row Ordering & 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).

Analyzes ownership record completeness data by applying numeric row ordering 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-116?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-numeric-row-ordering-adjacent-row-changes-e4d1e863
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AXisHHzH86uhtGl4xlRA2

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-numeric-row-ordering-adjacent-row-changes-e4d1e863 -d '<json body>'
```

Example prompt: Analyze these ownership completeness records for numeric row ordering and adjacent row changes — here are 4 rows with company groups, dates from 2026-10-01 to 2026-10-04, documented_links values of 10, 20, 15, 30, and required_links of 1, 2, 3, 4. Run both reports on the documented_links field.

## When to prefer this

Choose this endpoint when you have tabular ownership record completeness data with documented and required link counts, and need both a numerically ordered view of the data and a row-by-row change detection report in a single low-cost call. It is best suited for sequential, time-series-style ownership audit data grouped by company. Prefer it over general analytics tools when you want two focused, pre-built reports (ordering + adjacent changes) without building custom logic.

## Known failure modes

- More than 200 rows submitted — request will be rejected or truncated
- Missing required fields (row_id, company_group, date, documented_links, required_links) cause validation errors
- Invalid date format (not YYYY-MM-DD) triggers schema validation failure
- Numeric values outside allowed range (-1,000,000,000,000 to 1,000,000,000,000) rejected
- Empty rows array (minItems: 1 not met) causes error
- Invalid field enum value (not documented_links or required_links) causes failure

## How this service works

Ownership record completeness — Numeric row ordering + Adjacent row changes: Numeric row ordering + 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 numeric row ordering report showing the sorted sequence of the selected field across rows, and (2) an adjacent row changes report highlighting differences between consecutive rows for the selected field (documented_links or required_links), applied to up to 200 supplied ownership record rows.

## 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-numeric-row-ordering-adjacent-row-changes-e4d1e863/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)