Property context
Property facts without an automated valuation.
Join official property and neighbourhood sources through bounded, cited tools while keeping their real geography and limitations visible.
Free atomic endpoints
GET /v1/epc/E15%202NE?building_number=192 GET /v1/property-price-per-area/E15%202NE?building_number=192 GET /v1/deprivation/E15%202NE GET /v1/income/E15%202NE GET /v1/council-tax/E15%202NE GET /v1/connectivity/E15%202NE GET /v1/uprn/100023336956 GET /v1/property-tribunals/E15%202NE?building_number=192
MCP offers the corresponding get_epc_data, get_property_price_per_area, get_deprivation_data, get_income_data, get_council_tax_rates, get_connectivity_data, resolve_uprn and get_property_tribunal_decisions tools.
EPC floor area and observed sale ratios
EPC lookup accepts a postcode plus building number, or a full address through MCP, and reports ambiguity. Price per square metre and foot is calculated only when a complete normalised HM Land Registry Price Paid address exactly matches a published EPC address. Missing floor area is never estimated.
Neighbourhood and authority facts
- IMD 2025 ranks and deciles use the containing 2021 LSOA.
- ONS income returns four model-based MSOA means with their published 95% confidence intervals, not an estimate for a household or home.
- Council tax returns authority charges for bands A–H, not an inferred property band or final household bill.
- Ofcom fixed-broadband percentages describe the postcode aggregate; mobile coverage remains a separately dated local-authority aggregate. Neither is measured speed or availability at an address.
- OS Open UPRN resolves a numeric UPRN to its published coordinate only; it supplies no address or property attributes.
- Tribunal results are text-matched publisher links and do not establish title, occupier, liability or legal outcome for the queried property.
Coverage and release status
EPCs can be opted out, certificate and sale dates can differ, and recent Price Paid registrations are incomplete. These outputs are observed context, not a valuation, forecast, survey, recommendation or legal opinion. The live OpenAPI specification is authoritative for currently deployed operations.