shipapis
StarSubmit an APISubmit API

Open Government, ACT vs LocalGov.jp

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

APIOpen Government, ACTNEW—LocalGov.jpNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licensePer-datasetCC BY 4.0 (attribution: "via LocalGov.jp")
Free tierFree — app token optional (raises limits)Free — all endpoints currently free (per llms.txt)
Rate limitThrottled; higher limits with a free Socrata app token30 req/window · 29 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open Government, ACT vs LocalGov.jp: common questions

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

On our scheduled checks, LocalGov.jp leads on measured uptime — Open Government, ACT 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 Open Government, ACT and LocalGov.jp need an API key?

Neither needs a paid key — Open Government, ACT 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 Open Government, ACT and LocalGov.jp from the browser?

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

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