Surveyor · valuation report context
Postcode intelligence for property valuation
The problem
Valuation reports want context: is the area on the up, what's the crime trend, are there flood concerns, has the EPC band shifted. Surveyors stitch this together from postcodes.io for geography + Police.uk for crime + EA for flood + the EPC register for energy. Each one a separate JSON shape, each one missed when a new graduate runs the report.
How Stratum fits
One endpoint returns the full picture in a stable JSON shape: geography (region, LSOA), crime (8-bucket breakdown + 12-month trend), flood (river/sea + surface water bands + nearest EA station), radon (UKHSA Atlas), coal mining (Coal Authority DHRA point-in-polygon), contaminated land + landfill (per-LA register + EA national register), Japanese knotweed proxy. Each capability carries its own `source` provenance line, so the valuation appendix names the authoritative data source.
One request
# Request
curl "https://api.stratumapis.com/v1/postcode/PE34%201AA" -H "x-stratum-key: $KEY"
# Response
{ "postcode": "PE34 1AA", "crime": {"trend": {...}, "categoryBreakdown": {...}}, "flood": {"riverAndSea": "medium"}, "radon": {"band": "low"}, "knotweed": {"band": "low"} }Set $KEY from your dashboard.
Frequently asked
Does this cover Japanese knotweed?
Postcode-area proxy from INNS / iRecord aggregates. Carries an explicit disclaimer that the band is NOT a property-level survey — the valuer should still rely on TA6 disclosure + a chartered surveyor field check.
Is the crime data per-postcode or per-LSOA?
Police.uk publishes per-street-segment within a 1-mile radius. We return both an 8-bucket category breakdown and the 12-month trend with up/flat/down arrows.
How does this fit into RICS reports?
We don't produce the RICS-format report; we feed the data the surveyor's report-template needs. A standard pattern: pre-populate the 'environmental factors' section + the surveyor reviews + signs.