The website
Postcode report
Type a postcode, read the answer. Eleven categories, each fetched independently and appearing as it arrives, with the source and licence printed against every figure.
Run a report →UK open data · compiled 2 August 2026 · free and open
Enter a UK postcode and read what government open data says about it — demographics, crime, deprivation, prices, fibre, 5G, noise, transport, amenities, schools and planning constraints. Assembled live from the publishers' own APIs, in your browser. No account, no server in between.
Or try SW1A 1AA · M1 1AE · EH1 1YZ — the Edinburgh one shows you what an honest coverage gap looks like.
Neighbourhood data is easy to make impressive and hard to make truthful. These are the constraints this project holds itself to, and they are the reason to trust a number it shows you.
Every band word — "above the UK average" — comes from a threshold table, and always sits next to the figure it describes. No score is conjured out of a weighting nobody can see.
A Scottish postcode is told that data.police.uk excludes
Scotland, with a link to Police Scotland, rather than being shown a zero.
Deprivation is computed against each nation's own index and denominator.
The same provider layer underneath all three, so a threshold, a coverage gate or a caveat is written once and every surface agrees.
The website
Type a postcode, read the answer. Eleven categories, each fetched independently and appearing as it arrives, with the source and licence printed against every figure.
Run a report →For agents
The same research, agent-shaped. Five tools covering reports, lookups, side-by-side postcode comparison and the registry itself. One URL to paste, nothing to install.
Connect an agent →The raw material
Every dataset underneath, with its endpoint, API docs, licence, update cadence, coverage, and the questions it can actually answer. Searchable, and machine-readable as JSON and CSV.
Browse the registry →Counted from data/registry.json when this page loads,
never typed in — so it cannot drift from what the registry actually holds.
Fifteen categories. Each one opens the catalogue already filtered.
UK open data is not published evenly across the four nations, and pretending otherwise is how neighbourhood tools end up showing a zero where they mean "no data". Counted from each entry's own coverage statement.
| Nation | Datasets covering it |
|---|
These count datasets whose coverage statement includes the nation. They are not a claim about resolution — an England-wide index at LSOA level and a UK figure at local-authority level both count once here, and each entry records its own granularity.
The compilation is CC0. Take the registry, point your own thing at it.
Any MCP-speaking agent can run the same research. Paste this URL into Claude, ChatGPT or anything else that speaks the protocol — no account, no key, nothing to install.
https://agentic-house-search.vercel.app/mcp
Or in one command, if you would rather not click through a settings pane:
claude mcp add --transport http \ agentic-house-search \ https://agentic-house-search.vercel.app/mcp
45 entries, twelve fields each, also available as CSV.
curl -s https://agentic-house-search.vercel.app/data/registry.json
Or run the whole site locally:
git clone https://github.com/asturksever/\ agentic-house-search-data-registry cd agentic-house-search-data-registry python3 -m http.server 8000