# Data Ingestion Batches — Numeric Distribution & Keyed Dataset Comparison > Data Ingestion Batches — Numeric Distribution & 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-19). Analyzes data ingestion batch records by computing numeric distribution statistics and performing keyed dataset comparison between two supplied datasets for received_rows or accepted_rows. ## Facts - Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-01-084?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-ingestion-batches-numeric-distribution-keyed-dataset-comparison-15bfee3c - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LPpHsxkki9Wwk6NVXUH-A 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-numeric-distribution-keyed-dataset-comparison-15bfee3c -d '' ``` Example prompt: Can you run a numeric distribution and keyed dataset comparison on my two ingestion batch datasets — the first has rows like {row_id: 'run-1', dataset_group: 'orders', date: '2024-06-01', received_rows: 5000, accepted_rows: 4800} and the second has the same keys but different counts — and analyze the received_rows field? ## When to prefer this Choose this endpoint when you need both a numeric distribution analysis and a keyed record-level comparison for data ingestion batch metrics (received_rows, accepted_rows) in a single low-cost call. It is ideal for data engineers monitoring pipeline quality, detecting ingestion regressions between runs, or auditing batch acceptance rates — especially when both datasets are already available locally and no external data enrichment or prediction is needed. Prefer this over building custom analytics scripts when you want a fast, structured dual-report output for up to 200 rows at minimal cost. ## Known failure modes - Missing required fields (row_id, dataset_group, date, received_rows, accepted_rows) causes validation error - Submitting more than 200 rows exceeds the maxItems limit and is rejected - Invalid date format (not YYYY-MM-DD) triggers pattern validation failure - Null numeric values in received_rows or accepted_rows may affect distribution computation - Mismatched row_ids between primary and comparison datasets may result in incomplete keyed comparison - Payment failure via x402 protocol prevents endpoint execution ## How this service works Data ingestion batches — Numeric distribution + Keyed dataset comparison: Numeric distribution + 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 Returns two analytical reports: (1) a numeric distribution summary for the selected field (received_rows or accepted_rows) across the primary dataset, including statistics such as min, max, mean, and percentiles; and (2) a keyed dataset comparison report matching records by row_id between the primary and comparison datasets, highlighting differences in received_rows and accepted_rows values. All analysis is performed locally on the supplied data — no external lookups or predictions are made. ## 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 }, "field": { "enum": [ "received_rows", "accepted_rows" ], "type": "string", "default": "received_rows" }, "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" … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/data-ingestion-batches-numeric-distribution-keyed-dataset-comparison-15bfee3c/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)