Back to Browse
Job Listing Inventories — String Normalisation + Keyed Dataset Comparison
x402
Job Listing Inventories — String Normalisation + 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).
Performs string normalisation and keyed dataset comparison on two sets of job listing inventory records (listing_count, duplicate_listings) for up to 200 rows each, returning 2 independent analytical reports.
Price / call$0.01
Success—
StatusUnknown
How this service works
Job listing inventories — String normalisation + Keyed dataset comparison: String normalisation + Keyed dataset comparison for supplied job listing inventories records (listing_count, duplicate_listings). 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 string normalisation report cleaning company_group and date fields across the submitted rows, and (2) a keyed dataset comparison report showing row-level differences in listing_count and duplicate_listings between the two supplied datasets, matched by row_id.
Example use cases
Audit duplicate listings across company groups
“I've got two snapshots of job listing inventory for our company groups — one from last month and one from this month. Can you normalise the company_group strings and compare the two datasets row by row to show me where duplicate_listings changed?”
Detect listing count discrepancies between periods
“Here are two batches of job listing inventory records keyed by row_id, company_group, and date — can you run a keyed comparison and string normalisation to find any rows where listing_count differs between the two datasets?”
QA job board inventory before merging sources
“Before I merge these two job board inventory feeds, can you normalise the strings and do a keyed dataset comparison on the listing_count and duplicate_listings fields across both sets of up to 200 rows?”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ib26-company-13-036?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need offline, deterministic string normalisation and keyed row-by-row comparison of two job listing inventory datasets (up to 200 rows each) without requiring live lookups, external integrations, or predictions. Ideal for data quality audits, change detection between two inventory snapshots, or pre-merge validation of job listing feeds.
Side effects
- Input array exceeds 200 rows — request will be rejected
- Missing required fields (row_id, company_group, date, listing_count, duplicate_listings) on any row causes validation error
- Invalid date format (must match YYYY-MM-DD pattern) causes schema rejection
- row_id values that don't align between the two datasets may produce unmatched rows in comparison
- Null numeric values for listing_count or duplicate_listings may affect comparison completeness
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"