shipapis
StarSubmit an APISubmit API

LocalGov.jp vs Open Government, Australia

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

APILocalGov.jpNEW—Open Government, AustraliaNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseCC BY 4.0 (attribution: "via LocalGov.jp")Per-dataset (many CC BY 4.0)
Free tierFree — all endpoints currently free (per llms.txt)Free — no key required
Rate limit30 req/window · 29 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LocalGov.jp vs Open Government, Australia: common questions

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

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

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

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

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

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