Data validation APIs for regulated industries.
Narrow tools that check one thing correctly: hospital price files against the CMS v3.0 template, clinical trial tables before analysis, UAD 3.6 appraisal XML against the GSE rules, nursing home PBJ staffing files before they go to CMS, Davis-Bacon payrolls before they are certified. Per-use pricing. No subscriptions, no sales calls.
| Table | Row | Field | Rule |
|---|---|---|---|
| studies | 4 | trial_id | INVALID_NCT_ID |
| studies | 6 | trial_id | DUPLICATE_KEY |
| outcomes | 4 | primary_endpoint | MISSING_VALUE |
| outcomes | 5 | outcome_id | DUPLICATE_KEY |
| outcomes | 3 | results_first_post_date | INVALID_ISO_DATE |
| outcomes | 6 | trial_id | ORPHAN_OUTCOME |
| outcomes | 7 | outcome_type | INVALID_OUTCOME_TYPE |
How it works
Pick a validator
Each API does one job, documented end to end: what it checks, input schema, output schema, pricing.
Test it live
Every product page has a working test form. Run your real file or tables before you pay anything.
Call it from your pipeline
REST endpoints, API keys, structured JSON reports. Prepaid credits through Stripe.
The catalog
Hospital Price Transparency MRF Validator
Validates hospital machine-readable price files against the CMS v3.0.0 schema and CSV templates. JSON, tall CSV, wide CSV. Checks required metadata, template columns, billing code types, payer rules and the 2026 allowed-amount elements.
$0.25 per completed validation
Validate a fileClinical Trial Results Table QA
Audits normalized clinical-trial study and outcome tables: NCT ID validity, required fields, duplicates, orphan outcomes, outcome types and results-posting dates. Exact row locations for every finding.
$0.25 per completed audit
Audit your tablesUAD 3.6 Appraisal Report Validator
Checks UAD 3.6 URAR appraisal XML, or the whole ZIP package, against the GSE-published delivery specification and compliance rules. Every finding has an XPath, a rule ID and a message. A PASS is not UCDP acceptance.
$1.00 per completed report
Check a reportPBJ Staffing Data Pre-Submission QA
Checks a nursing home's quarterly Payroll Based Journal staffing XML, or the upload ZIP, against the CMS v4.10.0 specifications before it goes to CMS, and flags staffing patterns CMS has named as audit or rating risks. A PASS is not CMS acceptance.
$25.00 per completed report
Check a PBJ fileDavis-Bacon WH-347 Certified Payroll Pre-Check
Recomputes a weekly Davis-Bacon certified payroll against your wage determination rates before you sign it: basic rates, fringe benefits, overtime, apprentice rates and ratios, and the gross, deductions and net pay math. A PASS is not a compliance finding.
$25.00 per completed report
Check a payrollNext validator
The catalog grows from observed demand. Each new validator gets the same treatment: documented checks, live test, per-use pricing.
Suggest a validatorWhy this exists
Regulated data is full of narrow, annoying, high-stakes validation problems. The existing options are usually a government PDF, a command-line tool that takes an afternoon to install, or an enterprise vendor that wants a contract.
SpreadRun sits in the gap: hosted, documented, per-use tools for the specific checks that compliance teams, vendors, and data pipelines actually need, built to be called by people and by agents alike.
What we won't do: generic AI wrappers, broad horizontal platforms, or tools that need a sales call to understand. If a validator can't be explained, tested, and bought in ten minutes, it doesn't belong here.
Questions
What is SpreadRun?
A small catalog of data-validation APIs for regulated industries. Each product checks one specific thing, currently hospital price transparency files, clinical trial results tables, UAD 3.6 appraisal reports, nursing home PBJ staffing files and Davis-Bacon certified payrolls, through a documented REST API with per-use pricing.
How is this different from the free government tools?
Government validators, like the one CMS publishes, are built for one-off manual checks, and they are good at that. SpreadRun's APIs are built for repeated, programmatic use: no installation, structured JSON reports, and endpoints your pipeline or agent can call directly.
How does pricing work?
You buy prepaid credits through Stripe: $5, $20, $50 or $100 of credit that works on every API. Each API has its own price per completed run, from $0.25 (a $5 pack covers 20 standard runs). Credits never expire. No subscriptions, no seat licenses. Requests rejected as invalid input are not charged. The full price list is on the APIs page.
Do I need an account to try it?
No. Every product page has a live test form. Run a real validation or audit before creating an account or paying anything.
Who builds the validators?
SpreadRun's catalog is supplied by DataForge, which builds narrow data-validation capabilities and operates them as hosted APIs.
Can I suggest a validator?
Yes. The catalog grows from observed demand. Tell us what you need to check on the contact page.