Apiverket vs LocalGov.jp

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms4441274
P95 · ms38271718
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0 (attribution: "via LocalGov.jp")
Free tierFree tier — API key requiredFree — all endpoints currently free (per llms.txt)
Rate limitUnpublished30 req/window · 29 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Apiverket vs LocalGov.jp: common questions

Which is more reliable, Apiverket or LocalGov.jp?

Both are neck-and-neck — Apiverket 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, Apiverket or LocalGov.jp?

Apiverket has the lower median latency in our checks — Apiverket responds in 444 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 Apiverket and LocalGov.jp need an API key?

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

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

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

Apiverket 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.