Back to Browse
Join Coverage Analytics: Numeric Interval Filter + Two-Measure Correlation
x402
Join Coverage Analytics: Numeric Interval Filter + Two-Measure Correlation 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-23).
Filters join coverage rows by a numeric interval on a chosen measure and computes correlation between matched_rows and source_rows for supplied dataset records.
Price / call$0.01
Success—
StatusUnknown
How this service works
Join coverage — Numeric interval filter + Two-measure correlation: Numeric interval filter + Two-measure correlation 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 analytical reports: (1) rows from the input dataset that fall within the specified numeric interval for the chosen field (matched_rows or source_rows), and (2) a correlation analysis between matched_rows and source_rows across the supplied records. Results are based solely on the supplied data — no external lookups or live data.
Example use cases
ETL pipeline join quality check
“I have join coverage data from my ETL pipeline with matched_rows and source_rows per day. Can you filter the records where matched_rows is between 10 and 500, and then compute the correlation between matched_rows and source_rows? Here's the data: [{row_id:'etl-1', date:'2025-03-01', dataset_group:'orders', matched_rows:120, source_rows:300}, {row_id:'etl-2', date:'2025-03-02', dataset_group:'orders', matched_rows:8, source_rows:310}].”
Dataset group coverage comparison
“Can you analyze my join coverage for two dataset groups — 'customers' and 'transactions' — filtering on source_rows between 50 and 1000 and then telling me how correlated source_rows and matched_rows are across those records? My rows are: [{row_id:'c1', date:'2025-06-01', dataset_group:'customers', matched_rows:400, source_rows:500}, {row_id:'t1', date:'2025-06-01', dataset_group:'transactions', matched_rows:200, source_rows:600}].”
Anomaly detection in join results
“I suspect some of my join results are anomalous. Can you filter my join coverage records where matched_rows is between 0 and 50 — which I consider suspect — and compute the correlation between matched_rows and source_rows so I can see if there's a pattern? Data: [{row_id:'row-a', date:'2025-09-15', dataset_group:'inventory', matched_rows:30, source_rows:900}, {row_id:'row-b', date:'2025-09-16', dataset_group:'inventory', matched_rows:45, source_rows:850}, {row_id:'row-c', date:'2025-09-17', dataset_group:'inventory', matched_rows:200, source_rows:820}].”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ib26-analytics-09-131?utm_source=zero.xyzWhen to prefer
Use this endpoint when you have pre-collected join coverage data (matched_rows and source_rows per record) and need both a numeric range filter and a correlation analysis in a single $0.01 call. Ideal for data engineers and analytics pipelines that want to QA join quality, detect anomalies, or measure the statistical relationship between source and matched row counts without sending data to an external live system. Prefer this over general-purpose analytics tools when you need offline, deterministic computation on up to 200 rows.
Side effects
- Input array is empty or missing — returns validation error
- Rows exceed 200 item limit — request rejected
- minimum greater than maximum — may return empty filtered set or validation error
- Missing required fields (row_id, date, matched_rows, source_rows, dataset_group) — schema validation failure
- Null values in both measure fields — correlation computation may be undefined or return NaN
- Date field not matching YYYY-MM-DD pattern — schema validation error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| rows | array | |
| field | string | |
| maximum | number | |
| minimum | number |
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"