Back to Browse
Join Coverage Duplicate Key Report and Numeric Distribution
x402
Join Coverage Duplicate Key Report and Numeric Distribution 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 join coverage data (matched_rows, source_rows) to produce a duplicate key report and numeric distribution summary for up to 200 rows.
Price / call$0.01
Success—
StatusUnknown
How this service works
Join coverage — Duplicate key report + Numeric distribution: Duplicate key report + Numeric distribution 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 duplicate key report identifying any repeated row IDs or key collisions in the supplied join coverage records, and (2) a numeric distribution summary (e.g. min, max, mean, percentiles, histogram bins) for the selected numeric field (matched_rows or source_rows), covering up to 200 input rows.
Example use cases
ETL pipeline join quality check
“I just ran a join between two tables and got these results — row-1 through row-4 across group-a and group-b, with matched_rows of 10, 20, 15, 30 and source_rows of 1, 2, 3, 4. Can you check for duplicate keys and show me the numeric distribution of matched_rows?”
Dataset group match rate analysis
“I have daily join coverage records for October 2026 across two dataset groups and I want to understand how source_rows are distributed — run both a duplicate key check and a numeric distribution report on the source_rows field for my 4 rows.”
Data quality audit before pipeline merge
“Before I merge these datasets, can you run a duplicate key report and a numeric distribution check on my join coverage metrics? I have 4 records from group-a and group-b with matched_rows and source_rows values, and I want to audit the matched_rows column.”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ib26-analytics-09-055?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need both a duplicate key diagnostic and a numeric distribution analysis on join coverage data in a single paid call. It is purpose-built for ETL and data quality workflows where matched_rows and source_rows are the key metrics, and avoids the need for two separate API calls. Best for datasets up to 200 rows where local analytical computation is sufficient and no live data lookup or external enrichment is needed.
Side effects
- Input array empty or missing — returns validation error
- More than 200 rows submitted — rejected with maxItems error
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Numeric values outside allowed range (±1,000,000,000,000) — rejected
- Missing required fields (row_id, dataset_group, date, matched_rows, source_rows) — schema error
- Invalid field enum value (not 'matched_rows' or 'source_rows') — rejected
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| rows | array | |
| field | string |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"