Data.parliament.uk API vs OpenCaged Geocoder (Open Source option)

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Data.parliament.uk API vs OpenCaged Geocoder (Open Source option): common questions

Which is more reliable, Data.parliament.uk API or OpenCaged Geocoder (Open Source option)?

On our scheduled checks, OpenCaged Geocoder (Open Source option) leads on measured uptime — Data.parliament.uk API at —% versus OpenCaged Geocoder (Open Source option) at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Data.parliament.uk API and OpenCaged Geocoder (Open Source option) need an API key?

Both ask you to authenticate — Data.parliament.uk API uses an API key and OpenCaged Geocoder (Open Source option) uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Data.parliament.uk API and OpenCaged Geocoder (Open Source option) from the browser?

Yes — both Data.parliament.uk API and OpenCaged Geocoder (Open Source option) send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Data.parliament.uk API and OpenCaged Geocoder (Open Source option) free for commercial use?

Data.parliament.uk API has unclear commercial terms, and OpenCaged Geocoder (Open Source option) has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.