# Join Coverage Analytics — Numeric Row Ordering + Keyed Dataset Comparison

> Join Coverage Analytics — Numeric Row Ordering + Keyed Dataset Comparison 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-23).

Analyzes join coverage records by producing two reports: a numeric row ordering analysis and a keyed dataset comparison between two supplied datasets of up to 200 rows each.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-09-123?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/join-coverage-analytics-numeric-row-ordering-keyed-dataset-comparison-1a6833c0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IhhE0yiwAkMee4plEZgD6

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 join-coverage-analytics-numeric-row-ordering-keyed-dataset-comparison-1a6833c0 -d '<json body>'
```

Example prompt: I have two sets of join coverage records — my baseline and a comparison snapshot — each with row_id, date, dataset_group, matched_rows, and source_rows. Can you run a numeric row ordering report and a keyed dataset comparison on the matched_rows field for both sets of up to 200 rows?

## When to prefer this

Choose this endpoint when you need to both rank join coverage records numerically and compare two versions of a join coverage dataset side-by-side in a single low-cost call. Ideal for data engineers auditing ETL join completeness, QA analysts comparing pipeline snapshots, or anyone needing a lightweight, offline join coverage diff without external data dependencies.

## Known failure modes

- Missing required fields (row_id, dataset_group, date, matched_rows, source_rows) cause validation errors
- Exceeding 200 rows per dataset results in rejection
- Invalid date format (not YYYY-MM-DD) causes schema validation failure
- Providing an unrecognized field value for the 'field' enum causes rejection
- Empty rows array (minItems:1 not met) returns an error

## How this service works

Join coverage — Numeric row ordering + Keyed dataset comparison: Numeric row ordering + Keyed dataset comparison for supplied join coverage records (matched_rows, source_rows). 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 of the supplied join coverage records sorted by the selected field (matched_rows or source_rows), and (2) a keyed dataset comparison highlighting differences between the primary and comparison datasets by row_id and dataset_group. Both reports are computed locally with no external lookups.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "dataset_group",
     "date",
     "matched_rows",
     "source_rows"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "source_rows": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "matched_rows": {
      "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_rows": 1,
     "matched_rows": 10,
     "dataset_group": "group-a"
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "source_rows": 2,
     "matched_rows": 20,
     "dataset_group": "group-b"
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "source_rows": 3,
     "matched_rows": 15,
     "dataset_group": "group-a"
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "source_rows": 4,
     "matched_rows": 30,
     "dataset_group": "group-b"
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "matched_rows",
    "source_rows"
   ],
   "type": "string",
   "default": "matched_rows"
  },
  "other": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "dataset_group",
     "date",
     "matched_rows",
     "source_rows"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "source_rows": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "matched_rows": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "dataset_group": {
      "type": "string",
  
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/join-coverage-analytics-numeric-row-ordering-keyed-dataset-comparison-1a6833c0/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)