Signals
Crime, deprivation, sale prices, schools, amenities, transport and flood risk for 43,064 neighbourhoods, through one API. Every value carries its source, the period it describes, a confidence level and its rank in the nation, and every place has a permanent ID your records can key on.
See it run
A postcode goes in. The neighbourhood comes back with its permanent ID and every signal, each one sourced, dated and rated.
One shape across three nations, a rank in the nation, a confidence level and a source with two dates. The same four properties on every value we return.
England, Wales and Scotland come back in one response shape, each nation's deprivation in its own official index. Integrate once and read every category the same way.
Every stored value says where it sits among the nation's neighbourhoods and among its region's, so a number means something on its own.
Each value says how solid it is, from how complete and how recent the data behind it is, so thin data never reads as a hard fact.
Every value names the dataset it came from, the period it describes and when its publisher released it, so you can cite it and know how old it is.
One API · seven categories · three nations
Every neighbourhood, and the group, district, region and nation above it, has an ID that survives census boundary changes and postcode retirements. Resolve any postcode, live or retired, or any official code to its place once, 1,000 records per call or 20,000 as a job, and key your records on it.
Read a neighbourhood, or the group or district that contains it, with grain=group or grain=district. Aggregates carry crime so far, with the rate recomputed over the places counted and no estimated ranks.
Sourced, dated, confidence-rated and keyed on a permanent place ID. The facts a product team needs about every neighbourhood, without owning the pipeline.
Get a sandbox key
The Signals workspace in the console
The same facts behind a listing page, a dataset you sell, a search filter or a customer's portfolio.
One integration, kept current by us, underneath features you already ship.
Show the neighbourhood's facts beside each listing or valuation, each with its source and date, in your own design.
Enrich every row of a dataset you sell or analyse with the same sourced values, keyed on the place ID so the join holds when boundaries move.
Resolve a customer's addresses to places once, then read the places' facts whenever the customer opens them.
Rank and filter neighbourhoods by a signal's value or its national rank, and page through the result.
Frequently asked
Every neighbourhood in England, Wales and Scotland, 43,064 of them, on the 2021 census geography for England and Wales and the 2022 Data Zones for Scotland. Send a postcode, live or retired, an official code or a place ID and you get the neighbourhood back. Northern Ireland is not covered yet.
police.uk, the Office for National Statistics, HM Land Registry, MHCLG's IMD 2025, the Welsh Government's WIMD 2019, the Scottish Government's SIMD 2020 and council-area crime, Ofsted, the Environment Agency, SEPA, Natural Resources Wales, NaPTAN and OpenStreetMap. Every value names the dataset it came from.
Each publisher on its own clock. Crime is checked daily and loaded when police.uk publishes. Land Registry sales load monthly and ONS prices each quarterly release. Deprivation loads with each new edition. Schools, transport and amenities load monthly. Flood maps load monthly in England and quarterly in Scotland and Wales. Every value carries the period it describes and the date its publisher released it.
How complete and how recent the data behind the value is. Thin data, such as a price median on a handful of sales or a schools figure with few graded schools, is marked down rather than hidden.
They move when the data or the method does, and both are visible. Every response carries the methodology version that produced it, every release is published in the changelog with what it changed, and the change feed says whether an area moved or our method did.
A permanent identifier, oga_pl_ and thirteen characters, for every neighbourhood and the places above it. It stays the same when a postcode is retired or a census boundary moves, so your records can key on it. Resolve any input to its place with /v1/places/resolve, 1,000 at a time, or 20,000 as a job.
A REST API with a published OpenAPI specification, bulk mapping for a whole catalogue, and an MCP server so the AI features in your product can call the same layer.
One API, three nations, a permanent ID for every place, and a source and date on every value. Start in the free sandbox.