# Data Ingestion Batches — Equal-Width Histogram + Keyed Dataset Comparison > Data Ingestion Batches — Equal-Width Histogram + 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-21). Generates an equal-width histogram and a keyed dataset comparison report for up to 200 data ingestion batch records, analyzing received_rows or accepted_rows metrics. ## Facts - Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-01-174?utm_source=zero.xyz - Price: $0.01/call - Payment: x402 - Status: unknown - Last checked: 2026-10-21 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/data-ingestion-batches-equal-width-histogram-keyed-dataset-comparison-dd9709c2 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_keWdC7P-GZ-J0BnkUnwp3 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-equal-width-histogram-keyed-dataset-comparison-dd9709c2 -d '' ``` Example prompt: Can you run a histogram with 10 bins on the received_rows field for my ingestion batch data, and also compare it against a second dataset by row_id? Here are my primary rows: [{"row_id":"row-1","dataset_group":"group-a","date":"2025-01-01","received_rows":500,"accepted_rows":480}] and my comparison rows: [{"row_id":"row-1","dataset_group":"group-a","date":"2025-01-01","received_rows":510,"accepted_rows":470}]. ## When to prefer this Choose this endpoint when you need both a frequency distribution view (histogram) and a row-level keyed comparison of two ingestion batch datasets in a single call. It is purpose-built for data ingestion monitoring use cases involving received_rows and accepted_rows metrics, and is cost-effective at $0.01 for both reports simultaneously. Prefer it over generic analytics tools when your data already conforms to the ingestion batch schema (row_id, dataset_group, date, received_rows, accepted_rows) and you want local analytical computation without external lookups or predictions. ## Known failure modes - Exceeding 200 rows in either the primary or comparison dataset returns a validation error - Missing required fields (row_id, dataset_group, date, received_rows, accepted_rows) cause row-level rejection - Invalid date format (non YYYY-MM-DD) triggers pattern validation failure - Bin count outside 1–30 range returns a schema validation error - Null numeric values in the selected field may affect histogram bin calculation - Empty rows array returns an error due to minItems:1 constraint ## How this service works Data ingestion batches — Equal-width histogram + Keyed dataset comparison: Equal-width histogram + 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) an equal-width histogram showing frequency distribution of the selected numeric field (received_rows or accepted_rows) across the specified number of bins, and (2) a keyed dataset comparison identifying matching, missing, and differing rows between the primary and secondary datasets using row_id as the join key. ## Request schema (JSON Schema) ```json { "type": "object", "properties": { "bins": { "type": "integer", "default": 5, "maximum": 30, "minimum": 1 }, "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": "", "maxLengt … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/data-ingestion-batches-equal-width-histogram-keyed-dataset-comparison-dd9709c2/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)