shipapis
StarSubmit an APISubmit API

LocalGov.jp vs OpenRegistry

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

APILocalGov.jpNEW—OpenRegistryNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseCC BY 4.0 (attribution: "via LocalGov.jp")Unverified
Free tierFree — all endpoints currently free (per llms.txt)Free tier — API key required
Rate limit30 req/window · 29 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LocalGov.jp vs OpenRegistry: common questions

Which is more reliable, LocalGov.jp or OpenRegistry?

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

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

Can I call LocalGov.jp and OpenRegistry from the browser?

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

LocalGov.jp allows commercial use on its free tier, and OpenRegistry 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.