shipapis
StarSubmit an APISubmit API

Open Government, Singapore vs LocalGov.jp

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

APIOpen Government, SingaporeNEW—LocalGov.jpNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseSingapore Open Data LicenceCC BY 4.0 (attribution: "via LocalGov.jp")
Free tierFree — no API key required; 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

Open Government, Singapore vs LocalGov.jp: common questions

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

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

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

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

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