Back to Browse
Record Routing Analytics — Two-Measure Correlation + Keyed Dataset Comparison
x402
Record Routing Analytics — 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-23).
Computes Pearson/Spearman correlation between accepted_records and rejected_records, and compares two keyed datasets of record routing data, returning two independent analytical reports for up to 200 rows.
Price / call$0.01
Success—
StatusUnknown
How this service works
Record routing — Two-measure correlation + Keyed dataset comparison: Two-measure correlation + Keyed dataset comparison for supplied record routing records (accepted_records, rejected_records). 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 two-measure correlation report showing the statistical relationship (e.g. Pearson or Spearman coefficient) between accepted_records and rejected_records across the supplied rows, and (2) a keyed dataset comparison report contrasting the primary and secondary datasets row-by-row using shared keys, highlighting differences in accepted and rejected record counts by group and date. All analysis is performed locally on the supplied data with no external lookups.
Example use cases
ETL pipeline acceptance rate audit
“I've got daily routing logs for October with accepted_records and rejected_records across group-a and group-b. Can you compute the correlation between accepted and rejected counts and compare this week's data against last week's to flag any drift?”
Data quality regression between releases
“We just deployed a new routing config. Here are two datasets — before and after — each with about 80 rows tagged by dataset_group and date. Please run a two-measure correlation on each and compare them side by side so I can see if rejection rates changed.”
Multi-group routing performance comparison
“I have routing records split across group-alpha, group-beta, and group-gamma for the past month. Can you correlate accepted_records vs rejected_records within each group and compare the two most recent 30-day windows to see which group's performance diverged?”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ib26-analytics-19-183?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you have record routing data with acceptance and rejection counts that you want to analyze statistically without any external API calls or live data lookups. It is ideal for offline ETL audit, pipeline regression testing, or comparing two snapshots of routing data. Prefer it over general BI tools when you need a fast, cheap ($0.01 USDC), self-contained computation that covers both correlation and dataset comparison in a single call for up to 200 rows.
Side effects
- Input rows array is empty or missing — returns validation error
- More than 200 rows submitted — request rejected with row limit error
- Required fields (row_id, dataset_group, date, accepted_records, rejected_records) missing from any row — schema validation failure
- Date fields not matching YYYY-MM-DD pattern — rejected by pattern validator
- Null values in both accepted_records and rejected_records for all rows — correlation cannot be computed
- Mismatched row_ids between primary and comparison datasets — keyed comparison may return partial or empty diff results
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| rows | array | |
| other | array |
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"