shipapis
StarSubmit an APISubmit API

City, Helsinki vs Data.gov

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

APICity, HelsinkiNEW—Data.govNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Helsinki vs Data.gov: common questions

Which is more reliable, City, Helsinki or Data.gov?

On our scheduled checks, Data.gov leads on measured uptime — City, Helsinki at —% versus Data.gov 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 City, Helsinki and Data.gov need an API key?

Neither needs a paid key — City, Helsinki is callable with no signup, and Data.gov is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call City, Helsinki and Data.gov from the browser?

Neither sends browser-friendly CORS headers reliably, so call City, Helsinki and Data.gov from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are City, Helsinki and Data.gov free for commercial use?

City, Helsinki has unclear commercial terms, and Data.gov 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.