REST API · Category
Valuation
Automated valuation with the evidence behind it.
Endpoints (5)
Valuation accuracy
GET /v1/valuation/accuracyOur valuation error, measured forward: every month, each registered sale the model had already valued is compared with the price actually paid (MdAPE, PPE20, n) per asset class and model version. Nothing in it could have been seen by the model. Until the first vintage lands (October 2026) `status` is `no_rows_yet` — an empty table, not a zero error.
Valuation comps adjustments
GET /v1/valuation/{uprn}/comps-adjustmentsSame-building comparables for a property with the adjustment ledger: each comp's sale, its time adjustment by the district index to today, any relisting penalty, and the IQR fence that decided which comps count. This is the evidence behind `/valuation/full`, itemised.
Valuation transaction anchor
GET /v1/valuation/{uprn}/transaction-anchorThe subject property's own last registered sale, carried to today by the district index: the price, the date, the index factor applied and the anchored value. Where a property has sold, this is the single strongest piece of evidence a valuation has, and it is stated on its own here.
Valuation estimate
POST /v1/valuation/estimateAutomated value estimate for a property: a point value plus a range.
Valuation full
POST /v1/valuation/fullFull valuation block for a property: the value and its range, a monthly
Pilot the Valuation API.
30-minute call. We'll provision a key and walk through the endpoints on a real address.