Skip to main content
29M UK properties, one API call Get your API key →
Homedata vs Street Data

Predictable token pricing.
Not per-lookup billing.

Both are developer-first property data APIs. The difference is how you pay. Street Data charges per lookup, at £0.02 to £0.50 per call depending on the endpoint. Homedata charges in tokens: every endpoint at a published weight, same price, predictable bill.

Get started See the comparison ↓

Pay as you go: 100 tokens = £1. Transparent weights: address find 2 tokens, retrieve 5. No per-lookup charges.

Two billing models, same data

Street Data

Pay per lookup

Variable cost per lookup

£0.02–£0.50 per lookup depending on endpoint. Costs scale linearly with usage.

Different endpoints, different prices

Each data type has its own per-lookup cost. A 5-endpoint workflow costs 5 different amounts.

Developer-first API

Good documentation, JSON responses, REST endpoints. Built for integration.

Homedata

Prepaid tokens

Predictable cost

Prepaid tokens, 100 = £1. Every endpoint has a published weight.

Transparent token weights: you know the cost upfront

Most property data endpoints cost 1 token; address find/postcode 2, retrieve 5, the complete property profile 50, reflecting real infrastructure costs.

Pay as you go

Pay as you go: 100 tokens = £1, no subscription needed. Address find costs 2 tokens, retrieve 5, still far cheaper than per-lookup competitors.

Both products serve developers building on UK property data. The key difference is billing predictability.

The portfolio problem

Per-lookup pricing works fine for one-off checks. But if you're building portfolio tools, due diligence workflows, or bulk enrichment, the maths changes fast.

100 properties

5 data points each (address, EPC, flood risk, sold prices, property detail)

Street Data (PAYG)

£10 – £250

Depends on endpoint mix

Homedata (tokens)

£5

500 tokens at 1 token a call

1,000 properties

5 data points each: typical monthly portfolio refresh

Street Data (PAYG)

£100 – £2,500

Wide range based on endpoints

Homedata (tokens)

£50

5,000 tokens at 1 token a call, or £50 a month adds 5,500 tokens a month

10,000 properties

5 data points each: enterprise portfolio management

Street Data (PAYG)

£1,000 – £25,000

Highly variable by endpoint

Homedata (tokens)

£500

50,000 tokens at 1 token a call, or £500 a month adds 67,500 tokens a month

The point isn't just cost. It's that you can calculate your Homedata number on day one: before you write a line of code. With per-lookup pricing, your bill depends on which endpoints you use, how often, and at what scale. That makes budgeting a guess until you're in production.

Feature comparison

Side by side: what each API offers.

Homedata
Street Data
Billing model Prepaid tokens at published weights: pay as you go, or monthly with bonus tokens Pay-as-you-go: £0.02–£0.50 per lookup
Entry price Pay as you go: 100 tokens = £1, first top-up matched, no credit card required Limited trial / demo
Cost predictability Fixed: know your max cost before you build Variable: depends on endpoint mix and volume
Address search V1: 2 tokens Charged per lookup
EPC data 1 token: transparent token weights across all endpoints Available: per-lookup charge
Flood / environmental risk 7 risk types: flood, radon, noise, landfill… Available: per-lookup charge
Comparable sales PostGIS radius search Available: per-lookup charge
Planning applications Radius search by lat/lng Available: per-lookup charge
Embeddable address widget Drop-in JS typeahead widget API only: build your own UI
Documentation Interactive docs + Python/JS/cURL examples Good developer docs

What Street Data offers that we don't

Honest comparison: some things they do differently or have that we don't yet.

Pay-as-you-go flexibility

If your usage is very low and sporadic, paying per lookup with no prepaid balance might cost less than Homedata's minimum £20 top-up. PAYG works well for occasional one-off lookups.

Established developer community

Street Data has been serving developers longer. Their API patterns and data coverage may be more mature in certain areas.

Granular endpoint pricing

Per-endpoint pricing means you only pay for what you use. If you only need one data type, PAYG avoids paying for endpoints you don't call.

Different data sources

They may source or process certain datasets differently. Always verify coverage for your specific use case with both providers.

Try it: zero cost, zero commitment

Get an API key in 30 seconds. Address find costs 2 tokens via V1. Property data is pay as you go — 100 tokens = £1.

Search → Property → EPC 
# 1. Search for a property
curl "https://api.homedata.co.uk/address/find/?q=10+Downing+Street+London" \
  -H "Authorization: Api-Key YOUR_API_KEY"

# 2. Get property details (1 token)
curl -H "Authorization: Api-Key YOUR_API_KEY" \
  "https://api.homedata.co.uk/properties/100023336956/"

# 3. Get EPC data (1 token)
curl -H "Authorization: Api-Key YOUR_API_KEY" \
  "https://api.homedata.co.uk/epc-checker/100023336956/"
quickstart.py 
import requests

API_KEY = "your_api_key_here"
headers = {"Authorization": f"Api-Key {API_KEY}"}

# Address search: 2 tokens
results = requests.get("https://api.homedata.co.uk/address/find/", params={"q": "10 Downing Street"}, headers=headers).json()
uprn = results["suggestions"][0]["uprn"]

# Get property + EPC: 2 tokens total
prop = requests.get(f"https://api.homedata.co.uk/properties/{uprn}/", headers=headers).json()
epc = requests.get(f"https://api.homedata.co.uk/epc-checker/{uprn}/", headers=headers).json()

print(f"{prop['address']}: {prop['bedrooms']} bed {prop['property_type']}")
print(f"EPC: {epc['current_energy_efficiency']}/100")
quickstart.js 
const API_KEY = 'your_api_key_here';
const headers = { 'Authorization': `Api-Key ${API_KEY}` };

// Address search: 2 tokens
const search = await fetch('https://api.homedata.co.uk/address/find/?q=10+Downing+Street', { headers });
const { suggestions } = await search.json();
const uprn = suggestions[0].uprn;

// Get property + EPC: 2 tokens total
const prop = await fetch(`https://api.homedata.co.uk/properties/${uprn}/`, { headers }).then(r => r.json());
const epc = await fetch(`https://api.homedata.co.uk/epc-checker/${uprn}/`, { headers }).then(r => r.json());

console.log(`${prop.address}: ${prop.bedrooms} bed ${prop.property_type}`);
console.log(`EPC: ${epc.current_energy_efficiency}/100`);
Get your API key Read the docs →

Know your costs before you build

Pay as you go — 100 tokens = £1. Every endpoint has a published token weight. Top up when you're ready.

Get your API key → View pricing

Compare other alternatives

vs PropertyData vs getAddress vs Ideal Postcodes vs Loqate vs Searchland

Compare Homedata with other providers

Sprift Alternative

PDF property reports vs raw API access

PropertyData Alternative

Pay-as-you-go tokens vs £1,300/mo

Homedata vs Realyse

Self-serve API vs enterprise dashboards

getAddress Alternative

Address lookup + full property data

Searchland Alternative

Property search + data enrichment API

UK Property Data API

29M properties, 15+ data categories, pay as you go
View all property data API comparisons →