Back to Browse
Transport Ridership Record Quality Audit and Numeric Row Ordering
x402
Transport Ridership Record Quality Audit and 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-10-26).
Audits transport ridership records for data quality issues and sorts rows numerically by a chosen metric (passenger_count or service_count), returning two independent analytical reports for up to 200 rows.
Price / call$0.01
Success—
StatusUnknown
How this service works
Transport ridership — Record quality audit + Numeric row ordering: Record quality audit + Numeric row ordering for supplied transport ridership records (passenger_count, service_count). 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 reports: (1) a record quality audit flagging issues such as nulls, out-of-range values, or malformed entries in the ridership rows; (2) a numeric row ordering of the supplied records ranked by the chosen field (passenger_count or service_count). Both reports are computed locally with no external lookups.
Example use cases
Transit agency data quality check
“I have a batch of daily ridership records from three regions — each row has a row_id, region, date, passenger_count, and service_count. Can you audit them for quality issues and also sort them by passenger_count so I can see which days had the highest ridership?”
Cleaning regional service count dataset
“Before I hand off this dataset to our reporting team, can you run a quality audit on these transport records and order them by service_count? I have about 120 rows with region, date, passenger_count, and service_count fields.”
Spotting bad rows in bus ridership exports
“I exported ridership data from our bus network — about 80 rows — and I want to check for any data quality problems in the passenger_count field and get the rows sorted numerically by that field. Can you run both reports?”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ib26-economics-05-007?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need both a data quality audit and a numeric ordering of transport ridership records (passenger_count and service_count) in a single $0.01 call covering up to 200 rows. It is ideal for pre-processing or validation pipelines before downstream analysis, where no live lookups, predictions, or external data enrichment are needed — just local analytical assessment of supplied records.
Side effects
- More than 200 rows submitted — request will be rejected or truncated
- Missing required fields (row_id, region, date, passenger_count, or service_count) on any row causes validation failure
- Invalid date format (not YYYY-MM-DD) triggers schema rejection
- Field enum value not one of 'passenger_count' or 'service_count' causes error
- Numeric values outside the allowed range (-1,000,000,000,000 to 1,000,000,000,000) rejected
- Empty rows array rejected (minItems: 1)
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"