# Data Ingestion Batches — Two-Measure Correlation + Keyed Dataset Comparison > Data Ingestion Batches — 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-16). Computes Pearson/rank correlation between received_rows and accepted_rows, and compares two keyed data ingestion batch datasets, returning two independent analytical reports for up to 200 rows. ## Facts - Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-01-183?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/data-ingestion-batches-two-measure-correlation-keyed-dataset-comparison-4a2a72b8 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8nSxf_6vu4AJ7ALTc0-uu 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-ingestion-batches-two-measure-correlation-keyed-dataset-comparison-4a2a72b8 -d '' ``` Example prompt: Run a two-measure correlation between received_rows and accepted_rows plus a keyed dataset comparison on my two ingestion batch logs — the primary dataset has rows like row-1 on 2026-10-01 in group-a with received_rows=10 and accepted_rows=1, and the secondary is nearly identical but with slightly different received_rows values; up to 4 rows each. ## When to prefer this Choose this endpoint when you need both a two-measure Pearson/rank correlation between received_rows and accepted_rows AND a keyed comparison of two ingestion batch datasets in a single $0.01 call. It is purpose-built for data ingestion pipeline QA, ETL audit, and batch acceptance-rate analysis on up to 200 rows. Prefer this over general-purpose analytics APIs when your data is already structured with row_id, dataset_group, date, received_rows, and accepted_rows fields and you do not need live external data, predictions, or professional assessments. ## Known failure modes - Submitting more than 200 rows results in a validation error - Missing required fields (row_id, dataset_group, date, received_rows, accepted_rows) cause row-level rejection - Date values not matching YYYY-MM-DD format fail schema validation - Null values in received_rows or accepted_rows may reduce correlation sample size - Mismatched row_ids between primary and secondary datasets result in unmatched keys in comparison report - Submitting fewer than 2 rows may produce degenerate or undefined correlation results ## How this service works Data ingestion batches — Two-measure correlation + Keyed dataset comparison: Two-measure correlation + Keyed dataset comparison for supplied data ingestion batches records (received_rows, accepted_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 two-measure correlation report quantifying the statistical relationship between received_rows and accepted_rows across the supplied rows, and (2) a keyed dataset comparison report highlighting differences between the primary and secondary datasets matched by row_id. 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", "received_rows", "accepted_rows" ], "properties": { "date": { "type": "string", "default": "", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "maxLength": 10 }, "row_id": { "type": "string", "default": "", "maxLength": 80, "minLength": 1 }, "accepted_rows": { "type": [ "number", "null" ], "maximum": 1000000000000, "minimum": -1000000000000 }, "dataset_group": { "type": "string", "default": "", "maxLength": 80 }, "received_rows": { "type": [ "number", "null" ], "maximum": 1000000000000, "minimum": -1000000000000 } }, "additionalProperties": false }, "default": [ { "date": "2026-10-01", "row_id": "row-1", "accepted_rows": 1, "dataset_group": "group-a", "received_rows": 10 }, { "date": "2026-10-02", "row_id": "row-2", "accepted_rows": 2, "dataset_group": "group-b", "received_rows": 20 }, { "date": "2026-10-03", "row_id": "row-3", "accepted_rows": 3, "dataset_group": "group-a", "received_rows": 15 }, { "date": "2026-10-04", "row_id": "row-4", "accepted_rows": 4, "dataset_group": "group-b", "received_rows": 30 } ], "maxItems": 200, "minItems": 1 }, "other": { "type": "array", "items": { "type": "object", "required": [ "row_id", "dataset_group", "date", "received_rows", "accepted_rows" ], "properties": { "date": { "type": "string", "default": "", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "maxLength": 10 }, "row_id": { "type": "string", "default": "", "maxLength": 80, "minLength": 1 }, "accepted_rows": { "type": [ "number", "null" ], "maximum": 1000000000000, "minimum": -1000000000000 }, "dataset_group": { "type": "string", "default": "", "maxLength": 80 }, "received_rows": { "type": [ "number", "null" ], "maximum": 1000000000000, "minimum": -1000000000000 } }, "additionalProperties": false }, "de … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/data-ingestion-batches-two-measure-correlation-keyed-dataset-comparison-4a2a72b8/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)