shipapis
StarSubmit an APISubmit API

Data.gov vs LocalGov.jp

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

APIData.govHEALTHY79LocalGov.jpHEALTHY81
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms9311274
P95 · ms20351718
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0 (attribution: "via LocalGov.jp")
Free tierFree — 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

Data.gov vs LocalGov.jp: common questions

Which is more reliable, Data.gov or LocalGov.jp?

Both are neck-and-neck — Data.gov and LocalGov.jp each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Data.gov or LocalGov.jp?

Data.gov has the lower median latency in our checks — Data.gov responds in 931 ms versus LocalGov.jp at 1274 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Data.gov and LocalGov.jp need an API key?

Neither needs a paid key — Data.gov 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 Data.gov and LocalGov.jp from the browser?

Only LocalGov.jp is browser-friendly — it returns CORS headers over HTTPS. Data.gov needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Data.gov and LocalGov.jp free for commercial use?

Data.gov 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.