Back to Browse
Release Note Coverage — Duplicate Key Report + Numeric Distribution
x402
Release Note Coverage — Duplicate Key Report + 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-23).
Analyzes up to 200 release note coverage records to produce two local analytical reports: a duplicate key report and a numeric distribution summary for documented_changes or released_changes.
Price / call$0.01
Success—
StatusUnknown
How this service works
Release note coverage — Duplicate key report + Numeric distribution: Duplicate key report + Numeric distribution for supplied release note coverage records (documented_changes, released_changes). 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
Two independent analytical reports: (1) a duplicate key report identifying rows sharing the same key values across up to 200 input records, and (2) a numeric distribution summary for the selected field (documented_changes or released_changes), including frequency and spread statistics. No external lookups or predictions are made.
Example use cases
Auditing duplicate release note entries
“I have a batch of release note coverage records from our last sprint and I want to know if any row IDs or document groups are duplicated, and how the documented_changes counts are distributed — can you run the duplicate key report and numeric distribution on these rows?”
Distribution analysis of released changes
“Can you analyze the numeric distribution of released_changes across my 150 release note records? I also want to catch any duplicate keys before I finalize the dataset.”
Pre-publish release coverage QA
“Before we publish our release notes, run a duplicate key report and a numeric distribution check on these coverage records using the released_changes field — I need to make sure everything looks clean and well-distributed.”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ib26-writing-15-055?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to quickly audit a batch of release note coverage records (up to 200 rows) for duplicate keys and understand the numeric distribution of change counts, without requiring external data lookups or real-time computation. It is ideal for pre-publish QA, sprint review automation, or data hygiene checks on release documentation datasets.
Side effects
- Empty rows array returns an error (minItems: 1)
- More than 200 rows submitted exceeds the maxItems limit
- Invalid date format (not YYYY-MM-DD) causes schema validation failure
- Missing required fields (row_id, document_group, date, documented_changes, released_changes) on any row causes rejection
- Invalid field enum value (not 'documented_changes' or 'released_changes') causes an error
- Numeric values outside allowed range (-1e12 to 1e12) are 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"