Open Government, Luxembourg vs LocalGov.jp

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0 (attribution: "via LocalGov.jp")
Free tierFree tier — API key may be required for productionFree — all endpoints currently free (per llms.txt)
Rate limitUnpublished30 req/window · 29 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open Government, Luxembourg vs LocalGov.jp: common questions

Which is more reliable, Open Government, Luxembourg or LocalGov.jp?

Only LocalGov.jp is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Open Government, Luxembourg and LocalGov.jp need an API key?

LocalGov.jp needs no key, while Open Government, Luxembourg requires a free API key. If you want to start calling without signup, reach for LocalGov.jp first.

Can I call Open Government, Luxembourg and LocalGov.jp from the browser?

Yes — both Open Government, Luxembourg and LocalGov.jp 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 Open Government, Luxembourg and LocalGov.jp free for commercial use?

Open Government, Luxembourg 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.