Address intelligence usually means one of two things: validating that an address is real, or working out what an address implies about risk, value, and lifestyle. Zyfy is the second one — take the postcode you already have on a lead, a customer record, or an order, and get 45+ enrichment signals back in one call.
Postcode-level enrichment, not address validation. See "What this API does — and doesn't do" below.
{
"postcode": "EC2A 4NE",
"adminDistrict": "Hackney",
"region": "London",
"signals": {
"property": { "averagePrice": 612000 },
"flood": { "riversSea": "low" },
"crime": { "rateBand": "medium" },
"deprivation": { "imdDecile": 5 },
"housing": { "epcAverageRating": "C" }
},
"scores": {
"propertyRiskScore": 0.31,
"liveabilityScore": 0.58
},
"checkedAt": "2026-07-09T10:22:31Z"
}"Address intelligence" gets used for two different products, and it's worth being upfront about which one this is. If you need to confirm a typed string is a real, deliverable UK address — or offer autocomplete as someone types — that's address validation, built on Royal Mail's PAF (Postcode Address File). Zyfy doesn't do that; PAF is a separately licensed, paywalled dataset, and providers who specialise in it (getAddress.io, Loqate, Ideal Postcodes) do it well.
What Zyfy does is the step that usually comes after — you already have a real address, likely already validated at the point it entered your system, and you want to know what it tells you: is this a flood risk area, what's the crime rate, what do properties nearby sell for, how deprived is the area. That's enrichment, computed at postcode level from the postcode you already have on the record.
| Capability | Zyfy |
|---|---|
| Address validation / does this address exist? | ✗ — not what this API does |
| Address autocomplete (type-ahead as a user types) | ✗ — not what this API does |
| Individual property detail (PAF, UPRN-level) | ✗ — not what this API does |
| Postcode-level risk and lifestyle enrichment | ✓ — this is what this API does |
| Turning a postcode field you already have into 45+ signals | ✓ |
| Bulk enrichment of an existing address database | ✓ — up to 500 per call, or async bulk jobs for larger sets |
A subset of what's returned — 45+ signals on every plan, including free. View the full signal reference →
signals.property.averagePrice integer | null Median sale price (GBP), 12-month rolling window, from HMLR Price Paid data.
signals.flood.riversSea string | null Environment Agency flood risk classification for the address's postcode.
signals.crime.rateBand string | null National percentile band from Police UK LSOA crime counts.
signals.deprivation.imdDecile integer | null Index of Multiple Deprivation decile, 1–10 — useful context for credit and affordability checks.
signals.housing.epcAverageRating string | null Average Energy Performance Certificate rating for the postcode — a proxy for property age and condition where an exact EPC isn't available.
scores.livabilityScore number | null Pre-computed composite of air quality, crime, deprivation, green space, and EPC. Useful for lead scoring and relocation tools.
Enriching an address record you already trust — not validating it.
The term covers two genuinely different problems that get lumped together. One is address validation — confirming a typed string is a real, deliverable address, usually backed by Royal Mail PAF. The other is location enrichment — given an address you already trust, telling you something useful about the area it sits in: risk, deprivation, property value, demographics. Zyfy does the second. It does not validate, correct, or autocomplete addresses.
No. Zyfy does not use Royal Mail PAF and does not offer address validation or type-ahead autocomplete. If you need that, providers like getAddress.io, Loqate, or Ideal Postcodes specialise in it. Zyfy is the enrichment step that typically comes after — once you have a validated address (or just a trusted postcode) and want to know what it implies.
Send the postcode component of the address — Zyfy's signals are computed at postcode level, not individual property level, so the street number and name don't change the result. Extract the postcode from your address record (most CRM and checkout systems already store it as a separate field) and pass that.
No. Individual property-level address data is paywalled at source (Royal Mail PAF licensing), so it's out of scope. Every signal Zyfy returns — property price, flood risk, crime, deprivation — is accurate to the postcode, which for most enrichment use cases (CRM scoring, insurance pricing, logistics tiering) is the right level of granularity anyway.
Extract the postcode from each address record and submit the list to POST /v1/postcode/bulk (up to 500 per call depending on plan) or POST /v1/postcode/bulk/async for larger batches, which runs as a background job with a poll URL for results.
Common patterns: scoring inbound leads by area before a sales call, flagging high flood-risk addresses in an insurance quote flow, tiering delivery SLAs by rural/urban classification, or adding location context to a CRM record with a single lookup instead of a manual data join. See our CRM enrichment and logistics use case pages for worked examples.
Contains public sector information licensed under the Open Government Licence v3.0.
Free tier. No credit card. 100 requests/month.
Get your free API key