Back to Browse
Accessibility Findings — Record Quality Audit + Adjacent Row Changes
x402
Accessibility Findings — Record Quality Audit + Adjacent Row Changes 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).
Runs two local analytical reports (record quality audit and adjacent row changes) on up to 200 rows of accessibility findings data covering the 'findings' and 'resolved_findings' fields.
Price / call$0.01
Success—
StatusUnknown
How this service works
Accessibility findings — Record quality audit + Adjacent row changes: Record quality audit + Adjacent row changes for supplied accessibility findings records (findings, resolved_findings). 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 record quality audit identifying data issues, anomalies, or quality flags at the row level; and (2) an adjacent row changes report showing how values shift between consecutive rows — all computed locally without external lookups, covering up to 200 rows per call.
Example use cases
Audit accessibility findings for data quality
“I've got a table of accessibility findings records with columns for game_area, date, findings, and resolved_findings — can you run a record quality audit on the 'findings' field and tell me which rows have quality problems?”
Detect row-to-row changes in resolved findings
“Please analyze my accessibility findings dataset and flag any significant adjacent row changes in the 'resolved_findings' column — I want to see where numbers shift unexpectedly between consecutive rows.”
Validate game area accessibility data before reporting
“Before I submit our accessibility report, can you run both a record quality audit and adjacent row change analysis on our findings data? There are about 150 rows covering different game areas and dates, and I want to check the 'findings' field specifically.”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ib26-game-17-011?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need two simultaneous local analytical reports — record quality audit plus adjacent row changes — on accessibility findings data (findings and resolved_findings columns), without any live lookups or external data enrichment. It is cost-effective at $0.01 for both reports on up to 200 rows. Prefer it over general-purpose data tools when your dataset specifically matches the accessibility findings schema with game_area, date, findings, and resolved_findings fields.
Side effects
- Input array exceeds 200 rows — request will be rejected
- Missing required fields (row_id, game_area, date, findings, resolved_findings) cause row-level validation errors
- Date strings not matching YYYY-MM-DD pattern may be rejected
- Numeric fields outside allowed range (-1,000,000,000,000 to 1,000,000,000,000) will fail validation
- Empty rows array (minItems: 1 not met) returns an error
- Invalid field enum value (not 'findings' or 'resolved_findings') causes request failure
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"