Back to Browse
Content Reuse Duplicate Key Report + Numeric Row Ordering
x402
Content Reuse Duplicate Key Report + Numeric Row Ordering is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-02).
Generates a duplicate key report and numeric row ordering report for supplied content reuse records (reused_blocks, total_blocks) — up to 200 rows, no external lookups.
Price / call$0.01
Success—
StatusUnknown
How this service works
Content reuse — Duplicate key report + Numeric row ordering: Duplicate key report + Numeric row ordering for supplied content reuse records (reused_blocks, total_blocks). 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 rows with repeated key values across the supplied content reuse records, and (2) a numeric row ordering report ranking rows by the specified field (reused_blocks or total_blocks). Results cover up to 200 supplied rows using local analytical engines with no external data fetched.
Example use cases
Auditing duplicate document groups
“I've got a CSV of content reuse records with columns row_id, document_group, date, reused_blocks, and total_blocks — can you run a duplicate key report on them and also rank the rows numerically by reused_blocks? I want to catch any repeated keys before I import this data.”
Ranking blocks by reuse volume
“Here are 50 content reuse records with reused_blocks and total_blocks counts for each document group — please generate a numeric row ordering report ranked by total_blocks so I can see which groups have the most content being reused.”
Pre-publish content reuse QA
“Before we publish these document updates, I need a duplicate key check and a numerically ordered ranking of our content reuse dataset by reused_blocks — there are about 120 rows with row_id, document_group, date, reused_blocks, and total_blocks fields.”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ib26-writing-17-058?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need both a duplicate key audit and numeric row ordering in a single call on a batch of content reuse records (up to 200 rows). It is ideal for data quality checks before ingesting or publishing document reuse datasets, and is cost-effective at $0.01 for two reports. Prefer this over general-purpose analytics when your data specifically has reused_blocks and total_blocks fields and you want offline, local computation with no external lookups or predictions.
Side effects
- Fewer than 1 row supplied — minimum 1 row required
- More than 200 rows supplied — exceeds maxItems limit
- Invalid date format (not YYYY-MM-DD) — fails pattern validation
- Missing required fields (row_id, document_group, date, reused_blocks, total_blocks) — request rejected
- Invalid field enum value — must be 'reused_blocks' or 'total_blocks'
- Payment not included or insufficient — x402 payment required ($0.01 USDC)
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"