shipapis
StarSubmit an APISubmit API

City, Helsinki vs LocalGov.jp

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

APICity, HelsinkiNEW—LocalGov.jpNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0 (attribution: "via LocalGov.jp")
Free tierFree — limits not publishedFree — all endpoints currently free (per llms.txt)
Rate limitUnpublished30 req/window · 29 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Helsinki vs LocalGov.jp: common questions

Which is more reliable, City, Helsinki or LocalGov.jp?

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

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

Can I call City, Helsinki and LocalGov.jp from the browser?

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

Are City, Helsinki and LocalGov.jp free for commercial use?

City, Helsinki has unclear commercial terms, and LocalGov.jp allows commercial use on its free tier. 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.