Attribution
Built with Civic Data.
If a page, report, listing or agent answer uses Civic Data, say so. The badge links readers back to the provenance behind the numbers, and telling us what you built helps us show what is possible.
The badge
A 188×30 SVG that links here. Place it at the bottom of any page that shows Civic Data results, next to the data attribution.
HTML
<a href="https://civicdata.co.uk/built-with"><img src="https://civicdata.co.uk/built-with-civic-data.svg" alt="Built with Civic Data" width="188" height="30"></a>
Markdown
[](https://civicdata.co.uk/built-with)
How to attribute the data
Civic Data republishes official UK public data under the Open Government Licence and related open licences, which require the original publisher to be credited. Every REST response and MCP tool result carries a sources array with name, publisher and as_of; render it next to the numbers. A complete line looks like:
Data: Office for National Statistics — ONS Postcode Directory (2026-05); London Fire Brigade — Incident Records (2024-2026-04). Via Civic Data.
The postcode pages on this site carry the same strip at the bottom, so you can copy its structure. Licences and publishers are listed on the sources page.
What gets built
- Agent answers. Assistants connected to the MCP server cite the publisher, dataset version and freshness instead of guessing.
- Area and comparison pages. Factual, non-ranked tables for postcodes, wards, local authorities and MSOAs, regenerated when a source updates.
- Listing and report enrichment. Fire, recorded crime, road-collision and planning-designation context added to a property listing, conveyancing report or planning objection.
- Research and journalism. Scripted lookups through the CLI or REST into spreadsheets and notebooks, with the source version recorded.
Tell us what you built
Email [email protected] with the URL, one sentence on what it does, and which tools or endpoints it uses. Projects that attribute the publishers correctly are listed here.