# Ownership Record Completeness — Exact Row Deduplication + Numeric Row Ordering

> Ownership Record Completeness — Exact Row Deduplication + 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-11-04).

Deduplicates and numerically orders ownership record completeness rows (documented_links, required_links) for up to 200 supplied records, producing 2 independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-21-042?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ownership-record-completeness-exact-row-deduplication-numeric-row-d174c716
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nLRgKsKisVfYioi7zufAX

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-exact-row-deduplication-numeric-row-d174c716 -d '<json body>'
```

Example prompt: I have a batch of ownership completeness records for two company groups with documented_links and required_links values — can you deduplicate the exact duplicate rows and sort them numerically? Here are 4 rows: row-1 for group-a on 2026-10-01 with required_links=1 and documented_links=10, row-2 for group-b on 2026-10-02 with required_links=2 and documented_links=20, row-3 for group-a on 2026-10-03 with required_links=3 and documented_links=15, and row-4 for group-b on 2026-10-04 with required_links=4 and documented_links=30; analyze on the documented_links field.

## When to prefer this

Choose this endpoint when you need lightweight, local exact-duplicate removal and numeric ordering on ownership record completeness data (documented_links and required_links fields) without any external API calls, predictions, or professional assessments. Ideal for pre-processing compliance or audit datasets of up to 200 rows before reporting. At $0.01 USDC for 2 reports, it is cost-effective for routine data cleaning on ownership completeness records. Prefer alternatives if you need fuzzy deduplication, machine-learning-based anomaly detection, or data enrichment from external sources.

## Known failure modes

- Input array exceeds 200 rows — request will be rejected
- Missing required row fields (row_id, company_group, date, documented_links, required_links) cause validation errors
- Invalid date format (must match YYYY-MM-DD pattern) returns schema error
- Numeric values outside allowed range (-1,000,000,000,000 to 1,000,000,000,000) rejected
- Empty rows array (minItems:1 violated) returns error
- Invalid field enum value (must be 'documented_links' or 'required_links') causes rejection

## How this service works

Ownership record completeness — Exact row deduplication + Numeric row ordering: Exact row deduplication + Numeric row ordering 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 2 independent analytical reports covering exact row deduplication (identifying and removing identical rows) and numeric row ordering applied to the supplied ownership completeness records, using the selected field (documented_links or required_links). No external lookups or predictions are made — all analysis is performed locally on the supplied data.

## 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-exact-row-deduplication-numeric-row-d174c716/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)