# Join Coverage Analytics: Two-Measure Correlation + Keyed Dataset Comparison > Join Coverage Analytics: Two-Measure Correlation + 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-15). Runs two analytical reports on join coverage data: a correlation analysis between matched_rows and source_rows, plus a keyed comparison between two supplied datasets, for up to 200 rows. ## Facts - Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-09-183?utm_source=zero.xyz - Price: $0.01/call - Payment: x402 - Status: unknown - Last checked: 2026-10-15 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/join-coverage-analytics-two-measure-correlation-keyed-dataset-e711a42e - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_D4o2en0JC13f0zLmPVMgR 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-two-measure-correlation-keyed-dataset-e711a42e -d '' ``` Example prompt: I have two sets of join coverage records — each row has a row_id, dataset_group, date, matched_rows, and source_rows — can you run a two-measure correlation between matched_rows and source_rows and also do a keyed comparison between the two datasets? Here's dataset 1 with rows like {row_id: 'run-1', dataset_group: 'orders', date: '2024-01-15', source_rows: 1000, matched_rows: 950} and dataset 2 with the same keys but slightly different matched_rows values. ## When to prefer this Choose this endpoint when you need both a correlation analysis and a keyed dataset comparison on join coverage data (matched_rows, source_rows) in a single $0.01 call covering up to 200 rows. It is ideal for data engineers auditing ETL join quality, comparing two pipeline run snapshots, or measuring how source row counts relate to matched row counts across dataset groups. Prefer it over single-report endpoints when you need two complementary analyses on the same join coverage data in one request. ## Known failure modes - Input array exceeds 200 rows — request rejected - Missing required fields (row_id, dataset_group, date, matched_rows, source_rows) — validation error - Date field does not match YYYY-MM-DD pattern — schema validation failure - Numeric values outside allowed range (±1 trillion) — rejection - Empty rows array (minItems: 1 violated) — error - Malformed JSON body — 400 bad request - Payment not included or insufficient — 402 payment required ## How this service works Join coverage — Two-measure correlation + Keyed dataset comparison: Two-measure correlation + 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 Returns two independent analytical reports: (1) a two-measure correlation report quantifying the statistical relationship between matched_rows and source_rows across the supplied rows, and (2) a keyed dataset comparison report highlighting differences between the primary and secondary datasets matched by row_id and dataset_group. All analysis is performed locally on the supplied data 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 }, "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", "default": "", "maxLength": 80 } }, "additionalProperties": false }, "default": [ { "da … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/join-coverage-analytics-two-measure-correlation-keyed-dataset-e711a42e/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)