What an API would offer
- ZIP lookup endpoint. One call per ZIP returns drainage class, hydric rating, septic rating and limitations, farmland class, flooding/ponding frequency, water-table depth, and the plain-English verdicts — the same schema as our free lookup.
- Bulk data. Full JSON (and CSV on request) for every covered ZIP, for offline joins against your own parcel or listing data.
- Documented schema & vintage. Versioned fields, SSURGO refresh vintage per record, and a changelog — no silent field renames.
- Simple attribution terms. Source data is public-domain U.S. government data; our terms would ask for a link back to whiteharborlabs.com/soil-report/ and prohibit reselling the raw compilation as a competing dataset.
We’re testing demand. There is no API to sign up for and no pricing to quote —
emailing us just puts your use case on the list. If we build it, we’ll contact interested builders
first. We may never build it.
Express interest — email us
Your email app will open with the subject filled in. Tell us what you’d build, roughly how many lookups you’d need, and whether bulk files or an endpoint fit better — that shapes what we’d build.
Already machine-readable, no key needed
Our per-prefix data files are public and static — no signup, no key, no rate limit games:
https://whiteharborlabs.com/soil-report/api/v1/zip3/<NNN>.json
where <NNN> is the first 3 digits of the ZIP. Each file lists its covered ZIPs with
the full schema (drainage, hydric, septic, farmland, flooding/ponding, water table, verdicts, coverage %).
Prototype files currently hold 7,223 ZIPs across 8 states (AZ, CO, FL, GA, MO, NC, TN, TX);
the schema is the contract the full national pipeline will fill.