# Data Reconciliation — Duplicate Key Report + Numeric Row Ordering

> Data Reconciliation — Duplicate Key Report + 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-19).

Analyzes up to 200 data reconciliation rows to produce a duplicate key report and a numeric row ordering report for source_total or target_total values.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-11-058?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/data-reconciliation-duplicate-key-report-numeric-row-ordering-af0811c6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kjo1mLcAu8N9zbZn0YTMD

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 data-reconciliation-duplicate-key-report-numeric-row-ordering-af0811c6 -d '<json body>'
```

Example prompt: Can you run a duplicate key report and numeric row ordering on my reconciliation data? Here are the rows: row-1 on 2026-10-01 in group-a with source_total 10 and target_total 1, row-2 on 2026-10-02 in group-b with source_total 20 and target_total 2, and row-3 on 2026-10-01 in group-a with source_total 15 and target_total 3 — use source_total for the ordering.

## When to prefer this

Choose this endpoint when you need two lightweight analytical reports — duplicate key detection and numeric ordering — on a batch of up to 200 reconciliation rows without any external API calls, live data lookups, or ML inference. Ideal for data quality checks during ETL pipelines, financial close reconciliation, or cross-system data comparison workflows where you control the input data and want deterministic, local computation at low cost.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, dataset_group, date, source_total, target_total) cause schema validation failure
- Date values not matching YYYY-MM-DD pattern are rejected
- Numeric values outside ±1,000,000,000,000 are rejected
- Empty rows array (minItems:1 violated) returns an error
- Invalid field enum value (not source_total or target_total) returns a validation error
- Payment of 0.01 USDC required; missing payment results in 402 response

## How this service works

Data reconciliation — Duplicate key report + Numeric row ordering: Duplicate key report + Numeric row ordering for supplied data reconciliation records (source_total, target_total). 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 for the supplied rows: (1) a duplicate key report identifying any row_id values that appear more than once across the dataset, and (2) a numeric row ordering report ranking all rows by the chosen field (source_total or target_total). No external data is fetched; all computation is performed locally on the submitted rows.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "dataset_group",
     "date",
     "source_total",
     "target_total"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "source_total": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "target_total": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "dataset_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "source_total": 10,
     "target_total": 1,
     "dataset_group": "group-a"
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "source_total": 20,
     "target_total": 2,
     "dataset_group": "group-b"
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "source_total": 15,
     "target_total": 3,
     "dataset_group": "group-a"
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "source_total": 30,
     "target_total": 4,
     "dataset_group": "group-b"
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "source_total",
    "target_total"
   ],
   "type": "string",
   "default": "source_total"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/data-reconciliation-duplicate-key-report-numeric-row-ordering-af0811c6/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)