shipapis
StarSubmit an APISubmit API

City, Berlin vs Data.gov

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

APICity, BerlinNEW—Data.govNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseVaries per dataset (many CC-BY / dl-de-by-2.0)Unverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Berlin vs Data.gov: common questions

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

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

Neither needs a paid key — City, Berlin 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, Berlin and Data.gov from the browser?

Neither sends browser-friendly CORS headers reliably, so call City, Berlin 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, Berlin and Data.gov free for commercial use?

City, Berlin 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.