Apiverket vs City, Berlin

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms444861
P95 · ms38273231
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedVaries per dataset (many CC-BY / dl-de-by-2.0)
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Apiverket vs City, Berlin: common questions

Which is more reliable, Apiverket or City, Berlin?

On our scheduled checks, Apiverket leads on measured uptime — Apiverket at 100% versus City, Berlin at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Apiverket or City, Berlin?

Apiverket has the lower median latency in our checks — Apiverket responds in 444 ms versus City, Berlin at 861 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Apiverket and City, Berlin need an API key?

City, Berlin needs no key, while Apiverket requires a free API key. If you want to start calling without signup, reach for City, Berlin first.

Can I call Apiverket and City, Berlin from the browser?

Only Apiverket is browser-friendly — it returns CORS headers over HTTPS. City, Berlin needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Apiverket and City, Berlin free for commercial use?

Apiverket has unclear commercial terms, and City, Berlin 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.